Ok the double beep (post code) on start indicates a hardware problem. What it means can only be told by the manufacturer/manual of the mother board. But I would say ther is not much you can do about it except replace the mother board. Sorry
These are boot options, not “commands”.
On 10/05/2012 07:46 PM, MagnifiKat wrote:
> I continue also receive a Phoenix WARNING ERROR as
> follows: Resource Conflict - PCI in slot 02, Bus:04, Device:07,
> Function:00.
seems i over looked that in your initial post…so, here is what i want
you to try:
your mother board has several slots into which stuff can be added…some
of those are for RAM and some for other stuff (might be a sound board, a
ethernet board, a graphics board, a serial board, or other stuff…)
whatever they are i want you to shut down the machine and CAREFULLY
<read the caveat in my sig> take out all the add in boards, but NOT the
ram…
careful:
-
most will have a screw holding the end of the board which can be seen
from outside the case…and, into which you can plug in stuff… -
you must remember what went where and reassemble, eventually.
if your monitor is plugged into one of the boards and there is
another outlet on the back side with the same female plug
configuration, then i want you to take out that board and plug your
monitor into that other socket…
but, if you monitor is plugged into a removable card and there is not
other female jack on the back that can be used, then: disconnect the
monitor, remove the card and place the same card back into an
identically shaped, colored slot, and reconnect the monitor.
now try to boot, what happens?
if it boots without beep-beep we know one of the add-in cards OR their
slot is bad…
next step will be to step-by-step add one board at a time until it won’t
boot…and, we then know the bad actor.
If you’re tryng to find out what causes the beep-beep, I would first put the computer on a table, remove whatever extension card is in PCI slot 02, even if it’s a graphics card - and anyway remove the graphics card, turn the power on and count the beeps. But first try to boot with the options I suggested in another post.
You could also remove or switch the ram modules and see if it beeps differently. But if you’re not familiar with this kind of work, I’d suggest asking a computer technician.
- Before puting your fingers inside your computer, discharge your static electricity by touching something grounded … and deny help from cats! lol!
On 2012-10-06 00:16, please try again wrote:
>
> If you’re tryng to find out what causes the beep-beep, I would first put
> the computer on a table, remove whatever extension card is in PCI slot
> 02, even if it’s a graphics card - and anyway remove the graphics card,
> turn the power on and count the beeps. But first try to boot with the
> options I suggested in another post.
Have a look here:
At the end there is a link to «PhoenixBIOS 4.0 - Revision 6.0 POST Tasks and Beep Codes», but
the link is dead. There is another one to «Power On Self Test Beep Codes for AMI and Phoenix
BIOS - from PC Hell», and following it you get to a page that details the phoenix bios beep
codes. I understand the OP has that type of bios, if not, well, it is also listed there.
The first step is learning what two beeps means.
If it is two, it is memory, undetermined.
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
hello MagnifiKat,
do NOT overlook the excellent advice given by both please_try_again and
Carlos following my long #23!!
[this does NOT mean i disagree with any of the other posters in this
thread–i’m just talking about the improving remarks following my #23]
Hi, gogalthorp! Sorry for the delay reverting; and thank you to your good self and indeed to all you most helpful folks who have replied to my posts.
Now, folks, I have both GOOD NEWS and BAD NEWS to report:
Firstly, the GOOD news! Most unexpectedly — and despite regular daily FAILURE to boot, even after CMOS battery replacement and “under-the-bonnet” cleaning — my Siemens ‘Esprimo’ desktop PC one morning decided (just like a good child) to be on its very, very best bahaviour … and, surprise, surprise, it started normally, with no beeps at all! All my files, emails, etc, reappeared intact. So, for the next seven days, I was able to boot up normally EVERY morning, catch up with a lot of my work, and to shut down routinely at night. Everything was running like new! Brilliant!
But now we come to the BAD news! It’s back to square one! PC guilty yet again of “gross misbehaviour”! Once again, I am LOCKED OUT of my computer, with exactly the same symptoms and Phoenix Warning Error as per my original post #1: namely, Resource Conflict – PCI in slot 02, Bus 04, Device 07, Function 00.
Question: Does this unpredictable and irregular Good/Bad/Good/Bad performance cycle shed any new light upon this ongoing problem? Can this lock-out problem yet be resolved, or will the original 5½-years-old mainboard/motherboard need now finally be replaced? And, if so, what (if any) long-life components (nVidia chipset, CPU, memory boards, etc.) from my present D2461-B micro-BTX mainboard would you recommend I might usefully remove and re-use in a replacement new board? Or is there a likelihood these very soon would become banjaxed, also? Please advise. Many thanks!
On 10/30/2012 05:26 PM, MagnifiKat wrote:
> Does this unpredictable and irregular Good/Bad/Good/Bad
> performance cycle shed any new light upon this ongoing problem?
symptoms indicate one or more of these possibilities:
-cracked circuit board
-faulty ground (like a loose connection somewhere, anywhere)
-bad cable connection
-failing/weak power supply (components want STABLE, clean power)
-and about a thousand other things…
if you are not a computer repair person, but wish to keep using the
machine, you need to get it to a competent electronics repair shop…
if the drive(s) contains important information you wish to keep, then
you need to already have a backup, or ask the shop to remove and
protect the drive prior to repairs… (because, some [many? all? in your
area] shops begin by formatting the disk and installing a system they
know and trust…)