old computer won't turn on?

J

J Crew

New Member
i just bought a set of new HP computers, but i have an older p4 2.0ghz computer that i wanted to give to my brother-in-law as he's still using an old p3. but right before i got the new HP's in, she started acting up. when i go to start her up she'll start to load then she'll give two quick beeps and nothing. the fans are still going and everything seems to be getting power, but windows just doesn't load. anyone know what this could be? is it fixable? thanks for any help.

- Jason

btw... it's a p4 2ghz running on a pentium motherboard with 256mb of ram. thanks again.
 
try removing the stick of ram then putting it back properly. it might just be loose. also try reconnecting the hard drive.
 
bigsaucybob said:
try removing the stick of ram then putting it back properly. it might just be loose. also try reconnecting the hard drive.
Click to expand...

thanks, i'll try that when i get home. so basically it sounds like it's a loose connection somewhere... ram or whatever. anything else it could be?
 
Does it say that a file is corrupt, that its missing an operating system, or just a blank screen?
 
nothing stating a file is corrupt... it just stops booting. it never starts loading windows. right at the time that windows would normally start to load, it make two quick beeps. i still haven't messed with it over the last couple of days, so i've yet to find out if there is something loose. once i mess with it, i'll post back with the results. thanks again.
 
If you have an AMI bios, two short beeps indicates a parity circuit failure (http://www.hi-tech.net/zones/help-beep.html). This usually means either faulty RAM (which may just need to be reseated) or a faulty motherboard. Different BIOSes have different error codes, so it would be worth knowing what mobo you have.
 
ceewi1 said:
If you have an AMI bios, two short beeps indicates a parity circuit failure (http://www.hi-tech.net/zones/help-beep.html). This usually means either faulty RAM (which may just need to be reseated) or a faulty motherboard. Different BIOSes have different error codes, so it would be worth knowing what mobo you have.
Click to expand...

i believe that it's an intel board... but i'll have to check when i'm at home. thanks again.
 
You must log in or register to reply here.
Back
Top