Windows 10: IRQL_NOT_LESS_OR_EQUAL atleast once a day

This is my crash log, I have tried everything.


Microsoft R Windows Debugger Version 10.0.18362.1 X86
Copyright c Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\032220-62531-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP 12 procs Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff807`30c00000 PsLoadedModuleList = 0xfffff807`31048150
Debug session time: Sun Mar 22 11:14:25.264 2020 UTC + 0:00
System Uptime: 1 days 7:59:39.759
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...........................................
Loading User Symbols
Loading unloaded module list
...................................
For analysis of this file, run !analyze -v
8: 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: 00000000000000a2, 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: fffff80730cf6c7a, 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

SYSTEM_MANUFACTURER: System manufacturer

SYSTEM_PRODUCT_NAME: System Product Name

SYSTEM_SKU: SKU

SYSTEM_VERSION: System Version

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 5407

BIOS_DATE: 12/31/2019

BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT: PRIME B350-PLUS

BASEBOARD_VERSION: Rev X.0x

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

DUMP_TYPE: 2

BUGCHECK_P1: a2

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff80730cf6c7a

READ_ADDRESS: fffff807311733b8: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
00000000000000a2

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiCaptureDirtyBitToPfn+6
fffff807`30cf6c7a 448a4922 mov r9b,byte ptr [rcx+22h]

CPU_COUNT: c

CPU_MHZ: f3c

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 1

CPU_STEPPING: 1

BLACKBOXBSD: 1 !blackboxbsd


BLACKBOXNTFS: 1 !blackboxntfs


BLACKBOXPNP: 1 !blackboxpnp


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: System

ANALYSIS_SESSION_HOST: ZAKS-GAMING-PC

ANALYSIS_SESSION_TIME: 03-22-2020 11:33:40.0813

ANALYSIS_VERSION: 10.0.18362.1 x86fre

TRAP_FRAME: ffffda0c11f8bd50 -- .trap 0xffffda0c11f8bd50
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000080
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80730cf6c7a rsp=ffffda0c11f8bee8 rbp=ffffda0c11f8bfc0
r8=0000000000000000 r9=0000000000000000 r10=ffffb5817b700000
r11=ffffda0c11f8bea0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!MiCaptureDirtyBitToPfn+0x6:
fffff807`30cf6c7a 448a4922 mov r9b,byte ptr [rcx+22h] ds:00000000`000000a2=??
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80730dd41e9 to fffff80730dc2380

STACK_TEXT:
ffffda0c`11f8bc08 fffff807`30dd41e9 : 00000000`0000000a 00000000`000000a2 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffda0c`11f8bc10 fffff807`30dd052b : 00000000`00000001 00000000`00000040 00000000`00000040 ffffdc0a`49010000 : nt!KiBugCheckDispatch+0x69
ffffda0c`11f8bd50 fffff807`30cf6c7a : 00000000`00000030 0000003a`00000000 ffffda0c`11f8bfe0 ffffdc0a`6f561c20 : nt!KiPageFault+0x46b
ffffda0c`11f8bee8 fffff807`30e55152 : fffff807`30c5dc82 00000000`00000000 ffffda0c`11f8bfc0 00000000`00000030 : nt!MiCaptureDirtyBitToPfn+0x6
ffffda0c`11f8bf18 00000000`00000000 : ffffdc0a`6abc52f0 00007000`00007000 ffffdc0a`6abc52f0 ffff8a08`7947d3d0 : nt!MiWalkEntireImage+0x167072


THREAD_SHA1_HASH_MOD_FUNC: be76a44c770b3537a83aa6ec46ff7fda8367f3f5

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 9f27fe068673a3218725415357529b0c9ae088ab

THREAD_SHA1_HASH_MOD: f08ac56120cad14894587db086f77ce277bfae84

FOLLOWUP_IP:
nt!MiCaptureDirtyBitToPfn+6
fffff807`30cf6c7a 448a4922 mov r9b,byte ptr [rcx+22h]

FAULT_INSTR_CODE: 22498a44

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!MiCaptureDirtyBitToPfn+6

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: 6

FAILURE_BUCKET_ID: AV_nt!MiCaptureDirtyBitToPfn

BUCKET_ID: AV_nt!MiCaptureDirtyBitToPfn

PRIMARY_PROBLEM_CLASS: AV_nt!MiCaptureDirtyBitToPfn

TARGET_TIME: 2020-03-22T11:14:25.000Z

OSBUILD: 18362

OSSERVICEPACK: 720

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 784

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal

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: 27e3

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:av_nt!micapturedirtybittopfn

FAILURE_ID_HASH: {0ccb9dc3-365c-6fcc-7458-3ef0487fd899}

Followup: MachineOwner
---------

8: kd> .trap 0xffffda0c11f8bd50
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000080
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80730cf6c7a rsp=ffffda0c11f8bee8 rbp=ffffda0c11f8bfc0
r8=0000000000000000 r9=0000000000000000 r10=ffffb5817b700000
r11=ffffda0c11f8bea0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!MiCaptureDirtyBitToPfn+0x6:
fffff807`30cf6c7a 448a4922 mov r9b,byte ptr [rcx+22h] ds:00000000`000000a2=??

:)

 

Irql_not_less_or_equal

So I have this clients PC that blue screens and gives a IRQL_NOT_LESS_OR_EQUAL STOP 0x0000000A error message. Error Goblin (link in sig) says the following:

And I have NO IDEA what the hell that means. It has wrapped around my head 5 times and caused it to explode. Ive ran memtest for 7 and a half hours and it didnt find any errors. I will probably run it again overnight just to be safe. Ive also cleaned out the computer with an air compressor and checked the hard drive for bad sectors are none are to be found.

Im trying like hell to avoid reinstalling Windows but it seems unlikely.

Im going to try updating some drivers and see what happens. Some of the drivers on this computer date back to 2007.

Suggestions are greatly appreciated.

Thanks guys.

EDIT:

Alright so it doesnt look like ill be able to get onto the internet to do anything because nearly every time i try, i get the BSOD. Format seems imminent.

 

IRQL_NOT_LESS_OR_EQUAL

Hi,

I appreciate if you could answer few questions to narrow down to the issue.

• What is the make and model of the computer?
• Did you make any recent changes to computer settings or hardware?
• Did you install any third party security application?

The error code 'irql_not_less_or_equal’ indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

I suggest you try the below steps and check if it helps.

Step 1: Download and install the latest firmware driver form the manufacturer’s website.

Step 2: Update all the system drivers.

Refer to the following article and update all the drivers available.

How to: Install and Update drivers in Windows 10

For more information, refer to the below link:

How to: Install and Update Hardware Drivers in Windows 10

Also refer:

http://windows.microsoft.com/en-us/windows-10/troubleshoot-blue-screen-errors

Please follow the steps provided and check if the issue gets resolved.
Please do let us know if you need further assistance. We will be glad to assist you.

Thank you.

 

Windows 10 64bit, IRQL_Not_Less_Or_Equal error

Hi Connor,

Thank you for posting in Microsoft Community and being part of Windows 10.

I would like to inform that IRQL_Not_Less_Or_Equal error indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

Do let us know the following to assist you better with this issue:

• What is the make and model of your device?
• Have you made any changes to your system prior to this issue?
• Are you able to boot the device to desktop?
• Does this issue persists only while playing games?

This Stop error message usually occurs during installation when there was an attempt in kernel mode to touch pageable memory at too high a process internal request level (IRQL). Typically,
this error occurs when a driver uses an incorrect memory address. Other possible causes of this error include an incompatible device driver, a general hardware problem, or incompatible software.

If you are able to boot the device to desktop, try the below troubleshooting steps

Step 1: As an initial step,
, I suggest you to download and install any pending updates on the computer through Windows update and check if it helps to resolve the issue.

Steps:

• Connect to the internet.
• Press Windows key and type updates.
• Click on Check for updates.
• Under Windows Updates, click on Check for updates.
• Try to install the updates being shown.

Step 2: I suggest you to refer to the Microsoft article, try the troubleshooting steps mentioned and check if it helps.

Troubleshoot blue screen errors

Hope it helps. Get back to us with an updated status of this issue and required information for further assistance.