P
pirssn
I am having troubles with several different BSOD on Windows 10.
I have ran the latest one on the debugger and got IRQL_NOT_LESS_OR_EQUAL. Bugcheck Analysis below.
Minidump file on the link below:
Can anyone assist me?
*******************************************************************************
* *
* 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: 0000000000000000, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 0000000000000014, 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: fffff803542424ef, address which referenced memory
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2687
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-G0HJO63
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 2716
Key : Analysis.Memory.CommitPeak.Mb
Value: 74
Key : Analysis.System
Value: CreateObject
Key : WER.OS.Branch
Value: 19h1_release
Key : WER.OS.Timestamp
Value: 2019-03-18T12:02:00Z
Key : WER.OS.Version
Value: 10.0.18362.1
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: a
BUGCHECK_P1: 0
BUGCHECK_P2: ff
BUGCHECK_P3: 14
BUGCHECK_P4: fffff803542424ef
READ_ADDRESS: 0000000000000000
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
PROCESS_NAME: System
TRAP_FRAME: fffff88780a45770 -- (.trap 0xfffff88780a45770)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000037826ca063 rbx=0000000000000000 rcx=0000000000000001
rdx=0000000000000bd0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff803542424ef rsp=fffff88780a45900 rbp=fffff88780a45a00
r8=8000000000000000 r9=fffff88780a45b60 r10=0000003782aa6b5e
r11=ffffac79d7c00000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up di pl zr na po nc
nt!PpmIdlePrepare+0x15f:
fffff803`542424ef 488903 mov qword ptr [rbx],rax ds:00000000`00000000=????????????????
Resetting default scope
STACK_TEXT:
fffff887`80a45628 fffff803`543d5929 : 00000000`0000000a 00000000`00000000 00000000`000000ff 00000000`00000014 : nt!KeBugCheckEx
fffff887`80a45630 fffff803`543d1c69 : 00000000`00174848 fffff803`544efa1b 00000000`00000200 fffff803`54cb68f8 : nt!KiBugCheckDispatch+0x69
fffff887`80a45770 fffff803`542424ef : 00000000`028a6932 00000000`00989680 ffffd18f`c7989010 00000037`82aa5f8d : nt!KiPageFault+0x469
fffff887`80a45900 fffff803`542408a6 : 00000000`00000003 00000000`00000002 00000000`00000000 00000000`00000008 : nt!PpmIdlePrepare+0x15f
fffff887`80a45b00 fffff803`543c7584 : ffffffff`00000000 ffffbc81`53140180 ffffd18f`dfbab580 00000000`00000ca8 : nt!PoIdle+0x1e6
fffff887`80a45c60 00000000`00000000 : fffff887`80a46000 fffff887`80a40000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x44
SYMBOL_NAME: nt!PpmIdlePrepare+15f
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 15f
FAILURE_BUCKET_ID: AV_nt!PpmIdlePrepare
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {dd7d0096-4602-c4e5-a984-978d6ab3aa71}
Followup: MachineOwner
Continue reading...
I have ran the latest one on the debugger and got IRQL_NOT_LESS_OR_EQUAL. Bugcheck Analysis below.
Minidump file on the link below:
Can anyone assist me?
*******************************************************************************
* *
* 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: 0000000000000000, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 0000000000000014, 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: fffff803542424ef, address which referenced memory
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2687
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-G0HJO63
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 2716
Key : Analysis.Memory.CommitPeak.Mb
Value: 74
Key : Analysis.System
Value: CreateObject
Key : WER.OS.Branch
Value: 19h1_release
Key : WER.OS.Timestamp
Value: 2019-03-18T12:02:00Z
Key : WER.OS.Version
Value: 10.0.18362.1
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: a
BUGCHECK_P1: 0
BUGCHECK_P2: ff
BUGCHECK_P3: 14
BUGCHECK_P4: fffff803542424ef
READ_ADDRESS: 0000000000000000
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
PROCESS_NAME: System
TRAP_FRAME: fffff88780a45770 -- (.trap 0xfffff88780a45770)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000037826ca063 rbx=0000000000000000 rcx=0000000000000001
rdx=0000000000000bd0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff803542424ef rsp=fffff88780a45900 rbp=fffff88780a45a00
r8=8000000000000000 r9=fffff88780a45b60 r10=0000003782aa6b5e
r11=ffffac79d7c00000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up di pl zr na po nc
nt!PpmIdlePrepare+0x15f:
fffff803`542424ef 488903 mov qword ptr [rbx],rax ds:00000000`00000000=????????????????
Resetting default scope
STACK_TEXT:
fffff887`80a45628 fffff803`543d5929 : 00000000`0000000a 00000000`00000000 00000000`000000ff 00000000`00000014 : nt!KeBugCheckEx
fffff887`80a45630 fffff803`543d1c69 : 00000000`00174848 fffff803`544efa1b 00000000`00000200 fffff803`54cb68f8 : nt!KiBugCheckDispatch+0x69
fffff887`80a45770 fffff803`542424ef : 00000000`028a6932 00000000`00989680 ffffd18f`c7989010 00000037`82aa5f8d : nt!KiPageFault+0x469
fffff887`80a45900 fffff803`542408a6 : 00000000`00000003 00000000`00000002 00000000`00000000 00000000`00000008 : nt!PpmIdlePrepare+0x15f
fffff887`80a45b00 fffff803`543c7584 : ffffffff`00000000 ffffbc81`53140180 ffffd18f`dfbab580 00000000`00000ca8 : nt!PoIdle+0x1e6
fffff887`80a45c60 00000000`00000000 : fffff887`80a46000 fffff887`80a40000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x44
SYMBOL_NAME: nt!PpmIdlePrepare+15f
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 15f
FAILURE_BUCKET_ID: AV_nt!PpmIdlePrepare
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {dd7d0096-4602-c4e5-a984-978d6ab3aa71}
Followup: MachineOwner
Continue reading...