BSOD Crashes, 'IRQL_NOT_LESS_OR_EQUAL' & 'KMODE_EXCEPTION_NOT_HANDLED'

Toggle sidebar Toggle sidebar
C

calvinwakefield1

Mar 2, 2018
36
0
30
I'm getting some BSOD showing me 'IRQL_NOT_LESS_OR_EQUAL' and 'KMODE_EXCEPTION_NOT_HANDLED'.
This has been going on none-stop for the past 3 days, I've tried fixing it myself by updating my drivers and even performing a clean install of Windows 10 but the problem still persists.
I believe it's a corrupt or faulty driver but am unsure as the problem stuck around even after performing the Windows 10 Clean Install...

I opened up the Minidumps with BlueScreenView and the problem seems to be with something called 'ntoskrnl.exe'.
Any and all assistance would be greatly appreciated.

Minidump
http://www.mediafire.com/file/mon3xshq6bfdsa7/030218-24359-01.dmp

http://www.mediafire.com/file/86mei16ngntf68i/030218-28890-01.dmp

http://www.mediafire.com/file/8wc8om2undgmd47/030218-23640-01.dmp

http://www.mediafire.com/file/71putdbsiu16nd3/030218-28296-01.dmp

http://www.mediafire.com/file/nhl7rbioh1sdush/030218-27515-01.dmp
 
Sort by date Sort by votes
Hi, I ran the dump files through the debugger and got the following information: https://pste.eu/p/xhgV.html

File: 030218-28890-01.dmp (Mar 2 2018 - 16:13:01)
BugCheck: [IRQL_NOT_LESS_OR_EQUAL (A)]
Probably caused by: memory_corruption (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 05 Min(s), and 19 Sec(s)

File: 030218-28296-01.dmp (Mar 2 2018 - 16:35:07)
BugCheck: [KMODE_EXCEPTION_NOT_HANDLED (1E)]
Probably caused by: memory_corruption (Process: Battle.net Helper.exe)
Uptime: 0 Day(s), 0 Hour(s), 04 Min(s), and 25 Sec(s)

File: 030218-27515-01.dmp (Mar 2 2018 - 16:21:49)
BugCheck: [ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (FC)]
Probably caused by: memory_corruption (Process: backgroundTaskHost.exe)
Uptime: 0 Day(s), 0 Hour(s), 08 Min(s), and 08 Sec(s)

File: 030218-24359-01.dmp (Mar 2 2018 - 16:25:01)
BugCheck: [KERNEL_SECURITY_CHECK_FAILURE (139)]
Probably caused by: memory_corruption (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 00 Min(s), and 10 Sec(s)

File: 030218-23640-01.dmp (Mar 2 2018 - 16:30:02)
BugCheck: [KMODE_EXCEPTION_NOT_HANDLED (1E)]
Probably caused by: memory_corruption (Process: SystemSurvey.exe)
Uptime: 0 Day(s), 0 Hour(s), 03 Min(s), and 07 Sec(s)
Motherboard: https://www.asus.com/us/Motherboards/Z170-E/
There is a BIOS update available for your system. You are using version 2202 and the latest is 3703.

I can't help you with this. Wait for additional replies. Good luck.
 
Upvote 1 Downvote
I have to assume you got the lan drivers you have installed from Windows since its newer than whats on the Asus web site. Two of the programs that crashed ate made by Blizzard so I figured it might be the LAN drivers. You could check the intel web site and see if any updates for it there.

Updating BIOS, as suggested above, could help this as well. Newer drivers may have suggestions BIOS doesn't understand.


NTOSKRNL = windows kernel. It handles all driver requests, power management, and memory management. It sits between Hardware and Applications. It got blamed but its not the cause
 
Upvote 0 Downvote
I ran the dump files through the debugger and got the following information: https://pste.eu/p/PGsA.html

File: 030318-30625-01.dmp (Mar 3 2018 - 03:52:56)
BugCheck: [BAD_POOL_HEADER (19)]
Probably caused by: fileinfo.sys (Process: Taskmgr.exe)
Uptime: 0 Day(s), 0 Hour(s), 04 Min(s), and 39 Sec(s)

File: 030318-30156-01.dmp (Mar 3 2018 - 10:06:27)
BugCheck: [IRQL_NOT_LESS_OR_EQUAL (A)]
Probably caused by: ntkrnlmp.exe (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 05 Min(s), and 45 Sec(s)

I can't help you with this. Wait for additional replies. Good luck.
 
Upvote 1 Downvote
Upvote 0 Downvote
Hi, I ran the dump file(s) through the debugger and got the following information: https://pste.eu/p/sYuZ.html

File: 030318-33609-01.dmp (Mar 3 2018 - 14:36:18)
BugCheck: [SYSTEM_SERVICE_EXCEPTION (3B)]
Probably caused by: ntkrnlmp.exe (Process: DXSETUP.exe)
Uptime: 0 Day(s), 0 Hour(s), 59 Min(s), and 07 Sec(s)

File: 030318-32625-01.dmp (Mar 3 2018 - 13:35:22)
BugCheck: [IRQL_NOT_LESS_OR_EQUAL (A)]
Probably caused by: hardware (Process: firefox.exe)
Uptime: 0 Day(s), 0 Hour(s), 29 Min(s), and 45 Sec(s)

File: 030318-31421-01.dmp (Mar 3 2018 - 15:22:33)
BugCheck: [IRQL_NOT_LESS_OR_EQUAL (A)]
Probably caused by: ntkrnlmp.exe (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 16 Min(s), and 07 Sec(s)

File: 030318-30984-01.dmp (Mar 3 2018 - 17:51:29)
BugCheck: [SYSTEM_SERVICE_EXCEPTION (3B)]
Probably caused by: memory_corruption (Process: firefox.exe)
Uptime: 0 Day(s), 0 Hour(s), 03 Min(s), and 06 Sec(s)

File: 030318-28750-01.dmp (Mar 3 2018 - 17:47:12)
BugCheck: [SYSTEM_SERVICE_EXCEPTION (3B)]
Probably caused by: ntkrnlmp.exe (Process: SearchUI.exe)
Uptime: 0 Day(s), 0 Hour(s), 01 Min(s), and 21 Sec(s)

File: 030318-27125-01.dmp (Mar 3 2018 - 18:14:50)
BugCheck: [SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007E)]
*** WARNING: Unable to verify timestamp for rzendpt.sys
Probably caused by: rzendpt.sys (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 00 Min(s), and 14 Sec(s)

File: 030318-26234-01.dmp (Mar 3 2018 - 17:45:24)
BugCheck: [IRQL_NOT_LESS_OR_EQUAL (A)]
Probably caused by: hardware (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 00 Min(s), and 16 Sec(s)
I can't help you with this. Wait for additional replies. Good luck.
 
Upvote 0 Downvote
Update your razer drivers as the oldest part from 2015 is named in 1 error

Go here and select windows 10 and download latest LAN drivers - https://downloadcenter.intel.com/product/82186/Intel-Ethernet-Connection-I219-V since newest on Asus site are from 2015.

Not sure why DXSetup crashed, I assume you were installing a game. Still doesn't explain why it crashed. Normally errors related to DX are GPU related but that doesn't feel right this time. Why would GPU stop you installing other DX versions

what Nvidia GPU is it? I can see you have newest drivers, that can sometimes cause problems as Nvidia drivers aren't that reliable anymore.

run this and see if it finds anything
right click start button
choose powershell (admin)
type SFC /scannow and press enter
once its completed, copy/paste this command into same window:
Repair-WindowsImage -Online -RestoreHealth and press enter
SFC fixes system files, second command cleans image files, re run SFC if it failed to fix all files and restart PC
 
Upvote 0 Downvote


System File Checker didn't pick up anything and then it said ''Repair-WindowsImage' is not recognized as an internal or external command, operable program or batch file."

System Specs:

Motherboard: Asus Z170-E
CPU: Intel I7-6700k
GPU: Nvidia GeForce GTX 1070
SSD: Crucial MX300 750GB SATA 2.5"
Hard Drive: Seagate Desktop 2 TB Internal HDD - 3.5"
 
Upvote 0 Downvote
Upvote 0 Downvote
I ran the dump files through the debugger and got the following information: https://pste.eu/p/N8Xd.html

File: 030418-33125-01.dmp (Mar 4 2018 - 12:09:34)
BugCheck: [IRQL_NOT_LESS_OR_EQUAL (A)]
Probably caused by: ntkrnlmp.exe (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 01 Min(s), and 03 Sec(s)

File: 030418-32203-01.dmp (Mar 4 2018 - 13:54:59)
BugCheck: [IRQL_NOT_LESS_OR_EQUAL (A)]
Probably caused by: ntkrnlmp.exe (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 00 Min(s), and 49 Sec(s)

File: 030418-31187-01.dmp (Mar 4 2018 - 13:53:34)
BugCheck: [IRQL_NOT_LESS_OR_EQUAL (A)]
Probably caused by: ntkrnlmp.exe (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 05 Min(s), and 35 Sec(s)

File: 030418-30265-01.dmp (Mar 4 2018 - 11:38:59)
BugCheck: [IRQL_NOT_LESS_OR_EQUAL (A)]
Probably caused by: ntkrnlmp.exe (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 04 Min(s), and 28 Sec(s)

File: 030418-29500-01.dmp (Mar 4 2018 - 11:03:51)
BugCheck: [IRQL_NOT_LESS_OR_EQUAL (A)]
Probably caused by: ntkrnlmp.exe (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 01 Min(s), and 26 Sec(s)
I can't help you with this. Wait for additional replies. Good luck.
 
Upvote 0 Downvote
ntkrnlmp.exe = New Technology Kernel Multiple Processor. Its one of the most critical parts of win 10 and like the Kernel itself, . It handles all driver requests, power management, and memory management. It sits between Hardware and Applications. It got blamed but its not the cause.

All of them are IRQ errors which aren't so bad.. annoying but not too bad. More than likely caused by a driver.

problem is apart from Razer drivers, there isn't anything that stands out on there

drivers installed
Oct 15 2015 rzendpt.sys Razer RzEndPt driver https://www.razerzone.com/
Oct 15 2015 rzudd.sys Razer Rzudd Engine Driver https://www.razerzone.com/
Jun 14 2016 RTKVHD64.sys Realtek Audio Driver system driver http://www.realtek.com.tw/
Mar 19 2017 e1d65x64.sys Intel(R) Gigabit Adapter NDIS 6.x driver https://downloadcenter.intel.com/
Jul 16 2017 rzpnk.sys Razer Overlay Support https://www.razerzone.com/
Jul 18 2017 rzpmgrk.sys Razer Overlay Support https://www.razerzone.com/
Aug 22 2017 iqvw64e.sys Intel Network Adapter Diagnostic Driver http://www.intel.com/
Nov 19 2017 TeeDriverW8x64.sys Intel Management Engine Interface
Dec 15 2017 nvhda64v.sys Nvidia HDMI Audio Device http://www.nvidia.com/
Feb 23 2018 nvlddmkm.sys Nvidia Graphics Card driver http://www.nvidia.com/
Click to expand...

Which makes me wonder if its hardware corrupting the drivers.

Did disk checker find any errors or bad clusters on drive? Might want to run HDTune on drive and check it out (only as you did get stuck on 10% for a few hours), check the health tab and see its SMART score
 
Upvote 0 Downvote
I don't like suggesting this option but it will identify bad 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 and create a backup date to roll back to if necessary. Download the Windows 10 media creation tool and use it to make a win 10 installer on USB

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.

Once it bsod, upload the minidump file and we see what it shows us.

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 troubleshoot
choose advanced
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
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom