Dx2400 Microtower Won't Boot - Beep Codes

Hi all,
One of my users has a dx2400 microtower.  Yesterday, according to her, it just stopped working.  Upon visiting this morning, I find that when powering on, nothing is displayed on the monitor, the green light on the power button is solid, the LAN LED is solid green, and there is a beep code.
Beep, Beep, Beep, *Pause*, Beep.
It all just sits there doing nothing.  I reseated the RAM to no avail, and at this point, don't know what's wrong.  I tried to find a guide to tell me what the beep code means, but was unsuccessful.  Help!  Thanks!
Chris

Hi, Chris:
Sorry. I guess I was fast, but can't read numbers. 
Here is the link to the troubleshooting guide for your PC.
http://bizsupport1.austin.hp.com/bc/docs/support/SupportManual/c01385606/c01385606.pdf
The beep codes are in Chapter 2, page 14.
Paul

Similar Messages

  • HP Pavilion Elite e9240f won't boot -- beep codes

    When I try to boot my hp desktop I am getting beep codes.  As best I can tell it's one long then 8 short.
    I have not replaced or changed any hardware or software.
    I have used compressed air to blow out all the fans I saw.
    It's been an intermittent error that I thought was related to heat.  I'd turn it off, let it sit for the night, and it would work in the morning.
    The last time it worked, I was wondering about a virus so I ran an avast full system scan.  It found one file in the 1 tb drive (sorry, don't remember name, just that it was a .tmp file) and it said to move it to chest I believe so I did that.  It then suggested doing a boot scan so it restarted and has since given the same beep code errors.
    I have unattached the cables for the cd and dvd drives, as well as the hard drive, and I still get the error.  I've removed the video card and still get the error.  I've held the power button down so that the led light inside the computer shuts down.  I seem to get fans to run but nothing else.
    I made a system repair disk from another Windows 7 Professional (which I think this one is) and that won't work (I can't seem to boot into that) because it doesn't seem to get to an HP screen to boot into the cd.
    Thoughts?
    Thank you

    Hi,
    This is the HP troubleshooting link for POST error codes.
    You could try reseating memory modules or removing one at a time and testing for a successful POST.
    Jaco
    Errare humanum est.

  • BRAND NEW MSI x99s Gaming 7 Won't Boot, Debug Code 00

    Just completed my build and my pc won't boot. Everything plugged directly into the psu is working but fans plugged into mother board don't spin and getting debug code 00 nothing displayed on screen.

    Hmm ok.
    What you could do is: try each stick on its own, in every single DIMM slot. Make note which slots/sticks work or dont work. Then add to 1 (known to work) RAM stick and try moving this single one around all DIMMs again. Do the same until you get a failure or if works fine.
    Which slots did you use by the way?
    Quote from: robbie.bowden on 18-May-15, 04:23:08
    I then added the 4th one back in and now it boots. Any ideas why just switching those 2 positions would change anything??
    Maybe for the first time it didnt go all the way down?

  • Re: MSI X99S XPOWER AC - won't boot - debug code 67

    tried the psu on another board with same power cable and works fine,

    Quote from: dae.hansen on Today at 12:24:47Turns  out the Kingston RAM is ECC, which is unsupported by the i7 CPU. Bugger.
    Thanks for the help.
    Non ECC is max 8GB per stick as far as I know.
    Glad you got...

  • P67A-GD55 boot stops at POST 99 w/ 1-long+2short beep code.

    Well subject line tells most of the story:
    P67A-GD55 boot stops at POST 99 in lower right of display and with 1-long+2short beep code.
    I've found a note somewhere on these forums that 99 code means Super IO initialization,   though I'm not sure if this is the checkpoint before or after that process.
    I've found generic information that suggests 1long+2short beep code indicates a video card failure.   
    I'm surprised that the manual for the MB doesn't list these codes, and that they weren't listed in the troubleshooting FAQ on the MSI site.   So I still wonder if it may mean something else.
    I've disconnected all the SATA connections,  and removed all pci cards except for the video card.   Guess I'll try disconnecting the front-panel usb connectors too in a moment, but I'm running out of ideas.
    With a EVGA GT520 video card,   I get these symptoms regardless of which pcie slot I put the card in.
    With a Galaxy 8400GS  the beep code is the same but no output is ever visible on the display.  It seems possible that I just need an adapter to use the other connector on this card to see the output though.
    With a EVGA 7800GT   the symptoms are the same as with the EVGA GT520
    If I try removing the memory sticks I get 3-long beeps followed by system shutting itself down.

    Run of the mil keyboard.    (has a logo with a circle containing a crescent containing a D).   Suppose I could switch to a usb keyboard around here somewhere.  
    Disconnected the logitec usb mouse that I had connected to the back panel with no change in symptoms.
    Toughpower-650 power supply (had been in use on a system that was running an athlon x64 and the GT7800GT graphics card.  
    2 sticks PNY DDR3 PC3-10666 4G  ("compatible with 1333MHz")   1 stick in each blue slot.
    No idea how to tell you the UFEI/BIOS version.    The manual says its "CLiCK BiOS"   but since I've never seen anything but 98,99 and _  displayed by the BIOS  I really don't know.
    Removing the case front panel USB connectors didn't change symptoms.
    Resetting the bios by the button at the back panel connectors (near keyboard connector)  didn't change anything. (although it did not cause  "system will boot automatically"  as a line in the manual might suggest.  
    Tried using the JBAT connector to clear the bios as well and likewise no change in symptoms.
    There are no peripherals connected other than case power switch, power LED and HDD LED at this point.    Somehow I don't expect much change from disconnecting LED's.    Case switch seems to be behaving normally in that it causes the boot cycle to start, and if pressed while the "99" is sitting there in corner of screen it causes machine to shut down.
    No SATA devices are connected to it since they won't really be useful untill can at least get to the BIOS.   The sata cables that would go to those devices are still connected to the MB.  
    CPU:i5-2400 3.1GHz 6MB Cache LGA1155 95W 
    Heatsink:Cooler Master Vortex PlusRR-VTPS-28pk-r1  connected to the CPU fan connector on MB.
    No sysfan connections to MB.

  • RD230 - Won't boot after BIOS - Server beeps and the screen is blank.

    Hi there,
    I have a problem with one of our RD230.
    The Server seems to be ok. No Errors in BIOS. SATA Raid configured and so on...
    But the server simply won't boot from CD or USB Drive or HDD.
    After the whole BIOS Process the server gives a permanent beep and the Digitron shows code 00. The Screen just shows a blinking cursor top left.
    Nothing happens.
    Removing the RAID, CD Drive, Network Card doesn't help.
    Does anyone have an Idea whats going on with this server?
    Also setting the J45 Jumper doesn't help.
    Thanks in Advance,
    Cheers,
    Chris

    2 Things that can typically fix this issue. Please reseat the memory and if that does not fix it, please reseat the processor.
    Questions
    1 - Has this system worked prior to this or is this an out-of-box failure?
    2 - If it has worked in the past, what changes were made just prior to this issue? (ie Windows Update, BIOS Update, firmware update, driver(s) update, etc.)

  • Fail to boot (short-short-short-long beep code) after M92p BIOS Update

    Hi, 
    I recently updated my BIOS to the latest version using the System Update tool from Lenovo. For a while everything seemed to be working alright, as the BIOS was dowloaded and the computer rebooted. After rebooting the first time i was presented with the BIOS utility, and noticed that the update was progressing. 
    After 20 or so seconds the computer rebooted again. This is where my problems began. The computer immediately started beeping this short-short-short-long melody from the speakers. I thought this was normal, so I left the computer on for quite a while. 
    However, the beeping never stopped. Now the beeping resumed the instant i plug the power back in. I have yet been able to actually getting any sort of information on-screen telling me what's wrong. 
    I've tried following the "Recovering from a POST/BIOS update failure" on page 267 of the Hardware Maintenance Manual, but no luck with that so far. No matter where I place the jumper, the beeping code is the same short-short-short-long melody (yeah, it sounds like a disney tune or something).
    Any bright ideas? The machine type is a M92p 2992-B3G
    I'd hate to have to send it in for repairs, and Lenovo's Norwegian support line doesn't open until Monday, and there seems to be no way to call their 800-number in the states from here
    Oh, and would this be covered by my warranty if repairs / motherboard replacement is the only way out?
    UPDATE #1:
    I found this in the manual;
    3 short beeps and then 1 long beep DRAM memory
    error
    Perform the following actions in order.
    1. Make sure the memory module(s) are properly seated
    in the connector(s).
    2. Replace the memory module(s).
    3. Replace the system board.
    This is pretty much Lenovo's way of saying "You're screwed", isn't it?
    UPDATE #2: 
    I've now tried pretty much everything;
    The solution as proposed on page 267 in the Hardware Maintenance Manual
    Unplugging all cables and harddrives before booting
    Removing my PCIe video card and PCI Wireless NIC before booting
    Removing all memory modules, and trying 1 and 1 module
    Moved a memory module from another machine that I know is working
    No luck so far. 
    Ideas would be welcome at this point

    I'm glad to hear it's just a simple memory error, however the original problem in this post is a bit more than just a memory problem.
    This became a problem after a BIOS update, so somewhere along the way one of Lenovo's developer screwed up badly, and it's been bugging me ever since. There's absolutely no way for me to use any PCI-e card with my M92p. 
    I've tried 6 different cards, 3-4 different memory module combinaties, with our without harddrives plugged in, and every thinkable combination of these.
    No luck. Therefore, I simply conclude that Lenovo are dicks, and we all know what dicks enjoy doing; **bleep**ing people over.
    I've given up on the issue, and I'll never buy a Lenovo again after this.

  • Mac Mini won't boot up, just beeps once every 4 seconds. Is it dead?

    Mac Mini died, now it won't boot up. It just sits and beeps at me once every four seconds with the power light flashing once every four seconds also. If i shut it off, can't get it to turn on again without unplugging it. also, no boot sound. Time for a new one?

    Sounds like a RAM problem:
    1 tone, repeating every 5 seconds: This indicates no RAM is installed.
    Try reseat8ng the RAM. Finde you Mac here for how to access the RAM
    Or you can
    Make an appointment at the Genius Bar of an Apple store. No warranty required
      Apple Retail Store - Genius Bar

  • PC won't boot. MSI Gaming 7 motherboard had a debug code of 67.

    PC won't boot. MSI Gaming 7 motherboard had a **debug code of 67**.
    I ran Malwarebytes this morning, it found some stuff, I had it remove them and rebooted. Haven't been able to get my PC to boot since :(
    When I begin booting, nothing happens at all on the monitors, the PC itself has power and it looks like it's on but I only get this error code 67 on the motherboard and that's it.
    Really don't want to unseat the CPU for any reason to troubleshoot that. CPU is always a pain in the ass for me to remove and place back into a PC. lol.
    Specs:
    PC:
    * Windows 8.1 Pro 64-bit
    * Rosewill THOR V2 Case
    * EVGA GeForce GTX 970 FTW Edition GPU
    * Thermaltake NiC C5 CPU Cooler
    * Rosewill SSD/HDD Mountaing Kit with 60mm Fan
    * CORSAIR Vengeance 16GB RAM
    * CORSAIR HX850i 850W Power Supply
    * Intel i7-4790k CPU
    * MSI Z97-Gaming 7 Motherboard
    * Samsung 840 EVO 120GB SSD
    * Western Digital Blue 1TB Drive x 3
    Audio:
    * Blue Yeti Mic
    * Rode PSA1 Mic Boom Arm
    * Audio-Technica ATH-M30 Headphones
    Networking:
    * Cisco Linksys EA4500
    * Motorola SURFBoard SB6121
    * CAT 6 Ethernet Cables
    Peripherals & Misc:
    * PS4 Controller
    * Razer Naga 2014
    * ASUS VS278Q-P 27" 1ms Monitor x 2
    * HP 23" S2331 x1
    * Logitech C920 Webcam

    Quote from: Svet on 04-June-15, 22:06:26
    try >>Clear CMOS Guide<< with power cord removed
    Tried that, didn't work.
    Unseated each RAM stick, didn't work.
    Removed the CPU, cleaned off the thermal grease, reseated it, replaced grease and heatsink. Didn't work.
    Literally unplugged and replugged everything in one by one and none of it fixed the problem. Still receive error code 67.
    Have no damn idea what the heck is going on.

  • Long short short beep code then no boot when trying to reboot???

    I recently ran the recovery CD to get it back to factory condition and the same problems persisted (that I'll describe below) which indicates to me that there's some hardware issue. I've had the same issues before and after recovery was run.
    When I start it, it often starts just fine as long as it hasn't been on for at least an hour.  It seems to have memory management issues.  It hangs up, gets bogged down easily, hangs, crashes, etc.  It also seems to run hot.  There are quite a few programs that I was able to run when it was working well that it no longer tollerates. 
    If I reboot after it's been running for a while It makes three beeps (Long short short).  The screen goes black, the hard drive spins a little, but that's it.  I have to turn it off for about an hour or two before it will actually start up at that point.  Keep in mind, it doesn't start out at 100% and deteriorate.  It starts out at about 40% of what it used to do and deteriorates from there.  In needs to be rebooted about once a day. 
    Sometimes if it's hibernating, it will make the same beep code when I wake it up (Long short short) and most of the time it won't wake up from there. 
    So, can anyone tell me what that beep code refers to?
    Has anyone else experienced similar problems?
    Does anyone know which part is bad and if it's worth trying to fix it? 
    Thanks!

    I am having the same problem....i do believe its a memory problem..??

  • My iMac won't boot up it has a gray screen and makes a steady beeping sound

    My iMac won't boot up it makes a steady beeping sound and has a gray screen, occasionally it shows a picture of a file with a question mark blinking in the center, can anyone help

    The blinking question mark indicates that the firmware could not find a valid Operating System on your machine.
    Your harddrive may have failed. Your filesystem may have bcome corrupted.

  • Powerbook g4 won't boot - long beep

    Hi,
    My powerbook g4 (fw800 1.25Ghz 15") won't boot any more. Symptoms: after hitting the power button, it takes a while before it emits a long beep and flashes the sleep led a large number of times (I cannot count exactly how many times). This is different from the POST beeps mentioned on apple's web site: these beeps are shorter. This long beep also has nothing to do with the firmware upgrade procedures on other powerbook models.
    When I remove RAM memory, it first beeps and flashes as already mentioned, and then, after a while, gives one short beep and two flashes (this indeed corresponds to the POST messages published by apple). Reseating RAM does not solve the long beep/boot problem.
    I also tried the following: resetting pmu, resetting pram, without luck.
    Then I opened it, and verified that all cables were seated correctly, unplugged the backup battery (which still has the correct voltage), reassembled everything, also without luck. With/without hard disk or optical drive: makes no difference. Also using it with either or both battery or AC power makes no difference.
    Does anyone know what the long beep means? Is the logic board fried? Is there anything that I can try myself (I am somewhat experienced in fixing defective hardware in desktops and laptops). I probably have nothing to loose. I don't want to send it in for repair or spend money on a replacement board.
    Thanks in advance
    Patrick
    powerbook g4   Mac OS X (10.4.8)  

    Hi pwambacq,
    Welcome to Apple Discussions.
    You're much more likely to get the help you need in the Aluminum PB folder, which is what you own (this is the Titanium folder).
    FWIW, you've tried most of what I can think of. Not sure if you've done this or not, but give it a try if you haven't: in case one of the RAM modules is bad, try just one module at a time, and try it in both slots.
    Will it boot to the install disc?
    If it's not RAM, HD, or connections, seems likely it's the LB.
    Good luck.

  • H67MA-E45(B3) won't boot, no beeps. BIOS?

    It won't boot. The power LED comes on and fans spin, but I get no monitor activity and no beeps.
    I'm theorizing this is BIOS related. My BIOS sticker says E7678 IMS170. I'm using a Core i3-2100 3.1GHz. The website says I need 7678v17.zip. Do I have this already? I can't make the connection between the BIOS sticker and the 7678v17 file.
    I actually have two MB's, and two CPU's, and two sets of ram and a different power supply. No combination of MB, RAM, CPU, power supply, works. I went down to 1 stick of ram, no video card, and no peripherals. To my thinking it HAS to be the BIOS at this point.
    Thoughts?

    Yeah, I've got the 4pin plugged in.
    MSI H67MA-E45 (B3) LGA1155 Intel H67(B3) DDR3 SATA3 A&GbE MATX Motherboard
    Intel Core i3-2100 Processor 3.1GHz 3 MB Cache Socket LGA1155
    Kingston Technology HyperX Blu 8GB 1333MHz DDR3 Non-ECC CL9 DIMM (Kit of 2) KHX1333C9D3B1K2/8G
    Simplified loadout, so no fans but CPU, no HD, no CD, etc.
    Corsair T650 power supply (known good)
    I've tried it with and without the Sapphire HD 6850 PCIE Video Card.
    I've got two sets of everything, one for each of my kids. Any help is appreciated to turn these xmas gifts around.

  • P35 NEO-2 FR won't boot just beep beep every 10 seconds

    What's wrong with my system, My system won't boot and I get a beep beep every 10 seconds. I was updating my bios using the approved USB flash drive procedure, all I got was a blinking cursor. I rebooted and now my computer won't boot. Is my motherboard dead? I have successfully used the bios flashing tool in the past.

    Quote from: Hans Gruber on 11-March-08, 21:47:41
    That's a good question.
    Another problem has come up. I get CMOS bad check sum error. Press F1 for "can't remember" but it sends me to bios or F2 for default settings. Basically, I can't overclock because of this bad checksum error. Everything runs at stock speed. How do I fix this? On the bright side, I now have bios version 1.8
    On a side note for Remus, I never made it to the load new bios screen. The cursor "_" was blinking non stop for several minutes. According to the admins, another user in Germany had the exact same problem that had.
    Now, how do I fix the CMOS bad checksum error message?
    "Another problem has come up. I get CMOS bad check sum error. Press F1 for "can't remember" but it sends me to bios or F2 for default settings. Basically, I can't overclock because of this bad checksum error. Everything runs at stock speed. How do I fix this? On the bright side, I now have bios version 1.8"
    Enter in BIOS and "LOAD BIOS OPTIMIZED DEFAULTS", then "SAVE AND EXIT"
    If you still get "CMOS bad checksum error" at next reboot, do this:
    Login in your windows, then adjust USB key geometry. Do this:
    Quote from: Jack the Newbie on 11-December-07, 05:41:45
    Format your USB Flash Drive with >>this<< tool and then retry with "MSI Forum HQ USB Flashing Tool".
    And update BIOS via Forum Tool (Re-flash with the same BIOS 1.8) will fix the problem.

  • P35 NEO-2 FR won't boot. One beep every few seconds.

    Hello, I hope someone can help me
    Out of the nothing my computer crashed. There was a blue screen, but only for a split second, so I couldn’t get any information from that. After I tried to turn it back on I only got a black screen.
    Messages from my PC:
    One beep every few seconds. -- Means: DRAM refresh failure.
    The LEDs on the board have the combination red-red-green-green. -- Means: Decompressing BIOS Image to RAM for fast booting.
    Obviously I tried another RAM module. But it didn’t help. I don’t know what I should do, because I can’t even get to the BIOS. The screen just stays black.
    PS: I didn’t OC or try to flash a new Bios version.
    My system:
    P35 NEO-2 FR, BIOS v. 1.8, S/N: 601-7345-100B0805092463
    Intel Q9300
    G.Skill 2 GB DDR2 PC2-6400 CL5-5-5-15 (also tried brand new Corsair XMS2 DDR2 800 MHz CL5-5-5-18)
    MSI N460GTX Hawk
    beQuit Straight Power 600W

    Okay, please have a look at this document:
    http://www.ami.com/support/doc/AMIBIOS8_Checkpoint_and_Beep_Code_List_PUB.pdf
    As you can see, there are two main routines going on after you hit the power-on button:
    1. Bootblock Initialization
    __ and __
    2. POST Code
    Your problem description ...
    Quote
    The LEDs on the board have the combination red-red-green-green. -- Means: Decompressing BIOS Image to RAM for fast booting.
    ... indicates that your system halts in the first of the two main routines I just mentioned. To be more precise, it hangs at Bootblock Initialization Checkpoint D5, which is defined as follows:
    Quote
    Bootblock code is copied from ROM to lower system memory and control is given to it. BIOS now executes out of RAM. Copies compressed boot block code to memory in right segments. Copies BIOS from ROM to RAM for faster access. Performs main BIOS checksum and updates recovery status accordingly.
    In the last two phases of this checkpoint:
    Quote
    Copies BIOS from ROM to RAM for faster access. Performs main BIOS checksum and updates recovery status accordingly.
    The actual BIOS Code is copied into RAM and checked for integrity. When BIOS corruption is detected (=wrong BIOS checksum), the system will automatically jump into BIOS Recovery Mode (which is a sub-routine of the Bootblock Initialization routine).
    Now, this brings us to the actual meaning of the beep(s) you hear:
    Quote
    One beep every few seconds. -- Means: DRAM refresh failure.
    The BIOS Recovery mode (which is not part of the actual P.O.S.T. Routine, but a sub-routine of the Bootblick Intialization Routine) has its own set of Beep Code definitions which are described on page 15 of the document I linked you to:
    Quote
    Boot Block Beep Codes
    Number of Beeps -- Description
    1 -- No media present. (Insert diskette in floppy drive A:)
    2 -- ‘AMIBOOT.ROM’ file not found in root directory of diskette in A:
    3 -- Insert next diskette if multiple diskettes are used for recovery
    4 -- Flash Programming successful
    5 -- File read error
    7 -- No Flash EPROM detected
    10 -- Flash Erase error
    11 -- Flash Program error
    12 --‘AMIBOOT.ROM’ file size error
    13 -- BIOS ROM image mismatch (file layout does not match image present in flash device)
    Consequently, the meaning of that single beep, that repeats every few settings is not "DRAM refresh failure" (this would be its meaning in the P.O.S.T. Routine, but we are looking at the Recovery Routine), but it actually means:
    Quote
    1 -- No media present. (Insert diskette in floppy drive A:)
    What you have to do is this:
    1. Hook up an internal (!!) floppy drive to your mainboard
    2. Prepare an AMI BIOS Recovery disk:
    --> Download the latest BIOS Archive for your board from the product site
    --> Extract the actual BIOS File and rename it to AMIBOOT.ROM
    --> Copy the renamed BIOS File to an empty & formated floppy disk
    3. Put the disk that contains the AMIBOOT.ROM file into the internal floppy drive that you connected to the mainboard.
    4. Pray that the system finds the disk, reads the file on it and performs a recovery flash

Maybe you are looking for

  • Updating warehouse in PO

    Hi all, I'm trying to update the warehouse on the 3rd line of a open PO. I am getting the error You cannot open rows in the document [Purchase Order - Rows - Row Status][line: 0]  [Message 131-194] I am able to update other fields in the row, just no

  • Jobs as a OCA

    Need a bit of advice - I have recently passed my OCA exams and now certified. I would like to put a hold on my OCP certification and instead gain some real experience in a job and expand my knowledge much beyond than just books. I have looked at vari

  • Multiple Browsers with the same Page Flow

    I have a legacy application that I am working on migrating to Weblogic. The legacy application allowed the user to have multiple windows of the same module open at the same time. Users found this useful if they wanted to look at two different records

  • Multi Language implementation

    I want my project to be used in both languages i.e English and German. How can i do that. Is using unicode wud help me, but how can i implement that

  • Nokia 808 Mobile data switch off after loading a p...

    Dear Nokia When i load for example http://538radio.radio.de the page is loaded bud after 5 sec the music stiops playing and when i check the status of the connection is say's not active. How the hell is that possible if i want to stream some music Th