Anyone tried this registry fix for Eyefinity problems.

[bowenac]

[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

[INGlewood78]

Interesting. Will try when I get home.

[INGlewood78]

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

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

[INGlewood78]

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.

[INGlewood78]

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

[P-Storm]

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.

[sam400]

i try this method but didn't help me.

[Dave Baumann]

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?

[bowenac]

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.

[Dave Baumann]

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.

[bowenac]

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.

So are you saying the hotkey/shortcuts is a windows problem and it will not be fixed by ATI? And I do know my way around registry files. I have done a lot over the years with registry files. I have 3 classes left for my BS in Computer Science. But yea I am not the one who came up with that solution it was posted on other forums. It was given with instructions on exactly what to do. I do not think someone would have posted it on a forum if it caused problems. And yea I do agree if one is non techy and or beginner user then it would not be a good idea to mess with registry settings.

And again that registry key IS clearly for video drivers so why are you saying it has nothing to do with display haha. Every where that I have searched on that registry key always comes up with video driver. So it is odd to me that you are denying that it has anything to do with a video driver or display. If you don't think that registry has ANYTHING to do with video driver settings, then what is that registry for?

I know you can't openly admit to the problem or any problem that would not look good for you guys however you can't deny that this registry is video driver related.

[Dave Baumann]

So are you saying the hotkey/shortcuts is a windows problem and it will not be fixed by ATI?

No. Read it again. I am saying that when the Hotkey fix is in place the settings for the Hotkeys may not be kept from on driver install to another because when you do a driver install it installs a completely new registry branch for the new driver revision, orphaning the old branch.

Again, the comments concerning the registry do not pertain to any issues.

And again that registry key IS clearly for video drivers so why are you saying it has nothing to do with display haha. Every where that I have searched on that registry key always comes up with video driver. So it is odd to me that you are denying that it has anything to do with a video driver or display. If you don't think that registry has ANYTHING to do with video driver settings, then what is that registry for?

The particular branch is related to the video drivers, but the actual registry key being talked about is not related to Eyefinity, or its operation in any way.

[bowenac]

[quote]So are you saying the hotkey/shortcuts is a windows problem and it will not be fixed by ATI?

No. Read it again. I am saying that when the Hotkey fix is in place the settings for the Hotkeys may not be kept from on driver install to another because when you do a driver install it installs a completely new registry branch for the new driver revision, orphaning the old branch.

Again, the comments concerning the registry do not pertain to any issues.

And again that registry key IS clearly for video drivers so why are you saying it has nothing to do with display haha. Every where that I have searched on that registry key always comes up with video driver. So it is odd to me that you are denying that it has anything to do with a video driver or display. If you don't think that registry has ANYTHING to do with video driver settings, then what is that registry for?

The particular branch is related to the video drivers, but the actual registry key being talked about is not related to Eyefinity, or its operation in any way.

I did read it and you said "the registry is not something that is incorrect or will be changed, it is just how Windows works"

Well either way the hotkey shortcut issue has been there since I first installed the card. It has always been a problem before I installed any new drivers. I guess I just don't understand what you are saying but it seems like you are saying from one driver install to another orphaning the old branch. And that does not make sense at all.

And this fix was not JUST for Eyefinity mode and the problem is not just with Eyefinity mode but it is a problem with Eyefinity, Extended, anything and everything driver/display related. It was said from the person that posted this fix else where that it was related to "ULPS (Ultra Low Power State) is flawed and causes issues" so....Or are you admitting the problem to be with Eyefinity alone and this is not the fix for it. Are you aware of the problem I am referencing?

I am glad that you actually admit the registry to be video driver related I thought you were completely denying it.

[g00seberry]

I'm glad that you're searching for solutions to the various problems users are facing, however when an ATI rep wholly confirms this 'fix' has no impact on EyeFinity, it is wise and logical to believe him.

And you are often pointed out as "the bad guy" because your posts are overly confrontational. We know your angry. We've known for a while now. It does not need to be repeated within every post.
Contributions are fantastic and welcomed. Continued stabs, aggressive and argumental posts will see you taking another vacation from the boards.

Plus, 2 other users in this thread have stated it doesn't work even before Dave replied.

[Paradigm Shifter]

I checked on my non-EyeFinity 4870X2 rig, and my 4850 rig, and even got out my spare 3870 and popped it in a system this morning to check whether that registry entry is present. Windows 7 x64 and XP32.

It is present for all of those cards.

None of which can 'do' EyeFinity.

That registry entry might well be graphics related, but it is nothing to do with any issues EyeFinity users are having.

Best case scenario is that changing this is a placebo effect.

Worst case scenario is it breaks something 'in the background' that we have no idea about.

If I had an nVidia rig with Windows installed at the minute (my nVidia rig is currently linux only) I'd check in that for it too. I'll check my laptop for it later to see whether it's there in Vista.