Windows 10: IRQL_NOT_LESS_OR_EQUAL - Daily Blue Screens - Help with Minidump Interpretation

Hello,

I've been having trouble with blue screens for a while now and decided to try to fix the problem. I have installed WinDbg and analyzed a minidump, but don't know how to interpret it. Any help is much appreciated!!


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



Microsoft R Windows Debugger Version 10.0.18362.1 AMD64

Copyright c Microsoft Corporation. All rights reserved.





Loading Dump File [C:\Windows\Minidump\031620-4718-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available





************* Path validation summary **************

Response Time ms Location

Deferred srv*d:\symbols*https://msdl.microsoft.com/download/symbols

Symbol search path is: srv*d:\symbols*https://msdl.microsoft.com/download/symbols

Executable search path is:

Windows 10 Kernel Version 18362 MP 6 procs Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Machine Name:

Kernel base = 0xfffff804`63e00000 PsLoadedModuleList = 0xfffff804`64248150

Debug session time: Mon Mar 16 14:57:50.783 2020 UTC - 5:00

System Uptime: 0 days 0:55:53.531

Loading Kernel Symbols

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

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

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

Loading User Symbols

Loading unloaded module list

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

For analysis of this file, run !analyze -v

5: 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: 0000000000004000, 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: fffff80463ee459c, address which referenced memory



Debugging Details:

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





KEY_VALUES_STRING: 1





PROCESSES_ANALYSIS: 1



SERVICE_ANALYSIS: 1



STACKHASH_ANALYSIS: 1



TIMELINE_ANALYSIS: 1





DUMP_CLASS: 1



DUMP_QUALIFIER: 400



BUILD_VERSION_STRING: 10.0.18362.720 WinBuild.160101.0800



DUMP_FILE_ATTRIBUTES: 0x8

Kernel Generated Triage Dump



DUMP_TYPE: 2



BUGCHECK_P1: 4000



BUGCHECK_P2: 2



BUGCHECK_P3: 0



BUGCHECK_P4: fffff80463ee459c



READ_ADDRESS: fffff804643733b8: Unable to get MiVisibleState

Unable to get NonPagedPoolStart

Unable to get NonPagedPoolEnd

Unable to get PagedPoolStart

Unable to get PagedPoolEnd

0000000000004000



CURRENT_IRQL: 2



FAULTING_IP:

nt!MiWalkPageTablesRecursively+a6c

fffff804`63ee459c 498b11 mov rdx,qword ptr [r9]



CPU_COUNT: 6



CPU_MHZ: e10



CPU_VENDOR: GenuineIntel



CPU_FAMILY: 6



CPU_MODEL: 9e



CPU_STEPPING: a



CUSTOMER_CRASH_COUNT: 1



DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT



BUGCHECK_STR: AV



PROCESS_NAME: MDMAgent.exe



ANALYSIS_SESSION_HOST: CAC



ANALYSIS_SESSION_TIME: 03-16-2020 15:14:42.0803



ANALYSIS_VERSION: 10.0.18362.1 amd64fre



TRAP_FRAME: fffff683b3cd9e20 -- .trap 0xfffff683b3cd9e20

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=ffffe773b9dce000 rbx=0000000000000000 rcx=0000000000004000

rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000

rip=fffff80463ee459c rsp=fffff683b3cd9fb0 rbp=ffffb00266182580

r8=0000000000004000 r9=0000000000004000 r10=ffffe773b9dce000

r11=ffffe773b9dcefff r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei pl zr na po nc

nt!MiWalkPageTablesRecursively+0xa6c:

fffff804`63ee459c 498b11 mov rdx,qword ptr [r9] ds:00000000`00004000=????????????????

Resetting default scope



LAST_CONTROL_TRANSFER: from fffff80463fd41e9 to fffff80463fc2380



STACK_TEXT:

fffff683`b3cd9cd8 fffff804`63fd41e9 : 00000000`0000000a 00000000`00004000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx

fffff683`b3cd9ce0 fffff804`63fd052b : 00000000`00000000 fffff804`63ee4042 fffff683`b3cda310 fffff683`b3cda310 : nt!KiBugCheckDispatch+0x69

fffff683`b3cd9e20 fffff804`63ee459c : 00000000`00000000 fffff683`b3cda310 ffffb002`66182580 ffffe773`b9dce800 : nt!KiPageFault+0x46b

fffff683`b3cd9fb0 fffff804`63ee395c : fffff683`b3cda310 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiWalkPageTablesRecursively+0xa6c

fffff683`b3cda070 fffff804`63ee33e7 : fffff683`b3cda310 fffff683`00000002 00000000`00000001 00000000`00000000 : nt!MiWalkPageTables+0x36c

fffff683`b3cda170 fffff804`63ee2b22 : ffffb002`6687c0c0 00000000`00000000 ffff8700`85f****0`00000000 : nt!MiAgeWorkingSet+0x3a7

fffff683`b3cda690 fffff804`63ee243a : ffffb002`66182580 fffff683`b3cda950 00000000`00000000 00000000`00000000 : nt!MiTrimOrAgeWorkingSet+0x3b2

fffff683`b3cda780 fffff804`63ee0b50 : fffff804`00000003 00000000`00000000 fffff804`6426a3c0 ffffb002`5a8430f0 : nt!MiProcessWorkingSets+0x1fa

fffff683`b3cda930 fffff804`640ca5d6 : fffff804`64375ac0 00000000`00000001 00000000`ffffffff 00000000`00000001 : nt!MiWorkingSetManager+0xc8

fffff683`b3cda9f0 fffff804`63f8c8e5 : 00000000`ffffffff 00000000`00000000 fffff804`6426a3c0 00000000`0000010e : nt!MmWorkingSetManager+0x12

fffff683`b3cdaa20 fffff804`63e6bce5 : ffffb002`5a9df080 00000000`00000080 fffff804`63f8c790 00000000`00000000 : nt!KeBalanceSetManager+0x155

fffff683`b3cdab10 fffff804`63fc99ca : ffff8700`85fc7180 ffffb002`5a9df080 fffff804`63e6bc90 00000000`00000000 : nt!PspSystemThreadStartup+0x55

fffff683`b3cdab60 00000000`00000000 : fffff683`b3cdb000 fffff683`b3cd4000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a





THREAD_SHA1_HASH_MOD_FUNC: 26cd757e613f4c286963cde15e85fb6658057682



THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 0012032859914a3dda14f0a7b00a1c549ca2116d



THREAD_SHA1_HASH_MOD: fe34192f63d13620a8987d294372ee74d699cfee



FOLLOWUP_IP:

nt!MiWalkPageTablesRecursively+a6c

fffff804`63ee459c 498b11 mov rdx,qword ptr [r9]



FAULT_INSTR_CODE: 49118b49



SYMBOL_STACK_INDEX: 3



SYMBOL_NAME: nt!MiWalkPageTablesRecursively+a6c



FOLLOWUP_NAME: MachineOwner



MODULE_NAME: nt



DEBUG_FLR_IMAGE_TIMESTAMP: 0



IMAGE_VERSION: 10.0.18362.720



STACK_COMMAND: .thread ; .cxr ; kb



IMAGE_NAME: memory_corruption



BUCKET_ID_FUNC_OFFSET: a6c



FAILURE_BUCKET_ID: AV_nt!MiWalkPageTablesRecursively



BUCKET_ID: AV_nt!MiWalkPageTablesRecursively



PRIMARY_PROBLEM_CLASS: AV_nt!MiWalkPageTablesRecursively



TARGET_TIME: 2020-03-16T19:57:50.000Z



OSBUILD: 18362



OSSERVICEPACK: 720



SERVICEPACK_NUMBER: 0



OS_REVISION: 0



SUITE_MASK: 272



PRODUCT_TYPE: 1



OSPLATFORM_TYPE: x64



OSNAME: Windows 10



OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS



OS_LOCALE:



USER_LCID: 0



OSBUILD_TIMESTAMP: unknown_date



BUILDDATESTAMP_STR: 160101.0800



BUILDLAB_STR: WinBuild



BUILDOSVER_STR: 10.0.18362.720



ANALYSIS_SESSION_ELAPSED_TIME: 1bf3



ANALYSIS_SOURCE: KM



FAILURE_ID_HASH_STRING: km:av_nt!miwalkpagetablesrecursively



FAILURE_ID_HASH: {12fba877-ad3e-387f-8ff4-c53ceb2d754c}



Followup: MachineOwner

---------

:)

 

Blue Screen of Deaths on a Daily

Hi,

Blue screen errors can occur if a serious problem causes Windows to shut down or restart unexpectedly. This error can be caused by both hardware and software issues. To isolate your concern, we'd like to know if there were any changes made
prior to the issue.

In the meantime, we suggest that you follow the steps provided on this link for blue screen error basic
troubleshooting. Once you're on the page, select the option on when do you get the error and proceed with the steps listed.

Let us know how it goes after performing the suggested steps.

 

Blue Screen of Deaths on a Daily

I have tried all of the options there, Which is why i included in my post the lists of things that i performed to isolate the cause of bsod. Thanks

 

Frequent IRQL_NOT_LESS_OR_EQUAL Blue Screens

Hi! I have been suffering from these IRQL_NOT_LESS_OR_EQUAL blue screens since I built my PC. Can anyone check what software or hardware had caused these errors? These are the minidump files of my recent 3 blue screens: https://1drv.ms/u/s!Ao13cZP9awvojUng4tCOBSWNxDEK

Any help will be appreciated. Thank you!