Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Probably getting power saving features in place for the power whore that GF100 will be.
I doubt that's the drivers. Your overclock was probably unstable, so the drivers crashed and clocked the card in low-power 3D mode. Reboot your computer to allow the card to run at 3D clocks again, and decrease your overclock if you want to avoid encountering that issue.Do not install these horrid things. they cut my folding score in half lost my shader clock. the new evga precision makes it look like its back but when set on 700/1560 my clocks where only running 400/800 which i think is 2d mode.
The ability to overclock shaders was not removed... There was a bug in the drivers that prevented overclocking tools from working. Unwinder already compensated for it in the latest version of Precision and he submitted a bug report to nVidia, so when the next driver version is released, it should be back to normal.thats what i was thinking as well when i was reading that they removed the shader overclock.. makes me wonder if they plan to lock the ability to overclock the shaders on the GF100's..
I doubt that's the drivers. Your overclock was probably unstable, so the drivers crashed and clocked the card in low-power 3D mode. Reboot your computer to allow the card to run at 3D clocks again, and decrease your overclock if you want to avoid encountering that issue.
The ability to overclock shaders was not removed... There was a bug in the drivers that prevented overclocking tools from working. Unwinder already compensated for it in the latest version of Precision and he submitted a bug report to nVidia, so when the next driver version is released, it should be back to normal.
I doubt that's the drivers. Your overclock was probably unstable, so the drivers crashed and clocked the card in low-power 3D mode. Reboot your computer to allow the card to run at 3D clocks again, and decrease your overclock if you want to avoid encountering that issue.
The ability to overclock shaders was not removed... There was a bug in the drivers that prevented overclocking tools from working. Unwinder already compensated for it in the latest version of Precision and he submitted a bug report to nVidia, so when the next driver version is released, it should be back to normal.
Were you overclocked while folding after you installed the drivers? If you were, then my previous statements still apply. Reboot the PC, set the card to stock clocks, and I suspect you'll find that you don't have the same issue.there was no unstable overclock as i always set my clocks back before installing drivers. there is also a thread in video cards about the these drivers.
On NVIDIA's main download page, there is a link below to "Beta and Archived Drivers".Where do you guys DL older versions of nVidia drivers?
Ah, thanks.On NVIDIA's main download page, there is a link below to "Beta and Archived Drivers".![]()
On my 64-bit XP boxen, 191.07 is my favorite driver. When I installed Win7, I was pleasantly surprised to see it install the same version of the drivers by default and it worked just as well it did on XP.Next question is what's the best performing drivers for Win 7 X64 in anyone's experience? The v195.62 drivers I'm using are seeing less performance that I had in XP-32 using v177 and v178 drivers.
So, no driver install was even necessary then? I guess you manually added the nvcuda.dll file because I receive an error message about it?On my 64-bit XP boxen, 191.07 is my favorite driver. When I installed Win7, I was pleasantly surprised to see it install the same version of the drivers by default and it worked just as well it did on XP.
So, no driver install was even necessary then? I guess you manually added the nvcuda.dll file because I receive an error message about it?
191.07 was installed via my first Windows Update after installing the OS. I didn't have to manually add any CUDA DLL files.So, no driver install was even necessary then? I guess you manually added the nvcuda.dll file because I receive an error message about it?