Computer starts but deosn´t boot

Intel P4
May 9, 2007 at 05:12:32
Specs: Win XP, 3.4 GHz/1024MB Ram
When I start my computer all the fans,LED,HDDs,DVDs and so on is running but it doesn´t beep as it do when BIOS is loading. And the screen is still black.
I thought it was a BIOS problem so I bought a BIOS Savior (changed the BIOS-chip) but still got the same problem...!
What can I do?
Please help me!
Intel P4 3.4 GHz
Asus P5GD2 MotherBoard
Kingston 2x 512MB RAM

See More: Computer starts but deosn´t boot

Report •

May 9, 2007 at 06:05:38
"What can I do?"

You can start by improving your troubleshooting skills. Replacing the BIOS chip isn't an item that would be high on my list of possible fixes. Unless you did something that you're not telling us, such as attempted a BIOS flash?

The top 3 things to look at would be the PSU, CPU or motherboard.

Report •

May 9, 2007 at 06:22:53
You can start by improving your troubleshooting skills

That's a nice suggestion but in realty not everyone can become a technie overnight. If you can diagnose error codes then you are already one LOL


Report •

May 9, 2007 at 06:33:51
No I didn´t do any updates...The computer started to turn off by itself, then I turned it on, 5min later it turn off, again. And when I was turning it on for the 3rd time it was like this...
How can I test if it is one of those 3 you mentioned? How can it be a PowerSupplyUnit if the fan, HDD, LED, and so on, is working?
And by the way...there is no beep at all.
Thanks for your reply´s!

Report •

Related Solutions

May 9, 2007 at 07:07:13
mmm - perhaps it has overheated a little...?

Power off; remove mains-cable as well... Then open/remove the case and carefully check that all air vents etc. are free of dust; also that the psu and cpu cooling fan are clear and if possible that they do spin freely.

With cover off... restore power and switch on; carefully observe/watch that all fans run properly - including the cpu fan.

If all airways are clear, and all fans run OK, power off and remove mains-cable; then carefully check that "all" internal connections are "sound" - including all RAM sticks (although with no POST beeps they would not be the problem at this stage?).

And if practical - restore original bios chip as was; then see if you can boot and reload bios defaults etc.?

Report •

May 9, 2007 at 07:57:59
"How can it be a PowerSupplyUnit if the fan, HDD, LED, and so on, is working?"

Just like a weak battery on a car can put out enough power to play the radio or light up the headlights, but not have enough power to turn over the engine...a PSU can put out enough juice for fans & LEDs, but not enough to power up an entire system.

"not everyone can become a technie overnight"

I realize that. But using the same car analogy...if the lights & radio work but engine won't turn over, you don't have to be a mechanic to know that changing the spark plugs isn't gonna help.

Report •

May 9, 2007 at 08:16:02
I love it when for once people use their brains.

Seriously though, I'd have checked my power supply first.

You said that the computer was turning itself off -- surely the power supply is the culprit.

A quick google indicates that video cards, motherboards OR power supply could be your problem but changing the power supply is definitely your first task I'd say.

There is one subtle yet vital difference between opinion and fact; and the bigger man is he who can whole-heartedly admit this.

Report •

May 9, 2007 at 09:11:51
I just had this issue this morning -- the PC's status lights and fans come on, you get no post errors (beeps) and the monitor stays solid black yet the power light on the monitor is green (verifies its getting a signal from the vid card). It turned out to be bad ram, I was lucky enough to have a couple spare sticks laying around so I popped them in and viola PC is back to running like a champ.


Report •

May 9, 2007 at 09:16:34
Bad RAM *should* result in beep codes. And generally speaking, working RAM doesn't just suddenly "go bad".

Report •

May 9, 2007 at 09:19:04
I know that it *should* however that is not always the case, as this morning for me proved it.

Report •

May 9, 2007 at 11:33:07
A couple of years back at work we had a W2K system that one day failed to boot. Came up silently to a black screen - no beeps or whatever - and stayed there.

"They" (IT dept.) checked the drive etc. on another system; all OK... Checked PSU etc. etc. - OK... Swapped out RAM (two 128Meg sticks...) for new/known to be good sticks - and lo it did light up and was back again as a hot swap system...

This "box" had worked fine until the that morning...; although in hindsight it had been a little picky occasionally on boot up near to the time it actuall died... New RAM and it was a happy bunny...

I emphasise it booted to black/blank screen - silently; no beeps, groans, moans, screams or cries for help... HD light lit up - and stayed on - but no boot thru' to normal ops.... - until new RAM.

I can go along with the weak battery approach; not unknown for some kit - and there is wide range of it in all fields - to light up to some extent but fail to work properly. I have fixed a wide range of electronics over the years (from days of valves/tubes... to solid state); and seen an occasional PSU apparently OK but the kit didn't work - until the PSU was replaced - but not very often.

And as for RAM just going bad... we've had this discussion before. It does occasionally just decide to die or go bad...; it's just the manner or speed of the transition to a "no workie anymore" state that is the misdirect... Some solid sate items will just fail; some will go down slowly, and may/may not produce problems (symptoms) on the way...

Report •

May 9, 2007 at 14:14:33
Now it boot as normall...thanks for the help!
It was the RAM, I have 2 512MB DDR2(expensive I thought it was the best...but unfortunately not) and one of those wasen´t working. But I got a message after booting up screen: "Reboot and Select proper Boot device or Insert Boot Media in selected Boot device and press a key"
Is that meen that it is lack of any OS?
Thanks again for all your replay´s!!!

Report •

May 9, 2007 at 17:44:31
"but in realty not everyone can become a technie overnight"

What do realtors have to do with anything?

'Technie' or not - changing the BIOS chip is a big right angle jump from actual troubleshooting

"Is that meen that it is lack of any OS?"

Well, it means it can't boot from the hard drive, so if XP is installed, you may need to repair - assuming the drive is seen correctly in the BIOS

Maybe Fixboot from the recovery console

I'm not one of those who think Bill Gates is the devil. I simply suspect that if Microsoft ever met up with the devil, it wouldn't need an interpreter.

Report •

May 10, 2007 at 01:42:49
mmm RAM - yet again...?

Incidentally... it might not actually be a duff stick; but possibly it wasn't properly seated in its slot? But at this stage I'd be more inclined to dump that particular stick - or send it back for replacement if under warranty.

In your initial post you say you changed the bios chip - and things still didn't work OK.

Now you can boot at least... enter the bios settings and ensure they are correct; i.e. the bios does detect the drive and so on correctly. Use the auto-detect option for the drive(s).

Also set the boot order to be either: floppy first then hard-drive; or hard-drive then floppy; or even CD first then hd, then floppy. Personally on a system with a floppy I like to have the floppy as first boot-device, then the hard-drive. But some other folks will prefer a diffferent order; matter of taste.

Also I seem to recall that changing the bios chip can affect the XP authentication routine too? (But I wouldn't swear to to it; possibly XpUser et alii can confim or other wise in this latter regard?)

Might not hurt to replace orginal bios chip and see what happens...; this before running any repair routines?

Report •

Ask Question