Loading OS problem

gmc8757

Member
Feb 9, 2005
170
0
0
i have a computer that i'm fixing for a friend...when i got it, he said the motherboard would need to be changed...and he took out the cmos battery. So first thing i did was put in a cmos battery, and it booted up right away. so i let it sit for about 4 hrs, came back, and it turned off. So i wasn't sure if it was heating issues or what. Now, i try to start it up, and i get a the blinking cursor in the top left hand corner and that's it. So i leave it be for about 4 more hours, go back unseed everything put it back, try to start it, it starts right up.

Once it's up and running, i run stress test on it...for a day and a half it ran at 100% cpu speed with no problem, handled it very well. When the tests are done, i try to restart, and the same thing, blinking cursor in the top left hand corner. Keep tryint to start it, and finally it starts.

Do you guys have any idea what could be causing it to start sometime and not the other times?

It's a compaq pasario 6300us, celeron 1.4 with 192mb ram. Not a great machine by any means, but for what they want to do with it, it's enough.

Please any help????
 

aGreenAgent

Senior member
Apr 25, 2005
274
0
0
Try taking out the CMOS battery, unplugging it from the wall, wait 10 seconds, then plug it back in, still without the CMOS battery and see if it starts.
 

gmc8757

Member
Feb 9, 2005
170
0
0
Hey there, thanks for the response...i tried that. Sometimes it works, sometimes it doesn't.

It seems like now it's actually starting up everytime. I'm sure it's not fixed whatever the problem is, anyone else have some ideas?
Thanks again.
Joe
 

wpshooter

Golden Member
Mar 9, 2004
1,662
5
81
Could be marginal power supply ???

Do you have another power supply, you could try for a few days ?
 

gmc8757

Member
Feb 9, 2005
170
0
0
i can find one i'm sure.

You think the power supply would do that? Run no problem for hrs and then if i shutdown, and try to turn it back on, it won't come back? I never knew a power supply would do that.

I actually just went into the bios and changed back to all defaults, and it's been fine all day. So i'm hoping he went in there and made some bad changes, where setting it back to default fixed it. We'll see i guess.
Thanks