Nvidia crash of nvlddmkm.sys - DRIVER_IRQL_NOT_LESS_OR_EQUAL

tarnakk4

Commendable
Aug 23, 2016
11
0
1,510
So, I see that this is a long time issue with Nvidia drivers, but I'm having some trouble figuring this one out, as it doesn't quite fit the other reports I've been reading. I ran whocrashed - excellent utility, btw - and it came back indicating that the driver was 3rd party. Seems a little odd to me, because I just did a complete clean install of the driver due to another help forum. I'm adding the dump below. Any thoughts would be awesome.

Also note: This is happening frequently. 4 dumps recorded today, but I have several dozen in my event log since it started yesterday.

--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Tue 8/23/2016 5:23:28 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082316-27783-01.dmp
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF880133ED452)
Bugcheck code: 0xD1 (0x3F8, 0x8, 0x0, 0xFFFFF880133ED452)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 372.54
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 372.54
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 372.54 , NVIDIA Corporation).
Google query: NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Tue 8/23/2016 5:23:28 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x3E0452)
Bugcheck code: 0xD1 (0x3F8, 0x8, 0x0, 0xFFFFF880133ED452)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 372.54
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 372.54
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 372.54 , NVIDIA Corporation).
Google query: NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Tue 8/23/2016 1:03:01 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082316-24226-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x8CC01C)
Bugcheck code: 0x116 (0xFFFFFA8006C53010, 0xFFFFF880138FB01C, 0xFFFFFFFFC000009A, 0x4)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 372.54
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 372.54
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 372.54 , NVIDIA Corporation).
Google query: NVIDIA Corporation VIDEO_TDR_ERROR



On Tue 8/23/2016 10:42:44 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082316-22885-01.dmp
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF880133E9452)
Bugcheck code: 0xD1 (0x3F8, 0x8, 0x0, 0xFFFFF880133E9452)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 372.54
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 372.54
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 372.54 , NVIDIA Corporation).
Google query: NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

4 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:


***UPDATE***
I have used 3DGuru's DDU to completely remove the video driver and reinstall version 372.54 directly from Nvidia's website. Remained stable for the rest of the day, but then today it's crashing again. acting on the assumption that something I did damaged the driver again, I attempted this over again today to correct the issue. This time it is not working. Crash dump shows the same error.

So why is it seeing the driver from nvidia as a 3rd party driver??
 
which graphics card is it?

power plugs all inserted?

which power supply?

any other graphics card installed before with this windows installation?

chipset drivers up to date?

Which motherboard? BIOS up to date? flash inside bios itself, not in windows
 

tarnakk4

Commendable
Aug 23, 2016
11
0
1,510




My apologies, I forgot to mention some basic computer information. Please let me know if I miss anything.

The system is about 2 years old, and was running smoothly until this event a few days ago.

Graphic Card: nvidia GTX 670

Power and cables: I did attempt to re-seat the power cables. I have cats, the system could have been jostled.

Power Supply: I'm having trouble finding the name on it without dismantling the system, but it is one of those modular supplies with only a few of the cables plugged in. 1100 watts. (yeah, I was worried about power when I bought it)

Power Demand:
- 3x 3TB hard drives, internal
- 2x 3TB external drives
- Gigabyte GA-78LMT-USB3 motherboard (Bios Date is 11/25/2014, might need to update)
- 8GB DDR3 - I want to say Corsair brand
- GTX 670
- Generic DVD-R and Card Reader.
I should be well within the available wattage for the system.

Other Cards: This is the card the machine was built with. The system does have the ability to use multiple cards, but none were ever installed (so no remnants of a multi-driver package or anything).

Chipset drivers: I reinstalled the system a couple months ago with the driver package from Gigabyte's website, so I think so. I'll double-check to see if there is a newer package.

Motherboard: As mentioned under power demand, it's a GA-78LMT-USB3. I'll look into the bios updates.

OS: Windows 7, version 6.1, Build 7601 SP1
 

tarnakk4

Commendable
Aug 23, 2016
11
0
1,510


I forgot to mention that I'm running Windows 7 SP1. Is this still an issue under that OS, and if so, does the command require any modification to run? Thanks.
 

tarnakk4

Commendable
Aug 23, 2016
11
0
1,510


Looks like the BIOS and Chipset drivers are already at the most recent versions. Took a little while to nail down which GA-78LMT I had - looks like there were 3 revisions (4.1, 5, and 6). Mine is rev 6, last available BIOS update was the 2014 one I mentioned before.

I did reinstall the Chipset drivers just in case there's a difference I'm not seeing, but size and version numbers look the same (most recent on their site and my archived backups).
 

tarnakk4

Commendable
Aug 23, 2016
11
0
1,510


Looks like there's some dismantling involved there. Might take a little time to perform. I'll get back to you with a result when completed.
 

tarnakk4

Commendable
Aug 23, 2016
11
0
1,510


Strange question: I turned off a number of enhanced features in some of the games I was playing where it would crash like bloom, anti-aliasing, that sort of thing, and it seems to have stopped crashing. Bear in mind, I haven't really had enough time to do any real comprehensive stress testing to see if it will fail with those off, but it's not crashing within minutes of opening the games.

Not sure if that helps any, but I thought I'd mention it. Wasn't sure if that pointed more toward a possible hardware issue (overheating, aging card) or if that nvlddmkm.sys file controlled the library for those enhanced features.

I mean, turning those off may be entirely coincidental, too. Just wondering if you had any thought based on that.
 

tarnakk4

Commendable
Aug 23, 2016
11
0
1,510


I completed the reseats and ran System File Checker. Going to run chkdsk overnight - 15TB of drives to scan will probably take a while. Not sure I need to scan the storage drives, but I tend to run a number of things at once, so it's possible it accessed something from one of the storage drives while it was active and paged out. I'll get the memtest run tomorrow morning after the physical disks are cleared.

Plan for the balance of the evening is the startup repair and any other related windows repairs. I know SFC didn't come back with integrity failures, but seems safer to assume it's wrong and run the repairs anyway.

Stress test tomorrow after the memtest. Thanks again for the ideas. I'll post back once I see what happens.
 

tarnakk4

Commendable
Aug 23, 2016
11
0
1,510
So, didn't notice this when I did the first reseat. Got suspicious and examined the card more closely. There's a hole burned in it. Like, seriously, a scorched spot the size of a quarter and melted bits flaking off. So, kind of amazing the card was actually working at all. I appreciate the assistance from all parties, and hopefully some of the things we explored will help other folks in a less charred boat.
 

tarnakk4

Commendable
Aug 23, 2016
11
0
1,510
*grins* So, I was an idiot and left the actual card at my local parts retailer as a conversation piece before I thought to take a picture of it. But, I did find the same model in an image, and I've highlighted the burned section. The core damage seems to have been focused around the square wedge of contacts at the center of the circle. Most of those contacts were missing and the fiberglass was actually charred away and crumbly. There was also some scorching out to the edge of the circle.

http://imgur.com/odOHUc9
 

tarnakk4

Commendable
Aug 23, 2016
11
0
1,510
Also, if either of you know what's actually under those contacts, I am dying to know. Between the idea that it created sort of a phantom usb device and the idea that it caused the crash dump to think the real driver was a 3rd party one, I am now really, really wondering what the part that burned up was.
 

tarnakk4

Commendable
Aug 23, 2016
11
0
1,510


Been a while since I reviewed a crash dump, wasn't sure if that was odd or not. What interested me was that the card still functioned on some level, even with that level of burn damage. And causing it to see a phantom usb device was truly peculiar. It's almost like whatever burned was a specific module from the card, but that it was still functional enough for Windows to just have no clue what to do with it.