BSOD, random restarting, pc wont boot.

[apocalypseon]

Pc Specs - Amd Athlon II X2 240 (Regor). Asrock M3A785GXH/128M. Kingston KVR1333D3N9/2G 2GB DDR3 Ram. Cooler Master eXtreme Power Plus 390W. Windows 7 Professional.

The PC was assembled around 2 1/2 years back. Except for the PSU that was bought around 4 years back. Unfortunately I can't remember when exactly. I'll find out.

The issue at present, is random but frequent BSOD crashes. Sometimes while using the computer, mostly surfing and videos. Other times, when idle, like downloading.

I have replaced two hard drives since the BSOD crashes first started around a year back. It first surfaced around a year back. Now it's happening again. There was random restarting too. The pc would also not boot several times.

Memtest86 gave a 'unexpected interrupt' error, in garbled words, when I ran it overnight.

Couple of days back, a technician was called in. According to his diagnosis, the CMOS settings had become corrupt due to some changes I had made in the BIOS. I had overclocked the mGPU settings briefly. But reverted to default settings after the problems. I didn't touch the memory timings. He also added that the CPU was overloaded by this and was overheating. This morning it BSODed again.

Here's the link to the minidump. https://skydrive.live.com/#cid=D7725...100CD10F2A!105. Is there any other site?

I haven't run any cpu stress tests yet. I can't think of any other details as I am short on time(the pc might crash).

[James]

Basics:

1. Make sure all of your fans and heatsinks (and the computer in general) are dust free. Use canned air to blow out any accumulated dust.
2. Watch your temperatures with a temperature monitoring program.
3. If your temperatures aren't getting super high, then it probably isn't a heat issue.

[apocalypseon]

Cleaned the dust a couple of days back. Cpu temp would show a little high in the bios earlier. But now it's around the 45-50c mark. Anyway here's an update.

I ran memtest again, this time it passed. Could it be the corrupt CMOS settings that was making memtest give that weird erorr? Aww heck, now I can't remember if I first ran memtest, before or after the technician's diagnosis of the CMOS being corrupt. Matter of fact, I didn't even ask him how he fixed it! Isn't a CMOS corruption when you get a 'Checksum error' at bootup? Gotta lay off the mary jane.

Also, I had a another BSOD problem with a WRkrn.sys file after I uninstalled AVG. Turned out it was a Webroot AV driver. I had to do a 'last known good configuration'. All in all, I haven't had a BSOD since yesterday.

Right now, I'm thinking, I could sit on it and wait for it to happen again. Or I could run some stress tests? OCCT? Should I risk it though, considering my PSU is old and only 390W? Thanks for your suggestions and time.

[kujoe2002]

my gut reaction would be to say try other RAM. I bought brand new RAM only to RMA it right back for causing BSOD's. This is what I would do:

Open your system and unplug and reseat ALL of your hardware

ensure ALL of your drivers are up to date

try different RAM

[[PinPals]Apu]

If it does blue screen again, try to get the stop code (the 0x000000?? number). Those often help in diagnosis.

[agello24]

2 things i can suggest. 1. the kingston memory might be bad. they have released some bad batches of ddr2 and ddr3. i have stacks of it here for comparison from clients pc's. try getting some patriot or corsair memory. 2. the power supply is 390W from corsair. Name brand companies can release some bad or PSU too. try someone elses PSu.