Computer boot up

[Joe]

Hi sorry if this viewed as cross posting but the Microsoft Public hardware
is not replying to my post. When I try to boot my daughters computer the
power light comes on and
the fan starts up. I get no POST beep, no signal on the monitor. I have
checked all cables with another computer. Any ideas?
Joe

 

[Kenny]

Have seen this twice now, once it was the CMOS battery, the other time
faulty RAM.

 

[Paul]

Hi sorry if this viewed as cross posting but the Microsoft Public hardware
is not replying to my post. When I try to boot my daughters computer the
power light comes on and
the fan starts up. I get no POST beep, no signal on the monitor. I have
checked all cables with another computer. Any ideas?
Joe

One debugging technique, is to remove some hardware, and simplify the
configuration. For example, you can get POST beep codes by using only
the processor and the motherboard. You can remove the video card,
RAM, disconnect hard drives and CDROM etc. Once you get down to the motherboard
and CPU, there isn't much left to go wrong. Getting a beep code of
some sort, means the CPU has executed some code. If you still aren't
getting anywhere, the PSU has the highest odds of failure.
The motherboard would be next most likely. And the CPU should hardly
ever fail. The fact you have a fan spinning, means the PSU is not
completely dead. I would visually inspect the motherboard for any
damage (burned parts, leaking capacitors). You can also use your
nose, to sniff for anything that seems burnt.

When working inside the computer, make careful notes of where everything goes.
It might be a good idea, to not pull any hardware at first. Get out
your notepad, and make notes of the orientation of the connectors (which
side the red stripe goes on the cables, even if it looks unlikely they
can be mated wrong. The floppy cable can be inserted wrong for
example). Be especially careful with the PANEL header that has the
power LED, power switch, reset switch and so on. If you have a manual
for the motherboard, then you can make your notes right in the manual.

Also remember, to remove all power before working inside the computer.
You can damage RAM, for example, if the computer is "sleeping", as the
+5VSB from the supply may still be present. The safest procedure, is
to unplug the computer, and then make any hardware changes.

Paul

 

[Joe]

One debugging technique, is to remove some hardware, and simplify the
configuration. For example, you can get POST beep codes by using only
the processor and the motherboard. You can remove the video card,
RAM, disconnect hard drives and CDROM etc. Once you get down to the
motherboard
and CPU, there isn't much left to go wrong. Getting a beep code of
some sort, means the CPU has executed some code. If you still aren't
getting anywhere, the PSU has the highest odds of failure.
The motherboard would be next most likely. And the CPU should hardly
ever fail. The fact you have a fan spinning, means the PSU is not
completely dead. I would visually inspect the motherboard for any
damage (burned parts, leaking capacitors). You can also use your
nose, to sniff for anything that seems burnt.

When working inside the computer, make careful notes of where everything
goes.
It might be a good idea, to not pull any hardware at first. Get out
your notepad, and make notes of the orientation of the connectors (which
side the red stripe goes on the cables, even if it looks unlikely they
can be mated wrong. The floppy cable can be inserted wrong for
example). Be especially careful with the PANEL header that has the
power LED, power switch, reset switch and so on. If you have a manual
for the motherboard, then you can make your notes right in the manual.

Also remember, to remove all power before working inside the computer.
You can damage RAM, for example, if the computer is "sleeping", as the
+5VSB from the supply may still be present. The safest procedure, is
to unplug the computer, and then make any hardware changes.

Paul

Thanks very much for that, very helpful. Some one suggested a 'Soak Test
for the Mobo' What's all that about.

Joe

 

[paulmd]

Thanks very much for that, very helpful. Some one suggested a 'Soak Test
for the Mobo' What's all that about.

Joe

I've never heard of that before eiher, but a quick google search turned
up this.

http://loadtest.com.au/types_of_tests/soak_tests.htm

Except whoever suggested THAT is blowing smoke. You have to get it
WORKING first before you can do any sort of endurance test.

 

[VanShania]

I had a problem similar to that when I had reinstalled my sound card. After
loading my OS and drivers, I shut the computer down, put the card into its
normal spot and when I started up, it wouldn't boot. Reinstalled the card
into a different pci slot and away it went. I wonder if some of these
problems occur because dust gets between the connections somehow.

--
Love and Teach, Not Yell and Beat
Stop Violence and Child Abuse.
No such thing as Bad Kids. Only Bad Parents.
Friends don't turn friends on to drugs.
The path often thought about and sometimes chosen by abused children as
adults is Suicide. Be a real friend.

A64 3500+, Gigabyte GA-K8NSC-939,AIW 9800 128mb
MSI 550 Pro, X-Fi, Pioneer 110D, 111D
Antec 550 watt,Thermaltake Lanfire,2 Gb Dual Channel OCZ
2XSATA 320gb Raid Edition, PATA 120Gb
XP MCE2005, 19in Viewsonic,BenchMark 2001 SE- 19074
Games I'm Playing- Falcon 4, winSPWW2, winSPMBT

 

[Rod Speed]

Nope, its because the bios allocation of IRQs etc gets ****ed up.