Sajin
Uninstall xoc and use msi afterburner instead.

bob16314
You have 10 days to roll back to your previous Windows 10 version (1709 or whatever)

bob16314

Estin
I have the 970 SC that requires down clocking the GPU clock by 100 MHz so it does not crash my games.

What you said there is concerning, like maybe the 970 SC has one foot in the grave..If possible, you may want to test it in another compatible PC.

Estin

Sajin
Uninstall xoc and use msi afterburner instead.

Thanks! This seems to be working so far, thought it has only been about 12 hours.  But so far no blue screens or lockups, and it made it through the night for the first time.


 

bob16314
You have 10 days to roll back to your previous Windows 10 version (1709 or whatever)

 
This was going to be my last resort; it feels like it is just delaying the inevitable unless they really plan to fix Precision XOC soon; so I would prefer to get the problem solved now if possible.
 
 

bob16314

Estin
I have the 970 SC that requires down clocking the GPU clock by 100 MHz so it does not crash my games.

What you said there is concerning, like maybe the 970 SC has one foot in the grave..If possible, you may want to test it in another compatible PC.

This is a known problem for the EVGA 970 SC; basically the factory overclock was too aggressive. Anytime a game goes from low utilization to high in a very short period of time the voltage overshoots and causes a crash. I have two of these cards and they both behave the same and have done so since they were pretty close to new (since new really, but I didn't put the puzzle together and find the right information for a while).  When I first hit this problem I tried all the normal debug stuff, try it in different machines, w/ different monitors, w/ fresh install of OS, w/ different driver versions, etc.  I finally found the information about the voltage/down clock and this fixed it 100%.  In Elite: Dangerous a bunch of people with EVGA 970 SCs hit this problem; apparently black space to all the sudden lots of geometry exacerbated this voltage overshoot problem.
 

KarmaEnforcer
I know this thread is a month old now, but my system has been doing essentially the same thing. I've got an EVGA Z370 mb and a pair of 970 FTWs in SLI. KMODE_EXCEPTION_NOT_HANDLED (062518-6453-01.dmp 6/24/2018 22:35:29 KMODE_EXCEPTION_NOT_HANDLED 0x0000001e ffffffff`c0000005 00000000`00000000 00000000`00000008 00000000`00000000 nvlddmkm.sys nvlddmkm.sys+1ec3dd x64 ntoskrnl.exe+198330). Mine seems to happen while my system is at rest. I'll lock it, and wander off to adult for a bit or whatever, and come back and my Acer Predator X34 (via DisplayPort) will be in sleep mode, but my secondary, an older Acer X193W via VGA to DVI adapter on the same card) will have the blue light on it's power button which indicates powered on, but the screen will be black. I have to hard reset at that point, and when it comes back up, the nvlddmkm bugcheck is in my dumps folder. I've done all the various recommended steps from folks online (full DDU uninstall of the Nvidia drivers, clean install, etc) and switched to Afterburner for a while without much change, IIRC. I wish there was some way to just tell the damn cards to cool themselves as needed so I could go without either for a while to see if they behave. Anyway, at this point, I'm at wits end. 
 
So, my question is, did removing Precision X actually solve the problem for the folks in here? I've tried it before, and will happily try it again, but I want to be able to game without my cards overheating.

BernRJ
So glad I found this thread. I kept getting the K_mode_exception BSOD after finishing hours and hours of stress testing with realbench, OCCT, and Prime for an i9 7980xe dual 1080ti build. After uninstalling Precision XOC, I've never had the BSOD again. Thanks!

Dave3d
@Terabyte2007
Why would you use ocx instead of msi afterburner (which is updated almost weekly) ?
Ocx has been bad for years and years, and barely gets updated, if ever.
Just wondering, not a hate post or anything.