Multiple IRQL_NOT_LESS_OR_EQUAL BSODs

Hello,

Before continuing, just a bit of context to clarify the situation and avoid questions:

- I have changed most of my computer parts last august, this includes: the CPU (Ryzen 3600x), the GPU (GTX 2070), the MB (b450 tuf gaming, then b450 tomahawk max in january) and the RAM ; I went from intel to amd

- Since then, using the MB B450 tuf gaming, I had all kinds of random BSOD, always differents, the games I ran often crashed and where unstable, but all stress tests checked out and where good (RAM, CPU, GPU)

- I changed my RAM once to see if it solved it, but still had random BSODs, so I decided to change the MB to a B450 tomahawk max

- During the change, I made a clean install: I reinstalled my windows and everything in it, keeping nothing from the old OS.

- With this new MB, the games are uncomparably stable (I only got a few crashes but nothing alarming, and none are stuttering or show signs of any software or hardware issue), but I still have BSODs, and always the same this time: IRQL_NOT_LESS_OR_EQUAL, pointing to the following modules: ntkrnlmp.exe or ntoskrnl.exe

- I have run multiple stress tests using memtest86 for the RAM and OCCT for the CPU, RAM and GPU. None of them showed any errors.

- I have checked out all my drivers and they all seem to be in order and updated.

- I bought the professional version of Whocrashed to see if it could give me more information (or if someone with a better knowledge on this matter could)

- I have no way of reproducing the BSOD, it happens randomly at any time, even when the computer is idle.

- I have updated the MB (maybe not to its latest patch but fairly recently, like a month or 2 old)

One point that might be important: during the first MB change (from an old intel one to the B450 tuf gaming), I didn't put the spacers (entretoises in french, don't know if that is the good name in english) to protect the MB from the computer case. But when I checked out, the MB did not seem to touch the case, and overall I think the damages would have been final and lethal to my components if they did touch or if the case where not recent enough to protect itself.

But then again, I may not have sufficient experience in the domain and maybe some components where indeed damaged.

I did put spacers for the 2nd MB.

I am a bit out of options, not being able to test with another GPU or CPU. But maybe you can help me using the following dumps.

If anyone has any idea of what could cause the crashes or what to do next... I am all ears!

Thanks!

Links to dmp files:

minidump: https://matthiusd.wimi.pro/shared/#/file/6f07961cf450f7cae82b1581733f7c24

memory dump: https://matthiusd.wimi.pro/shared/#/file/87c60a1fd70d32d376eb4ab4a55d9270

msinfo32: https://matthiusd.wimi.pro/shared/#/file/c94718fea3716c638f811ddf161b428f
admin events: https://matthiusd.wimi.pro/shared/#/file/0bd7ffeece74600c9937e9f34921b041

Second BSOD:

minidump: https://matthiusd.wimi.pro/shared/#/file/a57dafca979e73e78addc55c9a5fd028

memory dump: https://matthiusd.wimi.pro/shared/#/file/5392252620cd1fb99b2da77059fac2ea

msinfo32: https://matthiusd.wimi.pro/shared/#/file/dacc4d5b4e49e592e33a95b1ebca91a5

admin events: https://matthiusd.wimi.pro/shared/#/file/8bd6a911309fb2026f08081e721cde7c


Now... here is the last WhoCrashed dumps:

On Tue 3/17/2020 3:22:06 PM your computer crashed or a problem was reported

crash dump file: C:\WINDOWS\Minidump\031720-9265-01.dmp

uptime: 02:56:59

This was probably caused by the following module: ntkrnlmp.exe (nt!KiBugCheckDispatch+0x69) 

Bugcheck code: 0xA (0xFFFF828087EB5990, 0xFF, 0xF5, 0xFFFFF801080BBF2B)

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. 


On Tue 3/17/2020 3:22:06 PM your computer crashed or a problem was reported

crash dump file: C:\WINDOWS\MEMORY.DMP

uptime: 02:56:59

This was probably caused by the following module: ntkrnlmp.exe (nt!KiBugCheckDispatch+0x69) 

Bugcheck code: 0xA (0xFFFF828087EB5990, 0xFF, 0xF5, 0xFFFFF801080BBF2B)

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. 

And the one of the DMP read from the windbg.exe:



Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.



Loading Dump File [C:\Windows\Minidump\031720-9265-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

Built by: 18362.1.amd64fre.19h1_release.190318-1202

Machine Name:

Kernel base = 0xfffff801`08000000 PsLoadedModuleList = 0xfffff801`08448150

Debug session time: Tue Mar 17 15:22:06.214 2020 (UTC + 1:00)

System Uptime: 0 days 2:56:59.790

Loading Kernel Symbols

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

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

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

...........

Loading User Symbols

Loading unloaded module list

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

For analysis of this file, run !analyze -v

11: 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: ffff828087eb5990, memory referenced

Arg2: 00000000000000ff, IRQL

Arg3: 00000000000000f5, 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: fffff801080bbf2b, address which referenced memory


Debugging Details:

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


*** WARNING: Unable to verify timestamp for win32k.sys


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:  18362.1.amd64fre.19h1_release.190318-1202


SYSTEM_MANUFACTURER:  Micro-Star International Co., Ltd


SYSTEM_PRODUCT_NAME:  MS-7C02


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


SYSTEM_VERSION:  1.0


BIOS_VENDOR:  American Megatrends Inc.


BIOS_VERSION:  3.50


BIOS_DATE:  11/07/2019


BASEBOARD_MANUFACTURER:  Micro-Star International Co., Ltd


BASEBOARD_PRODUCT:  B450 TOMAHAWK MAX (MS-7C02)


BASEBOARD_VERSION:  1.0


DUMP_TYPE:  2


BUGCHECK_P1: ffff828087eb5990


BUGCHECK_P2: ff


BUGCHECK_P3: f5


BUGCHECK_P4: fffff801080bbf2b


WRITE_ADDRESS: fffff801085733b8: Unable to get MiVisibleState

Unable to get NonPagedPoolStart

Unable to get NonPagedPoolEnd

Unable to get PagedPoolStart

Unable to get PagedPoolEnd

 ffff828087eb5990 


CURRENT_IRQL:  0


FAULTING_IP: 

nt!PpmIdlePrepare+31b

fffff801`080bbf2b 48897d80        mov     qword ptr [rbp-80h],rdi


CPU_COUNT: c


CPU_MHZ: ed8


CPU_VENDOR:  AuthenticAMD


CPU_FAMILY: 17


CPU_MODEL: 71


CPU_STEPPING: 0


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:  MATT-PC


ANALYSIS_SESSION_TIME:  03-17-2020 16:51:48.0947


ANALYSIS_VERSION: 10.0.18362.1 amd64fre


TRAP_FRAME:  ffff828086eb5780 -- (.trap 0xffff828086eb5780)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=0000000000000000 rbx=0000000000000000 rcx=000000000000000b

rdx=00000018b9e36ef7 rsi=0000000000000000 rdi=0000000000000000

rip=fffff801080bbf2b rsp=ffff828086eb5910 rbp=ffff828087eb5a10

 r8=0000000000000000  r9=ffffa900e5479180 r10=00000018ba07453a

r11=ffff98fe7ae00000 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0         nv up di pl nz ac pe cy

nt!PpmIdlePrepare+0x31b:

fffff801`080bbf2b 48897d80        mov     qword ptr [rbp-80h],rdi ss:0018:ffff8280`87eb5990=????????????????

Resetting default scope


LAST_CONTROL_TRANSFER:  from fffff801081d41e9 to fffff801081c2380


STACK_TEXT:  

ffff8280`86eb5638 fffff801`081d41e9 : 00000000`0000000a ffff8280`87eb5990 00000000`000000ff 00000000`000000f5 : nt!KeBugCheckEx

ffff8280`86eb5640 fffff801`081d052b : 00000000`00000000 00000000`00000000 00000000`000a5ef2 fffff801`082f066b : nt!KiBugCheckDispatch+0x69

ffff8280`86eb5780 fffff801`080bbf2b : 00000018`b9e39533 00000000`00989680 ffff8280`86eb5a10 ffffa900`e5479180 : nt!KiPageFault+0x46b

ffff8280`86eb5910 fffff801`080bac66 : 00000000`00000003 00000000`00000002 ffff****7`98b05100 00000000`00000008 : nt!PpmIdlePrepare+0x31b

ffff8280`86eb5b00 fffff801`081c5e88 : ffffffff`00000000 ffffa900`e5479180 ffff****7`a3363080 00000000`00000688 : nt!PoIdle+0x1e6

ffff8280`86eb5c60 00000000`00000000 : ffff8280`86eb6000 ffff8280`86eb0000 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`080bbf2b 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


IMAGE_VERSION:  10.0.18362.720


STACK_COMMAND:  .thread ; .cxr ; kb


BUCKET_ID_FUNC_OFFSET:  31b


FAILURE_BUCKET_ID:  AV_nt!PpmIdlePrepare


BUCKET_ID:  AV_nt!PpmIdlePrepare


PRIMARY_PROBLEM_CLASS:  AV_nt!PpmIdlePrepare


TARGET_TIME:  2020-03-17T14:22:06.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:  190318-1202


BUILDLAB_STR:  19h1_release


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


ANALYSIS_SESSION_ELAPSED_TIME:  3dee


ANALYSIS_SOURCE:  KM


FAILURE_ID_HASH_STRING:  km:av_nt!ppmidleprepare


FAILURE_ID_HASH:  {dd7d0096-4602-c4e5-a984-978d6ab3aa71}


Followup:     MachineOwner

---------


* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

Aaaand another.

Did you give up haha.

I think I will change the CPU... What do you think?

On Sat 4/11/2020 12:07:51 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\041120-9812-01.dmp
uptime: 01:19:56
This was probably caused by the following module: ntkrnlmp.exe (nt!KiBugCheckDispatch+0x69)
Bugcheck code: 0x7F (0x8, 0xFFFF82018A2841B0, 0x0, 0xFFFFF80730FC952A)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Most often this is caused by a software problem (kernel stack overflow) but this can also be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 4/11/2020 12:07:51 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
uptime: 01:19:56
This was probably caused by the following module: ntkrnlmp.exe (nt!KiBugCheckDispatch+0x69)
Bugcheck code: 0x7F (0x8, 0xFFFF82018A2841B0, 0x0, 0xFFFFF80730FC952A)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Most often this is caused by a software problem (kernel stack overflow) but this can also be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I have the same problem, my computer has taken damage cause to a fault and now it crashes with different bsod's and it's the same ones as you experince 

If you figure it out, please let me know 

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

One of the issues I found is that the PSU is a little weak for my configuration. I have bought another, waiting for it to arrive and will test it.

I also reflashed my BIOS and changed the power settings for Ryzen balanced or high performance and since then I didn't BSOD, but then again it can happen after 2 weeks of normal behavior.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I have found the issue: the CPU was faulty. I replaced it by another (Ryzen 5 3600) and it's been 2 weeks without any issue now :)

Thank you auggy for your support, it has been very helpful!

This issue is solved for me!

1 person found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

 
 

Question Info


Last updated December 7, 2020 Views 359 Applies to: