DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) BSOD from nvlddmkm.sys

Question

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) BSOD from nvlddmkm.sys

Markus-3317 20

So I have a slight problem. Everytime I boot up a game, sometimes it doesnt do anything, and after a while, my whole PC gets a BSOD. I have been vacationing for a month, and I recently returned from my trip, and this has been happening recently. It hasnt even happened before until my return.

here is the windbg bugcheck analysis.

It seems to have to do something with my NVIDIA drivers, or something faulty, I am not a very technical person so I would like to request some help. I will share two, the first one is one of my first crashes since and the second one is a recent crash.


VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)
The video memory manager encountered a condition that it can't recover from. By crashing,
the video memory manager is attempting to get enough information into the minidump such that
somebody can pinpoint what lead to this condition.
Arguments:
Arg1: 0000000000000037, The subtype of the BugCheck:
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000

Debugging Details:
------------------


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1484

    Key  : Analysis.Elapsed.mSec
    Value: 1508

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 1

    Key  : Analysis.IO.Write.Mb
    Value: 0

    Key  : Analysis.Init.CPU.mSec
    Value: 515

    Key  : Analysis.Init.Elapsed.mSec
    Value: 5096

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 85

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29617.1000

    Key  : Analysis.Version.Description
    Value: 10.2604.29.1 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2604.29.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x10e

    Key  : Bugcheck.Code.TargetModel
    Value: 0x10e

    Key  : Failure.Bucket
    Value: 0x10e_37_dxgmms2!VIDMM_GLOBAL::EnsureLockedPages

    Key  : Failure.Hash
    Value: {ad5e2e6c-33d9-5cb2-a19b-f33cceee5dc0}

    Key  : WER.OS.Branch
    Value: ge_release

    Key  : WER.OS.Version
    Value: 10.0.26100.1

    Key  : WER.System.BIOSRevision
    Value: 5.17.0.0


BUGCHECK_CODE:  10e

BUGCHECK_P1: 37

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FILE_IN_CAB:  072626-17562-02.dmp

FAULTING_THREAD:  ffffb00d304614c0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon) (!blackboxwinlogonnotify)


CUSTOMER_CRASH_COUNT:  2

PROCESS_NAME:  System

STACK_TEXT:  
ffff8805`1bdd46f8 fffff802`841b1316     : 00000000`0000010e 00000000`00000037 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffff8805`1bdd4700 fffff802`9b17f81d     : ffffb00d`305a0000 ffffe704`85e1c210 ffffb00d`305a0000 fffff802`00000002 : watchdog!WdLogSingleEntry5+0x156
ffff8805`1bdd4790 fffff802`9b149cb0     : ffffe704`7e7d4801 ffff1074`3eeab874 00000000`00000000 ffffb00d`305a0000 : dxgmms2!VIDMM_GLOBAL::EnsureLockedPages+0x161
ffff8805`1bdd4850 fffff802`9b1227ed     : ffffe704`6dda6a00 ffffe704`7e7d4840 ffffb00d`305a0000 00000000`00000000 : dxgmms2!VIDMM_GLOBAL::UnlockAllocation+0x1a4
ffff8805`1bdd48d0 fffff802`9b1228d2     : ffffe704`6dda6a00 ffffb00d`4ea12500 ffffb00d`4ea12500 ffffb00d`3029cca0 : dxgmms2!VIDMM_SEGMENT::UnlockAllocationBackingStore+0x91
ffff8805`1bdd4910 fffff802`9b11b8e0     : ffffe704`7e7d4840 ffff8805`1bdd49d0 ffffb00d`4ea12550 ffffb00d`4f11c7f0 : dxgmms2!VIDMM_SYSMEM_SEGMENT::EvictResource+0xb2
ffff8805`1bdd4960 fffff802`9b11a3ad     : 00000000`00000001 00000000`00000000 ffff8805`1bdd4a01 00000000`00000000 : dxgmms2!VIDMM_PHYSICAL_ADAPTER::EvictResources+0x25c
ffff8805`1bdd4a10 fffff802`9b11a306     : ffffe704`4e68d000 ffffb00d`305a0000 00000000`00000002 ffffb00d`2edf9300 : dxgmms2!VIDMM_SEGMENT::CleanupMarkedForEvictionAllocations+0x59
ffff8805`1bdd4a50 fffff802`9b11a22f     : ffffe704`4e68d000 ffff8805`1bdd4b89 80000000`00000000 ffffb00d`305a0000 : dxgmms2!VIDMM_GLOBAL::CleanupMarkedForEvictionAllocationsWorker+0x76
ffff8805`1bdd4a90 fffff802`9b15da80     : ffffe704`4e68d000 ffffb00d`305a9c20 ffffb00d`305a9c20 ffffb00d`305a9c20 : dxgmms2!VIDMM_GLOBAL::CleanupMarkedForEvictionAllocations+0x12f
ffff8805`1bdd4ad0 fffff802`f268212a     : ffffb00d`30461400 fffff802`9b15cb00 ffff8e01`90911100 000f807f`b4bbbd02 : dxgmms2!VidMmWorkerThreadProc+0xf10
ffff8805`1bdd4bf0 fffff802`f28acd94     : ffff8e01`90911180 ffffb00d`304614c0 fffff802`f26820d0 ccccc35f`5e415f41 : nt!PspSystemThreadStartup+0x5a
ffff8805`1bdd4c40 00000000`00000000     : ffff8805`1bdd5000 ffff8805`1bdcf000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME:  dxgmms2!VIDMM_GLOBAL::EnsureLockedPages+161

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

IMAGE_VERSION:  10.0.26100.8875

STACK_COMMAND: .process /r /p 0xffffb00d156b5040; .thread /r /p 0xffffb00d304614c0 ; kb

BUCKET_ID_FUNC_OFFSET:  161

FAILURE_BUCKET_ID:  0x10e_37_dxgmms2!VIDMM_GLOBAL::EnsureLockedPages

OS_VERSION:  10.0.26100.1

BUILDLAB_STR:  ge_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {ad5e2e6c-33d9-5cb2-a19b-f33cceee5dc0}

Followup:     MachineOwner
---------

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000000000002a0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff806937b61fa, address which referenced memory
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
KEY_VALUES_STRING: 1
    Key  : Analysis.CPU.mSec
    Value: 1531
    Key  : Analysis.Elapsed.mSec
    Value: 1622
    Key  : Analysis.IO.Other.Mb
    Value: 0
    Key  : Analysis.IO.Read.Mb
    Value: 1
    Key  : Analysis.IO.Write.Mb
    Value: 0
    Key  : Analysis.Init.CPU.mSec
    Value: 625
    Key  : Analysis.Init.Elapsed.mSec
    Value: 2696
    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 82
    Key  : Analysis.Version.DbgEng
    Value: 10.0.29617.1000
    Key  : Analysis.Version.Description
    Value: 10.2604.29.1 amd64fre
    Key  : Analysis.Version.Ext
    Value: 1.2604.29.1
    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xd1
    Key  : Bugcheck.Code.TargetModel
    Value: 0xd1
    Key  : Failure.Bucket
    Value: AV_nvlddmkm!unknown_function
    Key  : Failure.Exception.IP.Address
    Value: 0xfffff806937b61fa
    Key  : Failure.Exception.IP.Module
    Value: nvlddmkm
    Key  : Failure.Exception.IP.Offset
    Value: 0x3961fa
    Key  : Failure.Hash
    Value: {7eea5677-f68d-2154-717e-887e07e55cd3}
    Key  : Faulting.IP.Type
    Value: Paged
    Key  : Stack.Pointer
    Value: NMI
    Key  : WER.OS.Branch
    Value: ge_release
    Key  : WER.OS.Version
    Value: 10.0.26100.1
    Key  : WER.System.BIOSRevision
    Value: 5.17.0.0
BUGCHECK_CODE:  d1
BUGCHECK_P1: 2a0
BUGCHECK_P2: 2
BUGCHECK_P3: 0
BUGCHECK_P4: fffff806937b61fa
FILE_IN_CAB:  072726-18031-01.dmp
FAULTING_THREAD:  fffff806f37d25c0
READ_ADDRESS: fffff806f37c54d8: Unable to get MiVisibleState
 00000000000002a0 
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1 (!blackboxwinlogon) (!blackboxwinlogonnotify)
CUSTOMER_CRASH_COUNT:  1
PROCESS_NAME:  System
DPC_STACK_BASE:  FFFFF8068535EFB0
IP_IN_PAGED_CODE: 
nvlddmkm+3961fa
fffff806`937b61fa 4883baa002000000 cmp     qword ptr [rdx+2A0h],0
STACK_TEXT:  
fffff806`85356b38 fffff806`f2ebfbe9     : 00000000`0000000a 00000000`000002a0 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff806`85356b40 fffff806`f2ebaea8     : 00000000`01010101 00000000`00000000 ffffa809`f6a251d0 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff806`85356c80 fffff806`937b61fa     : ffffa809`f6a24000 00000000`ffffffff 00000000`00000000 ffffa809`e9a55000 : nt!KiPageFault+0x468
fffff806`85356e10 ffffa809`f6a24000     : 00000000`ffffffff 00000000`00000000 ffffa809`e9a55000 ffffa809`f6a251d0 : nvlddmkm+0x3961fa
fffff806`85356e18 00000000`ffffffff     : 00000000`00000000 ffffa809`e9a55000 ffffa809`f6a251d0 fffff806`93e52c39 : 0xffffa809`f6a24000
fffff806`85356e20 00000000`00000000     : ffffa809`e9a55000 ffffa809`f6a251d0 fffff806`93e52c39 fffff806`85357080 : 0xffffffff
SYMBOL_NAME:  nvlddmkm+3961fa
MODULE_NAME: nvlddmkm
IMAGE_NAME:  nvlddmkm.sys
STACK_COMMAND: .process /r /p 0xfffff806f37cff00; .thread /r /p 0xfffff806f37d25c0 ; kb
BUCKET_ID_FUNC_OFFSET:  3961fa
FAILURE_BUCKET_ID:  AV_nvlddmkm!unknown_function
OS_VERSION:  10.0.26100.1
BUILDLAB_STR:  ge_release
OSPLATFORM_TYPE:  x64
OSNAME:  Windows 10
FAILURE_ID

0 comments

Answer accepted by question author

0 additional answers

Your answer

Answer 1

David-M 121.9K Independent Advisor

Hi. I'm David, and I'm happy to help you.

Based on the information from the minidumps you attached, the problem is being caused by the Nvidia graphics driver.

To be able to assist you better, please clarify the following:

Is your PC a desktop or a laptop?

If it's a laptop, what is the manufacturer and model?

If you prefer, you can share a screenshot of your system information.

Press "Windows + R", type msinfo32 and press Enter.

Maximize the window and use the shortcut "Windows + Shift + S" to use the screenshot tool.

Looking forward to your reply.

Markus-3317 20 Reputation points

2026-07-27T15:19:10.96+00:00

It is a desktop PC. For some extra info, I have tried doing a clean install through the NVIDIA App, but it still does this.
David-M 121.9K Reputation points Independent Advisor

2026-07-27T15:25:03.61+00:00

Thanks for the clarification.

A clean install via the Nvidia App usually does not fix this type of problem. I suggest performing a clean install of the Nvidia driver as instructed below.

Download the latest driver for your graphics card from the Nvidia website. Then, use the free DDU tool to remove the current driver. Then, install the latest driver using the installer you downloaded.

(I suggest disconnecting from the internet during the entire procedure.)

DDU: https://www.guru3d.com/files-details/display-driver-uninstaller-download.html

Nvidia driver download: https://www.nvidia.com/en-us/drivers/

(Run the downloaded file and follow the on-screen instructions to install the driver.)

See if the system will work stably after this.

If the BSOD occurs again after doing this, share the minidump it created.

If you need a tutorial for using DDU, I recommend the video below.

https://www.youtube.com/watch?v=bP-2B14Nckw

Feel free to ask any questions you may have.

Standard Disclaimer: There are links to non-Microsoft websites. The pages appear to be providing accurate, safe information. Watch out for ads on the sites that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the sites before you decide to download and install it.
Markus-3317 20 Reputation points

2026-07-27T16:19:54.51+00:00

Thanks. Hopefully this has done it. It took me quite a bit of time since My main monitor wasnt working during safe mode for some reason so I had to get an extra monitor, but hopefully this has fixed it.
David-M 121.9K Reputation points Independent Advisor

2026-07-27T16:22:15.5233333+00:00

Glad to help.

If you have any questions, don't hesitate to ask.