blog:laptop_hard_reboot

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
blog:laptop_hard_reboot [2017/06/22 12:14] – brettblog:laptop_hard_reboot [2017/06/22 12:30] (current) – brett
Line 1: Line 1:
 ====== Laptop Hard Reboot ====== ====== Laptop Hard Reboot ======
  
-Model: HP EliteBook 745 G3+Model: **HP EliteBook 745 G3**
  
 For a number of months my laptop has done what I can only describe as a hard boot. For no apparent reasons it would power cycle. No windows shutdown message, no warning, its as if somebody has come along and pulled the power cord or held down a reset button. For a number of months my laptop has done what I can only describe as a hard boot. For no apparent reasons it would power cycle. No windows shutdown message, no warning, its as if somebody has come along and pulled the power cord or held down a reset button.
Line 10: Line 10:
  
 Clicking on the **view technical details** reveals this snippet of information Clicking on the **view technical details** reveals this snippet of information
- +<code> 
-''The computer has rebooted from a bugcheck.  +The computer has rebooted from a bugcheck.  
 The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffe000f3f6c838, 0x0000000000000000, 0x0000000000000000).  The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffe000f3f6c838, 0x0000000000000000, 0x0000000000000000). 
 A dump was saved in: C:\WINDOWS\Minidump\050517-14718-01.dmp. Report Id: e55192e8-8d9d-45c1-8c03-e14e66640510. A dump was saved in: C:\WINDOWS\Minidump\050517-14718-01.dmp. Report Id: e55192e8-8d9d-45c1-8c03-e14e66640510.
-'' +</code>
 Well at least windows agrees with me it was not shutdown correctly. Lets see if we can find out why. Well at least windows agrees with me it was not shutdown correctly. Lets see if we can find out why.
  
 We are going to need some additional windows tools to read that minidump We are going to need some additional windows tools to read that minidump
- +  * https://support.microsoft.com/en-us/help/315263/how-to-read-the-small-memory-dump-file-that-is-created-by-windows-if-a-crash-occurs
-https://support.microsoft.com/en-us/help/315263/how-to-read-the-small-memory-dump-file-that-is-created-by-windows-if-a-crash-occurs+
 I've been keeping a log but the minidump directory has these occasions time stamped for me. As you can see this is the 8th time this has happened. I've been keeping a log but the minidump directory has these occasions time stamped for me. As you can see this is the 8th time this has happened.
  
Line 64: Line 62:
  
 Use !analyze -v to get detailed debugging information. Use !analyze -v to get detailed debugging information.
- 
 BugCheck 124, {0, ffffe000f3f6c838, 0, 0} BugCheck 124, {0, ffffe000f3f6c838, 0, 0}
- 
 Probably caused by : AuthenticAMD Probably caused by : AuthenticAMD
- 
 Followup:     MachineOwner Followup:     MachineOwner
 --------- ---------
- 
 2: kd> !analyze -v 2: kd> !analyze -v
 ******************************************************************************* *******************************************************************************
Line 91: Line 85:
 Debugging Details: Debugging Details:
 ------------------ ------------------
- 
  
 DUMP_CLASS: 1 DUMP_CLASS: 1
- 
 DUMP_QUALIFIER: 400 DUMP_QUALIFIER: 400
- 
 BUILD_VERSION_STRING:  10.0.10586.839 (th2_release.170303-1605) BUILD_VERSION_STRING:  10.0.10586.839 (th2_release.170303-1605)
- 
 DUMP_TYPE:  2 DUMP_TYPE:  2
- 
 BUGCHECK_P1: 0 BUGCHECK_P1: 0
- 
 BUGCHECK_P2: ffffe000f3f6c838 BUGCHECK_P2: ffffe000f3f6c838
- 
 BUGCHECK_P3: 0 BUGCHECK_P3: 0
- 
 BUGCHECK_P4: 0 BUGCHECK_P4: 0
- 
 BUGCHECK_STR:  0x124_AuthenticAMD BUGCHECK_STR:  0x124_AuthenticAMD
- 
 CPU_COUNT: 4 CPU_COUNT: 4
- 
 CPU_MHZ: 705 CPU_MHZ: 705
- 
 CPU_VENDOR:  AuthenticAMD CPU_VENDOR:  AuthenticAMD
- 
 CPU_FAMILY: 15 CPU_FAMILY: 15
- 
 CPU_MODEL: 60 CPU_MODEL: 60
- 
 CPU_STEPPING: 1 CPU_STEPPING: 1
- 
 CUSTOMER_CRASH_COUNT:  1 CUSTOMER_CRASH_COUNT:  1
- 
 DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
- 
 PROCESS_NAME:  System PROCESS_NAME:  System
- 
 CURRENT_IRQL:  0 CURRENT_IRQL:  0
- 
 ANALYSIS_SESSION_HOST:  ENGLAND1 ANALYSIS_SESSION_HOST:  ENGLAND1
- 
 ANALYSIS_SESSION_TIME:  05-05-2017 14:34:37.0456 ANALYSIS_SESSION_TIME:  05-05-2017 14:34:37.0456
- 
 ANALYSIS_VERSION: 10.0.15063.0 amd64fre ANALYSIS_VERSION: 10.0.15063.0 amd64fre
  
Line 148: Line 120:
  
 STACK_COMMAND:  kb STACK_COMMAND:  kb
- 
 THREAD_SHA1_HASH_MOD_FUNC:  26acd050bd9f055d0a04825d57b9e0e6be9c1a07 THREAD_SHA1_HASH_MOD_FUNC:  26acd050bd9f055d0a04825d57b9e0e6be9c1a07
- 
 THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  5e1e1a155874296ef3d407b143c830e84a016e94 THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  5e1e1a155874296ef3d407b143c830e84a016e94
- 
 THREAD_SHA1_HASH_MOD:  30a3e915496deaace47137d5b90c3ecc03746bf6 THREAD_SHA1_HASH_MOD:  30a3e915496deaace47137d5b90c3ecc03746bf6
- 
 FOLLOWUP_NAME:  MachineOwner FOLLOWUP_NAME:  MachineOwner
- 
 MODULE_NAME: AuthenticAMD MODULE_NAME: AuthenticAMD
- 
 IMAGE_NAME:  AuthenticAMD IMAGE_NAME:  AuthenticAMD
- 
 DEBUG_FLR_IMAGE_TIMESTAMP:  0 DEBUG_FLR_IMAGE_TIMESTAMP:  0
- 
 FAILURE_BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_BUS_PRV FAILURE_BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_BUS_PRV
- 
 BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_BUS_PRV BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_BUS_PRV
- 
 PRIMARY_PROBLEM_CLASS:  0x124_AuthenticAMD_PROCESSOR_BUS_PRV PRIMARY_PROBLEM_CLASS:  0x124_AuthenticAMD_PROCESSOR_BUS_PRV
- 
 TARGET_TIME:  2017-05-05T17:51:37.000Z TARGET_TIME:  2017-05-05T17:51:37.000Z
- 
 OSBUILD:  10586 OSBUILD:  10586
- 
 OSSERVICEPACK:  839 OSSERVICEPACK:  839
- 
 SERVICEPACK_NUMBER: 0 SERVICEPACK_NUMBER: 0
- 
 OS_REVISION: 0 OS_REVISION: 0
- 
 SUITE_MASK:  272 SUITE_MASK:  272
- 
 PRODUCT_TYPE:  1 PRODUCT_TYPE:  1
- 
 OSPLATFORM_TYPE:  x64 OSPLATFORM_TYPE:  x64
- 
 OSNAME:  Windows 10 OSNAME:  Windows 10
- 
 OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS
- 
 OS_LOCALE:   OS_LOCALE:  
- 
 USER_LCID:  0 USER_LCID:  0
- 
 OSBUILD_TIMESTAMP:  2017-03-03 23:13:02 OSBUILD_TIMESTAMP:  2017-03-03 23:13:02
- 
 BUILDDATESTAMP_STR:  170303-1605 BUILDDATESTAMP_STR:  170303-1605
- 
 BUILDLAB_STR:  th2_release BUILDLAB_STR:  th2_release
- 
 BUILDOSVER_STR:  10.0.10586.839 BUILDOSVER_STR:  10.0.10586.839
- 
 ANALYSIS_SESSION_ELAPSED_TIME:  b84 ANALYSIS_SESSION_ELAPSED_TIME:  b84
- 
 ANALYSIS_SOURCE:  KM ANALYSIS_SOURCE:  KM
- 
 FAILURE_ID_HASH_STRING:  km:0x124_authenticamd_processor_bus_prv FAILURE_ID_HASH_STRING:  km:0x124_authenticamd_processor_bus_prv
- 
 FAILURE_ID_HASH:  {6fd7875b-9a1b-9e09-d6d6-816026a875c8} FAILURE_ID_HASH:  {6fd7875b-9a1b-9e09-d6d6-816026a875c8}
  
Line 212: Line 154:
 --------- ---------
 </code> </code>
-Ref http://www.tomshardware.com/answers/id-2196742/bluescreen-authenticamd-windows-64bytes.html 
 Decoding that ARG2 from the WHEA_UNCORRECTABLE_ERROR (124) Decoding that ARG2 from the WHEA_UNCORRECTABLE_ERROR (124)
 +  * http://www.tomshardware.com/answers/id-2196742/bluescreen-authenticamd-windows-64bytes.html
 <code> <code>
 2: kd> !errrec ffffe000f3f6c838 2: kd> !errrec ffffe000f3f6c838
Line 304: Line 245:
 {{:blog:cpucooling.png|}} {{:blog:cpucooling.png|}}
  
 +That did not help I'm still suffering random reboots latest happened 16-Jun-2017
 +  
 +{{:blog:reliabilityhistory2.png|}}
 +
 +This machine is being returned I cannot tolerate a computer randomly rebooting.
  • blog/laptop_hard_reboot.1498133652.txt.gz
  • Last modified: 2017/06/22 12:14
  • by brett