Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Random restart (BSOD-AuthenticAMD)


  • Please log in to reply
2 replies to this topic

#1 Sitbon

Sitbon

  • Members
  • 9 posts
  • OFFLINE
  •  

Posted 28 May 2018 - 11:55 AM

Encloses here the contents of the error:
Thanks to all those who answered!
 
My System:
Dell inspiron 5555
 
Graphics Chipset - AMD Radeon R6 Graphics
Memory Size - 512 MB
Memory Type - DDR3
Core Clock - 800 MHz
Windows Version - Windows 10 (64 bit)
System Memory - 12 GB
CPU Type - AMD A10-8700P Radeon R6, 10 Compute Cores 4C+6G
 
 
1.

Machine Name:
Kernel base = 0xfffff802`dc412000 PsLoadedModuleList = 0xfffff802`dc7cf2f0
Debug session time: Mon May 28 10:44:05.230 2018 (UTC - 4:00)
System Uptime: 0 days 0:00:02.341
*******************************************************************************
*                                                                             *
*                        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: ffffb58439ec58f8, 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:
------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
ffff840b`78dd25b0 fffff802`dc8aa901 : 00000000`00000000 ffffb584`39ec58d0 ffffb584`28873550 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x7b
ffff840b`78dd2ae0 fffff802`dc6dd8e8 : ffffb584`39ec58d0 fffff802`dc51fb51 00000000`00000000 ffffb584`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x2d
ffff840b`78dd2b10 fffff802`dc6de56b : fffff802`dc7c04e0 ffffb584`28873550 ffffb584`28873550 fffff80a`41e59b30 : nt!WheapProcessWorkQueueItem+0x48
ffff840b`78dd2b50 fffff802`dc438445 : 00000000`00000500 ffffb584`393d8040 ffffb584`28873550 ffffb584`28873550 : nt!WheapWorkQueueWorkerRoutine+0x2b
ffff840b`78dd2b80 fffff802`dc4f3ae7 : ffffb584`393d8040 00000000`00000080 ffffb584`288c5200 ffffb584`393d8040 : nt!ExpWorkerThread+0xf5
ffff840b`78dd2c10 fffff802`dc5b1bc6 : ffffcf81`e6946180 ffffb584`393d8040 fffff802`dc4f3aa0 00000003`cbec0000 : nt!PspSystemThreadStartup+0x47
ffff840b`78dd2c60 00000000`00000000 : ffff840b`78dd3000 ffff840b`78dcd000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

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

2.
Machine Name:
Kernel base = 0xfffff802`d861a000 PsLoadedModuleList = 0xfffff802`d89d72f0
Debug session time: Mon May 28 11:04:43.446 2018 (UTC - 4:00)
System Uptime: 0 days 0:00:02.558
*******************************************************************************
*                                                                             *
*                        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: ffff9b09a36158f8, 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:
------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
ffff9683`e404c5b0 fffff802`d8ab2901 : 00000000`00000000 ffff9b09`a36158d0 ffff9b09`920cfd20 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x7b
ffff9683`e404cae0 fffff802`d88e58e8 : ffff9b09`a36158d0 fffff802`d8727b51 00000000`00000000 ffff9b09`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x2d
ffff9683`e404cb10 fffff802`d88e656b : fffff802`d89c84e0 ffff9b09`920cfd20 ffff9b09`920cfd20 fffff802`d8c25e80 : nt!WheapProcessWorkQueueItem+0x48
ffff9683`e404cb50 fffff802`d8640445 : 00000000`00000700 ffff9b09`a3727040 fffff802`d86b9d40 ffff9b09`920cfd20 : nt!WheapWorkQueueWorkerRoutine+0x2b
ffff9683`e404cb80 fffff802`d86fbae7 : ffff9b09`a3727040 00000000`00000080 ffff9b09`920b6440 ffff9b09`a3727040 : nt!ExpWorkerThread+0xf5
ffff9683`e404cc10 fffff802`d87b9bc6 : ffff8580`81e40180 ffff9b09`a3727040 fffff802`d86fbaa0 00000000`00000000 : nt!PspSystemThreadStartup+0x47
ffff9683`e404cc60 00000000`00000000 : ffff9683`e404d000 ffff9683`e4047000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

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

Edited by Sitbon, 28 May 2018 - 11:57 AM.


BC AdBot (Login to Remove)

 


#2 jcgriff2

jcgriff2

  • BSOD Kernel Dump Expert
  • 1,109 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey Shore
  • Local time:05:23 AM

Posted 29 May 2018 - 03:06 PM

Hi. . .

A 0x124 bugcheck BSOD is the new code (as of Windows Vista) for a Machine Check Exception. It is definitely related to catastrophic hardware failure.

0x124 BSODs are notoriously difficult to solve because the cause is simply "unknown hardware failure".

Unfortunately, the dumps are incapable of telling us which piece of hardware has failed. Dumps are only good for figuring out software problems.

All I can really do here is to give you some hardware diagnostic programs to run.The problem may also be with other hardware parts such as the motherboard or PSU for which there are no software tests.

Regards. . .

jcgriff2
Microsoft MVP 2009-2015
Microsoft Windows Insider MVP 2018 - Present

#3 Sitbon

Sitbon
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  

Posted 31 May 2018 - 03:05 PM

ok, got it,

thanks.

but one question:

what is AuthenticAMD error?

 

Someone told me it was an unsupported component on a motherboard or something, its right?






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users