IRQL_NOT_LESS_OR_EQUAL

Question

Hello all, I've been having intermittent BSODs with the error reason IRQL_NOT_LESS_OR_EQUAL.

I've run Driver Verifier and initially found the cause to be an older Logitech Gaming Software driver - I've since updated it to the most recent version available on the manufacturer's website (driver date 3/8/2018). However, I still seem to encounter inconsistent crashes - sometimes within a few minutes of booting up, sometimes after a few hours of uptime, and sometimes I'll go through a week of regular use and turning on/off without any errors.

Most recent crash details:

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: 00000000000000ca, 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: fffff8071d31df55, address which referenced memory

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2624

    Key  : Analysis.Elapsed.mSec
    Value: 2656

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xa

    Key  : Dump.Attributes.AsUlong
    Value: 8

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Failure.Bucket
    Value: AV_nt!KiHeteroChooseTargetProcessor

    Key  : Failure.Hash
    Value: {107bb024-437a-c58e-f3f5-25fae0d730fc}

BUGCHECK_CODE:  a

BUGCHECK_P1: ca

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff8071d31df55

FILE_IN_CAB:  102023-7750-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

READ_ADDRESS: fffff8071dafb390: 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
 00000000000000ca 

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

TRAP_FRAME:  fffffc8514a8b440 -- (.trap 0xfffffc8514a8b440)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=fffff8071dafb3a0
rdx=0000000000000004 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8071d31df55 rsp=fffffc8514a8b5d0 rbp=fffffc8514a8b639
 r8=0000000000000002  r9=0000000000000002 r10=0000000000000037
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KiHeteroChooseTargetProcessor+0x5d5:
fffff807`1d31df55 4885b8c8000000  test    qword ptr [rax+0C8h],rdi ds:00000000`000000ca=????????????????
Resetting default scope

STACK_TEXT:  
fffffc85`14a8b2f8 fffff807`1d210029     : 00000000`0000000a 00000000`000000ca 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffffc85`14a8b300 fffff807`1d20bbe3     : 00000000`00000000 00000000`00000000 00000000`00000002 00000000`0000002f : nt!KiBugCheckDispatch+0x69
fffffc85`14a8b440 fffff807`1d31df55     : 00000000`00000000 ffffd401`00000000 fffffc85`14a8b639 00000000`00000000 : nt!KiPageFault+0x463
fffffc85`14a8b5d0 fffff807`1d22343a     : ffffd401`ebde0180 ffffe60d`00000000 ffffe60d`00000005 fffffc85`14a8b6dc : nt!KiHeteroChooseTargetProcessor+0x5d5
fffffc85`14a8b6a0 fffff807`1d08d63d     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeferredReadySingleThread+0x20989a
fffffc85`14a8b890 fffff807`1d10598b     : ffffe60d`22803080 00000000`00000000 ffffe60d`228031f0 ffffe60d`275fc2a0 : nt!KiReadyThread+0x4d
fffffc85`14a8b8c0 fffff807`1d08d958     : fffffc85`14a8b948 00000000`00000000 fffffc85`14a8bb10 ffffe60d`00000002 : nt!KiProcessThreadWaitList+0xcb
fffffc85`14a8b910 fffff807`1d08aee4     : 00000000`00000000 00000000`00000000 00000000`00000008 00000000`00017aa9 : nt!KiTimer2Expiration+0x198
fffffc85`14a8b9d0 fffff807`1d20092e     : ffffffff`00000000 ffffd401`ebde0180 ffffd401`ebdeb340 ffffe60d`13933040 : nt!KiRetireDpcList+0x874
fffffc85`14a8bc60 00000000`00000000     : fffffc85`14a8c000 fffffc85`14a86000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e

SYMBOL_NAME:  nt!KiHeteroChooseTargetProcessor+5d5

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.3086

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  5d5

FAILURE_BUCKET_ID:  AV_nt!KiHeteroChooseTargetProcessor

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {107bb024-437a-c58e-f3f5-25fae0d730fc}

Followup:     MachineOwner

Answer 1

Updating the BIOS is a good idea.

I suggest also downloading the latest chipset drivers and installing them.

Old Chipset drivers may have compatibility issues with the new BIOS version.

Answer 2

Hi David,

It appears to be an AMD driver this time:

Link to minidump: https://1drv.ms/u/s!ApcOGqzQiy4TgSw5sdQugC1b34KG?e=KeMvIn

I have also confirmed my RAM (CMK64GX4M2D3600C18) is compatible with my motherboard. After some online digging, it looks like one potential cause of this verifier crash is an out of date motherboard BIOS. My motherboard (MSI B550M PRO-VDH WIFI) BIOS version is from 8/5/2022, whereas the newest from MSI is on 10/12/2023. I'm going to download that and flash my BIOS, then see if the problem persists.

Thanks!

Answer 3

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

Your minidumps don't mention any driver as the cause of the crashes.

If you enable Driver Verifier again, is the Logitech Gaming Software driver still being mentioned?

Can you send the minidump created by the Driver Verifier?

I await your reply.

Answer 4

Link to minidump files: https://1drv.ms/f/s!ApcOGqzQiy4TgSv3ThUlyqxjVMhC?e=ugT13q