Restores didn't cure my BSOD 0x0000007E


  1. Posts : 1
    Win 7 Home Premium 64bit
       #1

    Restores didn't cure my BSOD 0x0000007E


    Well, 0x0000007E was the most recent...also have had 0x0000001A, and perhaps more. I have had a BSOD almost every day for weeks, and no amount of restoring the system back has been able to fix it.

    I don't know what most of the information in the attached files means, but I can tell you my mouse works fine, and the antivirus program was recently upgraded, so the past few times I have BSODed, I have had to re-install it.



    Windows 7 Home Premium 64-bit OEM - Computer is less than 6 months old.
    Last edited by noed; 24 Sep 2011 at 13:24. Reason: Windows 7 Home Premium 64-bit OEM - Computer is less than 6 months old.
      My Computer


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

    noed said:
    Well, 0x0000007E was the most recent...also have had 0x0000001A, and perhaps more. I have had a BSOD almost every day for weeks, and no amount of restoring the system back has been able to fix it.

    I don't know what most of the information in the attached files means, but I can tell you my mouse works fine, and the antivirus program was recently upgraded, so the past few times I have BSODed, I have had to re-install it.



    Windows 7 Home Premium 64-bit OEM - Computer is less than 6 months old.

    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
      My Computer


  3. Posts : 6,668
    Windows 7 x64
       #3

    Reformatting won't fix your problem, you are getting a very specific error related to hardware damage. (or a unstable overclock)
    I don't know of anything else that generates this error.
    Stop 0x124 - what it means and what to try

    Code:
    Probably caused by : hardware
    
    Followup: MachineOwner
    ---------
    
    1: 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: fffffa800503b038, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000b43c2000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000135, 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:  chrome.exe
    
    CURRENT_IRQL:  f
    
    STACK_TEXT:  
    fffff880`009f0a08 fffff800`02c16a3b : 00000000`00000124 00000000`00000000 fffffa80`0503b038 00000000`b43c2000 : nt!KeBugCheckEx
    fffff880`009f0a10 fffff800`02dda513 : 00000000`00000001 fffffa80`050157d0 00000000`00000000 fffffa80`05015820 : hal!HalBugCheckSystem+0x1e3
    fffff880`009f0a50 fffff800`02c16700 : 00000000`00000728 fffffa80`050157d0 fffff880`009f0db0 00000000`00c5d500 : nt!WheaReportHwError+0x263
    fffff880`009f0ab0 fffff800`02c16052 : fffffa80`050157d0 fffff880`009f0db0 fffffa80`050157d0 00000000`00000000 : hal!HalpMcaReportError+0x4c
    fffff880`009f0c00 fffff800`02c09e8f : 00000000`00c5d544 00000000`00000001 fffff880`009f0e30 00000000`00000000 : hal!HalpMceHandler+0x9e
    fffff880`009f0c40 fffff800`02cc852c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
    fffff880`009f0c70 fffff800`02cc8393 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
    fffff880`009f0db0 00000000`6a601450 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
    00000000`03e4f524 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6a601450
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: hardware
    
    IMAGE_NAME:  hardware
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE
    
    BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE
    
    Followup: MachineOwner
    ---------
    ...damn zigzag...
    Jinx!
    you owe me a coke.
      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 02:35.
Find Us