Annoying flicker when returning to desktop

  • Thread starter Thread starter Chuckg
  • Start date Start date
C

Chuckg

OK, the system I have is:

Mach Speed Viper MK8-939A motherboard (latest drivers installed, latest
BIOS flashed)

AMD64 X-2 4800+ processor (latest drivers & AMD dual-core optimizer
installed)

Windows XP (32-bit) SP2 (fully updated)

Radeon x1600 Pro (PCI-Express 16x) (Catalyst v6.8 & Control Center
installed)

The Windows install is fresh and new, as is the video card and
motherboard. For the first couple of days, it worked fine, but now
It's picked up an annoying habit. Nothing major, just annoying.

The habit is this: when coming out of a fullscreen 3-D game such as
KOTOR or KOTOR II, it'll go a few seconds and then I'll get a brief
flash of my cursor turning into an hourglass, and then *boom*, the
screen goes black for a second or so.

Even more annoying, it also does this a few seconds into KOTOR II
cutscenes -- I don't mean the camvator ones, I mean the ones where it
cuts to FMV. The disk access and the flicker to black, that is.

Did I tick some setting that wasn't supposed to be ticked, and if so,
can I untick it?

Note: auto-detect hardware is already turned off in Catalyst Control
Center.
 
Figured it out, mostly.

It's the damn overlock settings. The thing keeps turning them off
whenever I leave fullscreen 3D mode, even for a moment or a cutscene,
with the accompanying flicker.

I verified this by yanking Catalyst Control Center and instaling ATI
Tray Tools with overclocking disabled. It worked, but now I have
minor annoyances re: my fullscreen profile and gamma correction.
Here's hoping when I reinstall Control Center, it remembers to keep
overclocking off. Otherwise, how do you disable ATI overclocking?
 
Chuckg said:
Figured it out, mostly.

It's the damn overlock settings. The thing keeps turning them off
whenever I leave fullscreen 3D mode, even for a moment or a cutscene,
with the accompanying flicker.
Click to expand...

.... and now the flicker is back, dammit, even with the overclocking
disabled.

It's like clockwork -- 2-3 seconds after returning to desktop or
windowed mode from fullscreen mode, *BAM*, temporary blackout.

It's *really* annoying. Does anybody know HTF to fix this?
 
Does this flicker afflict both D3D and OpenGL applications, or just D3D.

And are you running different gamma or color-vibrance settings for desktop
and full-screen 3D?
 
First said:
Does this flicker afflict both D3D and OpenGL applications, or just D3D.
Click to expand...

It does it both for Doom 3 in fullscreen mode and KOTOR II, so yes.
And are you running different gamma or color-vibrance settings for desktop
and full-screen 3D?
Click to expand...

The gamma settings between fullscreen 3D and desktop are different.

Re: D3D, I have DirectX 9.0c installed, it came with the original XP
SP2 install.
 
:>First of One wrote:
:>> Does this flicker afflict both D3D and OpenGL applications, or just D3D.
:>
:>It does it both for Doom 3 in fullscreen mode and KOTOR II, so yes.
:>
:>> And are you running different gamma or color-vibrance settings for desktop
:>> and full-screen 3D?
:>
:>The gamma settings between fullscreen 3D and desktop are different.
:>
:>Re: D3D, I have DirectX 9.0c installed, it came with the original XP
:>SP2 install.

Microsoft has updated DirectX 9.0c numerous times without changing the
actual version number. The latest update I have to DirectX was
released in April, 2006 (long after SP2) and is still called 9.0c.
There may even be a newer 9.0c by now. So you might want to take a
little trip to Microsoft and get the latest one.

me/2
 
Chuckg said:
The gamma settings between fullscreen 3D and desktop are different.
Click to expand...

Does the flicker remain when you set both the desktop and fullscreen 3D
gamma value to the defaults (i.e. 1.0)?
Re: D3D, I have DirectX 9.0c installed, it came with the original XP
SP2 install.
Click to expand...

Microsoft updates DirectX every two months or so, without rolling the
version number. The latest one was released in August 2006. However, I don't
think this is the cause of your screen flicker.
 
First said:
Does the flicker remain when you set both the desktop and fullscreen 3D
gamma value to the defaults (i.e. 1.0)?
Click to expand...

Yes. The flicker remains when I set *everything* back to the defaults
in Catalyst Control Center, aamof.

Oddly enough, it appears that my old gamma settings are still being
applied, as the 3-D games I started to test this theory (KOTOR, KOTOR
II) were still as bright.

Maybe that's what's messing it up -- somehow, in all the ATI Catalyst
Control Center installing and uninstalling, the original profiles have
gotten nailed in there, and the current profiles conflict. I wouldn't
have the faintest idea how to confirm this guess, or resolve it if it's
true.

I do know that using ATI Uninstall utility to strip everything out and
reinstalling the ATI driver set from scratch hasn't worked so far, tho.

I really hope your bag of tricks ain't empty yet. *g*
Microsoft updates DirectX every two months or so, without rolling the
version number. The latest one was released in August 2006. However, I don't
think this is the cause of your screen flicker.
Click to expand...

It's not. I DL'ed the latest DirectX redist from Microsoft (Aug 2006)
and put it in -- no change.
 
Some more data for anyone.

I cleared out my Events log, then deliberately triggered the failure
again, twice.

Here's a dump of my ACE Event Log:

9/8/2006 6:35:45
PM ACEEventLogSource Information None 0 N/A GLASGOWC1 0000000004:
2006-09-08 18:35:45:218 Exception: Object reference not set to an
instance of an object.
Exception Called by: ATI.ACE.CLI.Component.Icomponent.Icomponent::Run
processID:00488
threadID:(CLIIcomponent ) domainName:(cli.exe )
assemblyName:(CLI.Component.Icomponent, Version=1.2.2405.30454,
Culture=neutral, PublicKeyToken=90ba9c70f846762e)
************************************************************************************************************************

9/8/2006 6:35:45
PM ACEEventLogSource Information None 0 N/A GLASGOWC1 0000000003:
2006-09-08 18:35:45:218 ATI ACE Runtime not found!
Error Called by:
ATI.ACE.CLI.Component.Icomponent.Icomponent::ConnectToRuntime
processID:00488 threadID:(CLIIcomponent )
domainName:(cli.exe )
assemblyName:(CLI.Component.Icomponent, Version=1.2.2405.30454,
Culture=neutral, PublicKeyToken=90ba9c70f846762e)
------------------------------------------------------------------------------------------------------------------------

9/8/2006 6:35:45
PM ACEEventLogSource Information None 0 N/A GLASGOWC1 0000000002:
2006-09-08 18:35:45:218 Can't connect to Runtime
Error Called by:
ATI.ACE.CLI.Component.Icomponent.Icomponent::ConnectToRuntime
processID:00488 threadID:(CLIIcomponent )
domainName:(cli.exe )
assemblyName:(CLI.Component.Icomponent, Version=1.2.2405.30454,
Culture=neutral, PublicKeyToken=90ba9c70f846762e)
------------------------------------------------------------------------------------------------------------------------

9/8/2006 6:35:45
PM ACEEventLogSource Information None 0 N/A GLASGOWC1 0000000001:
2006-09-08 18:35:45:203 Exception <Runtime@2308>: No connection
could be made because the target machine actively refused it
Exception Called by:
ATI.ACE.LOG.Foundation.Service.Service::ConnectToObjectImpl
processID:00488 threadID:(CLIIcomponent )
domainName:(cli.exe )
assemblyName:(LOG.Foundation.Service, Version=1.2.2405.30446,
Culture=neutral, PublicKeyToken=90ba9c70f846762e)
************************************************************************************************************************

9/8/2006 6:35:42
PM ACEEventLogSource Information None 0 N/A GLASGOWC1 0000000003:
2006-09-08 18:35:42:718 Exception: Object reference not set to an
instance of an object.
Exception Called by: ATI.ACE.CLI.Component.Icomponent.Icomponent::Run
processID:01952
threadID:(CLIIcomponent ) domainName:(cli.exe )
assemblyName:(CLI.Component.Icomponent, Version=1.2.2405.30454,
Culture=neutral, PublicKeyToken=90ba9c70f846762e)
************************************************************************************************************************

9/8/2006 6:35:42
PM ACEEventLogSource Information None 0 N/A GLASGOWC1 0000000002:
2006-09-08 18:35:42:687 ATI ACE Runtime not found!
Error Called by:
ATI.ACE.CLI.Component.Icomponent.Icomponent::ConnectToRuntime
processID:01952 threadID:(CLIIcomponent )
domainName:(cli.exe )
assemblyName:(CLI.Component.Icomponent, Version=1.2.2405.30454,
Culture=neutral, PublicKeyToken=90ba9c70f846762e)
------------------------------------------------------------------------------------------------------------------------

9/8/2006 6:35:42
PM ACEEventLogSource Information None 0 N/A GLASGOWC1 0000000001:
2006-09-08 18:35:42:656 Can't connect to Runtime
Error Called by:
ATI.ACE.CLI.Component.Icomponent.Icomponent::ConnectToRuntime
processID:01952 threadID:(CLIIcomponent )
domainName:(cli.exe )
assemblyName:(CLI.Component.Icomponent, Version=1.2.2405.30454,
Culture=neutral, PublicKeyToken=90ba9c70f846762e)
------------------------------------------------------------------------------------------------------------------------

9/8/2006 6:33:23
PM ACEEventLogSource Information None 0 N/A GLASGOWC1 0000000013:
2006-09-08 18:33:23:296 Target:
ATI.ACE.CLI.Aspect.OverDrive3.Graphics.Dashboard.DB_OverDrive3 Method:
ATI.ACE.CLI.Aspect.OverDrive3.Graphics.Dashboard.DB_OverDrive3
Error Called by:
ATI.ACE.CLI.Component.Dashboard.DashboardForm::DashboardForm_Closing
processID:03424 threadID:(CLIDashboard )
domainName:(cli.exe )
assemblyName:(CLI.Component.Dashboard, Version=1.2.2405.30455,
Culture=neutral, PublicKeyToken=90ba9c70f846762e)
------------------------------------------------------------------------------------------------------------------------

9/8/2006 6:33:23
PM ACEEventLogSource Information None 0 N/A GLASGOWC1 0000000012:
2006-09-08 18:33:23:296 Target:
ATI.ACE.CLI.Aspect.OverDrive3.Graphics.Dashboard.DB_OverDrive3 Method:
ATI.ACE.CLI.Aspect.OverDrive3.Graphics.Dashboard.DB_OverDrive3
Error Called by:
ATI.ACE.CLI.Component.Dashboard.DashboardForm::DashboardForm_Closing
processID:03424 threadID:(CLIDashboard )
domainName:(cli.exe )
assemblyName:(CLI.Component.Dashboard, Version=1.2.2405.30455,
Culture=neutral, PublicKeyToken=90ba9c70f846762e)
------------------------------------------------------------------------------------------------------------------------

9/8/2006 6:33:23
PM ACEEventLogSource Information None 0 N/A GLASGOWC1 0000000011:
2006-09-08 18:33:23:296 Target:
ATI.ACE.CLI.Aspect.DeviceDFP2.Graphics.Dashboard.DB_DeviceDFP2 Method:
ATI.ACE.CLI.Aspect.DeviceDFP2.Graphics.Dashboard.DB_DeviceDFP2
Error Called by:
ATI.ACE.CLI.Component.Dashboard.DashboardForm::DashboardForm_Closing
processID:03424 threadID:(CLIDashboard )
domainName:(cli.exe )
assemblyName:(CLI.Component.Dashboard, Version=1.2.2405.30455,
Culture=neutral, PublicKeyToken=90ba9c70f846762e)
------------------------------------------------------------------------------------------------------------------------

9/8/2006 6:33:23
PM ACEEventLogSource Information None 0 N/A GLASGOWC1 0000000010:
2006-09-08 18:33:23:296 Target:
ATI.ACE.CLI.Aspect.DeviceDFP2.Graphics.Dashboard.DB_DeviceDFP2 Method:
ATI.ACE.CLI.Aspect.DeviceDFP2.Graphics.Dashboard.DB_DeviceDFP2
Error Called by:
ATI.ACE.CLI.Component.Dashboard.DashboardForm::DashboardForm_Closing
processID:03424 threadID:(CLIDashboard )
domainName:(cli.exe )
assemblyName:(CLI.Component.Dashboard, Version=1.2.2405.30455,
Culture=neutral, PublicKeyToken=90ba9c70f846762e)
------------------------------------------------------------------------------------------------------------------------

9/8/2006 6:33:23
PM ACEEventLogSource Information None 0 N/A GLASGOWC1 0000000009:
2006-09-08 18:33:23:281 Removing errant RevertAfterComponentUpdated
observers.
Error Called by:
ATI.ACE.CLI.Component.Dashboard.DashboardForm::DashboardForm_Closing
processID:03424 threadID:(CLIDashboard )
domainName:(cli.exe )
assemblyName:(CLI.Component.Dashboard, Version=1.2.2405.30455,
Culture=neutral, PublicKeyToken=90ba9c70f846762e)
------------------------------------------------------------------------------------------------------------------------

Hope this helps.

Oh, and disabling SMARTGART with their utility (I have a PCI-Express
card) didn't help much either.
 
Chuckg said:
Yes. The flicker remains when I set *everything* back to the defaults
in Catalyst Control Center, aamof.

Oddly enough, it appears that my old gamma settings are still being
applied, as the 3-D games I started to test this theory (KOTOR, KOTOR
II) were still as bright.

Maybe that's what's messing it up -- somehow, in all the ATI Catalyst
Control Center installing and uninstalling, the original profiles have
gotten nailed in there, and the current profiles conflict. I wouldn't
have the faintest idea how to confirm this guess, or resolve it if it's
true.

I do know that using ATI Uninstall utility to strip everything out and
reinstalling the ATI driver set from scratch hasn't worked so far, tho.

I really hope your bag of tricks ain't empty yet. *g*


It's not. I DL'ed the latest DirectX redist from Microsoft (Aug 2006)
and put it in -- no change.
Click to expand...


This might be way off in left field but the I've noticed less flicker issues when
"Display Detection Option" in CCC is set to "use manual detection."


Dan
 
Danny said:
This might be way off in left field but the I've noticed less flicker issues when
"Display Detection Option" in CCC is set to "use manual detection."
Click to expand...

Thanks for trying, but it didn't work.
 
Use ATi Tray Tools. Apparently there are multiple ways to access color/gamma
adjustments, and the method employed by Tray Tools is more low-level.
 
First said:
Use ATi Tray Tools. Apparently there are multiple ways to access color/gamma
adjustments, and the method employed by Tray Tools is more low-level.
Click to expand...

Didn't work -- although the fact that I had Tray Tools on there once
before, and uninstalled it, may have been the cause of the problem in
the first place.

As of today, I've tried running the ATI uninstaller, then going through
and following /all/ the cleanup instructions here:

http://www.tweakguides.com/ATICAT_4.html

including running RegCleaner, then reinstalling the full ATI Catalyst
6.8 package again.

Still getting the flicker. Oddly enough, the event logs say that the
'Information' events show when I *start* the apps in question, not when
I log out of them.
 
Should have noted this earlier...

In ATi Tray Tools, go to Tools & Options -> General Options

Is the setting "Use new Apply 3D settings mode" checked?
 
First said:
Should have noted this earlier...

In ATi Tray Tools, go to Tools & Options -> General Options

Is the setting "Use new Apply 3D settings mode" checked?
Click to expand...

As per the prior post, I've uninstalled ATI Tray Tools, and everything
else, and reinstalled from scratch after some serious driver and
registration cleaning.

However, a new data point -- this /may/ be a KOTOR I/II specific or
OpenGL specific issue after all, or multiple issues going on at once,
as I just put Halo: Combat Evolved on, and I *didn't* get the flicker
exiting it.
 
And now, the point is entirely moot.

Something else failed (it's a long story) and I had to do a format and
clean reinstall. We shall see if the problems recur.
 
Chuckg said:
And now, the point is entirely moot.

Something else failed (it's a long story) and I had to do a format and
clean reinstall. We shall see if the problems recur.
Click to expand...

Which they did -- reoccur, that is. On a clean reinstall. Where I
had done absolutely nothing to the ATI Catalyst drivers except install
once, leave alone. Didn't even set up separate gamma profiles this
time.

Halo: Combat Evolved, OTOH, doesn't even notice. Alt-Tab in and out
while it's running, even, no worries.

So, apparently it was never a graphics card issue in the first place,
but a KOTOR I/II compatibility issue.

*bangs forehead on desk*

Ladies and gentlemen, if my past few days of futility are going to be
worth anything, at least them let be worth something as an object
lesson of how not to diagnose. Specifically, what happens when you
fail to check an assumption.
 
Microsoft has updated DirectX 9.0c numerous times without changing the
actual version number. The latest update I have to DirectX was
released in April, 2006 (long after SP2) and is still called 9.0c.
There may even be a newer 9.0c by now. So you might want to take a
little trip to Microsoft and get the latest one.

me/2
Click to expand...

LOL. What a great company. Screws up their revision system and
does a complete scan of your computer before allowing download. You
probably need active x for scan/download too ? I didn't get that
far. Nothing to worry about, just read their privacy policy and
their happy face pledge to you.
 
Back
Top