Windows 10: BSOD WHEA_UNCORRECTABLE_ERROR (hal.dll+395cf / ntoskrnl.exe+25bfbd)

BSOD WHEA_UNCORRECTABLE_ERROR (hal.dll+395cf / ntoskrnl.exe+25bfbd)
Bug Check Code: 0x00000124

Hello,
I started getting these BSOD's after updating my Windows 10 after 2 months of no usage at all.Windows downloaded and installed a lot of updates, maybe it is unrelated but I did a lot of research but I couldn't identify the root-cause of this. Did various tests on CPU and memtest for RAM for 5 hours all went OK. I would love to get some help to pinpoint what's wrong so I can change the defective parts or upgrade the whole system. Thanks in advance.
(ASUS RIVE Intel 3930K)

:)

 

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.

 

There were 3 bsod mini dump files that were debugged.
All 3 displayed WHEA 124 error.
This usually indicates a hardware problem.

1) open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /restorehealth
4) chkdsk /scan
5) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread


Sometimes there are problems in the bios that produce bsod.

6) The bios in your computer: BIOS Version/Date American Megatrends Inc. 4901, 14.05.2014

Please check to see if this is the most up to date version.

7) To ensure that there are no improper bios settings please reset the bios.

Sometimes there can be failure to boot after resetting the bios.

8) So please make sure your files are backed up.

9) Please make a backup image with Macrium:
Macrium Software | Macrium Reflect Free: Macrium Software | Your Image is Everything

10) And please create a restore point.

How to Clear Your Computers CMOS to Reset BIOS Settings:
How to Clear Your Computers CMOS to Reset BIOS Settings

3 Ways to Reset Your BIOS - wikiHow:
3 Ways to Reset Your BIOS - wikiHow

11) When testing for WHEA hardware errors we need to systematically check CPU, GPU, memory and drive.

Once the bios is reset and there is no overclocking:


12) Choose one of the temperature monitoring software applications: Speecy, HW monitor, Speed fan:


Speccy - Free Download - Piriform: Speccy - System Information - Free Download


HWMONITOR | Softwares | CPUID: HWMONITOR | Softwares | CPUID


SpeedFan - Access temperature sensor in your computer: SpeedFan - Access temperature sensor in your computer


13) download and install the Intel Processor Diagnostic Tool
When the test completes please use the Microsoft snipping tool to post an image into the thread.


Download Intel® Processor Diagnostic Tool: Download Intel® Processor Diagnostic Tool
The Intel® Processor Diagnostic Tool: The Intel® Processor Diagnostic Tool




14) Run Prime95 - Stress Test Your CPU
Prime95 - Stress Test Your CPU Windows 10 Performance Maintenance Tutorials


Prime95 - Stress Test Your CPU Windows 10 Performance Maintenance Tutorials


Please use the Microsoft snipping tool to post images into the thread.


Take Screenshot in Windows 10 Windows 10 General Tips Tutorials




15) Run memtest86+ version 5.01 for at least 8 passes.
This may take hours so plan to run it overnight.
Plan 1 -2 hours /GB RAM


Memtest86+ - Advanced Memory Diagnostic Tool


Microsoft Community


When Memtest86+ has completed 8 or more passes make an image of the results to post into the thread.
MemTest86+ - Test RAM Windows 10 BSOD Tutorials


MemTest86+ needs to be run for at least 8 complete passes for conclusive results.
There are significant false negatives if less than passes are made.
The more passes the better.
A false negative is getting a pass with malfunctioning RAM.
Running a test for less than 8 passes is wasting time as it is an inadequate test.
Set it running before you go to bed and leave it overnight.
We're looking for zero errors here.
Even a single error will indicate RAM failure.


Use a camera or a smart phone camera to take a photo of the result and post the image into the thread.


Addition:
If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
If errors show up and you see them a lot later, no problem, the errors don't affect the test.


RAM should not fail under any circumstances (exception for overclocking)


16) Run HD Sentinel:
Hard Disk Sentinel - HDD health and temperature monitoring
When it has completed please use the Microsoft snipping to make an image and post into the thread.
Take Screenshot in Windows 10 Windows 10 General Tips Tutorials


17) Run FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials


Please make note of the importance of temperature monitoring and aborting the test in the GPU link.


FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials:
FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials


All of these test should be done with the bios reset and no over clocking.


For each of the above tests please record maximum temperatures.
Also record the duration of testing.


And please make sure that you use the Microsoft snipping tool to post images of each into the thread.
Take Screenshot in Windows 10 Windows 10 General Tips Tutorials




18) Ten Forums System Specificiations (Specs)
Please fill in your system specs
Please follow this tutorial and download the tool.
System Info - See Your System Specs - Windows 7 Help Forums
The tool will give you detailed information about your system specs, please fill in your system specs more completely including other used stuff like mouse, keyboard, monitor, case, etc.
The PSU, cooling and other stuff are NOT mentioned in the tool but are need to if not already entered.


In the left corner below in your post you find 'My System Specs'. After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.






Code: BugCheck 124, {0, ffff868e59d04028, b2000000, 7c000402}Probably caused by : GenuineIntel[/quote] Code: WHEA_UNCORRECTABLE_ERROR (124)A fatal hardware error has occurred. Parameter 1 identifies the type of errorsource that reported the error. Parameter 2 holds the address of theWHEA_ERROR_RECORD structure that describes the error conditon.Arguments:Arg1: 0000000000000000, Machine Check ExceptionArg2: ffff868e59d04028, Address of the WHEA_ERROR_RECORD structure.Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.Arg4: 000000007c000402, Low order 32-bits of the MCi_STATUS value.[/quote] Code: Section 0 : Processor Generic-------------------------------------------------------------------------------Descriptor @ ffff868e59d040a8Section @ ffff868e59d04180Offset : 344Length : 192Flags : 0x00000001 PrimarySeverity : FatalProc. Type : x86/x64Instr. Set : x64Error Type : Micro-Architectural ErrorFlags : 0x00CPU Version : 0x00000000000206d7Processor ID : 0x000000000000000a[/quote]

 

Thank you I am starting to do all above mentioned but a quick question before I start. I resetted the BIOS and plugged off all HDDs attached to the system ( I have 5 SATA HDDs) Only the OS SSD is running now , I am assuming this is the correct config to start with)

 

Microsoft Windows [Version 10.0.15063]
(c) 2017 Microsoft Corporation. All rights reserved.

C:\Windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\Windows\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.15063.0

Image Version: 10.0.15063.0

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\Windows\system32>chkdsk /scan
The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
158976 file records processed.
File verification completed.
3621 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
216358 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
28692 data files processed.
CHKDSK is verifying Usn Journal...
35071856 USN bytes processed.
Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

124453887 KB total disk space.
33809576 KB in 126568 files.
95728 KB in 28693 indexes.
0 KB in bad sectors.
264775 KB in use by the system.
65536 KB occupied by the log file.
90283808 KB available on disk.

4096 bytes in each allocation unit.
31113471 total allocation units on disk.
22570952 allocation units available on disk.

C:\Windows\system32>

 

Intel Processor Diagnostic Tool Test Run Time 05:04:39Attachment 148402Attachment 148404

 

Hello thanks for your help @zbook first of all,
I started the testing process doing prime95 now it's been running for 1 hour how long should I run it? Or will it complete itself?

 

I've Run Prime 95 For 2 Hours and 17 Minutes and no errors were found temps are attached tooAttachment 148417Attachment 148418Attachment 148419Attachment 148420Attachment 148421Attachment 148422

 

Prime95 is designed to run indefinitely and if there is an error it is supposed to abort testing.
Temperature monitoring by the end user is important to be able to abort testing if temperatures remain high.
If there are no problems running prime 95 you can end testing at 3 hours. If you want you can run it longer as the longer the testing the more it will test the stability of the system.

See this link for more information: Prime95 - Stress Test Your CPU Windows 10 Performance Maintenance Tutorials

For all drives test them with HD tune and post images into the thread.
This way any hardware can be ruled in/ruled out as a source of the bsod.
For any HD also run Sea tools for windows on the drives using SMART, short and long generic tests:

How to use SeaTools for Windows
http://www.seagate.com/support/downl...ls-win-master/
How to use SeaTools for Windows
http://www.seagate.com/support/downloads/seatools/

For any new bsod please post a new zip: BSOD - Posting Instructions - Windows 10 Forums

 

I was doing memtest+ overnight and unfortunately I think there was a power outage
so I started it over again. Will post the remaining tests as soon as possible.

 

Running memtest and 44th minute I got this, not an error but interruption
please advise me what to do next.


Attachment 148526

 

On the memtest86+ there was no information about unexpected interrupt-halting cpu. On the web there were varied opinions. See if you can test the RAM in another computer.

 

Unfortunately I don't have such an option *Sad

 

I am running the memtest+ overnight again so far so good. Tomorrow I will update again Attachment 148752