GPU Overclock Causing BSOD?

[zola25]

I've recently added a small overclock to the GTX 980's in both my PCs and since have been having some random BSODs on the desktop. Both cards have stability tested fine and are working fine in every game I've tried them with, the crashing only occurs on the desktop with virtually no load.

I've clean installed Windows only 2 weeks ago and had no problems until I did the following:

Started using D3DOverrider (pretty confident this is not the culprit)
Installed MSI Afterburner
Added a small O/C to the GPU (+130 Core, +200 Mem, no additional voltage)

I've used Blue Screen View and the cause of each crash is different, for example NTFS.sys and the Razer synapse driver. Given this has only just started happening on both PCs and the only changes are the ones listed above, I suspect the GPU OC is the most likely cause. I just can't quite understand how it's fine under load, but presume it may result from the way clocks are ramped up and down as needed.

The most sensible next step is to remove the OC and see if the BSODs stop, but wondered if anyone had any further suggestions?

 

[zola25]

Thanks PayneUK.

I don't believe it's an HDD issue as it's happening on two separate machines. I am using Windows Defender and Malware bytes, I can do full scans with both with no issue.

I've checked the stock clocks and they do stay at the low level without adding the +130, but I'm not so sure about the mid-level clocks that are triggered when browsing etc, so think you may be correct with regard to increasing voltage.

 

[zola25]

Yes, using Windows 8.1 but no CoreTemp, I am using RealTemp.

I've removed Razer Synapse from one of the PCs and have since had the NTFS.sys blue screen. I'm now doing the usual disk and memory checks to make sure it was not a genuine problem. Pretty sure this is something to do with the O/C or Afterburner itself, but to be honest it's so random it's hard to tell.

 

[zola25]

Thanks Mei. The two machines are physically separate but have the same spec (as in sig), other than one SSD that's different. Mrs Zola is also an avid gamer, hence the two matching PCs. Having a gaming Mrs is great, but it does get expensive

As a number of people have said, this feels like a software problem. The hardware has not changed, and both PCs had not had a single blue screen since reinstall 2 weeks ago or before that even. Since the changes I listed in the OP we've had 4 BSOD's across the 2 machines.

My feeling is that Afterburner is the culprit and doesn't like something else I am using, just wish the crashes were consistent! I've been playing around with the voltages and adding volts in Afterburner only impacts the load voltage, not idle/low use volts so I think I've ruled that out.

I think the best way to narrow this down is to leave Afterburner running but return to stock clocks - if it still happens it's probably Afterburner rather than the GPU overclock.

 

[zola25]

Out of interest have you run Prime95 at that OC?

Yep used Prime and Realbench to stress test. I don't think the CPU o/c is the issue, both CPUs have been running at 4.5Ghz since we got them.

The recent change is the GPU o/c and installation of Afterburner, and the BSODs only started after that.

 

[zola25]

nono a gaming mrs saves u money!! but maybe thats hard to see right now lol

It's quite amusing actually as I see many good people on here having to hide purchases or justify them to the Mrs. In my case I am encouraged. "I want a new GPU?" "Yes go ahead, I want one too"

erm yeh you dont normally see gfx card overclocks causing bsod afaik, you are more likely to see onscreen jaggies and lines than something that dramatic
i guess yeh close any software thats not 100% needed, update what software you have running, things like chipset drivers too, it has to be something thats the same on both machines right?

This us what I don't get, it's only on the desktop I am seeing issues, gaming is absolutely fine - no BSOD's, no CTDs, not even any artefacts. I completely agree, it must to be a software problem or incompatibility.

All drivers are up to date, with the minor exception of the NVidia driver; we're using 347.25 at present (not the later .52). Afterburner, D3Doverrider and the GPU overclock are the only changes we made between smooth sailing and the BSODs starting.

does sound like its dropping too much volts at idle
would have been my first guess

tho u say it happens very rarely so i duno

Indeed. I can rule that out with a small voltage bump or removing the GPU o/c.

 

[zola25]

That's certainly worth a try.

 

[zola25]

One other thought - should adaptive power management be disabled when overclocking the GPU?

 

[zola25]

I've been using 347.25 since they were released with no issues of any kind until now. I don't believe these drivers are the issue in my case.

 

[zola25]

Quick update; I've removed Afterburner and the GPU overclock and had no issues since. D3Doverrider is still in place.

I'll now reintroduce O/C via NV inspector and see what happens - if the issues persist I'll add a GPU voltage bump, then will try the CPU at stock.

 

[zola25]

No issues at all when overclocking with NV inspector. It would seem that some piece of hardware or software just doesn't like Afterburner on our PCs.