[SOLVED] BSOD: DRIVER_IRQL_NOT_LESS_OR_EQUAL, what failed: nvlddmkm.sys

May 25, 2021
4
0
10
0
Hi all, been trying to fix this unstable system for a while now. I receive the mentioned BSOD error, which I am told is an NVIDIA related driver error.

This is a camera server running GeoVision VMS 17.4.1 with Ubiquiti antennas to connect to other buildings in the plaza. Here are the specs and network layout (simplified)

Win 10 Home
i7-10700
ASUS Pro WS W480-ACE
1x16GB Kingtson 2666
Nvidia GT 710
Seagate 500GB HDD (OS)
Seagate 4x6TB HDD



So it seems to only crash when it is connected to the antenna system, which starts from a switch located in an electrical room of building A. It is completely stable when only the local switches/cameras are connected. So far I have tried updating video drivers, Windows, running DDU and reinstalling drivers, reinstalling the VMS software, refreshing Windows from their repair menu, and formatting all drives plus reinstalling Windows with USB media. Is there possibly a device on the network that absolutely will not work with my Nvidia card/drivers? I am pretty stumped at this point, this system received a full makeover with upgraded parts 2 months ago, and has seen this issue for many more months. It crashes anywhere from 3 to 10 times a day, and it doesn't always reboot properly.

In reliability report, I get 'Windows stopped working' with this code
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0x00000000000003c0, 0x0000000000000002, 0x0000000000000000, 0xfffff8013846090f). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 91865f7b-6d72-46e5-80ea-d2381de25f7e.
 
Last edited by a moderator:

Colif

Win 10 Master
Moderator
90% of the times crash dumps won't show the driver name. 5% of the time it shows the driver name once in the dump text.
Then there is yours
yours is different, its screaming Nvidia

fffff8044866d828 fffff80443c08c69 : 000000000000000a 00000000000003c0 0000000000000002 0000000000000000 : nt!KeBugCheckEx
fffff8044866d830 fffff80443c04f69 : 0000000000000000 ffff8c8f675b4000 ffff8c8f71c46900 fffff8045f959ca5 : nt!KiBugCheckDispatch+0x69
fffff8044866d970 fffff8045f52090f : ffff8c8f68ab4910 fffff8045f344c03 ffff8c8f68ab4910 00000098aa0540e0 : nt!KiPageFault+0x469
fffff8044866db00 fffff8045f344c03 : ffff8c8f68ab4910 00000098aa0540e0 fffff8044866dbb1 0000000000000000 : nvlddmkm+0x3a090f
fffff8044866db10 fffff8045f58ba4d : 000000000000008a ffff8c8f68acb000 fffff8040000001f fffff80400000023 : nvlddmkm+0x1c4c03
fffff8044866dc10 fffff8045f5895a7 : 000000000000001f fffff8044866dd79 ffff8c8f68ab4910 000000000000001f : nvlddmkm+0x40ba4d
fffff8044866dcd0 fffff8045f58a0c4 : ffff8c8f68ab4910 ffff8c8f68ab4910 0000000000000089 ffff8c8f68ab4910 : nvlddmkm+0x4095a7
fffff8044866dde0 fffff8045f52869e : ffff8c8f67dbe7d0 fffff8041a151000 0000000000000089 0000000000000000 : nvlddmkm+0x40a0c4
fffff8044866def0 fffff8045f529044 : 000000000e0d9b63 ffff8c8f68aaa000 fffff80400000000 000000000e0d9b63 : nvlddmkm+0x3a869e
fffff8044866e000 fffff8045f526640 : fffff80400000000 ffff8c8f00000000 ffff8c8f68aaa000 fffff8045f8ff8e0 : nvlddmkm+0x3a9044
fffff8044866e110 fffff8045f529265 : 0000000000000008 fffff8045f22c3a5 fffff8044866e2a0 ffff8c8f68acb000 : nvlddmkm+0x3a6640
fffff8044866e220 fffff8045f529752 : ffff8c8f68acb000 0000000010000000 ffff8c8f68aaa000 ffff8c8f68acdae0 : nvlddmkm+0x3a9265
fffff8044866e270 fffff8045f486cd0 : ffff8c8f68aaa000 fffff8044866e310 0000000000000000 ffff8c8f68acb000 : nvlddmkm+0x3a9752
fffff8044866e2d0 fffff8045f4867fe : ffff8c8f68acb000 ffff8c8f68acb000 ffff8c8f68acb000 fffff8045f23f333 : nvlddmkm+0x306cd0
fffff8044866e350 fffff8045f486a2f : ffff8c8f71bba590 ffff8c8f00000015 ffff8c8f68acb000 ffff8c8f68287450 : nvlddmkm+0x3067fe
fffff8044866e3a0 fffff8045f487c63 : 0000000000000004 fffff8044866e5c0 0000000000000004 ffff8c8f68acb000 : nvlddmkm+0x306a2f
fffff8044866e420 fffff8045f4835d3 : fffff8044866e5c0 fffff8045f22a7e6 ffff8c8f68acb000 ffff8c8f6898d010 : nvlddmkm+0x307c63
fffff8044866e480 fffff8045f205277 : ffff8c8f68acb000 ffff8c8f6898d010 0000000000000000 ffff8c8f5ee1f050 : nvlddmkm+0x3035d3
fffff8044866e4c0 fffff80443b230ce : fffff8043fffe240 0000000000000000 fffff8044866ea20 fffff8043fffb180 : nvlddmkm+0x85277
fffff8044866e760 fffff80443b223b4 : 0000000000000000 0000000000000000 0000000000140001 0000000000000000 : nt!KiExecuteAllDpcs+0x30e
fffff8044866e8d0 fffff80443bfa85e : 0000000000000000 fffff8043fffb180 fffff80444526a00 ffff8c8f6ee72080 : nt!KiRetireDpcList+0x1f4
fffff8044866eb60 0000000000000000 : fffff8044866f000 fffff80448668000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x9e

Do you know if there is a newer version of this
Jan 06 2012GVUSBD.sysGeoVision driver
because its not a win 10 driver, its too old. It could be whats causing the conflict
 

Colif

Win 10 Master
Moderator
I edited your post as you had the same text twice. It looked like you had 2 pc.

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

  1. Open Windows File Explore
  2. Navigate to C:\Windows\Minidump
  3. Copy the mini-dump files out onto your Desktop
  4. Do not use Winzip, use the built in facility in Windows
  5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
  6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
  7. Then post a link here to the zip file, so we can take a look for you . . .
i know we know its the Nvidia drivers but dumps might offer a clue.

I am not sure about the card having a conflict with the network

The bugcheck was: 0x000000d1 - Driver IRQ error so its pointing at software. its unusual for Nvidia drivers to cause IRQ errors.
does motherboard have latest bios?
 
May 25, 2021
4
0
10
0
I edited your post as you had the same text twice. It looked like you had 2 pc.

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

  1. Open Windows File Explore
  2. Navigate to C:\Windows\Minidump
  3. Copy the mini-dump files out onto your Desktop
  4. Do not use Winzip, use the built in facility in Windows
  5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
  6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
  7. Then post a link here to the zip file, so we can take a look for you . . .
i know we know its the Nvidia drivers but dumps might offer a clue.

I am not sure about the card having a conflict with the network

The bugcheck was: 0x000000d1 - Driver IRQ error so its pointing at software. its unusual for Nvidia drivers to cause IRQ errors.
does motherboard have latest bios?

Thanks for the reply. I upgraded the BIOS to the latest version, and have set windows to create small dump files. I will leave the server in question running as normal and post the dump file if a BSOD occurs.
 

gardenman

Distinguished
Moderator
Hi, I ran the dump file through the debugger and got the following information: https://jsfiddle.net/xhz3tmjy/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.

File information:MEMORY.DMP (May 25 2021 - 18:07:52)
Bugcheck:DRIVER_IRQL_NOT_LESS_OR_EQUAL (D1)
Probably caused by:nvlddmkm.sys (Process: System)
Uptime:0 Day(s), 0 Hour(s), 10 Min(s), and 55 Sec(s)

The nvlddmkm.sys file is a NVIDIA graphics card driver. There are a few things you can do to fix this problem. First off, try a full uninstall using DDU in Safe Mode then re-install the driver (more information). Or try getting the latest version of the driver. Or try one of the 3 most recent drivers released by NVIDIA. Drivers can be found here: http://www.nvidia.com/ or you can allow Windows Update to download the driver for you, which might be a older/better version.

Possible Motherboard page: https://www.asus.com/Motherboards-Components/Motherboards/Workstation/Pro-WS-W480-ACE/
There are BIOS updates available for your system. Wait for additional information before deciding to update or not. Important: Verify that I have linked to the correct motherboard. Updating your BIOS can be risky. Never try it when you might lose power (lightning storms, recent power outages, etc).

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.
 

Colif

Win 10 Master
Moderator
90% of the times crash dumps won't show the driver name. 5% of the time it shows the driver name once in the dump text.
Then there is yours
yours is different, its screaming Nvidia

fffff8044866d828 fffff80443c08c69 : 000000000000000a 00000000000003c0 0000000000000002 0000000000000000 : nt!KeBugCheckEx
fffff8044866d830 fffff80443c04f69 : 0000000000000000 ffff8c8f675b4000 ffff8c8f71c46900 fffff8045f959ca5 : nt!KiBugCheckDispatch+0x69
fffff8044866d970 fffff8045f52090f : ffff8c8f68ab4910 fffff8045f344c03 ffff8c8f68ab4910 00000098aa0540e0 : nt!KiPageFault+0x469
fffff8044866db00 fffff8045f344c03 : ffff8c8f68ab4910 00000098aa0540e0 fffff8044866dbb1 0000000000000000 : nvlddmkm+0x3a090f
fffff8044866db10 fffff8045f58ba4d : 000000000000008a ffff8c8f68acb000 fffff8040000001f fffff80400000023 : nvlddmkm+0x1c4c03
fffff8044866dc10 fffff8045f5895a7 : 000000000000001f fffff8044866dd79 ffff8c8f68ab4910 000000000000001f : nvlddmkm+0x40ba4d
fffff8044866dcd0 fffff8045f58a0c4 : ffff8c8f68ab4910 ffff8c8f68ab4910 0000000000000089 ffff8c8f68ab4910 : nvlddmkm+0x4095a7
fffff8044866dde0 fffff8045f52869e : ffff8c8f67dbe7d0 fffff8041a151000 0000000000000089 0000000000000000 : nvlddmkm+0x40a0c4
fffff8044866def0 fffff8045f529044 : 000000000e0d9b63 ffff8c8f68aaa000 fffff80400000000 000000000e0d9b63 : nvlddmkm+0x3a869e
fffff8044866e000 fffff8045f526640 : fffff80400000000 ffff8c8f00000000 ffff8c8f68aaa000 fffff8045f8ff8e0 : nvlddmkm+0x3a9044
fffff8044866e110 fffff8045f529265 : 0000000000000008 fffff8045f22c3a5 fffff8044866e2a0 ffff8c8f68acb000 : nvlddmkm+0x3a6640
fffff8044866e220 fffff8045f529752 : ffff8c8f68acb000 0000000010000000 ffff8c8f68aaa000 ffff8c8f68acdae0 : nvlddmkm+0x3a9265
fffff8044866e270 fffff8045f486cd0 : ffff8c8f68aaa000 fffff8044866e310 0000000000000000 ffff8c8f68acb000 : nvlddmkm+0x3a9752
fffff8044866e2d0 fffff8045f4867fe : ffff8c8f68acb000 ffff8c8f68acb000 ffff8c8f68acb000 fffff8045f23f333 : nvlddmkm+0x306cd0
fffff8044866e350 fffff8045f486a2f : ffff8c8f71bba590 ffff8c8f00000015 ffff8c8f68acb000 ffff8c8f68287450 : nvlddmkm+0x3067fe
fffff8044866e3a0 fffff8045f487c63 : 0000000000000004 fffff8044866e5c0 0000000000000004 ffff8c8f68acb000 : nvlddmkm+0x306a2f
fffff8044866e420 fffff8045f4835d3 : fffff8044866e5c0 fffff8045f22a7e6 ffff8c8f68acb000 ffff8c8f6898d010 : nvlddmkm+0x307c63
fffff8044866e480 fffff8045f205277 : ffff8c8f68acb000 ffff8c8f6898d010 0000000000000000 ffff8c8f5ee1f050 : nvlddmkm+0x3035d3
fffff8044866e4c0 fffff80443b230ce : fffff8043fffe240 0000000000000000 fffff8044866ea20 fffff8043fffb180 : nvlddmkm+0x85277
fffff8044866e760 fffff80443b223b4 : 0000000000000000 0000000000000000 0000000000140001 0000000000000000 : nt!KiExecuteAllDpcs+0x30e
fffff8044866e8d0 fffff80443bfa85e : 0000000000000000 fffff8043fffb180 fffff80444526a00 ffff8c8f6ee72080 : nt!KiRetireDpcList+0x1f4
fffff8044866eb60 0000000000000000 : fffff8044866f000 fffff80448668000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x9e

Do you know if there is a newer version of this
Jan 06 2012GVUSBD.sysGeoVision driver
because its not a win 10 driver, its too old. It could be whats causing the conflict
 
May 25, 2021
4
0
10
0
I'll take a look at the GVUSBD driver, but for now we used DDU to uninstall the drivers and left it like that. Haven't had a problem since. Looks like we will be ok as long as we do not upgrade the drivers.
 

ASK THE COMMUNITY

TRENDING THREADS