Locked-Up System (no BSOD)

Hey guys,.

Some of you may know that I just rebuilt my rig, literally from the ground up. (The only not-new parts are my RAM and one of my hard drives, and 1 of 2 graphics cards).

Starting a couple days ago, I seem to come across an issue that locks up the system cold (no BSOD, though). It's happened twice so far. First was starting up Firefox. The moment I clicked the icon, it seized up. Second was when I tried to fire up Adobe Soundbooth CS5. The PC doesn't shut down, or blue-screen. It just freezes.

Usually pressing the hard reset button on the case works however after a doing that the 2nd time, Windows took 3 times too boot properly.

Startup repair found nothing. Eventually it booted as I am using it right now.

I want to lean on the RAM as the culprit. If it is, it's not a big deal to replace it. I've been pondering adding more RAM to go from 4GB to 6 or 8GB anyways.

Tell me what you guys think. Any ideas? (Spec in signature)

I've attached a text document of all my Crit and Errors. There is one bugcheck (1001) with 0x101 but that was due to my undervolting while attempting to overclock.

I can easily point you to each occurrence because each time the log only shows the events after the reboot (41, KernelPower; 6008, EventLog). The only other crits/warnings happen too far in the past to be related, IMO.

Any idea, people?

It seems to happen most of the time after a cold boot. The moment I launch any app of any kind (typically Firefox) it freezes (no BSOD). I hit the reset button and it works fine after that.

Can you upload a report. I'd like to take a look

https://www.sevenforums.com/crashes-d...tructions.html

mgorman87 said:

Can you upload a report. I'd like to take a look

https://www.sevenforums.com/crashes-d...tructions.html

Sure.

It hasn't happened to me the last few days. My normal morning launch doesn't lock up my system.

The only memory dump you'll find is from an attempt at overclocking back when I first built the machine. I haven't deleted any.

I want to post what I think is the resolution to my problem. It seems to be power supply related but since it has seemingly gone away on it's own, I see no need in continuing troubleshooting.