T
TTM99
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: 0000000000230200, 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: fffff80631d19396, address which referenced memory
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2952
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-821N2DU
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 7667
Key : Analysis.Memory.CommitPeak.Mb
Value: 78
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: 230200
BUGCHECK_P2: 2
BUGCHECK_P3: 0
BUGCHECK_P4: fffff80631d19396
READ_ADDRESS: 0000000000230200
PROCESS_NAME: System
TRAP_FRAME: fffff8063700d300 -- (.trap 0xfffff8063700d300)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000230000 rbx=0000000000000000 rcx=ffff9b890f377000
rdx=fffff8062e0a3180 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80631d19396 rsp=fffff8063700d490 rbp=fffff8063700d559
r8=fffff8063700d4f8 r9=ffff9b890f377080 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!KiGetHeteroThreadQos+0x4e:
fffff806`31d19396 8b8000020000 mov eax,dword ptr [rax+200h] ds:00000000`00230200=????????
Resetting default scope
STACK_TEXT:
fffff806`3700d1b8 fffff806`31c07769 : 00000000`0000000a 00000000`00230200 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff806`3700d1c0 fffff806`31c03a69 : 00000000`0000000f 00000001`0000000f fffff806`2e0a3180 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff806`3700d300 fffff806`31d19396 : 00000000`00c70000 fffff806`00550000 ffff9b88`ff420040 00000000`00e30000 : nt!KiPageFault+0x469
fffff806`3700d490 fffff806`31d191de : ffff9b89`0f377080 fffff806`3700d559 00000000`0000000c ffff9b88`ffebdc60 : nt!KiGetHeteroThreadQos+0x4e
fffff806`3700d4c0 fffff806`31d19572 : ffff9b88`ff5ddc20 fffff806`00000000 fffff806`2e0a3180 fffff806`31a363cb : nt!KiConvertDynamicHeteroPolicy+0x1e
fffff806`3700d4f0 fffff806`31c2c6fc : fffff806`2e0a3180 ffff9b89`051a80f0 fffff806`00000005 fffff806`3700d5fc : nt!KiHeteroChooseTargetProcessor+0x52
fffff806`3700d5c0 fffff806`31a44c4d : 00000000`000409be fffff806`3700da10 00000000`00000080 fffff806`2e0a3180 : nt!KiDeferredReadySingleThread+0x1e1bac
fffff806`3700d7b0 fffff806`31a45030 : fffff806`2e0a3180 00000000`00000000 ffff9b89`0f3771f0 00000000`00000000 : nt!KiReadyThread+0x4d
fffff806`3700d7e0 fffff806`31a072e9 : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`000409be : nt!KiProcessExpiredTimerList+0x290
fffff806`3700d8d0 fffff806`31bf92ee : 00000000`00000000 fffff806`2e0a3180 fffff806`32526600 ffff9b88`ff770040 : nt!KiRetireDpcList+0x9d9
fffff806`3700db60 00000000`00000000 : fffff806`3700e000 fffff806`37007000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e
SYMBOL_NAME: nt!KiGetHeteroThreadQos+4e
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 4e
FAILURE_BUCKET_ID: AV_nt!KiGetHeteroThreadQos
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {049b59b0-d37c-55ed-7782-1410db5f2ba6}
Followup: MachineOwner
---------
Continue reading...
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: 0000000000230200, 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: fffff80631d19396, address which referenced memory
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2952
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-821N2DU
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 7667
Key : Analysis.Memory.CommitPeak.Mb
Value: 78
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: 230200
BUGCHECK_P2: 2
BUGCHECK_P3: 0
BUGCHECK_P4: fffff80631d19396
READ_ADDRESS: 0000000000230200
PROCESS_NAME: System
TRAP_FRAME: fffff8063700d300 -- (.trap 0xfffff8063700d300)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000230000 rbx=0000000000000000 rcx=ffff9b890f377000
rdx=fffff8062e0a3180 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80631d19396 rsp=fffff8063700d490 rbp=fffff8063700d559
r8=fffff8063700d4f8 r9=ffff9b890f377080 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!KiGetHeteroThreadQos+0x4e:
fffff806`31d19396 8b8000020000 mov eax,dword ptr [rax+200h] ds:00000000`00230200=????????
Resetting default scope
STACK_TEXT:
fffff806`3700d1b8 fffff806`31c07769 : 00000000`0000000a 00000000`00230200 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff806`3700d1c0 fffff806`31c03a69 : 00000000`0000000f 00000001`0000000f fffff806`2e0a3180 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff806`3700d300 fffff806`31d19396 : 00000000`00c70000 fffff806`00550000 ffff9b88`ff420040 00000000`00e30000 : nt!KiPageFault+0x469
fffff806`3700d490 fffff806`31d191de : ffff9b89`0f377080 fffff806`3700d559 00000000`0000000c ffff9b88`ffebdc60 : nt!KiGetHeteroThreadQos+0x4e
fffff806`3700d4c0 fffff806`31d19572 : ffff9b88`ff5ddc20 fffff806`00000000 fffff806`2e0a3180 fffff806`31a363cb : nt!KiConvertDynamicHeteroPolicy+0x1e
fffff806`3700d4f0 fffff806`31c2c6fc : fffff806`2e0a3180 ffff9b89`051a80f0 fffff806`00000005 fffff806`3700d5fc : nt!KiHeteroChooseTargetProcessor+0x52
fffff806`3700d5c0 fffff806`31a44c4d : 00000000`000409be fffff806`3700da10 00000000`00000080 fffff806`2e0a3180 : nt!KiDeferredReadySingleThread+0x1e1bac
fffff806`3700d7b0 fffff806`31a45030 : fffff806`2e0a3180 00000000`00000000 ffff9b89`0f3771f0 00000000`00000000 : nt!KiReadyThread+0x4d
fffff806`3700d7e0 fffff806`31a072e9 : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`000409be : nt!KiProcessExpiredTimerList+0x290
fffff806`3700d8d0 fffff806`31bf92ee : 00000000`00000000 fffff806`2e0a3180 fffff806`32526600 ffff9b88`ff770040 : nt!KiRetireDpcList+0x9d9
fffff806`3700db60 00000000`00000000 : fffff806`3700e000 fffff806`37007000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e
SYMBOL_NAME: nt!KiGetHeteroThreadQos+4e
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 4e
FAILURE_BUCKET_ID: AV_nt!KiGetHeteroThreadQos
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {049b59b0-d37c-55ed-7782-1410db5f2ba6}
Followup: MachineOwner
---------
Continue reading...