Differences

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

--- blog:laptop_hard_reboot [2017/06/22 12:06] – created brett
+++ blog:laptop_hard_reboot [2017/06/22 12:30] (current) – brett
@@ Line 1: / Line 1: @@
 ====== Laptop Hard Reboot ======
+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.
+As this is the 2nd time its happened in less than 2 week this is really starting to cause me problems as I'm loosing work. You can see the last event 4/24/2017 on the reliability history report below.
+{{:blog:reliabilityhistory.png|}}
+Clicking on the **view technical details** reveals this snippet of information
+<code>
+The computer has rebooted from a bugcheck.
+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.
+</code>
+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
+  * 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.
+{{:blog:8minidumps.png|}}
+After installing the WDK we need to fire up windbg which can be found here.
+{{:blog:windbg.png|}}
+Pulling the 0505 minidump into windbg this is what it tells us.
+<code>
+Microsoft (R) Windows Debugger Version 10.0.15063.0 AMD64
+Copyright (c) Microsoft Corporation. All rights reserved.
+Loading Dump File [C:\Windows\Minidump\050517-14718-01.dmp]
+Mini Kernel Dump File: Only registers and stack trace are available
+Symbol search path is: srv*
+Executable search path is:
+Windows 10 Kernel Version 10586 MP (4 procs) Free x64
+Product: WinNt, suite: TerminalServer SingleUserTS
+Built by: 10586.839.amd64fre.th2_release.170303-1605
+Machine Name:
+Kernel base = 0xfffff803`d0218000 PsLoadedModuleList = 0xfffff803`d04f5c90
+Debug session time: Fri May  5 13:51:37.032 2017 (UTC - 4:00)
+System Uptime: 0 days 0:00:02.748
+Loading Kernel Symbols
+..
+Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
+Run !sym noisy before .reload to track down problems loading symbols.
+.............................................................
+..
+Loading User Symbols
+Mini Kernel Dump does not contain unloaded driver list
+*******************************************************************************
+*                                                                             *
+*                        Bugcheck Analysis                                    *
+*                                                                             *
+*******************************************************************************
+Use !analyze -v to get detailed debugging information.
+BugCheck 124, {0, ffffe000f3f6c838, 0, 0}
+Probably caused by : AuthenticAMD
+Followup:     MachineOwner
+---------
+: kd> !analyze -v
+*******************************************************************************
+*                                                                             *
+*                        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: ffffe000f3f6c838, 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.10586.839 (th2_release.170303-1605)
+DUMP_TYPE:  2
+BUGCHECK_P1: 0
+BUGCHECK_P2: ffffe000f3f6c838
+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:  ENGLAND1
+ANALYSIS_SESSION_TIME:  05-05-2017 14:34:37.0456
+ANALYSIS_VERSION: 10.0.15063.0 amd64fre
+STACK_TEXT:
+ffffd000`ab3245b0 fffff803`d05c77cd : 00000000`00000000 ffffe000`f3f6c810 fffff803`d04e96a0 fffff803`d05aa340 : nt!WheapCreateLiveTriageDump+0x81
+ffffd000`ab324ae0 fffff803`d0428c94 : ffffe000`f3f6c810 ffffe000`f3f73030 ffffd000`ab324af8 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x2d
+ffffd000`ab324b10 fffff803`d0429dd9 : fffff803`d04e9640 fffff803`d04e9640 fffff803`d04e96a0 fffff803`d028d710 : nt!WheapProcessWorkQueueItem+0x48
+ffffd000`ab324b50 fffff803`d025dcf9 : fffff803`d05aa200 ffffe000`f3bb8040 fffff803`00000000 ffffe000`f42fca48 : nt!WheapWorkQueueWorkerRoutine+0x25
+ffffd000`ab324b80 fffff803`d02cd9b5 : 00000205`b4bbbdff 00000000`00000080 ffffe000`f2427680 ffffe000`f3bb8040 : nt!ExpWorkerThread+0xe9
+ffffd000`ab324c10 fffff803`d035fae6 : fffff803`d0534180 ffffe000`f3bb8040 fffff803`d02cd974 00000000`00000000 : nt!PspSystemThreadStartup+0x41
+ffffd000`ab324c60 00000000`00000000 : ffffd000`ab325000 ffffd000`ab31f000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
+STACK_COMMAND:  kb
+THREAD_SHA1_HASH_MOD_FUNC:  26acd050bd9f055d0a04825d57b9e0e6be9c1a07
+THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  5e1e1a155874296ef3d407b143c830e84a016e94
+THREAD_SHA1_HASH_MOD:  30a3e915496deaace47137d5b90c3ecc03746bf6
+FOLLOWUP_NAME:  MachineOwner
+MODULE_NAME: AuthenticAMD
+IMAGE_NAME:  AuthenticAMD
+DEBUG_FLR_IMAGE_TIMESTAMP:  0
+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-05-05T17:51:37.000Z
+OSBUILD:  10586
+OSSERVICEPACK:  839
+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-03-03 23:13:02
+BUILDDATESTAMP_STR:  170303-1605
+BUILDLAB_STR:  th2_release
+BUILDOSVER_STR:  10.0.10586.839
+ANALYSIS_SESSION_ELAPSED_TIME:  b84
+ANALYSIS_SOURCE:  KM
+FAILURE_ID_HASH_STRING:  km:0x124_authenticamd_processor_bus_prv
+FAILURE_ID_HASH:  {6fd7875b-9a1b-9e09-d6d6-816026a875c8}
+Followup:     MachineOwner
+---------
+</code>
+Decoding that ARG2 from the WHEA_UNCORRECTABLE_ERROR (124)
+  * http://www.tomshardware.com/answers/id-2196742/bluescreen-authenticamd-windows-64bytes.html
+<code>
+: kd> !errrec ffffe000f3f6c838
+===============================================================================
+Common Platform Error Record @ ffffe000f3f6c838
+-------------------------------------------------------------------------------
+Record Id     : 01d2c5c83ca54560
+Severity      : Fatal (1)
+Length        : 928
+Creator       : Microsoft
+Notify Type   : Machine Check Exception
+Timestamp     : 5/5/2017 17:51:37 (UTC)
+Flags         : 0x00000002 PreviousError
+===============================================================================
+Section 0     : Processor Generic
+-------------------------------------------------------------------------------
+Descriptor    @ ffffe000f3f6c8b8
+Section       @ ffffe000f3f6c990
+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    @ ffffe000f3f6c900
+Section       @ ffffe000f3f6ca50
+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
+Proc. Info 0  @ ffffe000f3f6ca50
+===============================================================================
+Section 2     : x86/x64 MCA
+-------------------------------------------------------------------------------
+Descriptor    @ ffffe000f3f6c948
+Section       @ ffffe000f3f6cad0
+Offset        : 664
+Length        : 264
+Flags         : 0x00000000
+Severity      : Fatal
+Error         : BUSLG_OBS_ERR_*_NOTIMEOUT_ERR (Proc 0 Bank 4)
+  Status      : 0xfa000010000b0c0f
+</code>
+REF
+https://answers.microsoft.com/en-us/windows/forum/windows_7-performance/help-windows-7-bsod-system-service-exception/7f165f52-d13b-4c1f-8160-f8483727c874?page=2
+So my options are either:
+  * Your RAM is faulty (Bank 4 = 4th DIMM slot). Run Memtest for NO LESS than ~8 passes (several hours):
+  * Your motherboard is faulty, and will need to be replaced.
+Either way its a hardware problem. Others reporting the same
+  * https://www.tenforums.com/bsod-crashes-debugging/40306-random-restarts-0x124-dump.html
+Digging deeper: ref https://davidcmoisan.wordpress.com/2010/07/01/bad-hardware-day-more-on-hardware-bluescreens/
+<code>
+: kd> .formats 0xfa000010000b0c0f
+Evaluate expression:
+  Hex:     fa000010`000b0c0f
+  Decimal: -432345495507366897
+  Octal:   1750000001000002606017
+  Binary:  11111010 00000000 00000000 00010000 00000000 00001011 00001100 00001111
+  Chars:   ........
+  Time:    ***** Invalid FILETIME
+  Float:   low 1.01452e-039 high -1.66154e+035
+  Double:  -4.53808e+279
+</code>
+Wonder if this is heat related as I had this set to Passive as the FAN was noisy. Probably not that would imply that this laptop would never run on batteries ! We will change it back to ACTIVE and see if that helps any and I'll put up with the FAN spinning for a while.
+{{: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.