Windows 10: BSOD WHEA_UNCORRECTABLE_ERROR hal.dll+37203 ntoskrnl.exe

This started a couple months ago, and sometimes it happens around twenty times a day. Recently, within the last half hour, it's happened nine times (a couple times as I've been writing this). I'll get really lucky, and maybe go a day where it happens two-three times, but why that happens, I don't know. It seems completely random. It just happened while I was typing this for example, but at another time while at the login screen when I left my computer on while I showered.

Diagnostic is attached.

:)

 

hal.dll+35f1f bsod error in Windows 10

OT- hal.dll+35f1f bsod

Hello,

There was a bsod just now, which is the first time I've experienced it - and should I be worrying about it?

This is what I got from BlueScreenView:

071816-24656-01.dmp

18/7/2016 8:23:23 PM

0x00000124

00000000`00000000

ffffe000`2db12028

00000000`b2000000

00000000`00100402

hal.dll

hal.dll+35f1f

x64

ntoskrnl.exe+142940

C:\WINDOWS\Minidump\071816-24656-01.dmp

What caused this? Thanks!

 

BSOD errors without an identifiable cause

Okay I may or may not be onto something now. Since, from what I've read, it seems that most ntoskrnl.exe BSODs are not actually caused by ntoskrnl, but by another driver that takes up the krnl's space. When ntoskrnl.exe finds it, it throws the system into
a BSOD to prevent damage. Looking the the dump files, I found that there was a driver called hal.dll, but the crash address was different from the driver address. The crash address was ntoskrnl.exe+14ec00, the same as my above post. There is also another driver
called dxgmms2.sys who's crash address was ntoskrnl.exe+14ec00. I'm not sure if this will help or if it means anything but I'm looking for anything at this point.

 

Code: BugCheck 124, {0, ffffbe81a57a4028, f60006c0, 40150} Probably caused by : GenuineIntel[/quote] Code: BugCheck 124, {0, ffffab0a8dfa4028, f600d240, 40150} Probably caused by : GenuineIntel[/quote] In the log there were only 2 bsod. One was from 5/27 and the other 6/3.
The misbehaving driver is an Intel driver. The processor is Intel. Uninstall it and reinstall a new driver. If there are any other Intel drivers uninstall and reinstall them too.
Open device manager, expand processors, uninstall Intel drivers (wireless, bluetooth, etc)
There were many crashes but only 2 bsod.

In the event log there was a windows update failure. Attempt windows update now and indicate if there are any failures with KB# and error code.

 

I downloaded Intel's Driver Utility and updated the blutooth and wireless from there (I hope that's acceptable). I also went through a number of others in Device Manager, uninstalled then reinstalled what I assumed were the same ones.

I suppose that makes sense. I do recall one or two crashes where the screen stuck around a lot longer, enough to read it, whereas with most, the blue screen just flashes by the with text too fast to really read. So now, the waiting game.

And I checked for updates and also did wuauclt.exe /updatenow, but it says everything's up to date.

Thanks for the help.

 

For bsod during the use of windows driver verifier turn off automatic restart. This way if there is a displayed malfunctioning driver in the form *.sys you can record it.

Keyboard: win + r keys simultaneously > type or copy and paste: sysdm.cpl > click advanced tab > under startup and recover click settings > under system failure uncheck automatically restart


See this link: BSOD Finding and fixing them - Microsoft Community

Report the whocrashed and bluescreenview results and update the zip logs.
You can update the log or create a new one so that we can process the bsod.

 

Uninstall all identified misbehaving drivers (all Intel drivers) and use Microsoft default drivers as you use Windows driver verifier to see if you can boot without a bsod while using windows driver verifier.
Once you no longer have any bsod while using Microsoft default drivers (using the fewest Intel drivers that may be a source of bsods) you will then use the computer for a period of time. Then you can start testing each driver one at a time by installing the latest driver and then running Windows driver verifier. You will then repeat the process until you find the misbehaving driver. You must uninstall as many Intel drivers as possible so that you have no more bsod. If there is another misbehaving driver it should appear as no or very few drivers were reinstalled(using the default Microsoft drivers).

 

Alright so, I disabled and uninstalled a ton of Intel drivers... but in the middle of doing so, crash. It's becoming very difficult to do anything without being interrupted by a crash. Even typing a simple post like this. I amazingly, was able to compile another dump, from today's crashes. No idea what's different, but it's attached. Thinking of formatting because of how frustrating this is.

 

These are the debugging from todays (6/13/2017) dumps. The Intel drivers need to uninstalled and new ones found for installation.

Code: BugCheck 124, {0, ffff8e03e365e028, f6000480, 40150} Probably caused by : memory_corruption[/quote] Code: BugCheck 124, {0, ffffdd8e461b2028, f60011c0, 40150} Probably caused by : GenuineIntel[/quote]
Processor Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz, 4001 Mhz, 4 Core(s), 8 Logical Processor(s)intelpep

Intel(R) Power Engine Plug-in Driver c:\windows\system32\drivers\intelpep.sys
intelppm Intel Processor Driver c:\windows\system32\drivers\intelppm.sys


Run Memtest86+ for at least 8 runs (this will take many hours, run overnight). Sometimes it takes runs in the teens to find memory problems so the longer the better.
Memtest86+ - Advanced Memory Diagnostic Tool

 

So I delete that from system32, then reinstall?

Will also run Memtest tonight before I go to bed. Is the problem likely related to the actual sticks?

 

Only delete the Intel drivers that you find using device manager or control panel.
For memory if problems are detected then both the ram and the dim/motherboard connections need to be evaluated. If a problem is found, it sometimes takes more than 8 runs (sometimes in the teens). All of the ram except for one stick is used. Then the ram is switched. By process of elimination then the good ram when used one at a time can then be switched to another dim. Unfortunately this can consume a lot of time. Running the studies overnight makes it a little easier.

Once you uninstall Intel driver you can use the Intel driver install tool unless the computer manufacturer has approved drivers.

Uninstalling the Intel® Graphics Driver and Intel® Display HDMI/Audio...

 

Can you provide us with the kernel memory dump please? Its located in C:\Windows\MEMORY.DMP.
You can upload it to an cloud service like dropbox or onedrive.

 

MEGA

 

the dump is broken, i cannot read it correctly. My advice is just waiting a few days if another bsod comes up. Then pls reupload again.

 

I've uninstalled every Intel driver I could find and still receive multiple blue screens.
Attachment 140762Attachment 140763
Also something interesting, despite how I uninstall the Intel drivers, upon each reboot... they're back:
Attachment 140773

Memory Dump: MEGA