Need help. Computer sometimes loops BSOD IRQL_NOT_LESS_OR_EQUAL

1

1shike

How do I fix this error?


I ran memtestx86 and windows memory diagnostic for a total of 0 errors.

Below are the analyzed dump files:

Microsoft (R) Windows Debugger Version 10.0.19041.685 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.





Loading Dump File [C:\Users\shike\Desktop\MEMORY.DMP]

Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.



Symbol search path is: srv*

Executable search path is:

Windows 10 Kernel Version 19041 MP (12 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 19041.1.amd64fre.vb_release.191206-1406

Machine Name:

Kernel base = 0xfffff801`77400000 PsLoadedModuleList = 0xfffff801`7802a490

Debug session time: Sun Mar 14 11:20:57.009 2021 (UTC - 7:00)

System Uptime: 0 days 0:00:08.587

Loading Kernel Symbols

...............................................................

................................................................

.....................

Loading User Symbols



Loading unloaded module list

........

For analysis of this file, run !analyze -v

6: 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: ffffb60e5087e010, memory referenced

Arg2: 00000000000000ff, IRQL

Arg3: 0000000000000093, 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: fffff80177808bd3, address which referenced memory



Debugging Details:

------------------





KEY_VALUES_STRING: 1



Key : Analysis.CPU.Sec

Value: 3



Key : Analysis.DebugAnalysisProvider.CPP

Value: Create: 8007007e on DESKTOP-8K8F5DS



Key : Analysis.DebugData

Value: CreateObject



Key : Analysis.DebugModel

Value: CreateObject



Key : Analysis.Elapsed.Sec

Value: 3



Key : Analysis.Memory.CommitPeak.Mb

Value: 68



Key : Analysis.System

Value: CreateObject





BUGCHECK_CODE: a



BUGCHECK_P1: ffffb60e5087e010



BUGCHECK_P2: ff



BUGCHECK_P3: 93



BUGCHECK_P4: fffff80177808bd3



WRITE_ADDRESS: ffffb60e5087e010 Paged pool



PROCESS_NAME: System



TRAP_FRAME: ffff9d81cd92fc50 -- (.trap 0xffff9d81cd92fc50)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=ffffb60e5087e010 rbx=0000000000000000 rcx=ffffb60e5087e020

rdx=fffffffffffde4d0 rsi=0000000000000000 rdi=0000000000000000

rip=fffff80177808bd3 rsp=ffff9d81cd92fde8 rbp=ffff9d81cd930279

r8=000000000000001c r9=0000000000000001 r10=ffffb60e5085c4e0

r11=ffffb60e5085c54c r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up di pl nz na pe nc

nt!memcpy+0x113:

fffff801`77808bd3 0f2941f0 movaps xmmword ptr [rcx-10h],xmm0 ds:ffffb60e`5087e010=????????????????????????????????

Resetting default scope



LOCK_ADDRESS: fffff80178044c00 -- (!locks fffff80178044c00)



Resource @ nt!PiEngineLock (0xfffff80178044c00) Exclusively owned

Contention Count = 7

Threads: ffff870b5cf46080-01<*>

1 total locks



PNP_TRIAGE_DATA:

Lock address : 0xfffff80178044c00

Thread Count : 1

Thread address: 0xffff870b5cf46080

Thread wait : 0x225



STACK_TEXT:

ffff9d81`cd92fb08 fffff801`77807b69 : 00000000`0000000a ffffb60e`5087e010 00000000`000000ff 00000000`00000093 : nt!KeBugCheckEx

ffff9d81`cd92fb10 fffff801`77803e69 : 00000000`0000007c fffff801`77db1094 00000000`00000003 00000000`00000000 : nt!KiBugCheckDispatch+0x69

ffff9d81`cd92fc50 fffff801`77808bd3 : fffff801`7765c08b ffffb60e`5082fd70 ffffb60e`5085c4d0 00000000`00000005 : nt!KiPageFault+0x469

ffff9d81`cd92fde8 fffff801`7765c08b : ffffb60e`5082fd70 ffffb60e`5085c4d0 00000000`00000005 00000000`00001000 : nt!memcpy+0x113

ffff9d81`cd92fdf0 fffff801`77a1b053 : 00000000`00000001 ffffb60e`50800fc0 ffff9d81`cd92ffe0 00000000`00000000 : nt!CmpDoQueryKeyName+0x23b

ffff9d81`cd92ff30 fffff801`779d9ae3 : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000001 : nt!CmpQueryKeyName+0x13

ffff9d81`cd92ff80 fffff801`779d96da : ffffb60e`5082fd70 ffffb60e`5087e000 00000000`00001000 ffff9d81`cd9300f4 : nt!ObQueryNameStringMode+0xd3

ffff9d81`cd9300a0 fffff801`77b267ea : ffffffff`80001874 ffffffff`80001874 ffffb60e`00000000 ffffffff`00001000 : nt!NtQueryObject+0x18a

ffff9d81`cd9301f0 fffff801`77b25af9 : fffff801`804e0000 ffff870b`5cf46080 ffffffff`00000000 00000000`00000000 : nt!IopQueryRegistryKeySystemPath+0xda

ffff9d81`cd9302e0 fffff801`77b232c0 : fffff801`804e0000 fffff801`804e0000 00000000`00000000 00000000`00000000 : nt!IopBuildFullDriverPath+0xc1

ffff9d81`cd9303a0 fffff801`77b23228 : fffff801`804e0000 00000000`00000000 ffffffff`80001874 ffffb60e`49d83cb0 : nt!PpCheckInDriverDatabase+0x40

ffff9d81`cd930400 fffff801`77b26215 : ffff9d81`cd930580 fffff801`804e00d8 fffff801`78045a80 00000000`00000000 : nt!PnpPrepareDriverLoading+0x6c

ffff9d81`cd930480 fffff801`77b27e06 : 00000000`00000000 00000000`00000000 00000000`00000004 ffff9d81`00000004 : nt!IopLoadDriver+0x27d

ffff9d81`cd930650 fffff801`77b27b16 : fffff801`7740af01 00000000`00000000 ffff870b`611a6410 ffffffff`80001840 : nt!PipCallDriverAddDeviceQueryRoutine+0x1be

ffff9d81`cd9306e0 fffff801`77b274d4 : 00000000`00000000 ffff9d81`cd9307f0 00000000`6e657050 fffff801`0000000e : nt!PnpCallDriverQueryServiceHelper+0xda

ffff9d81`cd930790 fffff801`77b26c67 : ffff870b`67e75670 ffff9d81`cd9309d1 ffff870b`67e75670 00000000`00000000 : nt!PipCallDriverAddDevice+0x41c

ffff9d81`cd930950 fffff801`77b1fd96 : ffff870b`67e75600 ffff870b`68309301 ffff9d81`cd930a70 fffff801`00000000 : nt!PipProcessDevNodeTree+0x333

ffff9d81`cd930a20 fffff801`7776c31a : 00000001`00000003 ffff870b`67e75670 00000000`00000000 ffff870b`683093a0 : nt!PiRestartDevice+0xba

ffff9d81`cd930a70 fffff801`77625975 : ffff870b`5cf46080 ffff870b`5a713a60 fffff801`780435a0 ffff870b`00000000 : nt!PnpDeviceActionWorker+0x46a

ffff9d81`cd930b30 fffff801`77717e85 : ffff870b`5cf46080 00000000`00000080 ffff870b`5a684040 000fe067`b4bbbdff : nt!ExpWorkerThread+0x105

ffff9d81`cd930bd0 fffff801`777fd2a8 : fffff801`769d4180 ffff870b`5cf46080 fffff801`77717e30 00000000`00000000 : nt!PspSystemThreadStartup+0x55

ffff9d81`cd930c20 00000000`00000000 : ffff9d81`cd931000 ffff9d81`cd92a000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28





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_nt!KiPageFault



OS_VERSION: 10.0.19041.1



BUILDLAB_STR: vb_release



OSPLATFORM_TYPE: x64



OSNAME: Windows 10



FAILURE_ID_HASH: {22c06795-f62b-154a-eb13-05cdd373e37e}



Followup: MachineOwner

Continue reading...
 
Back
Top Bottom