Fall Creators Update random reboots WHEA_UNCORRECTABLE_ERROR (124)

dancedar · 16 Nov 2017

Same-no issue before on machine for 2yrs, not overclocked-'stock' everything. Thought it might be heat but no warnings and happens when relatively cool.

axe0 · 16 Nov 2017

dancedar said:

I, OP, definitely don't get a BSOD. Infact, I don't get any *SOD at all, just an instant power off and boot procedure begins, no bsod, no errors, no shutting down, nothing.

Crash is like the Microsoft link, ie 'No hardware errors, no BSOD, no critical event log entries before, just a spontaneous reboot then upon restart'

If it wasn't a BSOD, I wouldn't be able to provide suggestions, whether it being diagnostic suggestions or possible solutions, without asking for a lot more data :)

sowen said:

I found it amusing that axe0 said you got a BSOD even though you explicitly stated you didn't, and claimed the posting on Microsoft was different because it explicitly stated no BSOD.

A few facts,
- BSODs aren't always visible, mainly with graphics related crashes or with SSDs it can sometimes be too fast to notice.
- A hardware related BSOD is mentioned in the thread title
- Mentioned in post #14, @dancedar provided BSOD information in the first post
- Multiple logs about it, see below.

Code:

2017-10-29T11:03:06.165		The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffe10b804538f8, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\Minidump\102917-35843-01.dmp. Report Id: e632e8aa-0a1e-413b-ac08-3b5dd001002d.
2017-11-01T11:25:03.657		The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffd880d6a208f8, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\Minidump\110117-34187-01.dmp. Report Id: 8b5aff6a-2566-42f0-8ca6-dd92bf632e13.
2017-11-08T12:16:53.566		The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffc98e1b4d38f8, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\Minidump\110817-47734-01.dmp. Report Id: cb31ca4b-80f1-4f8d-9adf-299acaaf797e.
2017-11-16T19:51:39.817		The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffa88c79e758f8, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\Minidump\111617-28515-01.dmp. Report Id: 143d7edd-2688-4aa6-b378-11f8d8c3b705.

The latest dump is the same as the others

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: ffffa88c79e758f8, 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.

Debugging Details:
------------------


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  10.0.16299.64 (WinBuild.160101.0800)

DUMP_TYPE:  2

BUGCHECK_P1: 0

BUGCHECK_P2: ffffa88c79e758f8

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BUGCHECK_STR:  0x124_AuthenticAMD

CPU_COUNT: 4

CPU_MHZ: 705

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 15

CPU_MODEL: 60

CPU_STEPPING: 1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  DESKTOP-3NDMJ43

ANALYSIS_SESSION_TIME:  11-16-2017 23:27:59.0828

ANALYSIS_VERSION: 10.0.16299.15 x86fre

STACK_TEXT:  
ffff8802`de1e25b0 fffff803`4ec4c635 : ffffa88c`78077700 ffffa88c`79e758d0 ffffa88c`78056190 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x7b
ffff8802`de1e2ae0 fffff803`4ea9c278 : ffffa88c`79e758d0 fffff803`4ed99910 fffff803`00000000 ffffa88c`78079180 : nt!WheapCreateTriageDumpFromPreviousSession+0x2d
ffff8802`de1e2b10 fffff803`4ea9cd9b : fffff803`4eb6dd20 fffff803`4eb6dd20 ffffa88c`78056190 fffff803`4e933340 : nt!WheapProcessWorkQueueItem+0x48
ffff8802`de1e2b50 fffff803`4e857e05 : ffffa88c`78056190 ffffa88c`78077700 fffff803`4eb95900 ffffa88c`78056190 : nt!WheapWorkQueueWorkerRoutine+0x2b
ffff8802`de1e2b80 fffff803`4e843f87 : ffffa88c`78163040 00000000`00000080 ffffa88c`780de480 ffffa88c`78077700 : nt!ExpWorkerThread+0xf5
ffff8802`de1e2c10 fffff803`4e984676 : ffff9181`70a79180 ffffa88c`78077700 fffff803`4e843f40 00000000`00000000 : nt!PspSystemThreadStartup+0x47
ffff8802`de1e2c60 00000000`00000000 : ffff8802`de1e3000 ffff8802`de1dd000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


THREAD_SHA1_HASH_MOD_FUNC:  26acd050bd9f055d0a04825d57b9e0e6be9c1a07

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  e1ca14ad460db17fee32f4b133c79439b72309bb

THREAD_SHA1_HASH_MOD:  30a3e915496deaace47137d5b90c3ecc03746bf6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_BUS_PRV

BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_BUS_PRV

PRIMARY_PROBLEM_CLASS:  0x124_AuthenticAMD_PROCESSOR_BUS_PRV

TARGET_TIME:  2017-11-16T19:51:16.000Z

OSBUILD:  16299

OSSERVICEPACK:  64

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2017-10-25 05:06:03

BUILDDATESTAMP_STR:  160101.0800

BUILDLAB_STR:  WinBuild

BUILDOSVER_STR:  10.0.16299.64

ANALYSIS_SESSION_ELAPSED_TIME:  868

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x124_authenticamd_processor_bus_prv

FAILURE_ID_HASH:  {6fd7875b-9a1b-9e09-d6d6-816026a875c8}

Followup:     MachineOwner
---------

Debug session time: Thu Nov 16 20:51:16.132 2017 (UTC + 1:00)
System Uptime: 0 days 0:00:07.871
0: kd> !errrec ffffa88c79e758f8
===============================================================================
Common Platform Error Record @ ffffa88c79e758f8
-------------------------------------------------------------------------------
Record Id     : 01d35f143f67a872
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 11/16/2017 19:51:16 (UTC)
Flags         : 0x00000002 PreviousError

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ ffffa88c79e75978
Section       @ ffffa88c79e75a50
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   : 0x0000000000660f01
Processor ID  : 0x0000000000000000

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

Local APIC Id : 0x0000000000000000
CPU Id        : 01 0f 66 00 00 08 04 00 - 0b 32 d8 7e 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  @ ffffa88c79e75b10

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

Error         : BUSLG_OBS_ERR_*_NOTIMEOUT_ERR (Proc 0 Bank 4)
  Status      : 0xf2000010000b0c0f

Please fill in your system specs

Please follow this tutorial and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely including PSU, cooling and other used stuff like mouse, keyboard, monitor, case, etc.
The PSU, cooling and other stuff are NOT mentioned in the tool.

In the left corner below in your post you find 'My System Specs'. After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.

sowen · 17 Nov 2017

axe0 said:

A few facts,
- BSODs aren't always visible, mainly with graphics related crashes or with SSDs it can sometimes be too fast to notice.
- A hardware related BSOD is mentioned in the thread title
- Mentioned in post #14, @dancedar provided BSOD information in the first post
- Multiple logs about it, see below.

The point is, I said it looked like the same issue as in the Microsoft thread, but you said it wasn't because it stated there was no BSOD, then you continued by saying not all BSODs are visible. So how do you know it's not the same? Perhaps the Microsoft post was also a 'non-visible' BSOD. The effects described matched this thread.

BSODs always take a few moments to display, so even if the graphics card failed, there would still be a few moments pause before reboot. If the reboot is immediate, there is NO BSOD, although a log will still be produced on startup as a result of the unexpected restart.

axe0 · 17 Nov 2017

They have looked at the eventlog which should've shown a bugcheck.
Before the kernel event 41 there are events about the system initializing, then a bugcheck event (if any), then the events the user mentions (COM/CLSID) and other logs. The user would've noticed it as the bugcheck event is marked as 'error' in eventviewer.

Sometimes when my own laptop BSODs, there isn't always a moment of pause yet there are always logs about a BSOD. This is especially at startup.

dancedar · 17 Nov 2017

axe0 said:

Please fill in your system specs

Please follow this tutorial and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely including PSU, cooling and other used stuff like mouse, keyboard, monitor, case, etc.

Done. With driver verifier, does it not produce any output save trying to force a crash which can then be picked up in a minidump?

axe0 · 17 Nov 2017

If driver verifier finds any driver violating something, it does nothing more than instruct Windows to crash the system. The process where driver verifier finds something and notifies Windows, is saved in the dump.

dancedar · 17 Nov 2017

axe0 said:

If driver verifier finds any driver violating something, it does nothing more than instruct Windows to crash the system. The process where driver verifier finds something and notifies Windows, is saved in the dump.

Got it, thanks. I guess I'll have to run that again and how it does something during the next week or so, though it didn't cause one for the last three times. Surely if it's crashing something should be in the minidump to show what's causing it?

axe0 · 17 Nov 2017

Yep.

niknik · 17 Nov 2017

ARG2: These dumps
Arg2: ffffa88c79e75[b]8f8 CPER
Arg2: ffffc98e1b4d3[b]8f8 CPER
Arg2: ffffd880d6a20[b]8f8 CPER
ffffa88c`79e758f8 52455043 ffff0210 0003ffff 00000001 CPER............

nt
fffff803`4e944c12 43 50 45 52 41 0f b7 40-40 66 89 41 32 8d 42 d8 CPERA..@@f.A2.B.
fffff803`4ea9ba1b 43 50 45 52 75 69 0f b7-49 0a 8d 04 c9 8d 04 c5 CPERui..I.......
fffff803`4ea9c4e6 43 50 45 52 66 89 43 04-33 c0 66 89 43 0a 48 b8 CPERf.C.3.f.C.H.
fffff803`4f0688e2 43 50 45 52 4e 4f 44 45-3d 00 cc cc cc cc 20 4d CPERNODE=..... M
PSHED
fffff80d`fd6a29cb 43 50 45 52 75 7f 3b 0d-61 4d 00 00 77 77 e8 32 CPERu.;.aM..ww.2
fffff80d`fd6a3e38 43 50 45 52 75 1c 48 8b-41 6c 48 ba ff ff ff ff CPERu.H.AlH.....

fffff803`4e81b000 fffff803`4f0ed000 nt (private pdb symbols) c:\symbols\ntkrnlmp.pdb\9830E2E80FBE4576B2F4B86D1C4BCD951\ntkrnlmp.pdb
Loaded symbol image file: ntkrnlmp.exe
Mapped memory image file: c:\symbols\ntoskrnl.exe\59EFFF9B8d2000\ntoskrnl.exe
Image path: ntkrnlmp.exe
Image name: ntkrnlmp.exe
Timestamp: Wed Oct 25 06:06:03 2017 (59EFFF9B)
CheckSum: 00835AD3
ImageSize: 008D2000
File version: 10.0.16299.64
Product version: 10.0.16299.64
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 1.0 App
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: ntkrnlmp.exe
OriginalFilename: ntkrnlmp.exe
ProductVersion: 10.0.16299.64
FileVersion: 10.0.16299.64 (WinBuild.160101.0800)
FileDescription: NT Kernel & System
LegalCopyright: © Microsoft Corporation. All rights reserved.
Mini Kernel Dump does not contain unloaded driver list

fffff80d`fd6a0000 fffff80d`fd6b7000 PSHED # (pdb symbols) c:\symbols\pshed.pdb\1615C7B06C05561040971F13D251452D1\pshed.pdb
Loaded symbol image file: PSHED.dll
Mapped memory image file: c:\symbols\PSHED.dll\FE1A7C4017000\PSHED.dll
Image path: PSHED.dll
Image name: PSHED.dll
Timestamp: ***** Invalid (FE1A7C40)
CheckSum: 00016E41
ImageSize: 00017000
File version: 10.0.16296.0
Product version: 10.0.16296.0
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: pshed.dll
OriginalFilename: pshed.dll
ProductVersion: 10.0.16296.0
FileVersion: 10.0.16296.0 (WinBuild.160101.0800)
FileDescription: Platform Specific Hardware Error Driver
LegalCopyright: © Microsoft Corporation. All rights reserved.
Mini Kernel Dump does not contain unloaded driver list

1. The file PSHED.DLL is part of the component that enables hardware errors to be generated.

dancedar · 18 Nov 2017

niknik said:

ARG2: These dumps
Arg2: ffffa88c79e75[b]8f8 CPER
Arg2: ffffc98e1b4d3[b]8f8 CPER
Arg2: ffffd880d6a20[b]8f8 CPER
ffffa88c`79e758f8 52455043 ffff0210 0003ffff 00000001 CPER............

FileDescription: Platform Specific Hardware Error Driver
LegalCopyright: © Microsoft Corporation. All rights reserved.
Mini Kernel Dump does not contain unloaded driver list

1. The file PSHED.DLL is part of the component that enables hardware errors to be generated.

Thanks for the details; are you saying pshed.dll is to blame?