I have BSOD happening everytime error 0x00000124

Page 1 of 3 123 LastLast

  1. Posts : 14
    Windows 7 64 bit
       #1

    I have BSOD happening everytime error 0x00000124


    Hello guys,i am new here,and i have some problem with my pc,because it crashes suddenly and many times and it has given me this problems since i bought it,so i decided to post here to look up for the solution.

    My computer's OS is windows 7 x64,it has 8 GB of ram and an Intel I5 Quad core processor 3.20 GHz.

    I tried fixing the problem by updating drivers,searching for viruses,setting my pc to low power consumption,improving the heat dissipation with many fans and a new case and cleaning inside it,running chkdsk,uninstalling some useless programs and doing RAM tests but nothing of this worked.

    Please,help me fixing my pc's problems.

    Thank you .
      My Computer


  2. Posts : 306
    Windows 7 Ultimate x64
       #2

    The zip you've attached is damaged / corrupt. Please re-zip your dumps and then reattach.
      My Computer


  3. Posts : 14
    Windows 7 64 bit
    Thread Starter
       #3

    I uploaded the new files
      My Computer


  4. Posts : 306
    Windows 7 Ultimate x64
       #4

    All three dump files point to bugcheck 124, aka hardware. First thing I'd like you to do is uninstall Daemon Tools. Once you've uninstalled it and restarted your system, download DupexSecure's SPTD.sys uninstaller. This will ensure that the sptd.sys Daemon Tools driver is fully removed from your system. After you've removed it, restart again.

    If your issues still persist after removing Daemon Tools & SPTD.sys, I'd like you to run three tests:


    Chkdsk:


    1. Open the "Computer" window
    2. Right-click on the drive in question
    3. Select the "Tools" tab
    4. In the Error-checking area, click <Check Now>.



    Memtest:

    Read the following to test your memory for errors.

    Driver Verifier:

    Read the following
    to enable Driver Verifier. Use Driver Second if Memtest finds nothing, as it's likely a software / driver issue, we just aren't being told what it is, and hopefully Driver Verifier will than force a crash if it finds the violating driver.
    Code:
    *******************************************************************************
    *                                                                             *
    *                        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: fffffa8007f51028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000ba000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000400405, Low order 32-bits of the MCi_STATUS value.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x124_GenuineIntel
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  f
    
    STACK_TEXT:  
    fffff880`009f0a58 fffff800`02c1da3b : 00000000`00000124 00000000`00000000 fffffa80`07f51028 00000000`ba000000 : nt!KeBugCheckEx
    fffff880`009f0a60 fffff800`02de1513 : 00000000`00000001 fffffa80`07f52ea0 00000000`00000000 fffffa80`07f52ef0 : hal!HalBugCheckSystem+0x1e3
    fffff880`009f0aa0 fffff800`02c1d700 : 00000000`00000728 fffffa80`07f52ea0 fffff880`009f0e30 fffff880`009f0e00 : nt!WheaReportHwError+0x263
    fffff880`009f0b00 fffff800`02c1d052 : fffffa80`07f52ea0 fffff880`009f0e30 fffffa80`07f52ea0 00000000`00000000 : hal!HalpMcaReportError+0x4c
    fffff880`009f0c50 fffff800`02c1cf0d : 00000000`00000004 00000000`00000001 fffff880`009f0eb0 00000000`00000000 : hal!HalpMceHandler+0x9e
    fffff880`009f0c90 fffff800`02c10e88 : fffff880`035d8260 fffffa80`07fc4c20 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
    fffff880`009f0cc0 fffff800`02ccf52c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
    fffff880`009f0cf0 fffff800`02ccf393 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
    fffff880`009f0e30 fffff800`02cd5f54 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
    fffff880`051f0800 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x1f4
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: hardware
    
    IMAGE_NAME:  hardware
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
    
    BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
    
    Followup: MachineOwner
      My Computer


  5. Posts : 14
    Windows 7 64 bit
    Thread Starter
       #5

    Ok,i did run the test as you said,the last one caused a BSOD even before wieving the desktop
      My Computer


  6. Posts : 306
    Windows 7 Ultimate x64
       #6

    Driver Verifier? Yeah, that happens if the driver runs at startup especially. Disable Driver Verifier if you have access to safe mode and then boot into Windows and attach the verified enabled dumps (latest dump files).
      My Computer


  7. Posts : 14
    Windows 7 64 bit
    Thread Starter
       #7

    Ok,i hope i uploaded the files correctly
      My Computer


  8. Posts : 14
    Windows 7 64 bit
    Thread Starter
       #8

    don't forget me please
      My Computer


  9. Posts : 306
    Windows 7 Ultimate x64
       #9

    Hi,

    In the file you've attached I don't see the verifier enabled dump. The latest dump in that attached zip isn't verifier enabled (latest dump date is 2/26 @ 8:58 AM).
      My Computer


  10. Posts : 14
    Windows 7 64 bit
    Thread Starter
       #10

    ePeen said:
    Hi,

    In the file you've attached I don't see the verifier enabled dump. The latest dump in that attached zip isn't verifier enabled (latest dump date is 2/26 @ 8:58 AM).
    no,it isn't the latest one because i had another BSOD before uploading
      My Computer


 
Page 1 of 3 123 LastLast

  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 04:45.
Find Us