F
Francis WilliamArcher
My friend built me a computer about October last year. He's built a few computers now so I trust that he's done everything correctly. Everything seems to run smoothly. However, usually once or twice a week I experience a blue screen of death, each time a different stop code. This most recent one was DRIVER_IRQL_NOT_LESS_OR_EQUAL. I've run system file checker and everything was allgood. I've also tried running windows memory diagnostic and also checked my ram with the windows tool and it said both my ram and hard drive was fine. I've performed a reset of my computer but still experience bsods. I regularly check windows update and it says there are no updates and when I check device manager all devices that I've checked show that the device is running properly and the most current driver updates are installed already. Does anyone know what could be the problem? Running Windows 10 home 64-bit, Intel Core i5 10600K, 16gb dual channel unknown Ram, MPG Z490M gaming edge wifi motherboard, Nvidida Geforce RTX 2060 Super, 2TB Western Digital WDC SataSSd, and 500GB Western Digital Unknown SSD.
Dump File:
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff805a5fd1379, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: fffff805a5fd1379, address which referenced memory
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 1
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-PCJOJAV
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 10
Key : Analysis.Memory.CommitPeak.Mb
Value: 71
Key : Analysis.System
Value: CreateObject
BUGCHECK_CODE: d1
BUGCHECK_P1: fffff805a5fd1379
BUGCHECK_P2: 2
BUGCHECK_P3: 8
BUGCHECK_P4: fffff805a5fd1379
READ_ADDRESS: fffff805a5fd1379
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
PROCESS_NAME: esrv_svc.exe
TRAP_FRAME: ffff870b3ed8f440 -- (.trap 0xffff870b3ed8f440)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000003 rbx=0000000000000000 rcx=ffffe684b8d02130
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff805a5fd1379 rsp=ffff870b3ed8f5d0 rbp=0000000000000000
r8=ffffe684b4b02280 r9=0000000000000000 r10=ffffe684ab2a2b80
r11=ffffe684b8d02130 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
fffff805`a5fd1379 ?? ???
Resetting default scope
FAILED_INSTRUCTION_ADDRESS:
+0
fffff805`a5fd1379 ?? ???
STACK_TEXT:
ffff870b`3ed8f2f8 fffff805`6f007a69 : 00000000`0000000a fffff805`a5fd1379 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
ffff870b`3ed8f300 fffff805`6f003d69 : 00000000`00000001 00000000`00000000 ffffe684`00000000 00000000`00000100 : nt!KiBugCheckDispatch+0x69
ffff870b`3ed8f440 fffff805`a5fd1379 : ffffe684`c416f440 00000000`00000002 ffffe684`bbdafb30 ffffe684`c265bc80 : nt!KiPageFault+0x469
ffff870b`3ed8f5d0 ffffe684`c416f440 : 00000000`00000002 ffffe684`bbdafb30 ffffe684`c265bc80 ffff870b`3d4ed838 : 0xfffff805`a5fd1379
ffff870b`3ed8f5d8 00000000`00000002 : ffffe684`bbdafb30 ffffe684`c265bc80 ffff870b`3d4ed838 ffffe684`c265bcb0 : 0xffffe684`c416f440
ffff870b`3ed8f5e0 ffffe684`bbdafb30 : ffffe684`c265bc80 ffff870b`3d4ed838 ffffe684`c265bcb0 00000000`00000000 : 0x2
ffff870b`3ed8f5e8 ffffe684`c265bc80 : ffff870b`3d4ed838 ffffe684`c265bcb0 00000000`00000000 ffff870b`3ed8f600 : 0xffffe684`bbdafb30
ffff870b`3ed8f5f0 ffff870b`3d4ed838 : ffffe684`c265bcb0 00000000`00000000 ffff870b`3ed8f600 ffffe684`c416f440 : 0xffffe684`c265bc80
ffff870b`3ed8f5f8 ffffe684`c265bcb0 : 00000000`00000000 ffff870b`3ed8f600 ffffe684`c416f440 ffffe684`c265bc80 : 0xffff870b`3d4ed838
ffff870b`3ed8f600 00000000`00000000 : ffff870b`3ed8f600 ffffe684`c416f440 ffffe684`c265bc80 ffffe684`baead790 : 0xffffe684`c265bcb0
SYMBOL_NAME: nt!KiPageFault+469
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 469
FAILURE_BUCKET_ID: AV_CODE_AV_BAD_IP_nt!KiPageFault
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {73cd60cc-83fa-6b76-df08-1961c31d7403}
Followup: MachineOwner
Thanks
Continue reading...
Dump File:
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff805a5fd1379, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: fffff805a5fd1379, address which referenced memory
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 1
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-PCJOJAV
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 10
Key : Analysis.Memory.CommitPeak.Mb
Value: 71
Key : Analysis.System
Value: CreateObject
BUGCHECK_CODE: d1
BUGCHECK_P1: fffff805a5fd1379
BUGCHECK_P2: 2
BUGCHECK_P3: 8
BUGCHECK_P4: fffff805a5fd1379
READ_ADDRESS: fffff805a5fd1379
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
PROCESS_NAME: esrv_svc.exe
TRAP_FRAME: ffff870b3ed8f440 -- (.trap 0xffff870b3ed8f440)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000003 rbx=0000000000000000 rcx=ffffe684b8d02130
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff805a5fd1379 rsp=ffff870b3ed8f5d0 rbp=0000000000000000
r8=ffffe684b4b02280 r9=0000000000000000 r10=ffffe684ab2a2b80
r11=ffffe684b8d02130 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
fffff805`a5fd1379 ?? ???
Resetting default scope
FAILED_INSTRUCTION_ADDRESS:
+0
fffff805`a5fd1379 ?? ???
STACK_TEXT:
ffff870b`3ed8f2f8 fffff805`6f007a69 : 00000000`0000000a fffff805`a5fd1379 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
ffff870b`3ed8f300 fffff805`6f003d69 : 00000000`00000001 00000000`00000000 ffffe684`00000000 00000000`00000100 : nt!KiBugCheckDispatch+0x69
ffff870b`3ed8f440 fffff805`a5fd1379 : ffffe684`c416f440 00000000`00000002 ffffe684`bbdafb30 ffffe684`c265bc80 : nt!KiPageFault+0x469
ffff870b`3ed8f5d0 ffffe684`c416f440 : 00000000`00000002 ffffe684`bbdafb30 ffffe684`c265bc80 ffff870b`3d4ed838 : 0xfffff805`a5fd1379
ffff870b`3ed8f5d8 00000000`00000002 : ffffe684`bbdafb30 ffffe684`c265bc80 ffff870b`3d4ed838 ffffe684`c265bcb0 : 0xffffe684`c416f440
ffff870b`3ed8f5e0 ffffe684`bbdafb30 : ffffe684`c265bc80 ffff870b`3d4ed838 ffffe684`c265bcb0 00000000`00000000 : 0x2
ffff870b`3ed8f5e8 ffffe684`c265bc80 : ffff870b`3d4ed838 ffffe684`c265bcb0 00000000`00000000 ffff870b`3ed8f600 : 0xffffe684`bbdafb30
ffff870b`3ed8f5f0 ffff870b`3d4ed838 : ffffe684`c265bcb0 00000000`00000000 ffff870b`3ed8f600 ffffe684`c416f440 : 0xffffe684`c265bc80
ffff870b`3ed8f5f8 ffffe684`c265bcb0 : 00000000`00000000 ffff870b`3ed8f600 ffffe684`c416f440 ffffe684`c265bc80 : 0xffff870b`3d4ed838
ffff870b`3ed8f600 00000000`00000000 : ffff870b`3ed8f600 ffffe684`c416f440 ffffe684`c265bc80 ffffe684`baead790 : 0xffffe684`c265bcb0
SYMBOL_NAME: nt!KiPageFault+469
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 469
FAILURE_BUCKET_ID: AV_CODE_AV_BAD_IP_nt!KiPageFault
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {73cd60cc-83fa-6b76-df08-1961c31d7403}
Followup: MachineOwner
Thanks
Continue reading...