BSOD WHEA_UNCORRECTABLE_ERROR hal.dll+37203 ntoskrnl.exe

BSODHunter · 24 Jun 2017

I dont know if its good to confuse the user with so much Info. I think doing it step by step would be more helpful. Your advices are very good. But just let the user try one or two things after another. When I began i thought that "Genuineintel" has somehting to do with Intel drivers but it isnt in most cases. It just descripes the processor type and point to an hardware problem. At AMD system U will See "genuineamd" but no AMD drivers. The "caused by" section isnt the only thing u have to look at. U have to know how to debug whea errors. Its decriped in the tenforums bsod Tutorial.

philc43 · 24 Jun 2017

@BSODHunter I totally agree, analysis and troubleshooting is a step by step approach. This particular error is actually revealed by analysis of the error record and I showed the result in post #15. A faulty CPU is the most likely explanation and should be tested first. Try Prime95 if you want to do more testing.

zbook · 24 Jun 2017

The CPU is likely problematic per philc43's post.
There was a lot of information in the subsequent post.
It was various options to narrow down the misbehaving hardware/driver.
Some of it was later edited to reduce confusion but I see your point.
The step by step would be less confusing.
The prime95 may be able to confirm the CPU problem.

axe0 · 24 Jun 2017

@zbook, start using following commands when debugging a dump
- !analyze -v
- !thread
- dps {limit} {base}

See the Tenforums BSOD basics tutorial to find out what is meant with {limit} and {base}.
Learn using these commands, learn what they tell you and you'll come a lot further.

To show what @philc43 means, the second parameter is the one you want to dump out for the 0x124.
It shows why the CPU called for a BSOD event, it does NOT say what the cause is.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffff8e03e365e028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000f6000480, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000040150, Low order 32-bits of the MCi_STATUS value.


2: kd> !errrec ffff8e03`e365e028
===============================================================================
Common Platform Error Record @ ffff8e03e365e028
-------------------------------------------------------------------------------
Record Id     : 01d2e47146313ad0
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 6/13/2017 18:22:02 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ ffff8e03e365e0a8
Section       @ ffff8e03e365e180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Cache error
Operation     : Instruction Execute
Flags         : 0x00
Level         : 0
CPU Version   : 0x00000000000506e3
Processor ID  : 0x0000000000000002

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ ffff8e03e365e0f0
Section       @ ffff8e03e365e240
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000002
CPU Id        : e3 06 05 00 00 08 10 02 - bf fb fa 7f ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ ffff8e03e365e240

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ ffff8e03e365e138
Section       @ ffff8e03e365e2c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : ICACHEL0_IRD_ERR (Proc 2 Bank 0)
  Status      : 0xf600048000040150
  Address     : 0x000003ca91b8af0a
  Misc.       : 0x0000000000000000

24 Jun 2017

I. Yes, I did have that many yesterday.

2. It passed the stress testing 100%.

3. A lot, more than there are dumps.

I'll uninstall them again later, I guess. CPU is in warranty, I'm just reluctant to send the whole computer back.

What looks to be the issue with memory?

24 Jun 2017

Wow. I didn't see the third page... I also ran Prime95 a week ago and it went off without a hitch...

zbook · 25 Jun 2017

This is a count of the bsod by post and listed by date:
On post#1:
05/27: 1
06/03: 1

On post #7:
06/13: 2

On post #19
06/17: 4
06/18: 1
06/19: 2
06/21: 1
06/22: 11
06/23: 31

Total reported zip file bsod: 54

1) Which bsod were spontaneous?
2) Which bsod were using typical software applications and which ones using uncommon software applications?
3) Which ones were with windows driver verifier?
4) Which link for the customized settings was used for conifguring windows driver verifier?
5) Have you been doing any over clocking?
6) Have you been using either hardware or software raid?
7) Has the bios ever been modified?
8) When was the last time the bios was reset?

Philc43 has reported the WHEA hardware error is likely hardware failure:
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred.

The event logs have numerous events reporting: A corrected hardware error has occurred. Processor Core Cache Hierarchy Error

This is an example:

Event[23744]:
Log Name: System
Source: Microsoft-Windows-WHEA-Logger
Date: 2017-06-23T21:47:05.825
Event ID: 19
Task: N/A
Level: Warning
Opcode: Info
Keyword: N/A
User: S-1-5-19
User Name: NT AUTHORITY\LOCAL SERVICE
Computer: Ashley
Description:
A corrected hardware error has occurred.

Reported by component: Processor Core
Error Source: Corrected Machine Check
Error Type: Cache Hierarchy Error
Processor APIC ID: 2

The details view of this entry contains further information.

The event logs have numerous events reporting: The speed of processor X is being limited by system firmware. The processor has been in this reduced performance state for Y seconds since the last report.

This is an example:

Event[23697]:
Log Name: System
Source: Microsoft-Windows-Kernel-Processor-Power
Date: 2017-06-23T21:08:59.337
Event ID: 37
Task: N/A
Level: Warning
Opcode: Info
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: Ashley
Description:
The speed of processor 4 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 20 seconds since the last report.

Based on the debugging displaying WHEA, and the event logs it seems highly likely that the CPU is suspect. The IPDT and prime 95 stress test did not display failures.
Every test has true and false positives, and true and false negatives, as well as accuracy and inaccuracy.

With an active warranty and based on what is in the thread I would get the CPU replaced. I think all of the forum members would do the same.

The bsod debugging either displayed GenuineIntel or Memory. The Memtest86+ was ordered in the prior threads but the image of the runs and the results were not seen. Were you unable to do this test because of all of the bsod?
From 05/27 to 6/16 the bsod were infrequent. If you can possibly return to the computer environment that was present on those days maybe the Memtest86+ can be run for 8 or more passes to rule in or rule out memory problems?
Clean boot can be used to have the minimum number of drivers in use and possibly reduce the frequency or bsod.

Sometimes there are problems in the bios that produce bsod. The bios in your computer: BIOS Version/Date EVOC 1.05.03EVOC v1.5, 03/27/2016
To ensure that there are no improper bios settings please reset the bios.
Sometimes there can be failure to boot after resetting the bios. So please make sure your files are backed up. Please make a backup image with Macrium: Macrium Software | Macrium Reflect Free
And please create a restore point.

How to Clear Your Computers CMOS to Reset BIOS Settings
3 Ways to Reset Your BIOS - wikiHow

See this link about the false negative results using IPDT and Prime95 and the findings upon replacing the hardware with regards to performance the the event logs:

i7 6700K + Flood of Cache Hierarchy Error (Even... |Intel Communities

While the memory testing may be time consuming, and resetting the bios may be new to you, these additional tests appear to be important to Intel to complete the troubleshooting.

axe0 · 25 Jun 2017

Based on the debugging displaying WHEA, and the event logs it seems highly likely that the CPU is suspect. The IPDT and prime 95 stress test did not display failures.

Incorrect with the event logs.

These event logs you'll also see when no 0x124 crashes are around.

The event logs have numerous events reporting: The speed of processor X is being limited by system firmware. The processor has been in this reduced performance state for Y seconds since the last report.

This is an example:

Event[23697]:
Log Name: System
Source: Microsoft-Windows-Kernel-Processor-Power
Date: 2017-06-23T21:08:59.337
Event ID: 37
Task: N/A
Level: Warning
Opcode: Info
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: Ashley
Description:
The speed of processor 4 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 20 seconds since the last report.

This is close to a 0x124, but not there yet since a 0x124 is an uncorrected hardware error.
This event log is a bit similar to what is seen in the error structure of the 0x124, a core of the CPU has reported that a corrected hardware error occured.
In a 0x124, a core of the CPU has reported that an uncorrected hardware error occured, doesn't immediately make the CPU as the cause.

Event[23744]:
Log Name: System
Source: Microsoft-Windows-WHEA-Logger
Date: 2017-06-23T21:47:05.825
Event ID: 19
Task: N/A
Level: Warning
Opcode: Info
Keyword: N/A
User: S-1-5-19
User Name: NT AUTHORITY\LOCAL SERVICE
Computer: Ashley
Description:
A corrected hardware error has occurred.

Reported by component: Processor Core
Error Source: Corrected Machine Check
Error Type: Cache Hierarchy Error
Processor APIC ID: 2

When seeing CPU related event logs, do not confuse it with a CPU that may be faulty.

25 Jun 2017

1) Which bsod were spontaneous?
All of them.
2) Which bsod were using typical software applications and which ones using uncommon software applications?
They all happened regardless of what was open.
3) Which ones were with windows driver verifier?
A couple on the 24th. Ultimately made no difference.
4) Which link for the customized settings was used for conifguring windows driver verifier?
The one provided in this thread.
5) Have you been doing any over clocking?
Not in roughly eight months.
6) Have you been using either hardware or software raid?
No.
7) Has the bios ever been modified?
Yes, but it's also been reset since.
8) When was the last time the bios was reset?
A few days ago.

From 05/27 to 6/16 the bsod were infrequent.

No they weren't, I stated in my first post they were happening just as frequent. The only difference was that they weren't dumping properly. If anything, I get 30+ a day, but much of it depends on my patience.

If you can possibly return to the computer environment that was present on those does

Return it to the environment when I was having the same amount of problems...

maybe the Memtest86+ can be run for 8 or more passes to rule in or rule out memory problems?

I ran it overnight and it didn't detect any errors.

While the memory testing may be time consuming, and resetting the bios may be new to you, these additional tests appear to be important to Intel to complete the troubleshooting.

It's not new to me.

Also, I have just tried to format via Windows' reset option, but got the BSOD twice during driver installation (3%:6%). Currently loading a USB to see if, when booted from there, it persists. Also worth noting, I did not experience any crashes/BSOD while booting in safe mode; not once at any point. Then, roughly 40 seconds after booting normally, BSOD.

zbook · 25 Jun 2017

Please place the computer in clean boot:

Open administrative command prompt and type or copy and paste:
1) msconfig (in the pop up system configuration > move the dot from normal startup to selective startup > uncheck load startup items > click service tab > in left lower corner check hide all Microsoft services > in the lower right side click disable all > click apply or ok > do not reboot)

2) taskmgr (in the pop up task manager > click on the start up tab > click on status so that the column sorts with enable rising to the top > right click on each row with enable and change to disable)

3) shutdown /r (you will reboot the computer so that it is in clean boot)

https://support.microsoft.com/en-us/...oot-in-windows
How to perform a Clean Boot in Windows 10 - TechNet Articles - United States (English) - TechNet Wiki

Evaluate the boot times. Are they shorter, longer or the same. Evaluate shutdown times. Are they shorter, longer or the same.
Evaluate hangs. Are they more frequent, less frequent or the same. Evaluate bsod. Are they more frequent, less frequent, or the same?

For the memtest86+ how many runs were there?

Do you have a bootable windows 10 iso?
Download Windows 10