Widescreen Gaming Forum

[So far does not work. As with everything in the registry, USE AT YOUR OWN RISK.]

So a member on another forum told me about a fix in the registry so I went ahead and did this to try it out. I remember Dave saying something about a registry problem that would be fixed in later updates.

Here is what he said.

It is a driver issue but this is a temporary fix. It is caused by the 2D power saving mode.

Here is what you do:

Go to registry and disable Ulps:

1. Navigate to: [HKEY_LOCAL_MACHINESYSTEMControlSet001ControlClass{4D36E968-E325-11CE-BFC1-08002BE10318}]

2. change "EnableUlps" to 0 under the 0000 and 0001 keys. Since you don't have CF, I believe you will only have a 0000

3. Then reboot

Interesting. Will try when I get home.

Hmm I just did this and it stopped blinking.... :shock:

Been going strong for an hr...will report back later.

Well, got some good news and bad news.

Bad news: My DP-->DVI monitor still blinks
Good news: It significantly blinks less (<10 times in the past 6 hrs). It used to blink 10 times in 2-3 minutes before the registry change.

This is worth a shot for anyone with the monitor blinking problem.

Bad news. The monitor now back to blinking a lot now... :(

Bad news. The monitor now back to blinking a lot now... :(

It could be that a program writes every hour that registry key. Can you check if it has changed?
Because if that is the case, then you can search for the one who changed that key.

i try this method but didn't help me.

I remember Dave saying something about a registry problem that would be fixed in later updates.

1.) I do not recall having mentioned anything about registry issues.
2.) The registry values being tweaked here bear no relation to Eyefinity or display.

Mods, can this thread be locked?

FYI - the "bug" that we found with the CCC Hotkey / shortcut for the "Eyefinity" mode has been investigated, route caused and the will be a fix coming up in a couple of driver releases time. There may be a caveat in that the hotkey looks for saved settings in the registry but those settings are not carried across when a new driver is installed.

I'll let you know which driver it turn up in when its released, but its likely to be a couple of releases time.

Ok my mistake must have been a different registry issue or is it.

From Microsoft's Website

The registry 4D36E968-E325-11CE-BFC1-08002BE10318 is in fact a video driver registry so I don't know why you just said it has nothing to do with display.

http://support.microsoft.com/kb/314283

And another one with the search string of 4D36E968-E325-11CE-BFC1-08002BE10318

http://www.bing.com/search?q=4D36E968-E325-11CE-BFC1-08002BE10318&go=&form=QBLH&qs=n

And the original link to when you were talking about a registry issue.

http://www.widescreengamingforum.com/forum/viewtopic.php?f=64&t=17672

And with this statement you made do you have an idea of when this will be fixed.

But of course I am the bad guy again right.

bowenac, for starters, what is discussed in that post is a specific fix related only to the Hotkey saves. The comment on the registry is not something that is incorrect or will be changed, it is just how Windows works, but, again, I stress this is only related to the Hotkeys.

Now, in general, if you do not know what you are doing with the registry you should not go hacking around there try to "sort stuff out". The registry key that this thread is adcovating is neither a.) anything to do with Eyefinity or Display, or b.) related to the comments about the Hotkeys.