Message boards : Number crunching : Recommended driver for GF660?
Author | Message |
---|---|
Hello, | |
ID: 29756 | Rating: 0 | rate:
![]() ![]() ![]() | |
Your driver 314.22 generally works quite well. I don't think we could recommend any better one. However, I see that you jumped right in with the new Noelia klebe WUs. These are producing errors notoriously. One of them is the driver reset upon suspending / restarting tasks, so this is actually not caused by your system. Sorry, we don't know yet if there's anything we can do to avoid this (except not pausing the WUs). | |
ID: 29759 | Rating: 0 | rate:
![]() ![]() ![]() | |
Ok, thank you for reply. | |
ID: 29763 | Rating: 0 | rate:
![]() ![]() ![]() | |
Ok, thank you for reply. If you're running Windows there is a very easy regedit that can help stop the driver resets/restarts. It's a known issue in Windows, especially on the high end cards, that has received very little publicity. | |
ID: 29764 | Rating: 0 | rate:
![]() ![]() ![]() | |
If you get a driver restart, when the GPU app stops running for example, and you get an app error, close Boinc, wait a minute and open Boinc again. The GPUGrid WU will usually resume from it's last check point. If it doesn't then the registry hack might be useful. I suggest people only try it if they are getting repeated app crashes. | |
ID: 29771 | Rating: 0 | rate:
![]() ![]() ![]() | |
If you get a driver restart, when the GPU app stops running for example, and you get an app error, close Boinc, wait a minute and open Boinc again. The GPUGrid WU will usually resume from it's last check point. If it doesn't then the registry hack might be useful. I suggest people only try it if they are getting repeated app crashes. That is not the regedit I was referring to. I'll post the one I use on all my machines when I get home in case someone would like to try it. | |
ID: 29781 | Rating: 0 | rate:
![]() ![]() ![]() | |
Here is the regedit that should stop the driver has stopped responding/restart issues in Windows. Copy and paste all the text below into noterpad. Rename it fix.reg (or any name you'd prefer with .reg extension) | |
ID: 29802 | Rating: 0 | rate:
![]() ![]() ![]() | |
Do I understand it correctly that this change avoids "fake" driver resets, when the GPU wasn't actually hanging. But if you get a real error you're f*cked and probably need a hard reset, just like in the "good old times", before vid drivers could recover a GPU? | |
ID: 30030 | Rating: 0 | rate:
![]() ![]() ![]() | |
Looks like it to me. I think something along the reg edit I linked to would be safer as it basically just increases the time before the driver restarts (not that this is the only issue, otherwise I probably wouldn't get blue screens as well). | |
ID: 30048 | Rating: 0 | rate:
![]() ![]() ![]() | |
Do I understand it correctly that this change avoids "fake" driver resets, when the GPU wasn't actually hanging. But if you get a real error you're f*cked and probably need a hard reset, just like in the "good old times", before vid drivers could recover a GPU? This may explain it better than I could. http://msdn.microsoft.com/en-us/library/windows/hardware/ff553893(v=vs.85).aspx I only made the note about 1 BSOD that I had while running a highly OC card at E@H because I thought it might be related to the regedit. | |
ID: 30053 | Rating: 0 | rate:
![]() ![]() ![]() | |
I also found some good information here: | |
ID: 30057 | Rating: 0 | rate:
![]() ![]() ![]() | |
Trying SKs suggestion with a timeout of 10. | |
ID: 30066 | Rating: 0 | rate:
![]() ![]() ![]() | |
Message boards : Number crunching : Recommended driver for GF660?