Civilization V, Steam, BSOD Hardware issue?

Welcome to SF 60sIron :) .

The BugCheck Codes vary quite a bit!
I suggest we start with testing the RAM and overall system maintenance.

Testing the RAM:

koolkat77 said:

Test and Diagnose RAM Issues with Memtest86+:

• RAM - Test with Memtest86+

   Tip

• Pay close attention to part 3 of the tutorial "If you have errors"
• Test the RAM with Memtest86+ for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.

When done with the testing procedure take a picture and upload it here.

This will help you to determine where the issue is origination from (if any):

Arc said:

First run it with all the existing/installed RAM modules. If it comes with no error, all is good.

But if it starts showing errors, Stop testing. Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:
No code has to be inserted here. It is a RAM, a bad RAM.

But if you have got a result like that:
No code has to be inserted here. It is a motherboard issue. The particular slot is bad.

Clean up your start up be following this tutorial:

• Troubleshoot Application Conflicts by Performing a Clean Startup

Remove McAfee and replace it with MSE:

• Microsoft Security Essentials - Microsoft Windows

Post back with the results :).

You don't , you use a camera of some kind :).

60sIron said:

I ran the test overnight and found 5 errors. Correct me if I'm wrong, but it doesn't seem to pinpoint which module or which slot had the errors.

So I've got two modules in two slots. I'll pull one of them and re-run the test tonight. I've also got a new stick of DDR3 1600 which is waiting for a MB to come back from RMA that I could use to test.

No, unfortunately it doesn't :\, you can review post #2 for further diagnosis.

Keep us up to date with any developments :).

It's always handy to have spare parts :).
Pleas let us know about any developments.