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

Hello 1212 *Smile

I've just looked at the crash dumps from your last set of logfiles. Every crash is due to an error when the CPU is executing instructions in the L0 cache.

Code: Error Type : Cache error Operation : Instruction Execute Error : ICACHEL0_IRD_ERR (Proc 3 Bank 0)[/quote] The consistency of this error tends to suggest your CPU may be faulty. If it is still warranty try to get it replaced.

 

This link has the steps to modify windows so that you can turn off windows automatic updates of drivers and be able to manually install drivers:
Turn On or Off Device Driver Automatic Installation in Windows 10 Windows 10 Windows Update Activation Tutorials


The last bsod posted in the zip was on 6/13/2017.

Please post a new zip for any new bsod.

 

I updated all the drivers with Obsidian.
Here are all the recent minidumps.

 

The rar files I cannot open. If possible please use BSOD - Posting Instructions - Windows 10 Forums

 

Something happened to the log as so many of the minidump now have the same date.
Did you have that many bsod on 6/23/2017?

The bsod debugging points to Genuine Intel and memory.

See post 15 philc43 posted concerns about the CPU.

What happened when you used the Intel Processor Diagnostic Tool kit?
Did it pass or fail?
If it failed what was the cause?

How many spontaneous bsod have there been since 6/13/2017?

The debugging indicated GENUINE INTEL but did not specify which Intel driver may be at fault.
There are many Intel drivers on your computer and that would take a lot of time to individually uninstall and reinstall them.

You had already uninstalled many intel drivers.
However I don't think you had turned off windows automatic updating of the drivers.

Temporarily turn off windows updates for drivers:
Enable or Disable Driver Updates in Windows Update in Windows 10 Windows 10 Windows Update Activation Tutorials

Using device manger and the control panel you could attempt to uninstall and reinstall Intel drivers again:


If your files are backed up it may be easier to rule in or rule out the Intel CPU or drivers by the following:

Perform a clean install (delete partitions, format the drive, reinstall windows 10)
Do not perform windows updates.
Do not install any drivers.
Install two software programs for evaluating drivers: Bluescreen view and Whocrashed
Install two software programs for evaluating the CPU: IPDT and Prime95


In the left lower corner search type verifier, set up the custom settings for windows driver verifier, and run it to see if you can produce bsod with the fewest Intel drivers.
Then use Bluescreenview and Whocrashed to analyeze the bsod.
Send a new zip file with any new bsod minidump files for debugging.

Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

Or after the clean install instead use Prime95 and or IPDT for stress testing.



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


Prime95 - Stress Test Your CPU Windows 10 Performance Maintenance Tutorials Prime95 - Stress Test Your CPU Windows 10 Performance Maintenance Tutorials



Performing the testing after the clean install would reduce the software environment to a limited number of drivers and applications. There would be fewer drivers/applications to evaluate in the testing.

Have you already checked the warranty on the Intel CPU?
Are you files backed up? If not or if you additional back up options: Macrium Software | Macrium Reflect Free

 

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.

 

@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.

 

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.

 

@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[/quote]

 

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?

 

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

 

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.

 

Incorrect with the event logs.

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

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.

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

 

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.

 

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