One Beep- But No Video!

[QZ]

I never had a system, which I built, fail to work perfectly; well, this is
the first.

I have a P4P800S-X (AMI BIOS), Celeron 2.53, Radeon 9250 agp 8x, Antec TP-II
380,
Corsair VS PC3200 512MB (one module).

I have one beep, but no video. I re-seated the monitor cable. (The card seem
seated well, if not it would beep 8x, anyway.)

According to the AMI beep codes, one *short* beep is a DRAM Refresh Failure.
But some lists also show a *long* beep as a successful POST. The manual has
no list.

Indeed my P4C800-E Dlx. beeps once with AMI BIOS. I think it is the same
type of beep, but I am not sure.

Can it be a considered a 'Successful Post', yet have no video?

I am trying to think of what order to test things out. Maybe try the memory
in the other slot, then try the memory and video card in the P4C.
I have an old PCI video card, so I might be able to get in the BIOS, if that
helps.

What order do you suggest?

According to some people it could even be the mb, CPU, or PSU; but wouldn't
there be other or no beeps, if those were problems?

Now, I just found here it says 'one beep, no video' as a memory error.
<http://www.pctechnology.gr/vbull/vb/showthread.php?t=10858>
I am wondering if this is definitive, seeing as mb makers apparently are
customizing these codes somewhat.

Thanks,
QZ

 

[Paul]

I never had a system, which I built, fail to work perfectly; well, this is
the first.

I have a P4P800S-X (AMI BIOS), Celeron 2.53, Radeon 9250 agp 8x, Antec TP-II
380,
Corsair VS PC3200 512MB (one module).

I have one beep, but no video. I re-seated the monitor cable. (The card seem
seated well, if not it would beep 8x, anyway.)

According to the AMI beep codes, one *short* beep is a DRAM Refresh Failure.
But some lists also show a *long* beep as a successful POST. The manual has
no list.

Indeed my P4C800-E Dlx. beeps once with AMI BIOS. I think it is the same
type of beep, but I am not sure.

Can it be a considered a 'Successful Post', yet have no video?

I am trying to think of what order to test things out. Maybe try the memory
in the other slot, then try the memory and video card in the P4C.
I have an old PCI video card, so I might be able to get in the BIOS, if that
helps.

What order do you suggest?

According to some people it could even be the mb, CPU, or PSU; but wouldn't
there be other or no beeps, if those were problems?

Now, I just found here it says 'one beep, no video' as a memory error.
<http://www.pctechnology.gr/vbull/vb/showthread.php?t=10858>
I am wondering if this is definitive, seeing as mb makers apparently are
customizing these codes somewhat.

Thanks,
QZ

If it beeps, I think the processor must have executed a bit of
code. That means some portion of the motherboard, processor,
PSU are working (but we don't know how well or reliably).

I would start with a different video card. Then, perhaps different
memory. Kind of a tossup really. It shouldn't take long since you've
got spares to swap in.

Paul

 

[QZ]

If it beeps, I think the processor must have executed a bit of
code. That means some portion of the motherboard, processor,
PSU are working (but we don't know how well or reliably).

I would start with a different video card. Then, perhaps different
memory. Kind of a tossup really. It shouldn't take long since you've
got spares to swap in.

But it says a video memory error is 8 beeps.
Could the video card be faulty in another way?

The more I read, the more I think it is a faulty memory module. If that is
the case, I can move one of my two 512mb modules in, to see if it works. If
so, I will temporarily have each PC with 512mb, that is ok.

Someone in another NG suggested moving the CMOS jumper to the 'clear'
setting. I even read an archive that it helped someone in a *new* build,
with one beep and no video.

How is that possible? Does Asus test settings and once in awhile forget to
revert to defaults? Or do the settings get messed up by themselves
occasionally?

I have built a number of PC in the last few years, but I am always learning
new things.

Thanks,
QZ

 

[QZ]

Someone in another NG suggested moving the CMOS jumper to the 'clear'
setting. I even read an archive that it helped someone in a *new* build,
with one beep and no video.

Actually, I read it again, and the person was getting a CPU error, and
obviously no video. No mention of how many beeps.

 

[Paul]

Actually, I read it again, and the person was getting a CPU error, and
obviously no video. No mention of how many beeps.

There is a beep code list here:
http://www.bioscentral.com/beepcodes/amibeep.htm

or a list from AMI themselves here (note - I cannot get to their
web site right now, so cannot verify the doc is still there):

http://www.ami.com/support/downloaddoc.cfm?DLFile=support/doc/AMIBIOS-codes.pdf&FileID=572

Since their web site is down, you can also try here:
http://web.archive.org/web/20031209...File=support/doc/AMIBIOS-codes.pdf&FileID=572

I think the one beep thing is bogus, and that is just a POST
beep. One beep is used, as a speaker test, so the user knows the
speaker is working. It is like a lamp test on a diagnostic display,
to show that all the bulbs are still working.

If you stick a DOS boot floppy in the floppy drive, does the
computer attempt to access it ? Do you hear any floppy drive
noises ? That could mean that some computing is possible.

If the BIOS dies just a bit after the initial POST beep, the
BIOS may not have an opportunity to deliver any other POST
codes. A PCI POST card can be used to get more info about where
the BIOS code currently resides. The two digit display shows the
checkpoint codes listed in the AMIBIOS document above. A
checkpoint code is like a milestone, in that it shows the BIOS
got to that point - the PCI POST card does not show "error codes"
as such, it just shows where the code might be getting stuck.

http://cgi.ebay.com/PC-PCI-Motherbo...6809747448QQcategoryZ1244QQrdZ1QQcmdZViewItem

Paul

 

[QZ]

There is a beep code list here:
http://www.bioscentral.com/beepcodes/amibeep.htm

Yes, I have read that. And a short one beep is a memory error. It does sound
short, AFAICT.
The other link I posted, specifically says 'one beep and no video' is a
memory error.

or a list from AMI themselves here (note - I cannot get to their
web site right now, so cannot verify the doc is still there):

http://www.ami.com/support/downloaddoc.cfm?DLFile=support/doc/AMIBIOS-codes.pdf&FileID=572

I am able to get to that site, it has the same info.

I think the one beep thing is bogus, and that is just a POST
beep. One beep is used, as a speaker test, so the user knows the
speaker is working. It is like a lamp test on a diagnostic display,
to show that all the bulbs are still working.

Again, how there be a successful POST with no video?
(I reseated the monitor cable.)

If you stick a DOS boot floppy in the floppy drive, does the
computer attempt to access it ? Do you hear any floppy drive
noises ? That could mean that some computing is possible.

The PC definately tries to access the floppy, the light goes on briefly, and
I think it made a sound.
So what can I do?

If the BIOS dies just a bit after the initial POST beep, the
BIOS may not have an opportunity to deliver any other POST
codes. A PCI POST card can be used to get more info about where
the BIOS code currently resides. The two digit display shows the
checkpoint codes listed in the AMIBIOS document above. A
checkpoint code is like a milestone, in that it shows the BIOS
got to that point - the PCI POST card does not show "error codes"
as such, it just shows where the code might be getting stuck.

Yes, I forgot about them, but I am hoping to get this resolved w/o waiting
for a delivery, because my folks need this PC soon.
I found a number of US online vendors for the same card, but they all say
'no driver is included'. Where would I find one.?

Right now, I will clear the CMOS and see what happens.
If it fails, I guess the only option is swap out the memory for a module
from my existing PC.
I do hope if is no worse than the memory being bad, if that.

Thanks,
QZ

 

[Paul]

Yes, I have read that. And a short one beep is a memory error. It does sound
short, AFAICT.
The other link I posted, specifically says 'one beep and no video' is a
memory error.

http://www.ami.com/support/downloaddoc.cfm?DLFile=support/doc/AMIBIOS-codes.pdf&FileID=572

I am able to get to that site, it has the same info.


Again, how there be a successful POST with no video?
(I reseated the monitor cable.)


The PC definately tries to access the floppy, the light goes on briefly, and
I think it made a sound.
So what can I do?


Yes, I forgot about them, but I am hoping to get this resolved w/o waiting
for a delivery, because my folks need this PC soon.
I found a number of US online vendors for the same card, but they all say
'no driver is included'. Where would I find one.?

Right now, I will clear the CMOS and see what happens.
If it fails, I guess the only option is swap out the memory for a module
from my existing PC.
I do hope if is no worse than the memory being bad, if that.

Thanks,
QZ

But, don't you think using one beep for a successful POST and using
just one beep for an error condition, makes it kinda hard to tell
what is wrong. Maybe the beep is a different frequency or something.
A one-beep code is not going to be of much use for debugging, if you
cannot tell the difference. (I have one computer here, that runs
just fine, and it has a very short beep during POST. I don't think it
has a refresh problem.)

If you are getting to the stage of accessing the floppy, it could
well be just the output part of the video card, a bad video cable,
a bad monitor interface that is at fault. _Or_ it could be that
the computer is reporting a bad checksum for the BIOS, and the
floppy accesses are attempts to flash the BIOS. Perhaps trying
another video card will indicate what is going on. I had one
computer report a bad BIOS checksum, but that was printed on
the screen, implying the video card still got initialized.

If memory is bad, the computer can function in a very limited
way using registers in the CPU. But I would not expect the
BIOS code to attempt to do anything except deliver failure
codes for the memory, as running code that only stores
context in registers makes it hard to do much of anything
practical.

So, swap video card first. Use a known good cable and known
good monitor for testing.

Paul

 

[QZ]

But, don't you think using one beep for a successful POST and using
just one beep for an error condition, makes it kinda hard to tell
what is wrong. Maybe the beep is a different frequency or something.
A one-beep code is not going to be of much use for debugging, if you
cannot tell the difference. (I have one computer here, that runs
just fine, and it has a very short beep during POST. I don't think it
has a refresh problem.)

AMI uses a long beep for POST.

If you are getting to the stage of accessing the floppy, it could
well be just the output part of the video card, a bad video cable,
a bad monitor interface that is at fault.

I have a PC and LCD working, so we can rule out the video monitor cable and
monitor interface.
But not the video card output.

_Or_ it could be that

the computer is reporting a bad checksum for the BIOS, and the
floppy accesses are attempts to flash the BIOS. Perhaps trying
another video card will indicate what is going on. I had one
computer report a bad BIOS checksum, but that was printed on
the screen, implying the video card still got initialized.

I am getting access lights for HD, to see if it is there, then floppy and
CD-ROM for booting, then HDD again; I think this is normal. So what does it
mean?

If memory is bad, the computer can function in a very limited
way using registers in the CPU. But I would not expect the
BIOS code to attempt to do anything except deliver failure
codes for the memory, as running code that only stores
context in registers makes it hard to do much of anything
practical.

I cleared CMOS to no avail.

Well, now I listened to the beeping again, as I can push reset and listen to
it a few times. I am hearing two connected short beeps, like 'beep-eep'.
(Not 'beep' or 'beeeep')
Two short beeps is 'memory parity error'. Note: 'A memory parity error has
occurred in the first 64k of RAM. The RAM IC is probably bad.'

Does this clearly mean the memory is bad?
Is it possible the mb slot is bad instead or in addition?

So, swap video card first. Use a known good cable and known
good monitor for testing.

What do you suggest now?
I don't think it is the video at all.
I wonder if I should try the second memory slot, or maybe go right to
putting other memory in slot 2, and new memory in existing PC?
I want to be efficient, as it really isn't good taking parts in and out.

I am getting frustrated. I am going like a yo-yo connecting and
re-connecting the two PCs to one LCD, cable modem, etc., and I haven't even
changed a part yet.
If this continues, maybe it is best to give them the PC, and shuttle the
parts back and forth, as they live very close.

 

[QZ]

Can I use Memory Slot 2 w/o using Slot 1?

 

[Paul]

Can I use Memory Slot 2 w/o using Slot 1?

Yes. The P4P800S-X board is single channel, and according to the
manual, there isn't any distinction between slots.

If the motherboard is accessing all storage devices, there has
to be some working memory on the thing. I still think video
card, video cable, or monitor are at fault.

You have to start swapping stuff if you expect to figure it
out.

Always power down and unplug, before swapping components. The
components are rugged and can handle the little bit of swapping
you will be doing. Handle cards and memory devices by the edges
and not the contacts, to reduce the risk of damage from static
electricity.

If you swap video cards, you don't have to install drivers.
If necessary, you could boot Windows at 640x480 resolution,
long enough to check alternate hardware.

Paul

 

[QZ]

If the motherboard is accessing all storage devices, there has
to be some working memory on the thing. I still think video
card, video cable, or monitor are at fault.

Again, I have been using this same monitor cable and monitor with my
existing PC, and they work fine. This only leaves the video card as possibly
defective; but, that should be 8 beeps. Unless, there is an output problem
and the BIOS doesn't account for this?

How you can you ignore the two beeps?
Unless, you think it is really one long beep for successful POST?

You have to start swapping stuff if you expect to figure it
out.

I know, but I didn't want to just swap components without an plan. Now, I
see it more clearly, I can either start with memory or video card.

When it failed the first time, I re-seated the monitor cable, I should have
simultaneously re-seated the video card; that might be all it is. When I
cleared the CMOS, I should re-seated the memory, as well.

Now that it could be the memory, I should re-seat that, as well; and I might
as well save a step, and go to slot 2. (Having one verified good slot should
be fine for its use.)

I hope the other parts work, otherwise it is a bad mb, which is would be
difficult dealing with removing this HSF.

And then, I have to test the new parts in my existing PC, to see if the are
bad, as well.

Always power down and unplug, before swapping components. The
components are rugged and can handle the little bit of swapping
you will be doing. Handle cards and memory devices by the edges
and not the contacts, to reduce the risk of damage from static
electricity.

Yes, I am very careful, I have an anti-static wrist wrap and mat, and handle
only the edges.

If you swap video cards, you don't have to install drivers.
If necessary, you could boot Windows at 640x480 resolution,
long enough to check alternate hardware.

Yes, I have seen where it actully boots with a black screen with just thin
vertical lines, and I have to press F8 to boot into VGA mode to change the
res. to 640x480.

 

[Paul]

Again, I have been using this same monitor cable and monitor with my
existing PC, and they work fine. This only leaves the video card as possibly
defective; but, that should be 8 beeps. Unless, there is an output problem
and the BIOS doesn't account for this?

How you can you ignore the two beeps?
Unless, you think it is really one long beep for successful POST?


I know, but I didn't want to just swap components without an plan. Now, I
see it more clearly, I can either start with memory or video card.

When it failed the first time, I re-seated the monitor cable, I should have
simultaneously re-seated the video card; that might be all it is. When I
cleared the CMOS, I should re-seated the memory, as well.

Now that it could be the memory, I should re-seat that, as well; and I might
as well save a step, and go to slot 2. (Having one verified good slot should
be fine for its use.)

I hope the other parts work, otherwise it is a bad mb, which is would be
difficult dealing with removing this HSF.

And then, I have to test the new parts in my existing PC, to see if the are
bad, as well.


Yes, I am very careful, I have an anti-static wrist wrap and mat, and handle
only the edges.


Yes, I have seen where it actully boots with a black screen with just thin
vertical lines, and I have to press F8 to boot into VGA mode to change the
res. to 640x480.

So you are able to get video output from it ?

It sounds like a resolution is being used which the monitor
cannot handle. Does the monitor normally put up an error
message, when out of bounds conditions are detected ?

Perhaps a Windows registry value is corrupted, resulting
in the video card being set to some odd values the monitor
does not like ? Does Safe Mode reliably give you a working
display ?

This value could be stored in the Registry, and the value
might not get properly removed unless the "Add/Remove"
entry for the video driver package is used. But, you
likely won't be able to get at that.

Just deleting the video device entries while in Safe Mode,
may allow you to get to 640x480 in a normal Windows boot.
But, if those registry settings are still in there, as
soon as you reinstall the video driver, the problem will
likely come back. (The driver installer package may
leave the corrupt settings in the registry, thinking
they are the users preferred values.)

Perhaps someone else can suggest how to clean the registry
of that value. It may be associated with something
lke "ati2mtag".

Paul

 

[Markus L]

Had a similar case on my P4S800D-E.
Remembered this board comes with "ASUS POST reporter".
Connected a speaker to the audio output, then tried again.
A female voice told me there's a problem with my video card.
Confirmed the diagnosis by putting it into another system.
Replaced it, and everything is fine again.
Summary: Use ASUS POST reporter when available on your board.
It removes all ambiguities associated with counting beeps.

 

[digisol]

One short beep usually means all is OK, change over vid cards and tr
again, make sure the default card is AGP in the bios

 

[QZ]

So you are able to get video output from it ?

No, I was saying I *had* seen (IOW, on another PC) a video output of a
virtually blank screen, that just needed the VGA to get a resolution change.
On this PC I was getting a 'No Signal' or similar message.

Anyway, I solved the problem, shortly after my last message. I was so busy
installing and configuring Windows and getting Broadband for my folks, I
just forgot about this thread.

Thank you for being persistant that it was the video card; it was not seated
all the way. I should have known when the tab wouldn't go all the way over
it. The reason I discounted that was because the tab was partially locked,
and also the card mounted perfectly in line with the case.

Once I got the card into place, the lock is needed (or one has to hold the
card down) while fastening the screw in place, so the card doesn't
disengage; because it lines up poorly.

I am pretty sure there is no beep now when it POSTs. If it doesn't beep, it
means there was a beep code, that was different than any of the lists I
found. If it still beeps, it means the PC was previously getting enough of a
signal to POST.

QZ