Getting tons of BSOD's RRS feed

  • Question

  • Over the past three days I have been getting a massive amounts of blue screens. I don't know why honestly. I have checked all my drivers and they are all up to date. I also have ran test on my cpu. So this  is where the interesting part comes in (at least to me). So I ran cpu test with prime95 and ran the Small FFTs test, I ran it multiple times and increased the cores it tested each time. When I did 4 cores my computer blue screened, also my processor was only at 50% and was at about 33 Degrees Celsius. Please help!

    System Specs :
    AMD FX 8350 Eight Core at 4.0 GHz
    Hydro Series H60 Liquid cooling
    AMD Radeon RG2133 Gamer Series 16GB RAM
    Windows 7 Ultimate 64 Bit
    700 Watt PSU
    AMD Radeon 7870 HD GHz Edition 

    Link to my dmp files:

    Sunday, January 19, 2014 12:08 AM


  • Koolaidsman

    The vast majority of these appear to be hardware related (BCC124)  More specifically they point to AMD.

    Windows 7 Kernel Version 7600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.17273.amd64fre.win7_gdr.130318-1532
    Machine Name:
    Kernel base = 0xfffff800`02e13000 PsLoadedModuleList = 0xfffff800`0304fe70
    Debug session time: Sat Jan 18 16:09:54.932 2014 (UTC - 5:00)
    System Uptime: 0 days 0:10:57.321
    Loading Kernel Symbols
    BugCheck 124, {0, fffffa800ea08028, b0800000, 40151}
    Probably caused by : AuthenticAMD
    Followup: MachineOwner
    6: kd> !analyze -v
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    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.
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: fffffa800ea08028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000b0800000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000040151, Low order 32-bits of the MCi_STATUS value.
    Debugging Details:
    BUGCHECK_STR:  0x124_AuthenticAMD
    PROCESS_NAME:  chrome.exe
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    fffff880`03101b88 fffff800`033ff903 : 00000000`00000124 00000000`00000000 fffffa80`0ea08028 00000000`b0800000 : nt!KeBugCheckEx
    fffff880`03101b90 fffff800`02f98543 : 00000000`00000001 fffffa80`0e7b3140 00000000`00000000 fffffa80`0e7b3190 : hal!HalBugCheckSystem+0x1e3
    fffff880`03101bd0 fffff800`033ff5c8 : 00000000`00000728 fffffa80`0e7b3140 fffff880`03101f30 00000000`091a1c00 : nt!WheaReportHwError+0x263
    fffff880`03101c30 fffff800`033fef1a : fffffa80`0e7b3140 fffff880`03101f30 fffffa80`0e7b3140 00000000`00000000 : hal!HalpMcaReportError+0x4c
    fffff880`03101d80 fffff800`033f2e8f : 00000000`091a1000 00000000`00000001 fffff880`03101fb0 00000000`00000000 : hal!HalpMceHandler+0x9e
    fffff880`03101dc0 fffff800`02e8112c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
    fffff880`03101df0 fffff800`02e80f93 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
    fffff880`03101f30 00000000`5b56d707 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
    00000000`0408fdbc 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x5b56d707
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: AuthenticAMD
    IMAGE_NAME:  AuthenticAMD
    BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE
    FAILURE_ID_HASH_STRING:  km:x64_0x124_authenticamd_processor_cache
    FAILURE_ID_HASH:  {8bb1abe1-5cc5-4642-921b-5e3d4790100e}
    Followup: MachineOwner
    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

    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 and clear the CMOS.
    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 3rd-party memtest86 utility to run many hours worth of testing. (6-8 passes to stress the ram out)
    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.

    More advanced reading can be found here from a MS MVP IT PRO


    Wanikiya and Dyami--Team Zigzag

    • Marked as answer by Karen Hu Wednesday, February 5, 2014 6:01 AM
    Sunday, January 19, 2014 12:34 PM