Constant BSOD (kmode_exception_not_handled, irql_not_less_or_equal)

[Steven W]

Sorry if this thread is in the wrong part of the forums.

I just built my first gaming PC yesterday (3/26) and got it running. Shortly after starting up, I received my first BSoD. After restarting the PC, they kept coming. From what I have read, it is caused by drivers or something of the sort which I attempted to install, but couldn't due to all the BSoD happening.

I have gotten three different BSoD errors so far:
KMODE_EXCEPTION_NOT_HANDLED
IRQL_NOT_LESS_OR_EQUAL
DRIVER_IRQL_NOT_LESS_OR_EQUAL

After the PC was built, I installed Windows 10 Pro OEM from a 16GB USB. I then tried to installed drivers and anything else using the Windows Update tool. I managed to only get a few installed. I do have an ethernet connection.

Here is the list of parts I used in case that is needed (I used Win10 Pro, not Home.):
http://pcpartpicker.com/user/StevOrigins/saved/CQZp99

One more thing that I have been having an issue with... I can only see my SSD being used when I have both an SSD and HDD installed into the PC. OS is on SSD and I want everything else on the HDD. All the connectors are there except what looked like a jumper connector. Would that be the problem there?

EDIT: Would I just need to format and partition the HDD using Computer Management for it to be recognized?

Any help is greatly appreciated!

 

[Colif]

Install this: http://www.resplendence.com/whocrashed and let it do a scan
It will look at error logs and hopefully give us an indication of the problem.

If its not clear, paste them in here.

Is the hdd new? If its never been used then you need to format it so win 10 can see it. So yes, use disc management.

 

[Steven W]

Install this: http://www.resplendence.com/whocrashed and let it do a scan
It will look at error logs and hopefully give us an indication of the problem.

If its not clear, paste them in here.

Is the hdd new? If its never been used then you need to format it so win 10 can see it. So yes, use disc management.

I received another BSoD just after the scan completed so I was only able to gather a few bits of information. The IRQL_NOT_LESS_OR_EQUAL said it was caused by ntoskrnl.exe and I believe the KMODE_EXCEPTION_NOT_HANDLED said the hal.dll. Sorry I couldn't gather more information, it keeps crashing too quickly.

 

[Colif]

try loading into safe mode and run the program again

those two programs are part of windows 10, the errors probably are drivers.
HAL = hardware allocation layer, i remember that from an IT course i did centuries ago... no pod bay days are associated with it (sorry)

make sure all the hardware is in right, since you just made pc, it could be something loose or not attached right too. You getting way too many BSOD

what are specs of the machine as well?

 

[Steven W]

try loading into safe mode and run the program again

those two programs are part of windows 10, the errors probably are drivers.
HAL = hardware allocation layer, i remember that from an IT course i did centuries ago... no pod bay days are associated with it (sorry)

make sure all the hardware is in right, since you just made pc, it could be something loose or not attached right too. You getting way too many BSOD

what are specs of the machine as well?

These are just two of several:

crash dump file: C:\WINDOWS\Minidump\032716-2093-01.dmp
This was probably caused by the following module: hal.dll (hal!KeQueryPerformanceCounter+0x6E)
Bugcheck code: 0xD1 (0x2B4870EE, 0xFF, 0x63, 0x2B4870EE)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft Windows Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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.
This 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.

crash dump file: C:\WINDOWS\Minidump\032716-2093-01.dmp
This was probably caused by the following module: hal.dll (hal!KeQueryPerformanceCounter+0x6E)
Bugcheck code: 0xA (0xFFFFD00135579F70, 0xFF, 0x27, 0xFFFFF803728ABC6F)
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 appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
This crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

[Colif]

How soon after you installed win 10 did you get first bsod? Did you install the motherboard drivers from the MSI site?

i don't know if its the cause but your PSU is pretty low spec, its tier 4 on here: http://www.tomshardware.com/forum/id-2547993/psu-tier-list.html

Nice pc otherwise, almost a copy of what mine was 11 months ago.

 

[Steven W]

When I was installing Windows, I turned away for a few minutes and found the computer turned off without anyone doing anything else to it. It appeared that the OS installed and after a few minutes, I got the first BSoD. From there, I received a BSoD a couple minutes after startup. My friend was helping me out and I think we only installed the Ethernet drivers from the MSI disk.

 

[Colif]

You should use the ones on the web site, discs get out of date, I know it doesn't help now but should use the drivers from here: https://us.msi.com/Motherboard/support/Z97-GAMING-5.html#down-bios

Might also want the new bios too.

Win 10 install turns itself a few times as it installs things.

 

[Steven W]

Since I am using Safe Mode right now, should I download the drivers from my laptop to a USB and install that way?

 

[Colif]

See if new bios makes pc more stable, the bsod started too soon for my liking. I don't know if its hardware or software at this stage.

Do BSOD happen in safe mode? try installing drivers in here if you can - I suspect you can't. See if pc bsod in there

you may need to reinstall win 10 again but no point if problem is hardware instead.

 

[Steven W]

I booted back into normal mode and the drivers are currently being installed. No BSOD yet. I installed whatever drivers I could through safe mode and then switched back and installed chipset drivers and whatever looked the most important ASAP. Seems to be working so far. I didn't flash the BIOS, however I might later on just to have a newer and more stable version.

 

[Colif]

fingers crossed

 

[Steven W]

Turns out that didn't work. Still getting the BSOD of IRQL and DRIVER_IRQL. I thought I installed all necessary drivers, but I'm not sure.

 

[Colif]

did you install bios as well?

I have to go soon so hopefully someone else will help you out. Otherwise i look when i wake up.

 

[Steven W]

I'm about the flash the BIOS now. Hopefully that will be the solution.

 

[Steven W]

So it seems that the BSOD errors I posted about are fixed, however now I am getting WHEA_UNCORRECTABLE_ERROR. From what I know, this is a hardware issue. I have reset BIOS settings to default and plan to look at the PC sometime soon. I will post the WhoCrashed report here too when I can.

 

[Steven W]

Here is the WhoCrashed report:

crash dump file: C:\WINDOWS\Minidump\032816-3078-01.dmp
This was probably caused by the following module: hal.dll (hal!HalBugCheckSystem+0xCF)
Bugcheck code: 0x124 (0x0, 0xFFFFE001C1241028, 0xB2000000, 0x10019)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
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.