Recurring WHEA Uncorrectable Error

Mitch4003 · 22 Aug 2018

Hello all,

A few hours ago I experienced the latest in a series of BSOD's. The cause is always a WHEA error. This last time the error occurred I was away from my laptop for about 5 minutes when it happened. I had Firefox open and I believe I had JRiver Media Center running too but it wasn't playing anything at the time. The other times had the BSOD taking place when I had Firefox open and browsing the web, with VLC running in the background playing a video file. So, the CPU was under load at those times, though it didn't appear to be under heavy load. As far as how many times this has happened, I'm not 100% sure but I'd say about 6 times just during 2018. I don't think it started before this year. That's a summary of what's happened. Send a reply if you need more info, of course.

I thank you for your time

Ztruker · 23 Aug 2018

Dump shows a fatal hardware error:

Code:

3: kd> !errrec ffffdc05c4bf9028
===============================================================================
Common Platform Error Record @ ffffdc05c4bf9028
-------------------------------------------------------------------------------
Record Id     : 01d43a47fc64de4c
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 8/23/2018 0:45:35 (UTC)
Flags         : 0x00000000

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

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Cache error
Operation     : Generic
Flags         : 0x00
Level         : 3
CPU Version   : 0x00000000000306d4
Processor ID  : 0x0000000000000003

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

Local APIC Id : 0x0000000000000003
CPU Id        : d4 06 03 00 00 08 10 03 - 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  @ ffffdc05c4bf9240

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

Error         : GCACHELG_ERR_ERR (Proc 3 Bank 5)
  Status      : 0xbe0000000100110b
  Address     : 0x000000009e000000
  Misc.       : 0x0000001084000086

Check the manufacturers web site for a BIOS update. Other than that I think you have a bad CPU.

What is the full model number of the laptop? Aspire E5-772-??????

Mitch4003 · 23 Aug 2018

Hi Ztruker,

I have tried to get a BIOS update through Acer's Community forum, but never got a reply. I remember asking for an update last year using the forum (for this same type of problem) and I was able to get one then and for awhile it worked. So I have no idea why I got nothing but crickets this time. The full model # is: E5-772-554Y. I had previously thought this all had to do with a bad driver or drivers, but it just might be a bit more serious than that.

zbook · 23 Aug 2018

See if you can use this link with serial number to find the drivers and BIOS:
Download Drivers and Manuals | Acer Official Site

Mitch4003 · 24 Aug 2018

Already beat you to it zbook. There hasn't been a BIOS update for this computer since last year, when I requested it.

Thanks anyway!

Ztruker · 24 Aug 2018

I see the latest is 1.15 on that site as you said: https://www.acer.com/ac/en/US/conten...oduct/5992?b=1

What about the Chipset driver? Have you installed that?

Code:

Date: 2016/04/27
Version: 10.1.1.13
Vendor: Intel
Size: 4.7 MB

ThrashZone · 24 Aug 2018

Hi,
Do you monitor your temperatures ?
You might start
Download Core Temp - MajorGeeks

Mitch4003 · 24 Aug 2018

Hi Rich and ThrashZone,

I'm pretty sure that Chipset driver has been updated because I recall updating all of the outdated drivers after I bought this laptop. I've been trying to find out for sure but I'm not having any luck. I have looked in System Info and in the Device Manager thus far. As far as monitoring CPU temps, I am running Core Temp already and have been for at least the past year. Before that, I was using Speccy and other various monitoring software and I've never had an overheating alert or event.

rickchristine · 03 Sep 2018

Mitch4003 said:

Hi Rich and ThrashZone,
I'm pretty sure that Chipset driver has been updated because I recall updating all of the outdated drivers after I bought this laptop. I've been trying to find out for sure but I'm not having any luck. I have looked in System Info and in the Device Manager thus far. As far as monitoring CPU temps, I am running Core Temp already and have been for at least the past year. Before that, I was using Speccy and other various monitoring software and I've never had an overheating alert or event.

Yes, update the drivers and check the CPU temps is necessary. After that, I think you can try to use the CHKDSK to scan the System C disk chkdsk /r c:. This may help.

And if you updated your system recently, you can try to uninstall the recent update to see if it works.

fireberd · 03 Sep 2018

I had that error on an i7 3770 CPU desktop. All diagnostics passed including Intel CPU diagnostic. As I do PC repair I had spare parts and started a "shotgun" approach. I replaced power supply with no change, I replaced motherboard with no change, did a clean Windows install with no change. Finally replaced the CPU and the problem was resolved. The CPU was under warranty and Intel eventually replaced it.