BSOD stopcode: IRQL_NOT_LESS_OR_EQUAL

Question

So i've been getting the same random BSOD even after reinstalling windows, updating bios, updating drivers. Here is the minidumpfile, please help.

Microsoft (R) Windows Debugger Version 10.0.22621.1778 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\101523-20640-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*

Executable search path is:

Windows 10 Kernel Version 19041 MP (12 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Edition build lab: 19041.1.amd64fre.vb_release.191206-1406

Machine Name:

Kernel base = 0xfffff8036ac00000 PsLoadedModuleList = 0xfffff8036b82a360

Debug session time: Sun Oct 15 04:28:49.561 2023 (UTC + 2:00)

System Uptime: 2 days 4:16:57.235

Loading Kernel Symbols

...............................................................

................................................................

................................................................

Loading User Symbols

Loading unloaded module list

..................................................

For analysis of this file, run !analyze -v

0: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)

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 a kernel debugger is available get the stack backtrace.

Arguments:

Arg1: fffffffffffffc44, memory referenced

Arg2: 0000000000000002, IRQL

Arg3: 0000000000000000, bitfield :

bit 0 : value 0 = read operation, 1 = write operation 

bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) 

Arg4: fffff8036aecfb61, address which referenced memory

Debugging Details:

---

*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec 

Value: 6358 

Key  : Analysis.DebugAnalysisManager 

Value: Create 

Key  : Analysis.Elapsed.mSec 

Value: 7667 

Key  : Analysis.Init.CPU.mSec 

Value: 1421 

Key  : Analysis.Init.Elapsed.mSec 

Value: 12283 

Key  : Analysis.Memory.CommitPeak.Mb 

Value: 90 

Key  : WER.OS.Branch 

Value: vb\_release 

Key  : WER.OS.Timestamp 

Value: 2019-12-06T14:06:00Z 

Key  : WER.OS.Version 

Value: 10.0.19041.1 

FILE_IN_CAB: 101523-20640-01.dmp

BUGCHECK_CODE: a

BUGCHECK_P1: fffffffffffffc44

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff8036aecfb61

READ_ADDRESS: fffff8036b8fb390: 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

fffffffffffffc44

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: Discord.exe

TRAP_FRAME: ffffd30096c998e0 -- (.trap 0xffffd30096c998e0)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000

rdx=0000000000002710 rsi=0000000000000000 rdi=0000000000000000

rip=fffff8036aecfb61 rsp=ffffd30096c99a70 rbp=ffffd30096c99b80

r8=0000000000002710 r9=fffff8036b819570 r10=0000000000000000

r11=ffffd30096c99a90 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei pl nz na po cy

nt!ExpUpdateTimerResolution+0xf1:

fffff8036aecfb61 f78144fcffff00100000 test dword ptr [rcx-3BCh],1000h ds:fffffffffffffc44=????????

Resetting default scope

STACK_TEXT:

ffffd30096c99798 fffff8036b011729 : 000000000000000a fffffffffffffc44 0000000000000002 0000000000000000 : nt!KeBugCheckEx

ffffd30096c997a0 fffff8036b00d2e3 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiBugCheckDispatch+0x69

ffffd30096c998e0 fffff8036aecfb61 : 0000000000000000 ffffac0bae1b8080 ffff09b635147fff ffffac0bae1b8080 : nt!KiPageFault+0x463

ffffd30096c99a70 fffff8036b284be8 : ffffac0bae1b8080 0000000000002710 ffffd30096c99b18 0000000000000000 : nt!ExpUpdateTimerResolution+0xf1

ffffd30096c99aa0 fffff8036b010ef8 : ffffac0bae1f8080 0000000000000010 00000000106bf684 ffffac0b00000000 : nt!NtSetTimerResolution+0xd8

ffffd30096c99b00 0000000077221cfc : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x28

000000000f16ef78 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x77221cfc

SYMBOL_NAME: nt!ExpUpdateTimerResolution+f1

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.3570

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: f1

FAILURE_BUCKET_ID: AV_nt!ExpUpdateTimerResolution

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {f9e8116d-dce8-6c39-9263-2a27148f9460}

Followup: MachineOwner

---

Answer 1

Hello omoman，

Welcome to the Microsoft Community!

Having read your question in its entirety and thanking you for the error reporting information.

According to the error code you provided: IRQL_NOT_LESS_OR_EQUAL

This error code usually refers to the Windows or kernel-mode driver Microsoft accessing paged memory at an invalid address during the raised interrupt request level (IRQL), for a detailed description of the code, you can read the following link:

Bug check 0xA IRQL_NOT_LESS_OR_EQUAL - Windows drivers | Microsoft Learn

The error could be caused by a device driver, system service, virus scanner, or a backup utility that is not compatible with the new version, but considering that you have already reinstalled your system system and updated the BIOS and drivers, I honestly think that a system failure is less likely, unless you are using a faulty USB installation media.

Based on the dmp log files you have subsequently provided, the main process causing this blue screen problem is: ntkrnlmp.exe

This is a Windows kernel process. You may have been running Discord.exe at the time of the blue screen problem, so for now you can try uninstalling and deleting Discord.exe, and then reinstalling it again to see if the problem reoccurs.

If the problem reoccurs, I assume that there is something wrong with the USB installation media you are using, so I am providing you with the official and complete procedure for installing a new system:

Reinstall Windows - Microsoft Support

Disclaimer: We still recommend backing up your computer in advance if it contains important data.

Please refer to the instructions in this link to create a new installation media and try the installation, I believe the problem should not reoccur after you follow the official instructions.

However, if the problem reoccurs, you may need to send your device to after-sales support for a thorough checkup, as we have received feedback from some users that they experienced compatibility issues after updating the BIOS, but we are unable to confirm this at this time due to our constraints, so we recommend that you check this out with the assistance of after-sales support.

Best Regarts,

Morning | Microsoft Technical Support Community