Windows 10: Bsod "whea_uncorrectable_error (124)"

Only two dumps in the zip file, should be more. There are 22 WHEA 124 entries in Event log. Are you running a program like CCleaner to cleanup your hard drive? If so, please stop until this is resolved.

Both dumps indicate a hardware CPU failure:

Code:

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: ffffa08986814028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000f60017c0, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000040150, Low order 32-bits of the MCi_STATUS value.

Code:

!errrec  ffffa08986814028
===============================================================================
Common Platform Error Record @ ffffa08986814028
-------------------------------------------------------------------------------
Record Id     : 01d37f2a7a4ed1ff
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 12/27/2017 15:54:16 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ ffffa089868140a8
Section       @ ffffa08986814180
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   : 0x00000000000906e9
Processor ID  : 0x0000000000000005

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

Local APIC Id : 0x0000000000000005
CPU Id        : e9 06 09 00 00 08 10 05 - 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  @ ffffa08986814240

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

Error         : ICACHEL0_IRD_ERR (Proc 5 Bank 0)
  Status      : 0xf60017c000040150
  Address     : 0x00007ffd6ef7db20
  Misc.       : 0x0000000000000000

Event log also shows hardware failure:

Code:

Event[16431]:
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2017-12-27T16:55:46.832
  Event ID: 19
  Task: N/A
  Level: Warning
  Opcode: Info
  Keyword: N/A
  User: S-1-5-19
  User Name: AUTORITE NT\SERVICE LOCAL
  Computer: LAPTOP-GREG
  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: 4

The details view of this entry contains further information.

Event[16432]:
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2017-12-27T16:56:46.825
  Event ID: 19
  Task: N/A
  Level: Warning
  Opcode: Info
  Keyword: N/A
  User: S-1-5-19
  User Name: AUTORITE NT\SERVICE LOCAL
  Computer: LAPTOP-GREG
  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: 4

The details view of this entry contains further information.

It's possible this is caused by a device driver but unlikely. You can try setting up Driver Verifier as follows to see what it shows:

===================================================
Driver Verifier is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The required result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.
Machines exposed to Driver Verifier will run very sluggishly due to the stress being applied to the drivers.

Driver Verifier - Enable and Disable in Windows 10

Pay close attention to PART TWO and make sure the correct boxes are checked.

Warning:
It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.

Always create a Restore Point prior to enabling Driver Verifier.

What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it. If you get a BSOD, rerun dm_log_collector and upload the resulting zip file.
===================================================

If this doesn't show anything then you need to start thinking about replacing the motherboard since it's impossible to replace the CPU on a laptop board.

You have a 500GB SSD though, the dumps don't take up that much room, a little over 1MB per. Change your CCleaner setup to not delete minidumps then delete them manually later.



If the laptop is still under warranty then definitely start the RMA process.