Blue Screen Ntoskrnl caused by WHEA

Toggle sidebar Toggle sidebar
M

mwtrevi

Mar 13, 2018
12
0
10
Hey all,
I've been having a recurring blue screen issue. Sometimes I'll go weeks without one, other times within an hour of each other. There is no pattern to what I am doing when the BSOD's appear.

Drivers are up to date, my CPU/GPU are not overclocked, temps don't exceed the recommended limit on my CPU or GPU.

Here is a link to two of my recent BSOD dump files - https://drive.google.com/drive/folders/1hUKt02ZNLb2_VGwDPPnq5yLUT1zftK3O?usp=sharing

On the first one shown there is no overclocking on the CPU. After the first blue screen today I reset my BIOS to default which reactivated the 'turbo' feature on my CPU giving it a slight overclock. I don't see that being the issue though since it was happening whether that was activated or not.

Here are my specs

ASUS SABERTOOTH Z97 MARK1 motherboard
Intel Core i7-4770K Quad-Core Desktop Processor (3.5 GHz, 8 MB Cache)
EVGA GeForce GTX 1070 SC GAMING ACX 3.0 Black Edition, 8GB GDDR5
Kingston HyperX Beast 16 GB Kit (2x8 GB) 2400MHz DDR3

Windows 10 Current version 1709 build 16299.248

If anyone has any idea of a fix, it'd be much appreciated.
 
Sort by date Sort by votes
Colif

Colif

Win 11 Master
Moderator
Jun 12, 2015
66,677
6,868
168,140
Do you have AI Suite installed? It can cause WHEA errors, so remove it if its installed.
remove any overclocking software as well, it can have the same effect. This includes MSI Afterburner & Intel extreme tuning utility

I will ask someone to read the dumps for me.
 
Upvote 0 Downvote
gardenman

gardenman

Splendid
Moderator
Jun 16, 2016
4,266
507
26,590
Hi, I ran the dump files through the debugger and got the following information: https://pste.eu/p/Vx7q.html

File: 033018-42453-01.dmp (Mar 30 2018 - 21:13:27)
BugCheck: [WHEA_UNCORRECTABLE_ERROR (124)]
Probably caused by: GenuineIntel (Process: FortniteClient)
Uptime: 0 Day(s), 4 Hour(s), 25 Min(s), and 29 Sec(s)

File: 033018-41578-01.dmp (Mar 30 2018 - 16:44:33)
BugCheck: [WHEA_UNCORRECTABLE_ERROR (124)]
Probably caused by: GenuineIntel (Process: Streamlabs OBS)
Uptime: 7 Day(s), 23 Hour(s), 40 Min(s), and 38 Sec(s)

Motherboard: https://www.asus.com/us/Motherboards/SABERTOOTH_Z97_MARK_1/
The ASUS site isn't loading for me. I'm not sure if you have the latest BIOS or not. You have version 2702 installed.

I can't help you with this. Wait for additional replies. Good luck.
 
Upvote 0 Downvote
Colif

Colif

Win 11 Master
Moderator
Jun 12, 2015
66,677
6,868
168,140
Did you remove AI Suite?

AsIO.sys dated 2012 is still active, its the Asus Input Output driver and is part of AI Suite, and can change values in CPU that can cause WHEA errors,

Wait and see if JohnBL answers as he can often find more in dump files than I can. None of the other drivers installed would normally cause a WHEA error.
 
Upvote 0 Downvote
Colif

Colif

Win 11 Master
Moderator
Jun 12, 2015
66,677
6,868
168,140
look on this link - https://pste.eu/p/Vx7q.html - its from Gardenmans post, I asked him to look at the dump file for me.
Under the driver tab is showing all the drivers that were running when error occurred.

Openhardwaremonitor sure needs an upgrade as its from 2008 but not sure it would cause this error
Scarlet crush could be cause as its known to cause bsod but not necessarily this one.

All the other drivers are from 2015 and should work with win 10

it also has a listing of both errors but they aren't showing a clue as to what cause is.
 
Upvote 0 Downvote
M

mwtrevi

Mar 13, 2018
12
0
10
I also am unable to delete asIO.sys due to it being open in another program - can't seem to find what is accessing that currently, any idea?

Edit - Started in safe mode, was able to remove.
 
Upvote 0 Downvote
M

mwtrevi

Mar 13, 2018
12
0
10
In my Event Viewer I am getting a Warning related to Kernel-PnP.

The driver \Driver\WUDFRd failed to load for the device ACPI\PNP0A0A\2&daba3ff&0.

Could this have any relation to the Bluescreens?
 
Upvote 0 Downvote
Colif

Colif

Win 11 Master
Moderator
Jun 12, 2015
66,677
6,868
168,140
Those WUDFRd errors are not ACPI errors. No matter if they point to ACPI\PNP0A0A\2&daba3ff&2. This is just a PNP (Plug and Play) indentifier that points to a device class.

WUDFRd is Windows User Mode Driver Framework. This is a framework for drivers that run in user mode, in contrast to kernel mode that most drivers run as. These are drivers that do not need Ring-0 security layer access for those familiar with technical details. For the rest it's too complicated to explain.

Those errors happen because of bugs in Windows and specifically the Framework itself. WUDFRd is not available when Windows tries to load the driver so you get these errors in the event viewer. Afterwards the driver for the device is loaded normally, if it wasn't then the device that uses WUDFRd would not work (would not be seen by your PC). These errors can be safely ignored untill Microsoft decides to fix those issues. You will usually see these errors when devices that use WUDFRd are connected during boot/reboot. In case of software using a user mode driver, you will see these errors always if the driver get initiated on boot (so yes it's possible to see these errors caused by software BUT again they are harmless)
Click to expand...

https://rog.asus.com/forum/showthread.php?48808-Help-Multiple-ACPI-Errors/page17

I will get gardenman to look at dump for me again
 
Upvote 0 Downvote
Colif

Colif

Win 11 Master
Moderator
Jun 12, 2015
66,677
6,868
168,140
Try running this on PC and see if it comes out clear - https://downloadcenter.intel.com/download/19792/Intel-Processor-Diagnostic-Tool

5 days uptime sure makes me think its not hardware or CPU anyway. If it were CPU it would happen much faster in most cases. Like at boot. Figured best to check CPU out anyway.

I still suspect its a driver, its just not showing its face. Oldest driver on PC is scarlet crush, this next bit will tell us if its a problem. All 3 WHEA errors have occurred during gaming, do you use a PS3/4 controller to play Fortnite?

i don't like suggesting this next thing but its perfectly safe, its part of win 10.

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.
Download the Windows 10 media creation tool and use it to make a win 10 installer on USB
Also helps to run system restore before hand to create a restore point to roll back to if necessary.
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
M

mwtrevi

Mar 13, 2018
12
0
10
Ran the program, cpu passed all tests. I don't play with a controller at all. Going to run driver verifier here shortly and will post back with results, thanks!
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom