Random Windows Shutdowns Error 0x124


  1. Posts : 11
    Windows 7 Ultimate x64
       #1

    Random Windows Shutdowns Error 0x124


    Hello, I recently got hit with some random Windows 7 shutdowns. Please help me diagnose this issue.

    Report from WhoCrashed:

    On Sun 6/2/2013 7:25:31 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\060213-29109-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x4ADE0C)
    Bugcheck code: 0x124 (0x0, 0xFFFFFA800667F8F8, 0x0, 0x0)
    Error: WHEA_UNCORRECTABLE_ERROR
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
    This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

    I attached my dump files in the post, I don't think it is a hardware issue, well, I did upgrade this computer a while back, but from the reliability monitor, the data does not correlate with the time of upgrade and the time of windows errors. From the time of Windows crashes shown on the monitor, I think it was around the time I installed a new hard drive, it has nothing on it except a few backup files. It does not seems like a hardware issue, but, I will check my PSU if needed. I think it was from the time I installed Nvidia Beta Drivers for my graphics card. Thank you!
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings. Also set the BIOS to default, too.
    How To Clear CMOS (Reset BIOS)

    The BIOS seems to be old.
    Code:
    BiosMajorRelease = 8
    BiosMinorRelease = 14
    BiosVendor = American Megatrends Inc.
    BiosVersion = 5.43   
    BiosReleaseDate = 09/10/2009
    SystemManufacturer = HP-Pavilion
    SystemProductName = FQ621AA-A2L a6752f
    SystemFamily = 103C_53316J
    Search in HP for any possible BIOS update.

    Test your RAM modules for possible errors.
    How to Test and Diagnose RAM Issues with Memtest86+
    Run memtest for at least 8 passes, preferably overnight.

    Stress test the Graphics Card using Furmark.
    Video Card - Stress Test with Furmark

    Stress test the CPU.
    Hardware - Stress Test With Prime95

    Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.

    Let us know the results.
    ____________________________________________________________________________________
    BSOD ANALYSIS:
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 124, {0, fffffa800673d028, b2000040, 800}
    
    Probably caused by : GenuineIntel
    
    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: 0000000000000000, Machine Check Exception
    Arg2: fffffa800673d028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000b2000040, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000800, Low order 32-bits of the MCi_STATUS value.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x124_GenuineIntel
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  f
    
    STACK_TEXT:  
    fffff880`03b6ba58 fffff800`03428a3b : 00000000`00000124 00000000`00000000 fffffa80`0673d028 00000000`b2000040 : nt!KeBugCheckEx
    fffff880`03b6ba60 fffff800`035eb443 : 00000000`00000001 fffffa80`0673ed30 00000000`00000000 fffffa80`0673ed80 : hal!HalBugCheckSystem+0x1e3
    fffff880`03b6baa0 fffff800`03428700 : 00000000`00000728 fffffa80`0673ed30 fffff880`03b6be30 fffff880`03b6be00 : nt!WheaReportHwError+0x263
    fffff880`03b6bb00 fffff800`03428052 : fffffa80`0673ed30 fffff880`03b6be30 fffffa80`0673ed30 00000000`00000000 : hal!HalpMcaReportError+0x4c
    fffff880`03b6bc50 fffff800`03427f0d : 00000000`00000004 00000000`00000001 fffff880`03b6beb0 00000000`00000000 : hal!HalpMceHandler+0x9e
    fffff880`03b6bc90 fffff800`0341be88 : fffff880`03b63180 fffffa80`04418e40 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
    fffff880`03b6bcc0 fffff800`034d34ec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
    fffff880`03b6bcf0 fffff800`034d3353 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
    fffff880`03b6be30 fffff800`034d7b12 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
    fffff880`03b92fb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterrupt+0x32
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: GenuineIntel
    
    IMAGE_NAME:  GenuineIntel
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS
    
    BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS
    
    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 11
    Windows 7 Ultimate x64
    Thread Starter
       #3

    Reply


    I did notice that my games crashed right after exiting them, and I was also overclocked so I turned the Mhz down on my graphics card and that fixed the issue right away, I am guessing that the major of the errors came from this, the issue I now have was that latest one as it does not seem like a hardware error. I do remember using a program called "JetClean" to clean my computer and the problems started there, I did undo the changes made but it seems like that has worked to a certain extent. I will test the hardware and try to find a BIOS update. Thanks!
      My Computer


  4. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #4

    Brainiac777 said:
    I did notice that my games crashed right after exiting them, and I was also overclocked so I turned the Mhz down on my graphics card and that fixed the issue right away,
    If it is the situation, you can leave the rest for now. Observe how the computer is running at stock configuration and let us know. Go for the next depending on the situation.

    Brainiac777 said:
    I am guessing that the major of the errors came from this, the issue I now have was that latest one as it does not seem like a hardware error. I do remember using a program called "JetClean" to clean my computer and the problems started there, I did undo the changes made but it seems like that has worked to a certain extent. I will test the hardware and try to find a BIOS update. Thanks!
      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 15:08.
Find Us