1. Computer problem? Tech Support Guy is completely free -- paid for by advertisers and donations. Click here to join today! If you're new to Tech Support Guy, we highly recommend that you visit our Guide for New Members.

0x124 BSODs

Discussion in 'Hardware' started by Darkicon, Dec 12, 2014.

Thread Status:
Not open for further replies.
  1. Darkicon

    Darkicon Thread Starter

    Feb 12, 2008
    When I play any graphically-intensive video game for more than an hour, I get a 0x124 BSOD. I do have my CPU slightly overclocked and my GPU not at all, RAM is all default timings.

    I used to get that error back awhile ago due to a failing DIMM, since I pulled the chip, no more problems. Lately though it's been doing it again, but I don't think it's a failing DIMM this time around because if I crank my exhaust fan to max, it won't crash. But I've monitored my temps many times and they're all well within safe range (Plus it's almost winter and very cold).

    It's strange that my temps are fine, yet maxing out my fan fixes the problem. The bug check analysis reports driver fault, which I do believe would be my GPU driver considering when it crashes, the screen turns black, I see static on screen and then the BSOD.

    Attached is the minidump. Anyone have a solution? Thanks.

    Attached Files:

  2. Macboatmaster

    Macboatmaster Trusted Advisor Spam Fighter

    Jan 14, 2010
    I will analyse your dump for you and post back
    In the meantime, it is possible that when a chip on a stick of ram is suspect it can overheat - this MAY although I consider it very unlikely be the cause
    I suspect the more likely cause is, although not detected by the temp monitoring overheat, not of a ram stick but of the processor, or indeed the HD7850

    There is no reason to suspect a driver IMHO if the increased air flow solves the problem

    Whilst I analyse the dump I suggest you return CPU settings to default and try

    I am hesitant to mention it as you are obviously tech aware but are all fans and cooling fins clean
  3. Macboatmaster

    Macboatmaster Trusted Advisor Spam Fighter

    Jan 14, 2010
    As I am sure you have seen it is WHEA fatal hardware error
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Machine Name:
    Kernel base = 0xfffff800`03453000 PsLoadedModuleList = 0xfffff800`036966d0
    Debug session time: Fri Dec 12 13:59:59.783 2014 (UTC - 5:00)
    System Uptime: 0 days 0:00:09.796
    * *
    * 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: fffffa8005b41038, 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 : e:\dump_analysis\program\triage\modclass.ini, error 2

    BUGCHECK_STR: 0x124_AuthenticAMD


    PROCESS_NAME: System


    fffff880`033af6f0 fffff800`03713ca9 : fffffa80`05b41010 fffffa80`04606040 fffffa80`00000005 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
    fffff880`033afc10 fffff800`035f4ea7 : fffffa80`05b41010 fffff800`0366e2d8 fffffa80`04606040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
    fffff880`033afc40 fffff800`0355c275 : fffff800`036cfb40 00000000`00000001 fffffa80`05aee640 fffffa80`04606040 : nt!WheapProcessWorkQueueItem+0x57
    fffff880`033afc80 fffff800`034d2261 : fffff880`0106fe00 fffff800`0355c250 fffffa80`04606000 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
    fffff880`033afcb0 fffff800`037652ea : 00000000`00000000 fffffa80`04606040 00000000`00000080 fffffa80`045ffb30 : nt!ExpWorkerThread+0x111
    fffff880`033afd40 fffff800`034b98e6 : fffff880`03164180 fffffa80`04606040 fffff880`0316efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`033afd80 00000000`00000000 : fffff880`033b0000 fffff880`033aa000 fffff880`033af9e0 00000000`00000000 : nt!KxStartSystemThread+0x16


    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: AuthenticAMD

    IMAGE_NAME: AuthenticAMD




    It is a machine check exception and that USUALLY indicates
    There most common reason for MCE events to occur are:

    • Memory errors or Error Correction Code (ECC) problems
    • Inadequate cooling / processor over-heating
    • System bus errors
    • Cache errors in the processor or hardware
    I would as I said earlier check processor cooling fins
    Run MEMTEST - at least 2 complete passes - each pass consists of 8-10 tests. MEMTEST test all memory not just physical ram.

    Return to default on processor
    I would also check if possible with side panel removed

    I am reasonably convinced this is a temp issue
  4. Macboatmaster

    Macboatmaster Trusted Advisor Spam Fighter

    Jan 14, 2010
    See this quote from memtest

    Troubleshooting Memory Errors
    Please be aware that not all errors reported by MemTest86 are due to bad memory. The test implicitly tests the CPU, L1 and L2 caches as well as the motherboard. It is impossible for the test to determine what causes the failure to occur. However, most failures will be due to a problem with memory module. When it is not, the only option is to replace parts until the failure is corrected.

    Once a memory error has been detected, determining the failing SIMM/DIMM module is not a clear cut procedure. With the large number of motherboard vendors and possible combinations of memory slots it would be difficult if not impossible to assemble complete information about how a particular error would map to a failing memory module. However, there are steps that may be taken to determine the failing module. Here are four techniques that you may wish to use:
    1. Removing modules This is simplest method for isolating a failing modules, but may only be employed when one or more modules can be removed from the system. By selectively removing modules from the system and then running the test you will be able to find the bad modules. Be sure to note exactly which modules are in the system when the test passes and when the test fails.
    2. Rotating modules When none of the modules can be removed then you may wish to rotate modules to find the failing one. This technique can only be used if there are three or more modules in the system. Change the location of two modules at a time. For example put the module from slot 1 into slot 2 and put the module from slot 2 in slot 1. Run the test and if either the failing bit or address changes then you know that the failing module is one of the ones just moved. By using several combinations of module movement you should be able to determine which module is failing.
    3. Replacing modules If you are unable to use either of the previous techniques then you are left to selective replacement of modules to find the failure.

    AND MY post here

    ignore for the time being the removing of ram sticks - run it for the two complete passes
As Seen On
As Seen On...

Welcome to Tech Support Guy!

Are you looking for the solution to your computer problem? Join our site today to ask your question. This site is completely free -- paid for by advertisers and donations.

If you're not already familiar with forums, watch our Welcome Guide to get started.

Join over 733,556 other people just like you!

Similar Threads - 0x124 BSODs
  1. Kevscrazylife
  2. FloofTheBird
Thread Status:
Not open for further replies.

Short URL to this thread: https://techguy.org/1139160

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice