irql not less or equal bsod

Jul 6, 2018
1
0
10
0
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: fffff78020000369, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 0000000000000082, 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: fffff8009d8ceedb, address which referenced memory

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
fffff78020000369

CURRENT_IRQL: 0

FAULTING_IP:
nt!RtlGetInterruptTimePrecise+6b
fffff800`9d8ceedb a06903002080f7ffff mov al,byte ptr [FFFFF78020000369h]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: System

BAD_PAGES_DETECTED: 6eea8

TRAP_FRAME: fffff5869f829490 -- (.trap 0xfffff5869f829490)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000002316214 rbx=0000000000000000 rcx=000000357fe29cc6
rdx=000000357fe29cc6 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8009d8ceedb rsp=fffff5869f829620 rbp=fffff78000000350
r8=000000dba0bbcd9b r9=0000000000000000 r10=00000000000000ff
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up di pl nz na po nc
nt!RtlGetInterruptTimePrecise+0x6b:
fffff800`9d8ceedb a06903002080f7ffff mov al,byte ptr [FFFFF78020000369h] ds:fffff780`20000369=??
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff8009d9a8e69 to fffff8009d998330

STACK_TEXT:
fffff586`9f829348 fffff800`9d9a8e69 : 00000000`0000000a fffff780`20000369 00000000`000000ff 00000000`00000082 : nt!KeBugCheckEx
fffff586`9f829350 fffff800`9d9a5ae5 : ffffb60e`d33e3000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff586`9f829490 fffff800`9d8ceedb : 00000000`02316214 fffff800`9d8ce86d 00000000`00252abf 000000db`a44c0000 : nt!KiPageFault+0x425
fffff586`9f829620 fffff800`9d8e2bdf : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!RtlGetInterruptTimePrecise+0x6b
fffff586`9f829670 fffff800`9d89e9e2 : 00000000`00000000 ffff8101`0450dec8 ffff8101`04508180 00000000`00000000 : nt!KePrepareClockTimerForIdle+0x14f
fffff586`9f829720 fffff800`9d89df35 : 00000000`00000003 00000000`00000002 00000000`00000000 00000000`00000008 : nt!PpmIdleExecuteTransition+0x922
fffff586`9f829b00 fffff800`9d99ba5c : 00000000`00000000 ffff8101`04508180 ffff8101`04518100 ffffb60e`d81ac700 : nt!PoIdle+0x345
fffff586`9f829c60 00000000`00000000 : fffff586`9f82a000 fffff586`9f824000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c


STACK_COMMAND: kb

SYMBOL_NAME: PAGE_NOT_ZERO

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUCKET_ID: PAGE_NOT_ZERO

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

*** Memory manager detected 454312 instance(s) of page corruption, target is likely to have memory corruption.
 

Colif

Win 11 Master
Moderator
Jun 12, 2015
60,295
5,056
166,290
10,414
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
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it :)

dump files will show us what drivers were running at time of crash

IRQ errors are normally drivers but can be ram as well.

I would run memtest86 on your ram, 1 stick at a time, up to 8 passes. Any error count higher than 0 is too many and is likely cause of errors. Remove/replace any sticks that get errors.
 

Colif

Win 11 Master
Moderator
Jun 12, 2015
60,295
5,056
166,290
10,414
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
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it :)

dump files will show us what drivers were running at time of crash

IRQ errors are normally drivers but can be ram as well.

I would run memtest86 on your ram, 1 stick at a time, up to 8 passes. Any error count higher than 0 is too many and is likely cause of errors. Remove/replace any sticks that get errors.
 

ASK THE COMMUNITY