how To fix DRIVER_IRQL_NOT_LESS_OR_EQUAL

Question

Hello. Every now and then my system displays a blue screen with DRIVER_IRQL_NOT_LESS_OR_EQUAL. I recently received this after Microsoft officially announced the upgrade from Windows 10 to Windows 11. I checked the components and there was no hardware problem. I wanted to see how I could solve the problem. (I encounter this problem at least once or twice a month!) This information is WINdbg information:

This link contains dump files:

https://1drv.ms/f/c/5baf439896761797/EjEmqiSMgApBoiUkLP1nVtwBvN3sYRmmA0AR0BSmcIUnCQ?e=RiFYZq

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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: 00000000c00fd0dc, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8043d2985b7, address which referenced memory

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1375

    Key  : Analysis.Elapsed.mSec
    Value: 10031

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27871.1001

    Key  : Analysis.Version.Description
    Value: 10.2505.01.02 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2505.1.2

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xd1

    Key  : Bugcheck.Code.TargetModel
    Value: 0xd1

    Key  : Dump.Attributes.AsUlong
    Value: 0x8

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Failure.Bucket
    Value: AV_nt!KiPageFault

    Key  : Failure.Exception.IP.Address
    Value: 0xfffff8043d2985b7

    Key  : Failure.Hash
    Value: {ec3e2762-48ae-ffe9-5b16-fbcb853e8320}


BUGCHECK_CODE:  d1

BUGCHECK_P1: c00fd0dc

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff8043d2985b7

FILE_IN_CAB:  082425-7406-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffce8b40ff5040

READ_ADDRESS: fffff80436cfb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
 00000000c00fd0dc 

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
ffffe201`67f5f068 fffff804`36411da9     : 00000000`0000000a 00000000`c00fd0dc 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffe201`67f5f070 fffff804`3640d778     : 00000000`00000818 00000000`00000094 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffe201`67f5f1b0 fffff804`3d2985b7     : ffffe201`67f5f331 ffffe201`67f5f3e0 ffffe201`67f5f480 00031196`1f3a1262 : nt!KiPageFault+0x478
ffffe201`67f5f340 ffffe201`67f5f331     : ffffe201`67f5f3e0 ffffe201`67f5f480 00031196`1f3a1262 00000000`012004c0 : 0xfffff804`3d2985b7
ffffe201`67f5f348 ffffe201`67f5f3e0     : ffffe201`67f5f480 00031196`1f3a1262 00000000`012004c0 00000000`00000000 : 0xffffe201`67f5f331
ffffe201`67f5f350 ffffe201`67f5f480     : 00031196`1f3a1262 00000000`012004c0 00000000`00000000 00000000`00000002 : 0xffffe201`67f5f3e0
ffffe201`67f5f358 00031196`1f3a1262     : 00000000`012004c0 00000000`00000000 00000000`00000002 ffffe201`67f5f4f8 : 0xffffe201`67f5f480
ffffe201`67f5f360 00000000`012004c0     : 00000000`00000000 00000000`00000002 ffffe201`67f5f4f8 00000000`00000002 : 0x00031196`1f3a1262
ffffe201`67f5f368 00000000`00000000     : 00000000`00000002 ffffe201`67f5f4f8 00000000`00000002 ffffe201`67f5f448 : 0x12004c0


SYMBOL_NAME:  nt!KiPageFault+478

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.6218

STACK_COMMAND: .process /r /p 0xffffce8b18502080; .thread 0xffffce8b40ff5040 ; kb

BUCKET_ID_FUNC_OFFSET:  478

FAILURE_BUCKET_ID:  AV_nt!KiPageFault

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {ec3e2762-48ae-ffe9-5b16-fbcb853e8320}

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

3: kd> .thread /r /p ffffce8b40ff5040
Implicit thread is now ffffce8b`40ff5040
Implicit process is now ffffce8b`18502080
Loading User Symbols

3: kd> .process /r /p 0xffffce8b18502080; .thread 0xffffce8b40ff5040 ; kb
Implicit process is now ffffce8b`18502080
Loading User Symbols

Implicit thread is now ffffce8b`40ff5040
  *** Stack trace for last set context - .thread/.cxr resets it
 # RetAddr               : Args to Child                                                           : Call Site
00 fffff804`36411da9     : 00000000`0000000a 00000000`c00fd0dc 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
01 fffff804`3640d778     : 00000000`00000818 00000000`00000094 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
02 fffff804`3d2985b7     : ffffe201`67f5f331 ffffe201`67f5f3e0 ffffe201`67f5f480 00031196`1f3a1262 : nt!KiPageFault+0x478
03 ffffe201`67f5f331     : ffffe201`67f5f3e0 ffffe201`67f5f480 00031196`1f3a1262 00000000`012004c0 : 0xfffff804`3d2985b7
04 ffffe201`67f5f3e0     : ffffe201`67f5f480 00031196`1f3a1262 00000000`012004c0 00000000`00000000 : 0xffffe201`67f5f331
05 ffffe201`67f5f480     : 00031196`1f3a1262 00000000`012004c0 00000000`00000000 00000000`00000002 : 0xffffe201`67f5f3e0
06 00031196`1f3a1262     : 00000000`012004c0 00000000`00000000 00000000`00000002 ffffe201`67f5f4f8 : 0xffffe201`67f5f480
07 00000000`012004c0     : 00000000`00000000 00000000`00000002 ffffe201`67f5f4f8 00000000`00000002 : 0x00031196`1f3a1262
08 00000000`00000000     : 00000000`00000002 ffffe201`67f5f4f8 00000000`00000002 ffffe201`67f5f448 : 0x12004c0
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2506.12002.0_x64__8wekyb3d8bbwe\amd64\Visualizers\atlmfc.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2506.12002.0_x64__8wekyb3d8bbwe\amd64\Visualizers\concurrency.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2506.12002.0_x64__8wekyb3d8bbwe\amd64\Visualizers\cpp_rest.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2506.12002.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Kernel.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2506.12002.0_x64__8wekyb3d8bbwe\amd64\Visualizers\ObjectiveC.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2506.12002.0_x64__8wekyb3d8bbwe\amd64\Visualizers\stl.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2506.12002.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Usb4Kd.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2506.12002.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Windows.Data.Json.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2506.12002.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Windows.Devices.Geolocation.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2506.12002.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Windows.Devices.Sensors.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2506.12002.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Windows.Media.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2506.12002.0_x64__8wekyb3d8bbwe\amd64\Visualizers\windows.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2506.12002.0_x64__8wekyb3d8bbwe\amd64\Visualizers\winrt.natvis'

Answer 1

Your minidump files just indicate generic memory (RAM) corruption no specific cause of the crashes is listed

To try to force Windows to show any faulting drivers...etc., the best option would be to turn on Driver Verifier, let your PC crash 3 times, then you must turn off Driver Verifier, and finally, upload any newly created minidump files

Before you run Driver Verifier, please create a new System Restore Point

https://learn.microsoft.com/en-us/answers/questions/4377096/(article)-driver-verifier-tracking-down-a-mis-beha?forum=windows-windows_10-update&referrer=answers

.

.

.

---

Note, if you have any difficulty getting into Windows with Driver Verifier enabled:

Start your PC, just as Windows attempts to load (spinning dots), press and hold Power Button for 5 - 10 seconds to perform a Hard Shut Down

Do this twice

On the third start Windows will boot into the Recovery Environment and from there you can access System Repair, Safe Mode, Command Prompt... etc.

Go to Troubleshoot - Advanced Option - Startup Settings and click Restart

Upon restart, press 4 to enter Safe Mode

Open Command Prompt as Administrator and run these two commands, then restart your PC.

verifier /reset

verifier /bootmode resetonbootfail