That sounds a lot like DPC latency issues resulting in driver failsafe, Is Cuda multibeam the only app that runs on there ? (different but related issue)

No, it runs AP tasks, too. It will run either 2 MBs or 1 MB + 1 AP on the GPU.

OK, you'll need to consult the AP app author.
as per edit I can't vouch for the thread safety of any app other than x41zc builds, lack of which can easily cause driver 'sticky downclocks.', alongside the possible system driver DPC issues.

It's been running in that configuration since August of last year and, as far as I know, has never downclocked before. At least for now, I'm going to assume it was either the voltage increase and/or Precision X that caused the problem. I don't think it was any of the apps. I'll be keeping a closer eye on it now, of course!

Here's a quick screenshot of my ~6 year old Core2 (driving a 980SC) DPC latencies, grabbed with DPC Latency checker [while crunching], to compare:

http://prntscr.com/506a9i

It took manual piecewise force update replacement of various Intel Chipset drivers, and a modified Atheros Wireless driver to get that, Using 'LatencyMon' to identify the culprits

http://www.thesycon.de/eng/latency_check.shtml
http://www.resplendence.com/latencymon

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

Well, if it happens again, with the voltage back to the default and Precision X out of the picture, I suppose I'll have to dig deeper. I'll check it in the morning but, for now, it's bedtime. ;^)

Yep, sounds good. It's these rare obscure issues with an otherwise perfectly running system & software that test the patience. Sleep sounds like a good idea.

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.