Windows 7 - Windows has recovered from an unexpected shutdown


  1. Posts : 3
    Windows 7 Ultimate 32bit
       #1

    Windows 7 - Windows has recovered from an unexpected shutdown


    Hello, I'm facing this problem with my newly bought pc (1 month old), somehow even only after installation of the OS and standard hardware drivers. I've tried to update the graphics driver to the latest version (got it from asus.com) but the prob still persist.

    Appreciate anyone's help here with a familiar experience...thanks so much...
    Information provided below for your reference:

    OS Windows 7 Ultimate 32bit (Full Retail Version) 1st Installation.
    CPU AMD PHENOM II X4 945 3.00Ghz Motherboard ASUS M4A88T-M/USB3 880G CHIPSET Memory KINGSTON DDR3 1333 MHZ 2GB X 2 Graphics Card(s) ASUS EAH5670 1GB DDR5 Sound Card Built-in Monitor(s) Displays SAMSUNG LED EX1920 Screen Resolution N/A Hard Drives WESTERN DIGITAL SATA 1GB (GREEN) PSU COOLERMASTER 550W Case COOLERMASTER USP-100
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #2

    SapphireX said:
    Hello, I'm facing this problem with my newly bought pc (1 month old), somehow even only after installation of the OS and standard hardware drivers. I've tried to update the graphics driver to the latest version (got it from asus.com) but the prob still persist.

    Appreciate anyone's help here with a familiar experience...thanks so much...
    Information provided below for your reference:

    OS Windows 7 Ultimate 32bit (Full Retail Version) 1st Installation.
    CPU AMD PHENOM II X4 945 3.00Ghz Motherboard ASUS M4A88T-M/USB3 880G CHIPSET Memory KINGSTON DDR3 1333 MHZ 2GB X 2 Graphics Card(s) ASUS EAH5670 1GB DDR5 Sound Card Built-in Monitor(s) Displays SAMSUNG LED EX1920 Screen Resolution N/A Hard Drives WESTERN DIGITAL SATA 1GB (GREEN) PSU COOLERMASTER 550W Case COOLERMASTER USP-100

    These are all blamed on hardware. read here.

    Your .dmp file shows a stop error of 0x124 which is a general hardware error .. A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress. You can read more on this error and what to try here... Stop 0x124 - what it means and what to try Stop 0x124 - what it means and what to try

    Thanks


    Ken

    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\101710-22230-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
    *http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16385.x86fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0x82a00000 PsLoadedModuleList = 0x82b48810
    Debug session time: Sun Oct 17 10:06:16.880 2010 (GMT-4)
    System Uptime: 0 days 0:00:07.472
    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, 86281574, 0, 0}
    
    Probably caused by : hardware
    
    Followup: MachineOwner
    ---------
    
    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: 00000000, Machine Check Exception
    Arg2: 86281574, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 00000000, Low order 32-bits of the MCi_STATUS value.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x124_AuthenticAMD
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    8d98bcc4 82acefc5 86281558 82b67c28 82b67c20 nt!WheapCreateTriageDumpFromPreviousSession+0x32
    8d98bce4 82acfdef 82b67c20 86281558 82b67c50 nt!WheapProcessWorkQueueItem+0x56
    8d98bd00 82a6df2b 82b67c20 00000000 851a4a70 nt!WheapWorkQueueWorkerRoutine+0x1f
    8d98bd50 82c0e66d 00000001 bb38fb68 00000000 nt!ExpWorkerThread+0x10d
    8d98bd90 82ac00d9 82a6de1e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: hardware
    
    IMAGE_NAME:  hardware
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    FAILURE_BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_BUS_PRV
    
    BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_BUS_PRV
    
    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 10,200
    MS Windows 7 Ultimate SP1 64-bit
       #3

    The following assumes that you have a copy of the bios beep codes for your motherboard in front of you.

    Disconnect everything, and I mean everything except for the power supply unit from your motherboard.

    This means remove all memory, disconnect the keyboard, disconnect the display device.

    Now hopefully you will get a bios code.

    If you don't contact the supplier regarding returning the motherboard.

    If you get a bios beep code, then correct the problem. Probably the beep code will say that you need memory. Install one and only memory stick or memory pair if that is the smallest possible amount.

    Keep working thru the bios beep codes, connecting more and more.

    Let us know what you find out.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 10:54.
Find Us