locked
BSOD 0x00000124 Please help. RRS feed

  • General discussion

  • I have been getting this for some time now and cannot find the root cause. Can someone please help me?

     

     

    System Specs:

    Motherboard: ASUS M4A79XTD EVO 790X AM3

    CPU: AMD Phenom II X4 965 Black Edition Deneb 3.4GHz Socket AM3 125W Quad-Core

    Ram: Corsair Dominator GT 4GB (2 x 2GB) 240-Pin DDR3

    Video Card: XFX HD-585A-ZNBC Radeon HD 5850 (Cypress Pro) 1GB Black Edition 256-bit GDDR5 PCI Express 2.0 x16 HDCP

    Hard Drive: Western Digital WD Black WD1002FAEX 1TB 7200 RPM 64MB Cache SATA 6.0Gb/s

    Power Supply: Corsair HX Series HX850 850W ATX12V 2.3 / EPS12V

    • Changed type Leo Huang Tuesday, July 30, 2013 3:16 AM
    Wednesday, July 3, 2013 12:31 AM

All replies

  • We do need the actual DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.  

    WE NEED AT LEAST TWO DMP FILES TO SPOT TRENDS AND CONFIRM THE DIAGNOSIS.
    You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.
    If you are overclocking stop.  (chances are if you dont know if you are, you are not)a
    To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.  We need at least 2 DMP FILES to diagnose and confirm
    The procedure:
    * Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
    * Zip up the copy.
    * Attach the ZIP archive to your post using the "paperclip" (file attachments) button. (if available on  your site, MS doesnt have this)
     *Please upload them to a file sharing service like Skydrive or"Rapidshare" and put a link to them in your reply.
    Link for how to  upload below.
    To ensure minidumps are enabled:
    * Go to Start, in the Search Box type: sysdm.cpl, press Enter.
    * Under the Advanced tab, click on the Startup and Recovery Settings... button.
    * Ensure that Automatically restart is unchecked.
    * Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
    * Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
    * OK your way out.
    * Reboot if changes have been made.
    Please also run MSinfo32 and upload the output as well.
    To run MSinfo32 please go to start>run>MSinfo32
    Go to "file" "save" and upload the saved file with the DMPS
    System specs are extremely useful so please include whatever you know.

    Wanikiya & Dyami--Team Zigzag

    Wednesday, July 3, 2013 12:50 AM
  • Dennis

    You link yields this

    https://gtipjg.bay.livefilestore.com/y2pccyzH37ef7rfvvAPJnBobC0evgCoVc2WzyqXkXSeUpBPdnGrgp8EDR5uJPwGTJrTno5wGwSkQIui07dkmFufcQl6A_O0beOZUAmKOndMQnDIW6RfRTbSmI8zNYER4DKL/Expired%20link2.jpg?psid=1


    Wanikiya & Dyami--Team Zigzag

    Wednesday, July 3, 2013 2:25 AM
  • Hi,

    The dump file analyze:

    ****************************************************************************

    *                                                                             *

    *                        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: fffffa80052ad8f8, Address of the WHEA_ERROR_RECORD structure.

    Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.

    Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

    Debugging Details:

    ------------------

    TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2

    TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2

    BUGCHECK_STR:  0x124_AuthenticAMD

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

    PROCESS_NAME:  System

    CURRENT_IRQL:  0

    STACK_TEXT: 

    BUGCHECK_STR:  0x124_AuthenticAMD

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

    PROCESS_NAME:  System

    CURRENT_IRQL:  0

    STACK_TEXT: 

    fffff880`031bd6f0 fffff800`030dfca9 : fffffa80`052ad8d0 fffffa80`03aa2040 00000000`0000000e 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c

    fffff880`031bdc10 fffff800`02fc0e87 : fffffa80`052ad8d0 fffff800`0303a2d8 fffffa80`03aa2040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49

    fffff880`031bdc40 fffff800`02f28285 : fffff800`0309bae0 00000000`00000001 fffffa80`053251c0 fffffa80`03aa2040 : nt!WheapProcessWorkQueueItem+0x57

    fffff880`031bdc80 fffff800`02e9e251 : fffff880`01173e00 fffff800`02f28260 fffffa80`03aa2000 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25

    fffff880`031bdcb0 fffff800`03132ede : 00000000`00000000 fffffa80`03aa2040 00000000`00000080 fffffa80`039e4b30 : nt!ExpWorkerThread+0x111

    fffff880`031bdd40 fffff800`02e85906 : fffff880`02f63180 fffffa80`03aa2040 fffff880`02f6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a

    fffff880`031bdd80 00000000`00000000 : fffff880`031be000 fffff880`031b8000 fffff880`03d0d2d0 00000000`00000000 : nt!KiStartSystemThread+0x16

    fffff880`031bd6f0 fffff800`030dfca9 : fffffa80`052ad8d0 fffffa80`03aa2040 00000000`0000000e 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c

    fffff880`031bdc10 fffff800`02fc0e87 : fffffa80`052ad8d0 fffff800`0303a2d8 fffffa80`03aa2040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49

    fffff880`031bdc40 fffff800`02f28285 : fffff800`0309bae0 00000000`00000001 fffffa80`053251c0 fffffa80`03aa2040 : nt!WheapProcessWorkQueueItem+0x57

    fffff880`031bdc80 fffff800`02e9e251 : fffff880`01173e00 fffff800`02f28260 fffffa80`03aa2000 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25

    fffff880`031bdcb0 fffff800`03132ede : 00000000`00000000 fffffa80`03aa2040 00000000`00000080 fffffa80`039e4b30 : nt!ExpWorkerThread+0x111

    fffff880`031bdd40 fffff800`02e85906 : fffff880`02f63180 fffffa80`03aa2040 fffff880`02f6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a

    fffff880`031bdd80 00000000`00000000 : fffff880`031be000 fffff880`031b8000 fffff880`03d0d2d0 00000000`00000000 : nt!KiStartSystemThread+0x16

    STACK_COMMAND:  kb

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME:

    STACK_COMMAND:  kb

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: AuthenticAMD

    AuthenticAMD

    IMAGE_NAME:  AuthenticAMD

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

    FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

    BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

    Followup: MachineOwner

    ---------

    IMAGE_NAME:  AuthenticAMD

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

    FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

    BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

    Followup: MachineOwner

    ---------

    About bugchck 0x124, you can refer this article:

    http://msdn.microsoft.com/en-us/library/windows/hardware/ff557321(v=vs.85).aspx

    Stop 0x124 is a hardware error.... if you are overclocking try resetting your processor to standard settings and see if that helps.

    Regards,

    Leo   Huang

    TechNet Subscriber Support

    If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.


    Leo Huang
    TechNet Community Support

    Wednesday, July 3, 2013 2:49 AM
  • Stop 0x124 is a hardware error
    If you are overclocking try resetting your processor to standard settings and see if that helps.
    If you continue to get BSODs here are some more things you may want to consider.

    This is usually heat related, defective hardware, memory or even processor though it is"possible" that it is driver related (rare).

    Stop 0x124 - what it means and what to try

    Synopsis:
    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.


     Generic "Stop 0x124" Troubleshooting Strategy:

    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.
    2) Ensure that the machine is adequately cooled.
     If there is any doubt, open up the side of the PC case (be mindful of any relevant warranty conditions!) and point a mains fan squarely at the motherboard. That will rule out most (lack of) cooling issues.
    3) Update all hardware-related drivers: video, sound, RAID (if any), NIC... anything that interacts with a piece of hardware.
    It is good practice to run the latest drivers anyway.
    4) Update the motherboard BIOS according to the manufacturer's instructions.
    Their website should provide detailed instructions as to the brand and model-specific procedure.
    5) Rarely, bugs in the OS may cause "false positive" 0x124 events where the hardware wasn't complaining but Windows thought otherwise (because of the bug).
    At the time of writing, Windows 7 is not known to suffer from any such defects, but it is nevertheless important to always keep Windows itself updated.
    6) Attempt to (stress) test those hardware components which can be put through their paces artificially.
    The most obvious examples are the RAM and HDD(s).
    For the RAM, use the in-built memory diagnostics (run MDSCHED) or the 3rd-party memtest86 utility to run many hours worth of testing.
    For hard drives, check whether CHKDSK /R finds any problems on the drive(s), notably "bad sectors".
    Unreliable RAM, in particular, is deadly as far as software is concerned, and anything other than a 100% clear memory test result is cause for concern. Unfortunately, even a 100% clear result from the diagnostics utilities does not guarantee that the RAM is free from defects - only that none were encountered during the test passes.
    7) As the last of the non-invasive troubleshooting steps, perform a "vanilla" reinstallation of Windows: just the OS itself without any additional applications, games, utilities, updates, or new drivers - NOTHING AT ALL that is not sourced from the Windows 7 disc.
    Should that fail to mitigate the 0x124 problem, jump to the next steps.
    If you run the "vanilla" installation long enough to convince yourself that not a single 0x124 crash has occurred, start installing updates and applications slowly, always pausing between successive additions long enough to get a feel for whether the machine is still free from 0x124 crashes.
    Should the crashing resume, obviously the very last software addition(s) may be somehow linked to the root cause.
    If stop 0x124 errors persist despite the steps above, and the hardware is under warranty, consider returning it and requesting a replacement which does not suffer periodic MCE events.
    Be aware that attempting the subsequent hardware troubleshooting steps may, in some cases, void your warranty:
    8) Clean and carefully remove any dust from the inside of the machine.
    Reseat all connectors and memory modules.
    Use a can of compressed air to clean out the RAM DIMM sockets as much as possible.
    9) If all else fails, start removing items of hardware one-by-one in the hope that the culprit is something non-essential which can be removed.
    Obviously, this type of testing is a lot easier if you've got access to equivalent components in order to perform swaps.

    Should you find yourself in the situation of having performed all of the steps above without a resolution of the symptom, unfortunately the most likely reason is because the error message is literally correct - something is fundamentally wrong with the machine's hardware.

    Wanikiya & Dyami--Team Zigzag

    Wednesday, July 3, 2013 3:16 AM
  • That's what I thought but I can not pin down the hardware at fault. Nothing on the system is overclocked. I have ran HDD scans and ram Memtest 86+ for hours and everything came back ok. Do you know any testing programs I can run that might check the CPU, video card and motherboard thoroughly?

    Wednesday, July 3, 2013 1:07 PM
  • Dennis

    For CPU use Prime 95

    Try this free stress test:  http://www.mersenne.org/freesoft/

    Prime95 Setup;
    - extract the contents of the zip file to a location of your choice
    - double click on the executable file
    - select "Just stress testing"
    - select the "Blend" test.  If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
    - "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
    The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
    Then run the test for 6 to 24 hours - or until you get errors [b](whichever comes first)
    The Test selection box and the stress.txt file describes what components that the program stresses.

    For video (cards etc) run Furmark

    Try this free video stress test:  http://www.ozone3d.net/benchmarks/fur/
    FurMark Setup:

    - If you have more than one GPU, select Multi-GPU during setup
    - In the Run mode box, select "Stability Test" and "Log GPU Temperature"
    Click "Go" to start the test
    - Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first)
    - Click "Quit" to exit


    Wanikiya & Dyami--Team Zigzag

    Thursday, July 4, 2013 6:37 AM
  • Thx for the info. I remember running Prime95 and had no errors but I will run it again. Is there something you might know that will test the motherboard. I us to have one ( cant remember the name) but its old and does not work on newer boards. I will let you know the results of the 2 test.
    Thursday, July 4, 2013 2:44 PM
  • Hi,

    How’s everything going? Please feel free to give me any update.

    Thank you for your cooperation.

    Regards,

    Leo   Huang

    TechNet Subscriber Support

    If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.


    Leo Huang
    TechNet Community Support

    Monday, July 8, 2013 7:20 AM
  • Well for the Prime95 I ran the blend test for 4 hours with no errors. then I ran it again on priority 10 for another 4 hours and no errors. Then I ran it on Small FFTs on priority for 12 hours and no errors.

    Then I ran the FurMark  server times using a few different settings and did not have any problems.

    I also ran the Western Digital Hard Drive test on both of my Western Digital hard drives and they have no errors. I still have to run Hard Drive tests on my Seagate drive and my WD External drive. I will also run Memtest 86+ again over night to.

    Any other suggestions?

    Monday, July 8, 2013 1:20 PM
  • You have a timeout issue:

    ===============================================================================
    Common Platform Error Record
    -------------------------------------------------------------------------------
    Record Id     : 01ce7669b69039c5
    Severity      : Fatal (1)
    Length        : 928
    Creator       : Microsoft
    Notify Type   : Machine Check Exception
    Timestamp     : 7/1/2013 14:46:12 (UTC)
    Flags         : 0x00000002 PreviousError
    
    ===============================================================================
    Section 0     : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa80052ad978
    Section       @ fffffa80052ada50
    Offset        : 344
    Length        : 192
    Flags         : 0x00000001 Primary
    Severity      : Fatal
    
    Proc. Type    : x86/x64
    Instr. Set    : x64
    Error Type    : BUS error
    Operation     : Generic
    Flags         : 0x00
    Level         : 3
    CPU Version   : 0x0000000000100f43
    Processor ID  : 0x0000000000000000
    
    ===============================================================================
    Section 1     : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa80052ad9c0
    Section       @ fffffa80052adb10
    Offset        : 536
    Length        : 128
    Flags         : 0x00000000
    Severity      : Fatal
    
    Local APIC Id : 0x0000000000000000
    CPU Id        : 43 0f 10 00 00 08 04 00 - 09 20 80 00 ff fb 8b 17
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
    
    Proc. Info 0  @ fffffa80052adb10
    
    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa80052ada08
    Section       @ fffffa80052adb90
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    
    Error         : BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 4)
      Status      : 0xfa00000000070f0f
    

    do you use the latest BIOS?


    "A programmer is just a tool which converts caffeine into code"

    Thursday, August 1, 2013 7:08 PM
  • Yes I do have the latest BIOS and it is still doing it. Any help would be great.

    Sunday, August 4, 2013 11:29 AM
  • make sure the CPU doesn't overheat.

    "A programmer is just a tool which converts caffeine into code"

    Sunday, August 4, 2013 6:36 PM
  • My idol temp is 38c and after running Prime95 for 3.5 hours it was at 61c.
    Monday, August 5, 2013 5:37 PM
  • this temperature should be ok. Do you have a second CPU which you can test?

    My old X4 945 also bugchecked the box several times. In 1 dump I saw MSR calls from DWM and this showed me the CPU died even if all stress tests and the temperature were fine.


    "A programmer is just a tool which converts caffeine into code"

    Monday, August 5, 2013 6:14 PM
  • No I do not have another CPU I can test it with. I built this PC December of 2009 and this just started to happen in the last year or so. It does not do it every day. I might do it once or twice a month and sometimes might not do it for a few months.
    Thursday, August 8, 2013 2:39 PM
  • For me it was also after 3 years. Looks like the CPU is damaged. Replace the CPU.

    "A programmer is just a tool which converts caffeine into code"

    Thursday, August 8, 2013 7:18 PM
  • thx for all the help. I might be building a new system soon anyway but I still might try another cpu.
    Friday, August 9, 2013 1:38 PM