Windows 10: IRQL_NOT_LESS_OR_EQUAL - appears to be related to ntkrnlmp.exe

Greetings,


I would be most grateful if someone would be able to help me determine the source of my system instability. First, some context:


I've had BSODs on a particular machine for some time now. I'm not sure exactly when/how they began, but they've been happening an awful lot lately when the system idles, or during use. I can't determine a specific trigger or event that causes them, but it's incredibly disruptive when they do happen, and I'd love to find a cure.


I've run Memtest86, Windows Memory Diagnostics, various HDD diagnostics, etc. and nothing I can find so far points to a hardware failure. I'm running the latest BIOS for my motherboard, although it's happened irrespective of BIOS version. I've tried upgrade-in-places, and clean installs of Windows 10, but all of it is so far to no avail. Most recently, I did a clean install once more, only to find the issue has persisted. I do have one dump file so far thatI've shared here. I suspect it's a driver, but I can't figure out what driver it could be on my own. Your assistance is greatly appreciated!


WhoCrashed offers the following information:


Crash Dump Analysis
Crash dumps are enabled on your computer.

Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Mon 3/23/2020 12:47:44 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\032320-9390-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x1C2380
Bugcheck code: 0xA 0xFFFF89018D47D990, 0xFF, 0xB, 0xFFFFF801326BBF2B
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Mon 3/23/2020 12:47:44 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe nt!setjmpex+0x81A9
Bugcheck code: 0xA 0xFFFF89018D47D990, 0xFF, 0xB, 0xFFFFF801326BBF2B
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


Here is the summary from WinDBG:


*******************************************************************************
* *
* 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: ffff89018d47d990, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 000000000000000b, 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: fffff801326bbf2b, 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: 401

BUILD_VERSION_STRING: 18362.1.amd64fre.19h1_release.190318-1202

SYSTEM_MANUFACTURER: Micro-Star International Co., Ltd.

SYSTEM_PRODUCT_NAME: MS-7C37

SYSTEM_SKU: To be filled by O.E.M.

SYSTEM_VERSION: 2.0

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: A.70

BIOS_DATE: 01/09/2020

BASEBOARD_MANUFACTURER: Micro-Star International Co., Ltd.

BASEBOARD_PRODUCT: MPG X570 GAMING PLUS MS-7C37

BASEBOARD_VERSION: 2.0

DUMP_TYPE: 1

BUGCHECK_P1: ffff89018d47d990

BUGCHECK_P2: ff

BUGCHECK_P3: b

BUGCHECK_P4: fffff801326bbf2b

WRITE_ADDRESS: ffff89018d47d990

CURRENT_IRQL: 0

FAULTING_IP:
nt!PpmIdlePrepare+31b
fffff801`326bbf2b 48897d80 mov qword ptr [rbp-80h],rdi

CPU_COUNT: 10

CPU_MHZ: e10

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 71

CPU_STEPPING: 0

BLACKBOXBSD: 1 !blackboxbsd


BLACKBOXNTFS: 1 !blackboxntfs


BLACKBOXPNP: 1 !blackboxpnp


BLACKBOXWINLOGON: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: System

ANALYSIS_SESSION_HOST: DESKTOP-CDI8JLP

ANALYSIS_SESSION_TIME: 03-23-2020 19:54:15.0849

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

TRAP_FRAME: ffff89018c47d780 -- .trap 0xffff89018c47d780
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000007
rdx=00000061a74f2c01 rsi=0000000000000000 rdi=0000000000000000
rip=fffff801326bbf2b rsp=ffff89018c47d910 rbp=ffff89018d47da10
r8=0000000000000000 r9=ffffce819a516180 r10=00000061a798718a
r11=ffffbe79d3c00000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up di pl nz ac po cy
nt!PpmIdlePrepare+0x31b:
fffff801`326bbf2b 48897d80 mov qword ptr [rbp-80h],rdi ss:0018:ffff8901`8d47d990=ffff8f8c9d7310c0
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff801327d41e9 to fffff801327c2380

STACK_TEXT:
ffff8901`8c47d638 fffff801`327d41e9 : 00000000`0000000a ffff8901`8d47d990 00000000`000000ff 00000000`0000000b : nt!KeBugCheckEx
ffff8901`8c47d640 fffff801`327d052b : 00000000`00000000 00000000`00000000 00000000`0028f578 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffff8901`8c47d780 fffff801`326bbf2b : 00000061`a74f5299 00000000`00989680 ffff8901`8c47da10 ffffce81`9a516180 : nt!KiPageFault+0x46b
ffff8901`8c47d910 fffff801`326bac66 : 00000000`00000003 00000000`00000002 ffff8f8c`97806100 00000000`00000008 : nt!PpmIdlePrepare+0x31b
ffff8901`8c47db00 fffff801`327c5e88 : ffffffff`00000000 ffffce81`9a516180 ffff8f8c`a71ee080 00000000`000006e4 : nt!PoIdle+0x1e6
ffff8901`8c47dc60 00000000`00000000 : ffff8901`8c47e000 ffff8901`8c478000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x48


THREAD_SHA1_HASH_MOD_FUNC: bac30f8031bbad40506eeaabc9b982d6623c8637

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 06372c5c8e03168aff9eb00044cd61dcaa3f5946

THREAD_SHA1_HASH_MOD: ee8fcf1fb60cb6e3e2f60ddbed2ec02b5748a693

FOLLOWUP_IP:
nt!PpmIdlePrepare+31b
fffff801`326bbf2b 48897d80 mov qword ptr [rbp-80h],rdi

FAULT_INSTR_CODE: 807d8948

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!PpmIdlePrepare+31b

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 31b

FAILURE_BUCKET_ID: AV_CODE_AV_nt!PpmIdlePrepare

BUCKET_ID: AV_CODE_AV_nt!PpmIdlePrepare

PRIMARY_PROBLEM_CLASS: AV_CODE_AV_nt!PpmIdlePrepare

TARGET_TIME: 2020-03-23T18:47:44.000Z

OSBUILD: 18362

OSSERVICEPACK: 0

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: 190318-1202

BUILDLAB_STR: 19h1_release

BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME: 2501

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:av_code_av_nt!ppmidleprepare

FAILURE_ID_HASH: {0722116b-c23b-c6c2-0c96-05693152d11a}

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

:)

 

IRQL_NOT_LESS_OR_EQUAL BSOD errors, even after clean install

Hi, Bidley

My name is Maritza and I am an Independent Advisor. I would be happy to help you today.

The problem is caused by (ntkrnlmp.exe)

Check this link, I hope it helps

https://www.thewindowsclub.com/fix-ntkrnlmp-exe...

Note: This is a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised
on the site before you decide to download and install it.

Let us know if these steps help you to resolve the issue.

 

Bsod:- irql_not_less_or_equal


clfs.sys is a windows driver as described, this should have been solved with SFC if it indeed was the cause.
Windows drivers are rarely the real cause, but a lot blamed because they are the last active.
If it appears that a windows driver is causing problems and clean install, sfc and dism cannot solve it then the only other solution is windows update if the hardware is not defective.

Seeing the crashes are only IRQL_NOT_LESS_OR_EQUAL, the usual causes are

• Kernel mode driver,
• System Service,
• BIOS,
• Windows,
• Virus scanner,
• Backup tool,
• compatibility

Everything related to Windows drivers can be ruled out.

 

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.