Okay, so, recently I've started experiencing NVIDIA kernel-mode display driver crashes and blue screens (STOP code in thread title, of course) when placing significant load upon my six-year-old GTX 760. There is a small wrinkle here, though:
Things I have tested to eliminate components and drivers:
I've looked at these in windbg myself a couple of times, and one thing in particular sticks out to me, though I'm unsure of its significance: It seems like the driver is trying to write to null at an IRQL of DISPATCH_LEVEL. I'm not sure if this means null in VRAM or system memory, or even how significant it is in relation to the STOP errors. Even though I have my suspicions about the cause, a second opinion here would help out a lot.
SPECS:
NotWD
- Gaming in full screen will absolutely lock up the whole rig and produce a D1 STOP error if I don't hold the power button down. These STOPs all blame the NVIDIA kernel mode graphics driver.
- When NOT in full screen and applying significant stress to the GPU (for example, when using the Unreal Editor), the GPU driver seems to just crash silently and recover. UEd is good at handling this situation so I don't get a screen flicker, it just locks up, crashes and leaves the OS intact.
Things I have tested to eliminate components and drivers:
- Loading the RAM with contiguous data to eliminate memory errors. I have run a particularly heavy FL Studio project (full of instances of EastWest PLAY 6 with Hollywood Orchestra parts loaded, for an idea of just how much data is being loaded into RAM). No crash.
- Running a heavy DSP chain with Ozone 8 on the master in that same project, which has FL's CPU meter hovering around 70 in the same project. No crash.
- PLAY 6 will stream its audio data from disk when RAM is unavailable. Since I have 16 GB, it has to do this regularly. This does not cause any issues.
- Checked the motherboard for busted caps. There are none.
- Reinstalled the NVIDIA drivers using the Display Driver Uninstaller in safe mode. They still crash when the GPU is under stress.
I've looked at these in windbg myself a couple of times, and one thing in particular sticks out to me, though I'm unsure of its significance: It seems like the driver is trying to write to null at an IRQL of DISPATCH_LEVEL. I'm not sure if this means null in VRAM or system memory, or even how significant it is in relation to the STOP errors. Even though I have my suspicions about the cause, a second opinion here would help out a lot.
SPECS:
- ASRock X99 Extreme3
- Intel Core i7-5820K [stock clocks]
- Corsair H75 dual-fan liquid cooler
- 16 GB DDR4-2133 [Micron]
- 1 TB WD Blue main drive
- 6 TB WD MyBook external drive
- Gigabyte WindForce GTX760OC [2 fans]
- Audient iD4 USB audio interface
- Generic 550W PSU [replacement planned during tax season]
- Windows 10 build 1909
- NVIDIA GeForce Drivers, version 441.66
NotWD
Last edited: