BSOD/Cold booting on FEAR 3 and Portal 2 loading screens

[Dimefan3]

Hi all, new poster here, so please be fair.

2 days ago Portal 2 was playing fine, but yesterday I upgraded my CPU (to an AMD FX 4100 Quad Core Black edition), motherboard (Gigabyte 78LMT-S2P) and my Ram (4GB DDR 3). I figured I could just swap the components and keep going without reinstalling windows 7. But after swapping everything and loading up Portal 2 would just cold reset on me on the loading screen.

I've tried reinstalling windows 7 today and I'm in the process of reinstalling Portal, but now another game I've just purchased, FEAR 3 is now also cold resetting on the loading logo.

I've tried going through a few other suggestions, like running steam on just one core, with no luck. I've got a crash report below and attached the zip file. Any ideas?

I have a theory that it might be my PSU, which runs about 550W. (Also brand new)

[FONT=Segoe UI, Arial]On Mon 1/16/2012 1:08:49 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011512-34273-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x3224B3)
Bugcheck code: 0x124 (0x0, 0xFFFFFFFF85F528FC, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]WHEA_UNCORRECTABLE_ERROR[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA). [/FONT]

 

[JMH]

Dimefan3,

Your .dmp file shows a stop error of 0x124 which is a general hardware error .

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.

Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress

Some generic advice.

If you are overclocking STOP.
Return to the default settings at least for now.

If you are running a RAID update its driver.


You can read more on this error and what to try here...

http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html