Random Restarts as of today.....

[GoatyGoat]

Yesterday my PC worked perfectly fine.
Then I turned it on this morning, and just after the "Windows Lodaing" screen disappeared, it restarted. And then again, and again at the same point.

Then I tried Last Known Good Config. - didnt work the first time, but it did the second time.

Up comes Windows in glorious 4-bit colour and 640x480 res.

I reinstall graphics drivers...and then I'm OK.

THEN, Windows Media Player needs reinstalling for some reason (was fine yesterday).

Go to play my game, and it restarts randomly wile playing. So I tried again...same thing.

So I check the System Properties and breathe a sigh of relief - I found the culprit..."Automatically Restart on Errors" was ticked. So I unticked it, and restarted......

IT STILL HAPPENS!! What could be causeing this?? I pretty sure it's not heat since I have my deskfan blasting in my case and a new CPU fan and case fan.

Specs:
ECS K7VZM 1.0a Motehrboard
LASTEST BIOS 1.1g
AMD Athlon Thunderbird 1.2GHz (200MHz FSB)
512MB SDRAM (100Mhz)
20GB HDD
80GB HDD
Windows XP Pro (SP1a)
50x CD-ROM

 

[GoatyGoat]

Extra Info:

NO Virus'
85 tracking cookies found - all deleted
NO other Spyware
LATEST VIA chipset drivers
ALL Windows Updates
LATEST Graphics Card Drivers

 

[flyingwolf23]

bad Power supply?
Just a guess.

What error message do you get when it says "windows recovered from a serious error"?

Semper Fi

http://www.jnatek.kicks-ass.net

http://www.awh.kicks-ass.net

http://www.baby-james.kicks-ass.net

My new Baby BOY!!

 

[RebeccaLynn]

is it am IBM aptiva or do you have a UPS? we had a problem with both of those things doing exactly what you describe.

The IBM Aptiva had a defective MotherBoard.

The UPS had it's main board go bad.

Becca.

Somtimes, the easy answer is the hardest to find.

 

[flyingwolf23]

also the same problem with radeon 64 meg ddr video cards.

Semper Fi

http://www.jnatek.kicks-ass.net

http://www.awh.kicks-ass.net

http://www.baby-james.kicks-ass.net

My new Baby BOY!!

 

[dor35]

I had a similar problem on a nearly-new PC. turned out to be faulty memory, even though it checked out OK.