Hello altogether,

i would like to tell you all about my driver issues with Nvidia:
I like to run astropulse (former V6, now V7) at full throttle on my old XP-Box. The last driver, all things went well was (is) 337.88, where everything ran, as it should. My two GPUs only need together one single CPU core, to be fed well without -use_sleep. If i use the (a) newer driver (344.11), both instances use both(!!) cores to full throttle, but only use the GPUs to a merely 40-45%. Even using the "-cpu_lock_fixed_cpu 0" option led to the same odd behavior, to only use 40-45% of the GPUs. So i went back to 377.88 and everything is running well.

Well, i don't know, if it is my (too?) old system, but the newer drivers from Nvidia simply suck big time!!!

Is there anybody else having the same trouble or am i alone on the long run?!

Any comments appreciated!

Best regards, Uli

---

Aloha, Uli

Some users have reported issues with CPU usage, especially in combination with the use_sleep switch, since the release of the 340 drivers. I'm not sure if that's related to your circumstances, but certainly with WinXP I never experienced the need to 'free' CPU cores to keep GPUs running optimally - only with recent Windows and Linux kernels.

---

Soli Deo Gloria

Have you noticed anything weird with the Memory Controller load in GPU-Z? I've been using my old GTS 250 in Windows 8.1 running MBs. When AP_v7 came out I decided to see how it would work on the old card. While tuning it to run just below 100% GPU load I noticed it had a tendency to to jump back and forth between around 96-100%. Every time it went to & from 100% GPU load the Memory Controller load would jump from around 10-20% to 70-80%. Up & down every second or so. I don't remember it doing this a while back, but it does it now with 337. It looked so weird I just went back to MBs. I set up my other old card in XP with driver 266 and it doesn't do the 337 spike dance. The Memory Controller load jumps around a bit with 266, but not the spike every second it does in Win 8.1 with 337.88. Anyone else notice this in GPU-Z?