crash and automatic reboot on Win 8

Discussion in 'Windows 8 Blue Screen of Death (BSOD)' started by Greg Zyxog, Dec 8, 2014.

  1. Greg Zyxog

    Greg Zyxog New Member

    Joined:
    Dec 8, 2014
    Messages:
    1
    Likes Received:
    0
    I usually leave the machine running. It is set to produce a memory dump and to "automatically restart" upon system failure.

    When I came to the computer this afternoon, it said it had crashed and restared.

    Here's a summary of the machine by Speccy:

    Summary


    Operating System

    Windows 8 64-bit


    CPU

    AMD A10-6700 93 °C

    Richland 32nm Technology


    RAM

    7.00GB Single-Channel DDR3 @ 799MHz (11-11-12-28)


    Motherboard

    ASUSTeK COMPUTER INC. M11BB (FM2 )49 °C


    Graphics

    SA300/350/360= (1920x1080@60Hz)

    768MB ATI AMD Radeon HD 8670D (ASUStek Computer Inc) 20 °C


    Storage

    931GB TOSHIBA DT01ACA100 SATA Disk Device (SATA) 36 °C

    1863GB Western Digital WDC WD20 EARX-32PASB0 SATA Disk Device (SATA)34 °C


    Optical Drives

    ASUS DVD RAM GH95N SATA CdRom Device


    Audio

    Realtek High Definition Audio



    Here's an analysis by WinDbg...


    Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.

    Loading Dump File [C:\Windows\Minidump\120714-78811-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: srv*c:\symbols* h... : // msdl . microsoft . ...download/symbols

    //
    // Comment: I had to prevent the previous line from being a link because the
    // website won't allow me to include a link.
    //
    Executable search path is:
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 9200.16912.amd64fre.win8_gdr.140502-1507
    Machine Name:
    Kernel base = 0xfffff800`89076000 PsLoadedModuleList = 0xfffff800`89342aa0
    Debug session time: Sun Dec 7 05:43:35.416 2014 (UTC - 5:00)
    System Uptime: 0 days 0:00:06.095
    Loading Kernel 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, fffffa8008ce84f8, 0, 0}

    Probably caused by : AuthenticAMD

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


    <then I proceeded with the detailed debugging >

    2: 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: fffffa8008ce84f8, 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:
    ------------------


    BUGCHECK_STR: 0x124_AuthenticAMD

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

    PROCESS_NAME: System

    CURRENT_IRQL: 0

    STACK_TEXT:
    fffff880`02d39530 fffff800`893e4767 : 00000000`00000000 fffffa80`08ce84d0 fffff800`8935f0a0 00000002`00000005 : nt!WheapCreateLiveTriageDump+0x81
    fffff880`02d39a60 fffff800`891d6da7 : fffffa80`08ce84d0 fffff800`891d7d00 fffff800`8935f0a0 fffff800`30455600 : nt!WheapCreateTriageDumpFromPreviousSession+0x3b
    fffff880`02d39a90 fffff800`891d7d25 : fffff800`8935f040 fffff800`891d7d00 fffff800`8935f0a0 fffffffe`9a5f4400 : nt!WheapProcessWorkQueueItem+0x57
    fffff880`02d39ad0 fffff800`8910e411 : fffff800`892fc190 fffffa80`06d00b00 fffffa80`08cdc600 fffffa80`079c8300 : nt!WheapWorkQueueWorkerRoutine+0x25
    fffff880`02d39b00 fffff800`890a3075 : 19909630`26f3e2e9 00000000`00000080 fffff800`8910e2d0 fffffa80`06d00b00 : nt!ExpWorkerThread+0x142
    fffff880`02d39b90 fffff800`891573b6 : fffff880`02a00180 fffffa80`06d00b00 fffff880`02a0be40 fffffa80`06d20700 : nt!PspSystemThreadStartup+0x59
    fffff880`02d39be0 00000000`00000000 : fffff880`02d3a000 fffff880`02d33000 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: 0x124_AuthenticAMD_PROCESSOR_CACHE_PRV

    BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR_CACHE_PRV

    Followup: MachineOwner

    --------- ----------------------------------------------------------------------------

    I don't really know what conclusions to draw from that or what to do.

    I would appreciate any advice.
     
  2. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,828
    Likes Received:
    1,565

Share This Page

Loading...