BSOD IRQL_NOT_LESS_OR_EQUAL on 10.0.19041.1

S

Steve McAfee

Built this computer in the spring, after taking the win10 2004 update I was plagued with non-specific BSOD's every few days. Then an AMD video driver update fixed it. They actually noted in their release notes the problem. All was good. Unfortunately I took the 20H2 update in november and I've been chasing an infrequent problem ever since. The BSOD is really non-specific, although I find very similar dumps across the last five years so these seems to be a somewhat generic problem. Is not frequent, maybe once per week it happens. I've updated everything I can. Since the problem is infrequent it takes a long time to "try" any change. Any suggestions?


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*Symbol information
Symbol search path is: srv*Symbol information
Executable search path is:
Windows 10 Kernel Version 19041 MP (24 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff801`50000000 PsLoadedModuleList = 0xfffff801`50c2a2b0
Debug session time: Tue Jan 5 09:40:57.268 2021 (UTC - 5:00)
System Uptime: 0 days 17:12:28.918
Loading Kernel Symbols
...............................................................
...............Page 7f4b61 not present in the dump file. Type ".hh dbgerr004" for details
.......Page 16dbfc not present in the dump file. Type ".hh dbgerr004" for details
..........................................
................................................................
..................................
Loading User Symbols

Loading unloaded module list
.....................
For analysis of this file, run
!analyze -v
nt!KeBugCheckEx:
fffff801`503f5780 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff30a`136d1420=000000000000000a
13: 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: 000000903cb21bab, memory referenced
Arg2: 00000000000000ff, 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: fffff80150270d7d, address which referenced memory

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2437

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on VOYAGER2

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 2433

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

Key : Analysis.System
Value: CreateObject

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


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE: a

BUGCHECK_P1: 903cb21bab

BUGCHECK_P2: ff

BUGCHECK_P3: 0

BUGCHECK_P4: fffff80150270d7d

READ_ADDRESS: 000000903cb21bab

BLACKBOXBSD: 1 (
!blackboxbsd)


BLACKBOXNTFS: 1 (
!blackboxntfs)


BLACKBOXPNP: 1 (
!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: System

TRAP_FRAME: fffff30a136d1560 --
(.trap 0xfffff30a136d1560)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000004 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80150270d7d rsp=fffff30a136d16f0 rbp=0000000000000000
r8=0000000000000001 r9=0000000000000005 r10=ffffda89abb8d010
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up di pl zr na po nc
nt!PpmIdleExecuteTransition+0xaad:
fffff801`50270d7d 897e14 mov dword ptr [rsi+14h],edi ds:00000000`00000014=????????
Resetting default scope

STACK_TEXT:
fffff30a`136d1418 fffff801`50407769 : 00000000`0000000a 00000090`3cb21bab 00000000`000000ff 00000000`00000000 : nt!KeBugCheckEx
fffff30a`136d1420 fffff801`50403a69 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`000b88b6 : nt!KiBugCheckDispatch+0x69
fffff30a`136d1560 fffff801`50270d7d : 00000000`00000000 00000000`00000000 00000090`3cb21b97 00000000`00000000 : nt!KiPageFault+0x469
fffff30a`136d16f0 fffff801`50270154 : 00000000`00000000 00000000`00000000 00000000`06320000 00000000`00000004 : nt!PpmIdleExecuteTransition+0xaad
fffff30a`136d1af0 fffff801`503f92a4 : ffffffff`00000000 ffffa201`ad0cb640 ffffda89`bad3a080 00000000`000019c8 : nt!PoIdle+0x374
fffff30a`136d1c60 00000000`00000000 : fffff30a`136d2000 fffff30a`136cc000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x54


SYMBOL_NAME: nt!PpmIdleExecuteTransition+aad

MODULE_NAME:
nt

IMAGE_NAME: ntkrnlmp.exe

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: aad

FAILURE_BUCKET_ID: AV_nt!PpmIdleExecuteTransition

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {0ced0187-972d-f83e-de87-663d75806c32}

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


Continue reading...
 
Back
Top Bottom