BSOD 0x00000124 while playing game

[seeker555]

Hi, I've been getting this BSOD 0x00000124 recently by playing a free browser war game called atWar. It happens about half of the time, the longer I play the more likely it happens. No overclocking.

 

[HonorGamer]

Hey seeker555, Welcome to SF!

ctac32k.sys                 Wed Jul  2 03:38:22 [COLOR="Red"]2008[/COLOR] (486B3E7E)
amdiox64.sys                Thu Feb 18 09:17:53 2010 (4B7D5A21)
amdxata.sys                 Fri Mar 19 11:18:18 2010 (4BA3A3CA)
emupia2k.sys                Wed May  5 07:57:27 2010 (4BE16B37)
ctsfm2k.sys                 Wed May  5 07:57:33 2010 (4BE16B3D)
ctoss2k.sys                 Wed May  5 07:57:46 2010 (4BE16B4A)
ha20x2k.sys                 Wed May  5 07:59:10 2010 (4BE16B9E)
ctaud2k.sys                 Wed May  5 07:59:48 2010 (4BE16BC4)
ctprxy2k.sys                Wed May  5 07:59:51 2010 (4BE16BC7)
CTEXFIFX.SYS                Wed May  5 08:01:21 2010 (4BE16C21)
CT20XUT.SYS                 Wed May  5 08:01:28 2010 (4BE16C28)
CTHWIUT.SYS                 Wed May  5 08:01:32 2010 (4BE16C2C)
AsUpIO.sys                  Mon Aug  2 21:47:59 2010 (4C57835F)
AiChargerPlus.sys           Mon Nov  8 00:48:26 2010 (4CD79D3A)
jraid.sys                   Wed Nov 24 21:27:17 2010 (4CEDD795)
amd_sata.sys                Fri Mar  4 14:45:41 2011 (4D714F75)
amd_xata.sys                Fri Mar  4 14:45:44 2011 (4D714F78)
Rt64win7.sys                Fri Jun 10 01:33:15 2011 (4DF1BAAB)
LHidFilt.Sys                Fri Sep  2 01:23:09 2011 (4E60764D)
LMouFilt.Sys                Fri Sep  2 01:23:15 2011 (4E607653)
asmtxhci.sys                Wed Sep 14 02:36:09 2011 (4E705969)
asmthub3.sys                Wed Sep 14 02:36:19 2011 (4E705973)
dtsoftbus01.sys             Fri Jan 13 07:45:46 2012 (4F10358A)
AODDriver2.sys              Thu Apr  5 04:23:37 2012 (4F7D6499)
AsIO.sys                    Wed Aug 22 04:54:47 2012 (5034AC67)
inspect.sys                 Wed Nov  7 16:07:02 2012 (509ADB86)
cmdhlp.sys                  Wed Nov  7 16:07:03 2012 (509ADB87)
cmdguard.sys                Wed Nov  7 16:07:39 2012 (509ADBAB)
AtihdW76.sys                Thu Feb 14 16:11:09 2013 (511D60FD)
avkmgr.sys                  Fri Feb 22 03:33:49 2013 (51273B7D)
atikmpag.sys                Thu Mar 28 20:09:45 2013 (5154E9D9)
atikmdag.sys                Thu Mar 28 21:27:04 2013 (5154FBF8)
avipbb.sys                  Tue Jul  2 08:35:44 2013 (51D2D730)
SbieDrv.sys                 Mon Jul  8 06:28:31 2013 (51DAA25F)bieDrv.sys[/COLOR][/B][/url]

Normally drivers 2008 and earlier are known to cause problems. Please update it: Creative Worldwide Support

Start Menu\Programs\Wise Registry Cleaner	Public:Start Menu\Programs\Wise Registry Cleaner	Public

Registry cleaners are also known problems. It is wiser to never use registry cleaners. It is windows job to maintain the registry, and that it why it was created.

dtsoftbus01.sys             Fri Jan 13 07:45:46 2012 (4F10358A)

Daemon Tools are extremely well known to cause BSODs. Probably one of the top reasons BSODs happen. Uninstall.

Probably caused by : AuthenticAMD
 
WHEA_UNCORRECTABLE_ERROR (124)

This keeps popping up in the analysis. This is known as a hardware problem. Please run the following diagnostics.

BUG CHECK:

BugCheck 0x124

   Warning

Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. :warn:WARNING: The steps that follow can void your warranty!!!

For your hardware stop 0x124 crash, read through http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html and use the following hardware checks to supplement that link.

• If you are overclocking any hardware, please stop.
  
  
• If you have an SSD, make sure the following are up to date:
  • SSD firmware
  • BIOS Version
  • Chipset Drivers
  • Hard disk controller drivers/SATA drivers
  • If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.
  
  
• Run all but the advanced tests with SeaTools for HDDs.
  SeaTools for Windows
  
  SeaTools for DOS​
  
  
• Monitor temperatures during the following tests.
  
  Use the following programs to monitor the temperatures.​
  • Real Temp is a good CPU temperature monitor.
  • Speccy - System Information - Free Download will monitor all hardware temperatures.
  • HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
  • Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). The goal is to get a steady temperature, find out if the GPU is overheating, or to see if there are any artifacts present in the test itself: look for strange pixelated patterns on the screen or colors that do not look like they belong. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
    
    
  • Run http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
    
    
  • Follow the steps for doing CPU stress test using IntelBurnTest
  
  
• 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).
  
  For Part 3: If You Have Errors: 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. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
  Once these steps have been followed, it is safe to remove and replace components within your computer.

​

Coutesy of: writhziden

Post back results when completed!

-Justin