BSOD after playing BF3, error 124


  1. Posts : 2
    Windows 7 64
       #1

    BSOD after playing BF3, error 124


    Hi guys,

    First I would just like to explain what has happened in the past. My computer was overclocked to 3.4GHz and so was my gpu. It was an otherwise stable system but it would crash whilst I was playing Mafia II, Battlefield BC2 and Battlefield 3. What would happen is the game would sometimes crash to desktop with graphical glitches on pretty much everything or it would just blue screen and restart without actually displaying the blue screen.

    I tried many solutions I found online, even a clean install but none worked until I found a post on another forum that suggested a voltage in the bios was too high. I then reset the bios by taking out the battery and replacing it and booted up with everything set to auto. From what I would tell this has resolved my initial problem as I would play Mafia 2 all day and BF:BC2 too and it would not crash.

    I have not played BF3 for a while but I decided I wanted to play a few games last night, I ended up playing for about an hour maximum and I then quit the game. About 30 seconds after I quit the game my computer crashed and I was greeted with the loud kind of buzzing noise like the tripods make on war of the worlds. I rebooted to see the screen that tells you your computer has crashed and it displayed the error code 124. I am not sure if this crash is related to BF3 or something else but I would much appreciate it if you can help me get to the bottom of this.

    The PC is just over a year old.

    Spec
    AMD Athlon II X4 640
    Asus M4A78LT-M
    Corsair 'Cheapo' DDR3 1333 MHz RAM
    Corsair CX500 PSU
    MSI NGTX 460 1GB OC
    WD5000AAKS HDD
    Old IDE DVD drive and another old hard drive

    EDIT: Latest dump file is with the current problem, any before that could be Overclocking related or related to my previous problem.
      My Computer


  2. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #2

    Problem Devices:
    Code:
    NVIDIA High Definition Audio	HDAUDIO\FUNC_01&VEN_10DE&DEV_0012&SUBSYS_10DE0101&REV_1001\5&294C0782&0&0001	This device is disabled.
    NVIDIA High Definition Audio	HDAUDIO\FUNC_01&VEN_10DE&DEV_0012&SUBSYS_10DE0101&REV_1001\5&294C0782&0&0101	This device is disabled.
    Photosmart C4500 series	ROOT\IMAGE\0000	This device is disabled.
    Photosmart C4500 series	ROOT\MULTIFUNCTION\0000	This device is disabled.
    NVIDIA High Definition Audio	HDAUDIO\FUNC_01&VEN_10DE&DEV_0012&SUBSYS_10DE0101&REV_1001\5&294C0782&0&0201	This device is disabled.
    NVIDIA High Definition Audio	HDAUDIO\FUNC_01&VEN_10DE&DEV_0012&SUBSYS_10DE0101&REV_1001\5&294C0782&0&0301	This device is disabled.

    Antivirus Software:
    Code:
    avgcsrva.exe	c:\program files (x86)\avg\avg2012\avgcsrva.exe	644	8	200	1380	03/03/2012 15:30	12.0.0.1786	507.34 KB (519,520 bytes)	15/08/2011 07:21
    avgemca.exe	c:\program files (x86)\avg\avg2012\avgemca.exe	1732	8	200	1380	03/03/2012 15:30	12.0.0.1854	1.52 MB (1,593,696 bytes)	10/10/2011 07:23
    avgidsagent.exe	c:\program files (x86)\avg\avg2012\avgidsagent.exe	2848	8	200	1380	03/03/2012 15:30	12.0.0.1855	4.23 MB (4,433,248 bytes)	12/10/2011 07:25
    avgnsa.exe	c:\program files (x86)\avg\avg2012\avgnsa.exe	1728	8	200	1380	03/03/2012 15:30	12.0.0.1883	1.90 MB (1,987,424 bytes)	28/11/2011 01:19
    avgtray.exe	c:\program files (x86)\avg\avg2012\avgtray.exe	4500	8	200	1380	03/03/2012 15:30	12.0.0.1912	2.30 MB (2,416,480 bytes)	24/01/2012 17:24
    avgwdsvc.exe	c:\program files (x86)\avg\avg2012\avgwdsvc.exe	2164	8	200	1380	03/03/2012 15:30	12.0.0.1773	188.26 KB (192,776 bytes)	02/08/2011 07:09

    Possible out of date drivers:
    Code:
    AtiPcie	fffff880`01bf6000	fffff880`01bfe000	Tue May 05 09:00:22 2009 (4a005486)	000134c7		AtiPcie.sys
    PxHlpa64	fffff880`010f2000	fffff880`010fde00	Tue Jun 23 17:16:35 2009 (4a416253)	000111b7		PxHlpa64.sys
    AtiPcie.sys
    PxHlpa64.sys


    Code:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [D:\Kingston\BSODDmpFiles\scott1541\Windows_NT6_BSOD_jcgriff2\030212-39140-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Machine Name:
    Kernel base = 0xfffff800`0301c000 PsLoadedModuleList = 0xfffff800`03261670
    Debug session time: Fri Mar  2 12:58:39.749 2012 (UTC - 7:00)
    System Uptime: 0 days 0:00:11.356
    Loading Kernel Symbols
    ..........................................................
    Loading User Symbols
    Mini Kernel Dump does not contain unloaded driver list
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 124, {0, fffffa8008024038, 0, 0}
    
    Probably caused by : hardware
    
    Followup: MachineOwner
    ---------
    
    3: 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: fffffa8008024038, 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:
    ------------------
    
    
    BUGCHECK_STR:  0x124_AuthenticAMD
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    fffff880`033bd6f0 fffff800`032dec59 : fffffa80`08024010 fffffa80`06a35040 00000000`0000000b 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
    fffff880`033bdc10 fffff800`031bef57 : fffffa80`08024010 fffff800`032392b8 fffffa80`06a35040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
    fffff880`033bdc40 fffff800`031265d5 : fffff800`0329aae0 00000000`00000001 fffffa80`07ff7160 fffffa80`06a35040 : nt!WheapProcessWorkQueueItem+0x57
    fffff880`033bdc80 fffff800`030a3001 : fffff880`010c2e00 fffff800`031265b0 fffffa80`06a35000 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
    fffff880`033bdcb0 fffff800`03333fee : 00000000`00000000 fffffa80`06a35040 00000000`00000080 fffffa80`069a09e0 : nt!ExpWorkerThread+0x111
    fffff880`033bdd40 fffff800`0308a5e6 : fffff880`03164180 fffffa80`06a35040 fffff880`0316efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`033bdd80 00000000`00000000 : fffff880`033be000 fffff880`033b8000 fffff880`03057540 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: hardware
    
    IMAGE_NAME:  hardware
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
    
    BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
    
    Followup: MachineOwner
    ---------

    Start with Stop 0x124 - what it means and what to try and use the following to supplement the steps provided in that link:
    • If you are overclocking any hardware, please stop.

    • Monitor temperatures during the following tests.
      Use the following programs to monitor the temperatures.


    • Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).

      If you swap any memory components, follow these steps for ESD safety:
      1. Shut down and turn off your computer.
      2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
      3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
      4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.

      Once these steps have been followed, it is safe to remove and replace components within your computer.
      My Computer


  3. Posts : 2
    Windows 7 64
    Thread Starter
       #3

    I have run Prime95 and furmark previously and I know my hardware is not getting too hot. IIRC my gpu will max out in the high 60s (°C) and the cpu will get up to reach somewhere around 50°C as I have an aftermarket HSF.

    I am currently running Memtest now, I will get back to you with the results after a few runs :)

    Also is it alright to run memtest with both sticks of ram in? I know you try them one at a time when searching for a faulty stick so I assumed it is fine to leave them all in for this.
      My Computer


  4. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #4

    Yes, run with both first. Then if you have problems, follow part 3 of that tutorial. You also want to let them run for at least seven passes at some point. More than seven would be better if possible.
      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 06:25.
Find Us