Windows 10: 3 bugcheck crashes in 1 week. (The bugcheck was: 0x00000124 )

The latest dump bugcheck was WHEA 0x124 which is typically hardware problems.
All of the bugchecks posted have been consistent.


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: ffffc70729b578f8, Address of the WHEA_ERROR_RECORD structure. Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value. Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.[/quote]
Code: Common Platform Error Record @ ffffc70729b578f8------------------------------------------------------------------------------- Record Id : 01d378317f3ebfc8 Severity : Fatal (1) Length : 928 Creator : Microsoft Notify Type : Machine Check Exception Timestamp : 12/18/2017 18:53:35 (UTC) Flags : 0x00000002 PreviousError =============================================================================== Section 0 : Processor Generic ------------------------------------------------------------------------------- Descriptor @ ffffc70729b57978 Section @ ffffc70729b57a50 Offset : 344 Length : 192 Flags : 0x00000001 Primary Severity : Fatal Proc. Type : x86/x64 Instr. Set : x64 Error Type : BUS error Operation : Generic Flags : 0x00 Level : 3 CPU Version : 0x0000000000600f20 Processor ID : 0x0000000000000000 =============================================================================== Section 1 : x86/x64 Processor Specific ------------------------------------------------------------------------------- Descriptor @ ffffc70729b579c0 Section @ ffffc70729b57b10 Offset : 536 Length : 128 Flags : 0x00000000 Severity : Fatal Local APIC Id : 0x0000000000000000 CPU Id : 20 0f 60 00 00 08 06 00 - 0b 32 98 3e ff fb 8b 17 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 @ ffffc70729b57b10 =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ ffffc70729b57a08 Section @ ffffc70729b57b90 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : BUSLG_OBS_ERR_*_NOTIMEOUT_ERR (Proc 0 Bank 4) Status : 0xf2000010000b0c0f[/quote]
Code: Event[1756]: Log Name: System Source: Microsoft-Windows-WHEA-Logger Date: 2017-12-18T18:53:58.711 Event ID: 20 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-19 User Name: NT AUTHORITY\LOCAL SERVICE Computer: DESKTOP-TITQKKQ Description: A fatal hardware error has occurred. Component: AMD Northbridge Error Source: Machine Check Exception Error Type: 11 Processor APIC ID: 0 The details view of this entry contains further information.[/quote]

 

I have had the same issue however with different hardware. In my case graphics driver software was the culprit. Check to see if anything graphic card related might be conflicting with Windows 10 settings. It's a bit of a longshot but thought it might be worth mentioning just the same.

 

Update: no crashes since the last (crash-free for 5 days). I noticed my PC was shutting down slower than before, starting up faster and I also noticed that sometimes programs I had open when I shutdown would start up automatically when I started the PC. I found out this is a feature called "fast start up" which got turned on by the Fall Creator's update (which I got 2 days before the first crash on the 1st of December). I've turned fast start up off and everything's good!

 

In the next few days please post a new zip into the thread:
BSOD - Posting Instructions - Windows 10 Forums

 

Seeing many similar questions too in the community exactly identical to your issue. As here, I advised all of them to disable fast startup and I guess no one responded back saying the issue persists.
Looks like 1709 is conflicting with devices using AMD processors.

 

That would make sense, I've seen other people with 0x124 errors using AMD fx-series processors after fall creator's update, including myself. I ran all the usual hardware tests, furmark, intelburntest, memtest86, and hdd tests, and my PC flew through all of them. Also reinstalled windows 10 and had the same 0x124 bsods.

 

Please update the thread with a new zip:
BSOD - Posting Instructions - Windows 10 Forums

 

Here you go

 

Looking good.

The last WHEA 0x 124 was on 12/18/2017
The last crash was also on 12/18/2017.

There was a one day problem with the video card driver:

Code: Event[3045]: Log Name: System Source: Display Date: 2018-01-03T15:30:58.136 Event ID: 4101 Task: N/A Level: Warning Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-TITQKKQ Description: Display driver nvlddmkm stopped responding and has successfully recovered.[/quote]