IRQL Not Less or Equal BSOD

[alainFpitre]

Hey guys,


I've been getting the IRQL Not Less or Equal BSOD for quite some time now. I have even recently just sent it back to the seller to be repaired. Sent it back because I was under the impression that the mobo was causing the BSODs since I checked just about everything else. I just received it back today. Powered it up only to have it crash five minutes in with the same IRQL Not Less or Equal message. So the motherboard apparently was not the problem.

I'm 100% sure that faulty RAM is not the problem as I've tested three separate sticks.

I've recently read that peripheral devices could be the cause.
Does this mean that my mouse, keyboard, headset, or monitor could be the problem?

I'm running windows 10. If more system specs are needed let me know. I figured they would be irrelevant in this situation.

Thanks in advance!

 

[Colif]

IRQ errors can be drivers or ram... normally drivers

1. Can you download and run who crashed - it will give us a glimpse of the errors you getting and might help us solve them

Copy/paste summary in here and I see what I can do


2. Can you follow option one here: http://www.tenforums.com/tutorials/5560-bsod-minidump-configure-create-windows-10-a.html
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c windows/minidump
copy that file to documents
upload the copy from documents to a cloud server and share the link here

someone with right software to read them will help you fix it

 

[alainFpitre]

IRQ errors can be drivers or ram... normally drivers

1. Can you download and run who crashed - it will give us a glimpse of the errors you getting and might help us solve them

Copy/paste summary in here and I see what I can do [/b]

Here is the WhoCrashed summary. Thanks!

On Mon 6/5/2017 3:00:52 PM your computer crashed
crash dump file: C:\Windows\Minidump\060517-4390-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x149F90)
Bugcheck code: 0xA (0xFFFFEA03D45F5558, 0x2, 0x0, 0xFFFFF801CCAB019D)
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 appears to be a typical software driver bug and is not likely to 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.

 

[alainFpitre]

2. Can you follow option one here: http://www.tenforums.com/tutorials/5560-bsod-minidump-configure-create-windows-10-a.html
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c windows/minidump
copy that file to documents
upload the copy from documents to a cloud server and share the link here

someone with right software to read them will help you fix it

Here's the dump file link. Thanks for the help!

https://www.dropbox.com/s/b53agvo1hbcz9vp/060517-4390-01.dmp?dl=0

 

[gardenman]

Hi alainFpitre, I downloaded the dump file and ran it through the MS debugger and got the following results: https://pastebin.com/heVPqU4w

You had the error: [IRQL_NOT_LESS_OR_EQUAL (a)]

The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.

I cannot help you with this, wait for Colif or someone else to reply. Good luck.

 

[axe0axe0]

Run DDU, http://www.guru3d.com/files-details/display-driver-uninstaller-download.html, and download new drivers at http://www.geforce.com/drivers.
The nvidia display driver is dated 2016 and is being flagged.

 

[alainFpitre]

Run DDU, http://www.guru3d.com/files-details/display-driver-uninstaller-download.html, and download new drivers at http://www.geforce.com/drivers.
The nvidia display driver is dated 2016 and is being flagged.

Alright, I've done this. Hopefully everything goes smoothly. Thanks.

EDIT: This has not worked. Any other potential solutions?

 

[gardenman]

I'm no expert but, sometimes 1 dump file just isn't enough. I would wait until you have 3 to 5 more minidumps and then upload those and re-post here so we can review them and see if we can pinpoint a driver or cause. (Sometimes we can, sometimes we can't).

 

[alainFpitre]

Here is the most recent crash report:


On Wed 6/7/2017 1:57:57 PM your computer crashed
crash dump file: C:\Windows\Minidump\060717-3468-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x149F90)
Bugcheck code: 0xA (0xFFFFFE00497F8918, 0x2, 0x0, 0xFFFFF800646CA19D)
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 appears to be a typical software driver bug and is not likely to 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.

 

[Colif]

its blaming my fav thing, ntoskrnl otherwise known as New Technology Operating System Kernel, or the brains of windows. It is responsible for many things, some being memory management and driver requests.

Since driver is hiding behind windows, we can try to get it to show itself
you can try running driver verifer, just read the instructions carefully. It is part of win 10 designed to find misbehaving drivers. It will cause BSOD, that is its job since it tests drivers.
note: sometimes this will put you into a boot loop so it helps to have a win 10 installer handy to get out again.
Also helps to run system restore before hand to create a backup to roll back to if necessary.
Download the Windows 10 media creation tool and use it to make a win 10 installer on USB

Once it bsod, run Who crashed and see what driver it reveals

The instructions to stop it looping are in the link above I will show u anyway
change boot order so USB is first, hdd second
boot from installer
on screen after languages, choose repair this pc, not install.
choose start up options
hit the restart button
choose a safe mode (it doesn't matter which) by using number associated with it.
Pc will restart and load safe mode
Now open command Prompt
type verifer /reset and press enter
restart PC

also, upload dumps though verifer should give a driver name.

 

[axe0axe0]

Please upload all files in C:\Windows\Minidump to dropbox and post a share link.

 

[alainFpitre]

its blaming my fav thing, ntoskrnl otherwise known as New Technology Operating System Kernel, or the brains of windows. It is responsible for many things, some being memory management and driver requests.

Since driver is hiding behind windows, we can try to get it to show itself
you can try running driver verifer, just read the instructions carefully. It is part of win 10 designed to find misbehaving drivers. It will cause BSOD, that is its job since it tests drivers.
note: sometimes this will put you into a boot loop so it helps to have a win 10 installer handy to get out again.
Also helps to run system restore before hand to create a backup to roll back to if necessary.
Download the Windows 10 media creation tool and use it to make a win 10 installer on USB

Once it bsod, run Who crashed and see what driver it reveals

The instructions to stop it looping are in the link above I will show u anyway
change boot order so USB is first, hdd second
boot from installer
on screen after languages, choose repair this pc, not install.
choose start up options
hit the restart button
choose a safe mode (it doesn't matter which) by using number associated with it.
Pc will restart and load safe mode
Now open command Prompt
type verifer /reset and press enter
restart PC

also, upload dumps though verifer should give a driver name.

Here is the report from WhoCrashed:
On Thu 6/8/2017 3:04:01 PM your computer crashed
crash dump file: C:\Windows\Minidump\060817-22859-01.dmp
This was probably caused by the following module: mbamswissarmy.sys (MBAMSwissArmy+0x187C7)
Bugcheck code: 0xC4 (0x2000, 0xFFFFF80F256587C7, 0x0, 0x41724765)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\drivers\mbamswissarmy.sys
product: Malwarebytes SwissArmy
company: Malwarebytes
description: Malwarebytes SwissArmy
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: mbamswissarmy.sys (Malwarebytes SwissArmy, Malwarebytes).
Google query: Malwarebytes DRIVER_VERIFIER_DETECTED_VIOLATION

Here is the link to all dump files:

https://www.dropbox.com/sh/mrdyo6hpxi4t0kz/AABVAMO95ooxSb8k9SOcD5yMa?dl=0

 

[alainFpitre]

Please upload all files in C:\Windows\Minidump to dropbox and post a share link.

Here you go. Thanks.

https://www.dropbox.com/sh/mrdyo6hpxi4t0kz/AABVAMO95ooxSb8k9SOcD5yMa?dl=0

 

[axe0axe0]

Uninstall Malwarebytes, if Malwarebytes is your only security program use Windows Defender as alternative while troubleshooting.

Run driver verifier, https://www.sysnative.com/forums/bsod-crashes-kernel-debugging/29-driver-verifier-bsod-related-windows-10-8-1-8-7-vista.html

 

[alainFpitre]

its blaming my fav thing, ntoskrnl otherwise known as New Technology Operating System Kernel, or the brains of windows. It is responsible for many things, some being memory management and driver requests.

Since driver is hiding behind windows, we can try to get it to show itself
you can try running driver verifer, just read the instructions carefully. It is part of win 10 designed to find misbehaving drivers. It will cause BSOD, that is its job since it tests drivers.
note: sometimes this will put you into a boot loop so it helps to have a win 10 installer handy to get out again.
Also helps to run system restore before hand to create a backup to roll back to if necessary.
Download the Windows 10 media creation tool and use it to make a win 10 installer on USB

Once it bsod, run Who crashed and see what driver it reveals

The instructions to stop it looping are in the link above I will show u anyway
change boot order so USB is first, hdd second
boot from installer
on screen after languages, choose repair this pc, not install.
choose start up options
hit the restart button
choose a safe mode (it doesn't matter which) by using number associated with it.
Pc will restart and load safe mode
Now open command Prompt
type verifer /reset and press enter
restart PC

also, upload dumps though verifer should give a driver name.

On Fri 6/9/2017 3:08:23 PM your computer crashed
crash dump file: C:\Windows\Minidump\060917-3468-01.dmp
This was probably caused by the following module: intelppm.sys (intelppm+0x1125)
Bugcheck code: 0xD1 (0xFFFFDE0C823B5AC0, 0xFF, 0x2, 0xFFFFF80D5A5F1125)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\intelppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.


I'm constantly being informed that the BSODs have to do with Intelppm.sys
What does this mean?