continious beeps on p.o.s.t

By Bas van Berkel · 16 replies
Sep 4, 2005
  1. suddenly my computer stopped working.
    on post i hear a continious beep.
    long beep every 3 tot 4 seconds.
    ik have a award bios and a gigabyte ga 7n400 pro mobo with a athlon xp 3000+ cpu. i tried really everything. ik measured the voltage on de psu but it seems to work just fine. i tried diferent memory but it still dóens't work.
    the screen stays black and i just can't get any response.
    ally my fans are working and i tried to reset the bios.
    finally i cleaned the whole motherboard but still i can;t get any other response than the beep codes.
    does this mean my motherboard is fried or my cpu?

    can anybody help me with this
  2. DonNagual

    DonNagual TechSpot Ambassador Posts: 2,406

  3. SOcRatEs

    SOcRatEs TechSpot Paladin Posts: 966

    Hello! Welcome to TechSpot

    Check HERE
    for code list..
    Have you done a bare setup?
  4. Bas van Berkel

    Bas van Berkel TS Rookie Topic Starter

    I already checked that topic and those posts, but the all didn't help.
    I'm sure there is nog short beep in the post message. I goes like, long beep - 3/4 second silence - long beep again.

    What do you mean with bare setup?
  5. DonNagual

    DonNagual TechSpot Ambassador Posts: 2,406

    I think he means taking EVERYTHING out of your computer except the essentials. Mobo, ram, vid card and HDD.
  6. Merc14

    Merc14 TS Rookie Posts: 171

    You are going to have to do a barebones setup and test each component. This will read a lot harder than it actually is. The initial procedure takes only around 10-15 minutes. The follow on troubleshooting may take a lot longer though. Also, please do not skip steps. Do everything in order and as listed or your troubleshooting will be flawed.

    Caution: Please remember that turning a PC off does not mean there is no power going through it. Modern systems maintain a trickle of power to keep the standby functions running. You either have to turn off the switch on the Power Supply Unit (PSU) itself or unplug the system from the wall. Unplugging is best. If you have a LED on the mobo that is lighted all the time. make sure it is out before proceeding. Also, be aware of static. Make sure you wear and ESD strap or discharge yourself on a steel part of the case before touching anything inside.

    First, unplug the PC from the wall and then open it up. Disconnect all the drives (floppy, CDROM, DVD etc.)from the motherboard (mobo) and also disconnect your Hard Drive(s) from the mobo. Do not leave the hard drives connected. The system will boot into BIOS just fine with no hard drive attached. Unplug the power from all those drives you disconnected from the mobo. Remember to disconnect the front panel firewire and/or USB ports.

    Next, remove all the RAM, except for one stick, from the mobo. Some mobos are very picky about where the RAM needs to be placed so make sure the one stick of RAM is in the correct slot as per your manual.

    Now you are stripped down to a barebones system. The PSU, the mobo itself, 1 stick of RAM, the CPU/HSF and video card. Reset your CMOS/BIOS while the system is stripped down, unplugged and open. You do this by removing the battery and then moving a jumper near the battery around. Usually there are a set of three pins with two covered by a jumper. You move the jumper from pins 1&2 to pins 2&3 and let it set for a few minutes then reset the jumper to pins 1&2 and replace the battery. CMOS and BIOS will be back at default settings after doing this.

    Now check that everything is seated correctly, both the 4 pin and 20 or 24 pin power is connected and secure and if so then plug the PC back into the wall and make sure that any LEDs that should be lighted on the mobo are lighted. If all is still well then turn it on. Hopefully she boots right back into BIOS.

    If you get back into BIOS you can start troubleshooting by turning the PC off and unplugging it and reconnecting peripherals one at a time. The idea here is to connect and reboot until something hangs your system up This presumably is the bad piece of gear.

    If you cant get into BIOS and have the same problem as before then you know it is either the PSU, the RAM, the CPU, the mobo itself or the video card. Change out each these until you get into BIOS. I would start at the PSU as it is usually the guilty party in a situation like this and is also easy to change in and out you are down to just 2 plugs now remember). Next up would be the video card and/or RAM and if still no luck then things get hard as you now have to consider either the CPU or the mobo.

    Good luck and happy hunting.
  7. Bas van Berkel

    Bas van Berkel TS Rookie Topic Starter

    guys guys, i'm not an *****.
    the bare setup wil not work and i tried that already.
    that was actually my first step.
    don;t u think when i tried to meassure the voltage on the psu and tested the memory and cleaned the motherboard that i wouldn't try that?

    my opionion is that maybe the mobo or cpu has problems.
    mobo seems to work if it gives post, usb gives reaction.
    memory seems to be just fine. i;m not a quiter maybe somewhere there is al solution for this. but i am affraid i fried my cpu.
  8. SOcRatEs

    SOcRatEs TechSpot Paladin Posts: 966

    Hold up just abit

    Bottum line is, if it's fried (cpu) then no test is going to fix it.
    Try'in it on another MoBo may be only other option.

    We have no way of knowing how much you do or do not know about
    computers, we definately do not intend to insult you or your intelligence.
    We use these methods to work a problem with you, so that we're all on the same page.

    Together we may shake out a solution but not always.
    It does seem to me you are being thorough, I rarely hear some one taking out the MoBo to clean it.

    I have not found any code explination to the beep series you're getting.
    Maybe some one else here can offer help I seem to be missing.

    We'll stick it out with you..
    I for one know how frustrating it is when I need my machine to work
    and I've invested alot of time and money in it, I expect it to work.
  9. Bas van Berkel

    Bas van Berkel TS Rookie Topic Starter

    Solved the problem

    Thank u all for your kind responses and i think they ultimately shoved me in the right direction.

    Ik found out what the problem was.

    There was a mallfunction in the USB connector of the PC Case.
    When is disconnected it from the connector on the mobo, is started to boot.
    It's still very strange that such a small thing could make the whole thing so unstable it won't start.

    Thank u all, sorry i reacted a bit irritated earlier on, but i was very motivated to solve the problem and fortunatly i did.
  10. SOcRatEs

    SOcRatEs TechSpot Paladin Posts: 966


    Just the kind of ppl I hope to find here "Highly motivated"

    That is strange!?
    was it a one piece usb block that plugged into the MoBo or
    separate wires?
    I think even in the bare setup I would've missed it.
  11. DonNagual

    DonNagual TechSpot Ambassador Posts: 2,406

    Wow, ice post merc14. That should probably be made a sticky in a troubleshooting thread.
  12. Merc14

    Merc14 TS Rookie Posts: 171

    Thanks. I went back and added to unplug the firewire/USB ports. LOL
  13. Bas van Berkel

    Bas van Berkel TS Rookie Topic Starter

    It was a usb block that was attached to the mobo.
    A soon i disconnected the block, it worked again like a charm.

    What i suggest to all the people who have the same problem.
    Try all connections to the mobo and see what happens.

    The post message seems to refer to a short circuit.

    Happy problem solving everybody
  14. jobeard

    jobeard TS Ambassador Posts: 11,177   +990

    If a device captures the bus, then nothing else gets any cycles, commonly
    known as going disabled for interrupts. These are always nasty.
    Don't know I would have started disassembling the mobo components,
    but then I'm not desparate (at this moment). Good work! :angel:
  15. SOcRatEs

    SOcRatEs TechSpot Paladin Posts: 966

    I agree, merc14 did a better job explaining than me.
    I will be comming back here to cut and paste.
    We have alot of newcomers not just to TS but newcomers to computers
    that never think to run a bare bones setup for trouble shooting.
    It is kinda backward thinking;
    remove everything, then add each device til the offender is found..
  16. jobeard

    jobeard TS Ambassador Posts: 11,177   +990

    split halfs?

    instead is disecting the whole beast, try applying split-halfs;
    remove 1/2 of the resourse and test results
    ntf, it's in the removed 1/2​
    still here, iterate for 1/2 what's left​
    at least a few things might not get disturbed and every time you get into it,
    there's a risk that you can break something that was function.
  17. SOcRatEs

    SOcRatEs TechSpot Paladin Posts: 966

    I use this method on a machine that has been fuctioning for awhile then suddenly fails
    (all at once or intermitten) and I've exhausted device driver updates, OS updates,
    Virii scans, hardware testing and I'm finally at wits end.

    Or on a fresh build prior to os install.

    It may seem an extreme measure but ultimately saves me time chasing my tail.

    It's up to the user to decide what method they want to apply. This is only a
    suggested method that works for me and sometimes others.

    We have no way of knowing right away how much a given members knows, so
    establishing a common dialog helps us in getting to a solution quicker.

    There are as many different methods as there are ppl.
    Funny thing is with all the stickies there are on this forum and others,
    no one seem to read them. :giddy:
Topic Status:
Not open for further replies.

Similar Topics

Add your comment to this article

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...