Folding Forum

I noticed something. I tried proj 11733 first with driver 372.70 than with 419, the last driver that is out.
Results: on 372.70 driver the default clock of my 1070 msi gaming x gives errors after some time. tpf: 1:07-1:08 and 850k.
419 driver with defalut clocks does not give me any errors, furthermore I can overclock until 2088 before i begin receiving errors. tpf on defalut 1:09-1:10 and 750-800k.
Despite driver 372.70 brings better tpf, the 419 is more stable for core 22.
I am running on Windows 7 X 64.
I hope this helps.

Good catch, maybe several users with old drivers get the errors. I run nvidia driver 391.35 for gtx 1080 ti on Windows 7 without errors too.

In Bold I think are best Drivers ATM Under Windows 10 1709/1803/1809
390.65 & 391.35 on the GTX Cards are what I am now running.
417.71 & 417.01 on the RTX Cards are what I am now running.

I updated to latest 419.35 on Windows 7 for gtx 1080 ti and performance is the same as 391.35 but I will look out for errors.

Am successfully running GTX 1080ti and RTX 2080ti on 417.22 in win7.

418.91 and RTX 2060 under Win7 didn't work for me.
417.71 and RTX 2070 under Win7 did work for me.

I was using 372.70 for some time because was the fastest driver for core 21 and now for core 22 too, but the problem is with core 22 it's not so stable even in default clocks. To be stable I must put the core 15-20 mhz down. Another fact is that gpu utilization in driver 372.70 is 93-95%, in 419 is 96-98%, but the tpf is better with 372 driver. That's strange.

ra_alfaomega wrote:To be stable I must put the core 15-20 mhz down. Another fact is that gpu utilization in driver 372.70 is 93-95%, in 419 is 96-98%, but the tpf is better with 372 driver. That's strange.

So for that particular GPU it doesn't seem to be associated with the driver version or the particular model of the GPU.

Are the instabilities associated with temperature or with power draw?
Does increasing the fan speed without reducing the shader speed help?
Does decreasing memory speed help?

I am Going to Test this New NVIDIA Creator Ready Driver Version: 419.67 CRD Driver Today.
419.67-desktop-win10-64bit-international-crd-whql.exe Good for RTX Cards not so good for GTX Cards.
On the RTX Cards A Nice Jump from 5,695,484 to 6,148,165 and on the GTX Cards A Drop From 1,792,015 to 1,732,158

The power draw with driver 372.70 is 80-85% with 1.05 voltage and 1960mhz, the default boost clock, the temperature is 68-69C, so it's nothing too high. If I downclock memory by 200 mhz the performance it's not reduce, but if I overclock to more than 300, the performance decreases. So for now I let the memory at -200. Fan speed is 85-90%.. The instability increases when I watch a movie or navigate the internet.

It is not uncommon for drivers to get slower with the later versions. I always keep a copy of 373.06 for use with my Maxwell cards (Win7). So as a result, they get more "stable".
You could achieve the same effect by reducing the clocks on the older drivers. I think if you pushed each one to the maximum, you would probably get the same PPD in either case.

Funny!
Nvidia just released a new driver today, and it works great on my cards.
See my review here:
viewtopic.php?f=14&t=31468

Testing Creators on machine with RTX 2080TI and 1080TI in it to see how it goes.

Would be interesting if the new "NVIDIA Creator Ready Driver" for Windows 10 helps FAH compute or only video render.

GeForce RTX 2080
Up to 13% in Blender Cycles
Up to 9% in Adobe Photoshop CC
Up to 9% in Adobe Premiere Pro CC
Up to 8% in CINEMA 4D

My recommendation is to get something newest to run core 22 happily ... the time people could keep old drivers forever because they were faster is over in my opinion ...

About Game ready or Creator ready drivers, I'm pretty sure we won't see any differences for FAH since it only focus on specific optimizations (games or professional rendering applications) that we don't care about ... the only thing we could hope would be to use compute oriented drivers (using TCC instead of WDDM driver model), but it's not going to happen on Geforce series ...