No video on start

Hello group,
Apologies if this post should be in "hardware". A friend has a one
year old clone computer, windows XPPro sp2. I don't have the system
details, but I believe it's a late model Intel CPU. He used it for
flight simulator programs, so it's a pretty hefty system. He hasn't
turned it on for several months, but the box hasn't been moved or
damaged.
On startup, there are three long BIOS beeps, and no video at all.I
changed the monitor and that did not help. The fans are running.
I assume the problem is something very basic, since video comes up so
early in the startup process.
Does anyone have any thoughts about where to look first for the
problem? Obviously, I'd check for bad or poorly seated memory and
visually for any bad connections to the motherboard.
Is this a common problem?
Thanks for any suggestions.

Jack

Ace
Mon Oct 01 08:19:43 CDT 2007

Correct, should have posted in hardware group, but this is not something
specific to Windows XP, it is purely hardware, as the mainboard
desperately cries out to you with system beeps :)
You may want to find the mainboard's manual on the manufacturer's website
to discover what the beep pattern means exactly, this will help your
troubleshooting.

Your specific problem may lie in either:

Processor;
RAM Modules;
Video Card.

I would first try the RAM and Video card. remove these, clean the slots,
and re-seat them where they were.
Should beeping continue, you can also try with just 1 RAM stick, change
these to determine a possible faulty stick.
If you have another video card handy, same story - try it.






JClark <jclark@nomail.invalid> wrote in
news:0mj1g3t5h7c4k3imbv46qf23nc7md595tb@4ax.com:

> Hello group,
> Apologies if this post should be in "hardware". A friend has a one
> year old clone computer, windows XPPro sp2. I don't have the system
> details, but I believe it's a late model Intel CPU. He used it for
> flight simulator programs, so it's a pretty hefty system. He hasn't
> turned it on for several months, but the box hasn't been moved or
> damaged.
> On startup, there are three long BIOS beeps, and no video at all.I
> changed the monitor and that did not help. The fans are running.
> I assume the problem is something very basic, since video comes up so
> early in the startup process.
> Does anyone have any thoughts about where to look first for the
> problem? Obviously, I'd check for bad or poorly seated memory and
> visually for any bad connections to the motherboard.
> Is this a common problem?
> Thanks for any suggestions.
>
> Jack
>



--
*Reply to newsgroup please.
*Your mileage may vary.
*Spelling/Grammar errors free of charge.

Malke
Mon Oct 01 08:24:14 CDT 2007

JClark wrote:
> Hello group,
> Apologies if this post should be in "hardware". A friend has a one
> year old clone computer, windows XPPro sp2. I don't have the system
> details, but I believe it's a late model Intel CPU. He used it for
> flight simulator programs, so it's a pretty hefty system. He hasn't
> turned it on for several months, but the box hasn't been moved or
> damaged.
> On startup, there are three long BIOS beeps, and no video at all.I
> changed the monitor and that did not help. The fans are running.
> I assume the problem is something very basic, since video comes up so
> early in the startup process.
> Does anyone have any thoughts about where to look first for the
> problem? Obviously, I'd check for bad or poorly seated memory and
> visually for any bad connections to the motherboard.
> Is this a common problem?
> Thanks for any suggestions.

This is a hardware problem since your friend's computer isn't even
getting through the POST. The beeps are an audible code that tell what
is wrong. Your friend needs to go to the motherboard mftr.'s website or
look in his motherboard manual for the meaning of the audible code. If
he has an OEM machine such as a Dell or HP, he should check with the OEM
either by calling their tech support or looking on their website. That
will tell him which component has failed and you can troubleshoot
accordingly.


Malke
--
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"
MS-MVP Windows - Shell/User

JClark
Tue Oct 02 03:21:49 CDT 2007

On Mon, 01 Oct 2007 10:50:27 GMT, JClark <jclark@nomail.invalid>
wrote:

>Hello group,
>Apologies if this post should be in "hardware". A friend has a one
>year old clone computer, windows XPPro sp2. I don't have the system
>details, but I believe it's a late model Intel CPU. He used it for
>flight simulator programs, so it's a pretty hefty system. He hasn't
>turned it on for several months, but the box hasn't been moved or
>damaged.
>On startup, there are three long BIOS beeps, and no video at all.I
>changed the monitor and that did not help. The fans are running.
>I assume the problem is something very basic, since video comes up so
>early in the startup process.
>Does anyone have any thoughts about where to look first for the
>problem? Obviously, I'd check for bad or poorly seated memory and
>visually for any bad connections to the motherboard.
>Is this a common problem?
>Thanks for any suggestions.
>
>Jack
Ace and Malke,
Thanks for your suggestions and apologies for posting in the wrong
group. I know crossposting is frowned upon and decided to flip a coin
and post in this one.
I had pretty much figured out that is must be a very basic problem,
but I appreciate the specific suggestions.
It is not a branded computer, so I will have to figure out which BIOS
he has and interpret the beep code to get a clue.

Jack

Ace
Thu Oct 04 10:52:41 CDT 2007

Good luck and no problem. :)
On a side note, you may be able to deduct the manufacturer of the
motherboard by it's BIOS signature (often displayed at the top and bottom
of the very first screen, note the alpanumeric date codes)
And there may very well be a signature on the board itself, between the
ISA/PCI slots, printed in white.
Looking at some older boards today reminded me of that :)





JClark <jclark@nomail.invalid> wrote in
news:1jv3g3hna10tdlncnphgb5uilcur01inbq@4ax.com:

> Ace and Malke,
> Thanks for your suggestions and apologies for posting in the wrong
> group. I know crossposting is frowned upon and decided to flip a coin
> and post in this one.
> I had pretty much figured out that is must be a very basic problem,
> but I appreciate the specific suggestions.
> It is not a branded computer, so I will have to figure out which BIOS
> he has and interpret the beep code to get a clue.
>
> Jack



--
*Reply to newsgroup please.
*Your mileage may vary.
*Spelling/Grammar errors free of charge.