View Single Post
Old August 13th 16, 04:49 AM
navyfalcon navyfalcon is offline
First recorded activity by HardwareBanter: Aug 2016
Posts: 5

Originally Posted by View Post
On Wednesday, 19 November 2008 14:54:41 UTC-5, csar244 wrote:
This is kind of a long story...Please someone tell me what to do!
About 3 weeks ago my psu went out and I brought my PC to work to have
our IT guy fix it. He replaced it with a Rhino ATX 12v 450 watt
power supply (it had whatever the standard 12 v 300 watt for hp is).
My PC is a Compaq SR2180NX with Vista Home Premium.
Anyway, after he fixed it, it would come on, but now it will not stay
on! It will boot up and stay on for MAYBE 5 minutes and then it will
go blank. The power light is still on, but it will not do anything. I
have to hold the power button down for a few seconds before it will
go off. If I try to turn it on for the next hour or so (sometime
longer), it will only boot up to the start screen and do the same
thing. Sometimes the light will only blink and the fans start to
turn but they go off almost immediately. AgHHH! I have tried
everything. I have replaced the Bios Battery. I have cleaned my
DIMM. I have cleaned out all of the dust, checked my pins....I don't
know a lot about the "guts" of the computer so I am asking
for HELP! The other day I was able to get it to stay on for almost
an hour. I was playing solitaire and it shut off in the middle of
the game. This is driving me crazy. Do you think it could be a bad
power supply?
Go to and download (for free) the troubleshooting manual for your computer. This will give you a guide to follow. Then download the diagnostic program (some manufactures have it and it would be listed in the manual). Check the voltages from the Power Supply at their connectors (without the power supply connected to the Motherboard). The manual will state the voltages. This will check both the Power Supply and if the PSU (power supply unit) has the correct voltages to the MOBO (motherboard). Then check the manual for checking the computer for symptoms and solutions. This should give you a system to troubleshoot and not easter egg hunting (we call it easter egg hunting, not shotgunning, but the idea is the same). All troubleshooting should be systematic. That way the system is thoroughly checked without missing an area.
hope this helps