SLI DVI lockup problem - merkelig fix!

[marsboer]

Jeg fant akkurat ut dette, etter mye prøving og feiling, noe som sannsynligvis er interessant for en del SLI brukere her på hardware også:

Refererer til min egen post på nzone (dessverre på engelsk, tar så lang tid å skrive den på norsk også )

 

Her er den opprinnelige posten:

http://forums.nvidia.com/index.php?showtopic=7713

 

Her har jeg klippet ut posten for de som ikke gidder å klikke på linken

 

I have had 2 completely reproducable problems with SLI on my computer, that have plagued me since I bought SLI in may. I have really taken it upon myself to fix those problems this week, and finally I discovered a fix, without any huge compromise after systematically researching the problem by trial and error.

 

System specs:

Tyan K8WE (2xOpteron 246)

4x512mb Corsair DDR400 ECC/Reg

2xPoV 6800GT SLI

Lacie Photon Vision II 19" LCD using DVI

 

OS:Windows XP SP2 slipstreamed

Drivers: nforce4 v6.66

Problems on every forceware driver I have tried. Only confirmed fix on 78.03, probably works on every other driver to.

 

1. Most of my 3D games will crash during startup if my monitor is allowed to enter power saving mode.

 

My temporarily solution since I discovered the problem: Do not enter standby mode and disable the powersaving features in windows power options.

 

 

2. Most of my 3D games will crash during startup if I enter the advanced properties in display properties -> settings -> advanced to change nvidia settings like AA, AF etc.

This also includes using profile editors like nhancer without rebooting. This problem is caracterized by the monitor blacking out a short moment when pressing the advanced button. This is not correct behaviour since it don't happen when everything works correctly (on my computer).

 

My temporarily solution since I discovered the problem: Reboot after setting 3d options or editing profiles using nhancer before playing a game.

 

 

At first I couldn't tell if the two problems was independent of each other or not, but when I tried to use the analog monitor connection on the LCD instead of the DVI I noticed that both problems went away. Finally, I got rid of those annoying problems. I wasn't however, satisfied by using analog instead of DVI, because of noticable worse picture. Also I have payed extra to get DVI, and it should obviously work flawlessly out of the box too!!

 

Thinking I had found the temporarily solution until nVidia could release some new drivers I settled for analog mode. This only lasted for two days, when I finally couldn't stand not using DVI any more, and still wanting to find the ultimate solution to the problem. I then switched back to the DVI connection, and to my great surprise the problems were still gone!! I thought of what I had done these two last days, and remembered that I had installed the Coolbits2.reg. I then tried to uninstall the drivers, install them again so both problems could be reproduced again. I then installed Coolbits2.reg, and voila!! the problems were gone.

 

Conclusion:

Somewhere in Coolbits2.reg the solution to lot of the DVI problems lies. Why is this logical? Don't ask me!! but it definitly works if you have the two problems described above, and I can reproduce it at any time. Only backdrop is that you have to run coolbits2.reg every time you reinstall the forceware driver, but that is much better than running the monitor in analog mode.