Computer restarts -- probable cause AuthenticAMD

eSEB · 22 Jun 2018

Hello,

Last week my Dell laptop began to restart occasionally. There was no discernible pattern regarding apps running, etc--I play no games and no new apps; usually only Word, Firefox, Foxit Reader are running. The debugger gave a WHEA_ERROR_RECORD at ffff908ab5f108f8 and fingered AuthenticAMD as the probable cause. My knowledge on these matters permits me to go no further than reporting that. I was preparing to send several minidump files using the little app supplied here, but after another sudden restart and long boot they disappeared from their folder. So I have attached the dump file as instructed from the last crash an hour or so ago and hope that (along with the many other details the app gathered) will be sufficient. Any help would be truly appreciated.

Thanks,

eSEB

Ztruker · 24 Jun 2018

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: ffff908ab5f108f8, 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

Code:

!errrec ffff908ab5f108f8
===============================================================================
Common Platform Error Record @ ffff908ab5f108f8
-------------------------------------------------------------------------------
Record Id     : 01d40a69ebf92f03
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 6/22/2018 20:45:22 (UTC)
Flags         : 0x00000002 PreviousError

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ ffff908ab5f10978
Section       @ ffff908ab5f10a50
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    @ ffff908ab5f109c0
Section       @ ffff908ab5f10b10
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  @ ffff908ab5f10b10

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

Error         : BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 4)
  Status      : 0xf600000000070f0f
  Address     : 0x00000000ff708700
  Misc.       : 0x0000000000000000

Here is the same error on a Win 7 system: BSOD (WHEA_UNCORRECTABLE_ERROR)

A lot of the suggestions in that thread apply here as well. Especially overheating, since this is a laptop. Use a can of compressed air and clean out the vents as well as you can. Do this several times.

Also, please fill out your system specs. See here: System Specs - Fill in at Ten Forums

The more information you can provide the better.

eSEB · 25 Jun 2018

Ztruker said:

A lot of the suggestions in that thread apply here as well. Especially overheating, since this is a laptop. Use a can of compressed air and clean out the vents as well as you can. Do this several times.

Also, please fill out your system specs. See here: System Specs - Fill in at Ten Forums

The more information you can provide the better.

Thanks. The temperature lowered a bit after using the compressed air. Waiting to see what happens. I also reverted back to an older driver for the Radeon R6, which was the only recent change to my computer--I had updated using the driver directly from AMD instead of the Dell-supplied driver, since Dell is so often behind on these things. I (mostly) filled in my system's specs as well--sorry about that.

Thanks again,

eSEB

Ztruker · 25 Jun 2018

One thing we can do is run Driver Verifier, see if that shakes anything out.

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

eSEB · 25 Jun 2018

Ztrucker,

It didn't take long to crash again--after two years, until recently, with zero crashes.

The temp wasn't particular high (52-54C) and the address of the error was different: ffffce0ee74e0038. More fully:

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: ffffce0ee74e0038, 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:
------------------

KEY_VALUES_STRING: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1

DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  10.0.17134.112 (WinBuild.160101.0800)

DUMP_TYPE:  2

BUGCHECK_P1: 0

BUGCHECK_P2: ffffce0ee74e0038

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:  HUMEAN-NATURE

ANALYSIS_SESSION_TIME:  06-25-2018 17:58:04.0368

ANALYSIS_VERSION: 10.0.17674.1000 amd64fre

STACK_TEXT:  
fffff908`cf7bf5b0 fffff802`9f525991 : 00000000`00000000 ffffce0e`e74e0010 ffffce0e`e50c6600 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x7b
fffff908`cf7bfae0 fffff802`9f358f88 : ffffce0e`e74e0010 fffff802`9f19c4c1 00000000`00000000 ffffce0e`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x2d
fffff908`cf7bfb10 fffff802`9f359c0b : fffff802`9f43b4e0 ffffce0e`e50c6600 ffffce0e`e50c6600 fffff806`e7aa72a0 : nt!WheapProcessWorkQueueItem+0x48
fffff908`cf7bfb50 fffff802`9f0d2315 : 00000000`00000100 ffffce0e`e702a700 fffff806`00000000 ffffce0e`00001200 : nt!WheapWorkQueueWorkerRoutine+0x2b
fffff908`cf7bfb80 fffff802`9f174cb7 : ffffce0e`e702a700 00000000`00000080 ffffce0e`e50c52c0 ffffce0e`e702a700 : nt!ExpWorkerThread+0xf5
fffff908`cf7bfc10 fffff802`9f22f7d6 : ffffb301`dff80180 ffffce0e`e702a700 fffff802`9f174c70 00000000`00000000 : nt!PspSystemThreadStartup+0x47
fffff908`cf7bfc60 00000000`00000000 : fffff908`cf7c0000 fffff908`cf7ba000 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:  2018-06-25T22:40:44.000Z

OSBUILD:  17134

OSSERVICEPACK:  112

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  784

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2018-06-08 04:00:00

BUILDDATESTAMP_STR:  160101.0800

BUILDLAB_STR:  WinBuild

BUILDOSVER_STR:  10.0.17134.112

ANALYSIS_SESSION_ELAPSED_TIME:  89b

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x124_authenticamd_processor_bus_prv

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

eSEB · 25 Jun 2018

The crash came again with a new address for the error. Giving the driver verifier a go.

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: ffffce0ee74e0038, 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:
------------------


KEY_VALUES_STRING: 1


STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  10.0.17134.112 (WinBuild.160101.0800)

DUMP_TYPE:  2

BUGCHECK_P1: 0

BUGCHECK_P2: ffffce0ee74e0038

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:  HUMEAN-NATURE

ANALYSIS_SESSION_TIME:  06-25-2018 17:58:04.0368

ANALYSIS_VERSION: 10.0.17674.1000 amd64fre

STACK_TEXT:  
fffff908`cf7bf5b0 fffff802`9f525991 : 00000000`00000000 ffffce0e`e74e0010 ffffce0e`e50c6600 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x7b
fffff908`cf7bfae0 fffff802`9f358f88 : ffffce0e`e74e0010 fffff802`9f19c4c1 00000000`00000000 ffffce0e`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x2d
fffff908`cf7bfb10 fffff802`9f359c0b : fffff802`9f43b4e0 ffffce0e`e50c6600 ffffce0e`e50c6600 fffff806`e7aa72a0 : nt!WheapProcessWorkQueueItem+0x48
fffff908`cf7bfb50 fffff802`9f0d2315 : 00000000`00000100 ffffce0e`e702a700 fffff806`00000000 ffffce0e`00001200 : nt!WheapWorkQueueWorkerRoutine+0x2b
fffff908`cf7bfb80 fffff802`9f174cb7 : ffffce0e`e702a700 00000000`00000080 ffffce0e`e50c52c0 ffffce0e`e702a700 : nt!ExpWorkerThread+0xf5
fffff908`cf7bfc10 fffff802`9f22f7d6 : ffffb301`dff80180 ffffce0e`e702a700 fffff802`9f174c70 00000000`00000000 : nt!PspSystemThreadStartup+0x47
fffff908`cf7bfc60 00000000`00000000 : fffff908`cf7c0000 fffff908`cf7ba000 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:  2018-06-25T22:40:44.000Z

OSBUILD:  17134

OSSERVICEPACK:  112

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  784

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2018-06-08 04:00:00

BUILDDATESTAMP_STR:  160101.0800

BUILDLAB_STR:  WinBuild

BUILDOSVER_STR:  10.0.17134.112

ANALYSIS_SESSION_ELAPSED_TIME:  89b

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x124_authenticamd_processor_bus_prv

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

Followup:     MachineOwner

eSEB · 26 Jun 2018

Driver Verifier crashed my computer fairly quickly. Or maybe not. The dump had no obvious references to any driver. It was identical to the original one I attached to the first post except for a different "stack_text" and "address of the WHEA_ERROR_RECORD structure," though I suppose those could be important differences. This crash was different in that the display froze for three to five minutes before restarting. The previous crash had momentary (1-2 secs) glitches--always a sudden and brief jerky movement of the cursor or a stuttering of any audio playing--and immediate restart. The temp was between 45 and 52C when it froze, though likely hotter by the time it restarted. I'm not sure where to look from here.

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: ffffe10722b3b8f8, 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:
------------------


KEY_VALUES_STRING: 1


STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  10.0.17134.112 (WinBuild.160101.0800)

DUMP_TYPE:  2

BUGCHECK_P1: 0

BUGCHECK_P2: ffffe10722b3b8f8

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:  HUMEAN-NATURE

ANALYSIS_SESSION_TIME:  06-26-2018 00:05:30.0113

ANALYSIS_VERSION: 10.0.17674.1000 amd64fre

STACK_TEXT:  
ffffc808`8e0ca5b0 fffff803`17b26991 : 00000000`00000000 ffffe107`22b3b8d0 ffffe107`20e95bd0 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x7b
ffffc808`8e0caae0 fffff803`17959f88 : ffffe107`22b3b8d0 fffff803`1779d4c1 00000000`00000000 ffffe107`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x2d
ffffc808`8e0cab10 fffff803`1795ac0b : fffff803`17a3c4e0 ffffe107`20e95bd0 ffffe107`20e95bd0 fffff809`0fa072a0 : nt!WheapProcessWorkQueueItem+0x48
ffffc808`8e0cab50 fffff803`176d3315 : 00000000`00000100 ffffe107`23f2a700 fffff809`00000000 ffffe107`00001200 : nt!WheapWorkQueueWorkerRoutine+0x2b
ffffc808`8e0cab80 fffff803`17775cb7 : ffffe107`23f2a700 00000000`00000080 ffffe107`20e8e040 ffffe107`23f2a700 : nt!ExpWorkerThread+0xf5
ffffc808`8e0cac10 fffff803`178307d6 : ffff8b01`58880180 ffffe107`23f2a700 fffff803`17775c70 00000000`00000000 : nt!PspSystemThreadStartup+0x47
ffffc808`8e0cac60 00000000`00000000 : ffffc808`8e0cb000 ffffc808`8e0c5000 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:  2018-06-26T04:48:25.000Z

OSBUILD:  17134

OSSERVICEPACK:  112

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  784

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2018-06-08 04:00:00

BUILDDATESTAMP_STR:  160101.0800

BUILDLAB_STR:  WinBuild

BUILDOSVER_STR:  10.0.17134.112

ANALYSIS_SESSION_ELAPSED_TIME:  a98

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x124_authenticamd_processor_bus_prv

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

Followup:     MachineOwner

eSEB · 26 Jun 2018

In Windows' Reliability Monitor, I find two report for each crash event. The second always gives the error location I've found in the dump files. The first might be redundant--information I am missing in the dump but that you guys easily see--but if not, I thought I'd put that information here in case it is useful.

The one paired with the event in the dump file I initially sent (from June 22) is this:

Code:

Problem Event Name:	LiveKernelEvent
Code:	141
Parameter 1:	ffff9f8af353f4a0
Parameter 2:	fffff80423a9fea8
Parameter 3:	0
Parameter 4:	0
OS version:	10_0_17134
Service Pack:	0_0
Product:	768_1
OS Version:	10.0.17134.2.0.0.768.101
Locale ID:	1033

The ones from last night, mentioned in my last post, and earlier yesterday were identical:

Code:

Problem Event Name:	LiveKernelEvent
Code:	141
Parameter 1:	ffff9a00b35ca4a0
Parameter 2:	fffff80691a9f948
...

I hope this is relevant and useful.

Thanks again,

eSEB

HonorGamer · 27 Jun 2018

eSEB,

Can you rerun the tool, and post up all the new files so we can get the new dumps?

eSEB · 27 Jun 2018

HonorGamer,

I've attached the gathered information. Thanks for your interest. The computer hasn't crashed since late Monday, but I haven't used it much since then either.

eSEB