BSOD Xcom EW 0x00000124

[WillHops]

After downloading the expansion Xcom Enemy Within, I have been getting BSODs regularly after playing for ~5 minutes or so (sometimes sooner, sometimes longer)

I have had no issues running any other game on this computer beyond some minor troubleshooting (driver updates, reinstalls), but this one has really got me.

After exhausting every option imaginable, Ive stumbled across these forums and Blue Screen Viewer as my last resort.

I tried researching this on my own, but Im seeing that this particular error often represents a hardware issue, and its not something I feel comfortable troubleshooting on my own any longer. Im really hoping its not hardware related since Im flat broke, but any help with this issue would be greatly appreciated!

I'm attaching the dmp file (just 1 since theyre all the same, and only occur when trying to play this game), as well as my dxdiag since I know that is often useful..

Any other information that is needed to possibly address this issue just let me know, thanks for your time and support!


Edit: Ok ran DMLogCollecter and uploaded that as well

Edit 2: Btw have done the driver cleaner, updated my BIOS via manufacturer, tried with clean startup, and the problem persists, but oddly only for this game! (Which is why Im hoping its not a hardware issue)

 

[WillHops]

Anyone??

 

[HarriePateman]

Sorry for the slow replies, the problem is when people comment on their own threads they are no longer displayed as unready.

I will look into this for you now!

 

[HarriePateman]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

[COLOR="Red"]WHEA_UNCORRECTABLE_ERROR (124)[/COLOR]
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: fffffa80059c28f8, 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.

The Bugcheck is 0x124 this is a hardware error.

If you are overclocking please reset the OC to the default Values.

I also notice that your recent updates failed. It may be a good idea to run over these again.

 

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. Otherwise, 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 harware is under warranty, consider returning it and requesting a replacement which does not suffer periodic MCE events. Be aware that attempting the subsequent harware 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.

 

[WillHops]

Hey HarriePateman, thanks for your reply! I have never overclocked my cpu, I tried underclocking it with MSI Afterburner, but the issue persisted and I have since removed that program from my computer.

What do you mean by some of my updates failed? Could you be more specific? I recently did a driver sweep then reinstalled video drivers, but I also updated my BIOS, did that update not process cleanly? If so, what can I do differently to ensure a clean update?

Beyond that, Im hesitant to start taking the machine apart looking for hardware failures as I am only getting this error when trying to play this particular game, it is not a recurring problem on my machine outside of this program. Additionally Im not super excited about the idea of reinstalling windows..

Hence my post here, in the hopes that there is any kind of settings edit I could possibly make, or a possible error in some driver/registry somewhere...

Thanks again!

Edit: I frequently clean dust out of my case with approved products.. I performed a stress test using the Dell System Detect Software and everything came up clean..

 

[HarriePateman]

Could you download CPU Temp from my Sigs, and keep an eye over the TEMPS.

Just for a couple of hours.

After this we have a few other tests i would like you to run.

 

[WillHops]

Could you download CPU Temp from my Sigs, and keep an eye over the TEMPS.

Just for a couple of hours.

After this we have a few other tests i would like you to run.

After extracting the files in the download archive, I got the error message that my Real Temp does not support my processor (AMD Phenom II 1035t)

This is for both the RealTemp.exe and RealTempGT.exe

Edit: Ok using Core Temp instead as it would appear Real Temp only supports Intel processors.

 

[WillHops]

Ok so I've been running Core Temp for the last few hours. Just surfing the net and watching youtube, the min temp was 25*C and the Max was 37. Running a PC game for a bit, the max hit 45*C. Core Temp states that my Tj. Max is 70*.

What was that part about a faulty update you mentioned?

Thanks again for your help!

 

[WillHops]

U there Harrie?

 

[WillHops]

removed, can anyone take me to the next step?

 

[WillHops]

..............

 

[HarriePateman]

Sorry for the Late Reply.

Okay your Temps are fine.

2014-06-22	10:14:37:959	 888	10b8	Misc	WARNING: WinHttp: ShouldFileBeDownloaded [COLOR="Red"]failed [/COLOR]with 0x80190194
2014-06-22	10:14:37:959	 888	10b8	Misc	WARNING: DownloadFileInternal[COLOR="red"] failed[/COLOR] for http://download.microsoft.com/v9/1/windowsupdate/redir/muv4wuredir.cab: error 0x80190194

Now we need to stress you components as one of them is failing.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html

 

[WillHops]

Well I ran both of those diagnostics, my PC passed with flying colors..

Maybe my GPU is overheating? Not sure what else it could be.. besides poor coding of the game which is probable, but people are running it on specs similar to mine so who knows..

Is there any chance I need to just update my GPU bios?

 

[WillHops]

Well I ran both of those diagnostics, my PC passed with flying colors..

Maybe my GPU is overheating? Not sure what else it could be.. besides poor coding of the game which is probable, but people are running it on specs similar to mine so who knows..

Is there any chance I need to just update my GPU bios?

Well the GPU is not overheating, Used Speccy to check its temps... About to give up on this stupid game as I have diagnosed literally every piece of hardware in my machine, I guess theres a chance its my PSU but as far as I can tell the only way to troubleshoot that is to have another PSU on hand to replace it with, which I dont so, meh.