Posting from an unstable computer!

[CaptainWafflos]

My computer has been restarting frequently for the past few days. In order to fix this, I've tried many different methods. Switched out my power supply, pulled out both memory sticks to see if either one was malfunctioning, reformatted and reinstalled Windows from scratched, flashed my BIOS to see if that would fix anything. Nothing has worked.

Symptoms of crashing: usually occurs when Windows is running, but not always. Crashing tends to become more frequent the longer I've been on. My temperature monitor reports CPU temp at 40C and NB temp at 44C, so I've pretty much thrown the theory of overheating out the window.

Any suggestions?

 

[CraigRT]

I have what may be a stupid question.

when does it crash when windows is not running? I don't get it.

still sounds like a power issue to me, but not totally sure.
what PSU did you try to swap with?

 

[gsaldivar]

Check the Event Viewer for any signs of hardware/software malfunction.

Also, try disabling Windows XP's auto-reboot feature: Right-click My Computer > Properties > Advanced > Startup and Recovery, Settings > System Failure > Uncheck "Automatically Restart"

 

[CaptainWafflos]

When Windows has not started. As in, when the computer is starting up and is on the BIOS screen, it just stops responding.

Old PSU is Apex ALLIED 400w PSU. New PSU is OCZ Powerstream 420w PSU. Problem exists with both PSUs, which leads me to believe it isn't a PSU problem.

 

[gsaldivar]

Check the motherboard closely for any signs of capacitor damage.

Try removing all unnecessary PCI cards, and drives.

Swap out the video card with a known good unit to rule that out as a cause.

Remove all but 1 stick of RAM, and swap that stick out with a known good unit to rule that out as a cause.

 

[CaptainWafflos]

Already performed your RAM fix. I don't have a good video card on-hand that I can use to check my video card, but I'll try that later. I have no PCI devices installed.

 

[CaptainWafflos]

Gsald, where exactly should I look in the event viewer for hardware failures?

 

[gsaldivar]

Event Viewer (Local) > System

Unfortunately, XP will not log every type of hardware malfunction, however this is a good place to check when you are troubleshooting.

 

[gsaldivar]

You might also want to inspect the chassis closely for any loose connections. Inspect the power sockets of your drives closely for any signs of arcing (scorch marks, burnt smell). Make sure that the underside of the motherboard isn't making contact with the chassis itself (use standoff spacers if necessary). With the computer booted into DOS, try carefully shaking/vibrating the case to see if this causes the system to crash. Swap out the external AC cable and any power strip you are using to rule that out as a cause.

 

[CaptainWafflos]

I already have standoff spacers used when I initially mounted my motherboard. Tried connecting my PC (edit: with a different power cord) directly to a different power outlet. That didn't fix anything.

What should I look for when looking for damaged capacitors? I don't see any blaring differences between the "damaged" and "Repaired!" pictures on that website.

 

[gsaldivar]

Originally posted by: CaptainWafflos
What should I look for when looking for damaged capacitors? I don't see any blaring differences between the "damaged" and "Repaired!" pictures on that website.

To completely check for bad capacitors, it may be necessary to completely remove the MB from the chassis. Use a bright light and check for any signs of bulging on the tops of the capacitors. Also look for any signs of electrolyte leakage from the underside of the capacitors.

http://www.badcaps.net/ident/

While you have the board unmounted from the chassis, take the time to inspect very closely for any cracks, scorch marks, etc. on both sides of the board. Reseat the CPU/HSF while you're at it, etc.

Just in case - swap your KBD/mouse out to rule those out as a cause of intermittent unresponsiveness.

 

[CaptainWafflos]

Just got BSoD for the first time! It's like rolling dice to select the method of my computer crashing now!

I'll do the above method tomorrow. Right now, it's 1AM and I don't have time. Going to head to bed. If anyone else has any last minute suggestions, I'll be happy to read them when I wake up tomorrow morning.

Thanks for the help!

 

[fusion22]

most crashes or computer being unstable is due to a power supply being not adequate enough for the machine. 400 or 420w is probably not enough. Now before I get ahead of myself. wattage means a little but it is not everything. For an Athlon 64 system, I'd recommend a PSU that has at least 20a or higher. I have a PSU that has 28a. The only time it crashed was when I had a Thermaltake 480w PSU. Wattagew was great, but the Amerere was at 18a. Which caused the computer to crash using nero to burn cd's with the BSOD. One the new PSU that has the 28a on +12v rail into the case, I never seen the BSOD's again. So my suggestion would be to take a look at the PSU your trying to use with your system.

 

[CaptainWafflos]

My PSU has 30A on the +12v rail. There is no chance at all that my PSU is the problem.

 

[CaptainWafflos]

 

[CraigRT]

try 1 drive @ a time, it's likely not both.

 

[Googer]

Try a pc power and cooling PSU, because antec over-rates their PSU's.

 

[imported_NoGodForMe]

Loosen memory timings.
Some boards default everything to auto, and if you are running 2225 memory, it may crash.
I have to run my memory at 2336. When I first installed my OS, it would crash all the time until I got a memory error and figured it out.

 

[CaptainWafflos]

I don't have an Antec PSU.

Turns out restarts are still occuring even with the CD-RW/Floppy Drive fix. Thread still open for suggestions.