BSOD due to HAL

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by Super Sarge, Aug 1, 2010.

  1. Super Sarge

    Super Sarge New Member

    Joined:
    Jun 4, 2009
    Messages:
    1,737
    Likes Received:
    64
    I have changed nothing I got this BSOOD at o401 AM on 08-01-2010 I know it concerns thw hardware application Layer (HAL) but that is all I can figure out. I have added no new equipment nor softwareView attachment 080110-48032-01.zip Any and all help is appreciated
     
  2. TorrentG

    TorrentG Banned

    Joined:
    May 31, 2010
    Messages:
    7,814
    Likes Received:
    372
    Ouch, a 0x124 hardware error:

    Code:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [E:\Temp\Rar$DI00.092\080110-48032-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Machine Name:
    Kernel base = 0xfffff800`0364c000 PsLoadedModuleList = 0xfffff800`03889e50
    Debug session time: Sun Aug  1 05:01:23.539 2010 (UTC - 4:00)
    System Uptime: 3 days 16:24:39.844
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ......................................
    Loading User Symbols
    Loading unloaded module list
    ..................................................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 124, {0, fffffa800ce3c028, fe000000, 300152}
    
    Probably caused by : hardware
    
    Followup: MachineOwner
    ---------
    
    4: 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: fffffa800ce3c028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000fe000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000300152, Low order 32-bits of the MCi_STATUS value.
    
    Debugging Details:
    ------------------
    Here's the best resource available about 0x124 stops:

    Stop 0x124 - what it means and what to try - Windows 7 Forums

    Please pay special attention to the first thing listed:

    "1) Ensure that none of the hardware components are overclocked. Hardware that is driven beyond its design specifications - by overclocking - can malfunction in unpredictable ways."
     

Share This Page

Loading...