Welcome guest. Before posting on our computer help forum, you must register. Click here it's easy and free.

Author Topic: 1-3-3-1 Phoenix BIOS Beep Code problem  (Read 49572 times)

0 Members and 1 Guest are viewing this topic.

XRaptor

    Topic Starter


    Greenhorn

    1-3-3-1 Phoenix BIOS Beep Code problem
    « on: October 02, 2008, 08:16:11 PM »
        
    I have an HP a000 that Im trying to repair. The computer will not boot. And I get a series of beeps.

    My computer used to work with these original RAM sticks:

    DDR 256mb SDRAM
    DDR Kingston 512mb SDRAM

    Note, there are only 2 RAM slots in my comp.

    Now, my computer will not boot. No splash screen, no POST menu, no flashing cursor, nothing. And when I pressed the power button, I heard a series of beeps. 1 beep, pause, followed by 3 beeps, pause, followed by another 3 beeps, pause, 1 beep. 1-3-3-1

    I looked up this beep error on google, and 1-3-3-1 means "28 Autosize DRAM". Here is where I found it:

    http://www.computerhope.com/beep.htm

    Well, I proceeded with taking out the 256 mb RAM and replacing it with a 512 mb stick. This gave me a total of 1GB ram. Miraculously, the computer booted up. However, it asked me to reset CMOS settings, but I ignored that and it loaded Windows. I installed Avast and restarted the computer. After it booted again, I left the computer on all night running a virus scan.

    I left for school this morning, and my mom tried loading up the internet on it. Of course, she didnt realize I didnt have internet hooked up to it. So the internet window froze, and she went to restart the comp. Sure enough, after it restarted she discovered that it wouldnt boot. EVEN WITH THIS RAM THAT WORKED LAST NIGHT!! It did the same beep sequence.

    I am incredibly frustrated. For over 2.5 hours, I have tried:

    -Trying each 512mb stick independently.
    -Removing BOTH RAM sticks and turning it on with no RAM.
    -Switching each 512 mb stick to a different slot.
    -Trying the 256mb RAM stick w/ the Kingston 512mb
    -Trying the 256mb with the other 512 mb
    -Just the 256mb independently, trying in both slots.
    -Removing the CMOS battery for over 5 minutes and putting it back in again.
    -Removing my video card.
    -Searching endlessly on the internet for a solution.

    And unfortunately, none of the scenarios listed above helped. It keeps beeping 1-3-3-1.

    I dont get it. Why did it boot last night, but not today???

    Any help is greatly appreciated. I can provide more info if wished.

    XRaptor

      Topic Starter


      Greenhorn

      Re: 1-3-3-1 Phoenix BIOS Beep Code problem
      « Reply #1 on: October 04, 2008, 12:39:01 AM »
      Okay, here are two pictures of what the screen looked like when it booted successfully two days ago, before this problem happened:

      http://img134.imageshack.us/img134/5443/s6300822ad7.jpg

      http://img390.imageshack.us/img390/185/s6300823qu3.jpg

      As you can see, the checksum is bad.  I simply pressed F2 to resume, and it booted Windows.

      Did I do something wrong?  How can I get back to this screen?

      JJ 3000



        Egghead
      • Thanked: 237
      • Experience: Familiar
      • OS: Linux variant
      Re: 1-3-3-1 Phoenix BIOS Beep Code problem
      « Reply #2 on: October 04, 2008, 02:39:16 AM »
      Sounds like your CMOS battery may be dead.
      Have you taken out or replaced the CPU?
      Save a Life!
      Adopt a homeless pet.
      http://www.petfinder.com/

      XRaptor

        Topic Starter


        Greenhorn

        Re: 1-3-3-1 Phoenix BIOS Beep Code problem
        « Reply #3 on: October 05, 2008, 01:11:27 AM »
        Sounds like your CMOS battery may be dead.
        Have you taken out or replaced the CPU?

        That could be the case.  But honestly, could the CMOS battery die in less than 24 hours?  Seems illogical to me.  I mean, I left the computer on overnight and halfway during the next day.  Could the battery have died after the computer restarted??

        And no, I have not removed the CPU.  Its too risky for me, and I cant see how removing it would solve the problem.  Like earlier stated, the computer worked JUST GREAT until my mom restarted the computer.  After Windows shut down, instead of restarting, it went to a blank black screen and the 1-3-3-1 beep code sounded.

        JJ 3000



          Egghead
        • Thanked: 237
        • Experience: Familiar
        • OS: Linux variant
        Re: 1-3-3-1 Phoenix BIOS Beep Code problem
        « Reply #4 on: October 05, 2008, 01:31:47 AM »
        You just bought a new battery?
        Are you sure you have it installed correctly?

        http://www.smartcomputing.com/Editorial/article.asp?article=articles/2004/w1510/32w10/32w10.asp
        « Last Edit: October 05, 2008, 01:50:21 AM by JJ 3000 »
        Save a Life!
        Adopt a homeless pet.
        http://www.petfinder.com/

        XRaptor

          Topic Starter


          Greenhorn

          Re: 1-3-3-1 Phoenix BIOS Beep Code problem
          « Reply #5 on: October 05, 2008, 02:30:29 PM »
          You just bought a new battery?
          Are you sure you have it installed correctly?

          http://www.smartcomputing.com/Editorial/article.asp?article=articles/2004/w1510/32w10/32w10.asp

          No, I have not purchased a new CMOS battery. 

          Last night, I removed the CMOS battery and let it sit outside the computer overnight.  I put it back in this morning.  It can only go in one way, and when I turned the computer on, there was no "checksum bad" error screen.  No POST screen.  No BIOS screen.  No splash screen.  Nothing but that 1-3-3-1 beep code.

          I will buy a new 3V CMOS battery and give it a shot.  I will post whether or not it will work.

          Despite that, any other advice is greatly appreciated.  I will keep you guys updated.

          XRaptor

            Topic Starter


            Greenhorn

            Re: 1-3-3-1 Phoenix BIOS Beep Code problem
            « Reply #6 on: October 05, 2008, 09:33:05 PM »
            UPDATE

            Instead of buying a new CMOS battery, I replaced it with a different CMOS 3V battery used in another desktop.  Still, I get the same unrelenting result.

            Also, with trying both CMOS batteries, I disconnected EVERYTHING in the computer except the PSU, CPU, and RAM memory.  I still get that darn beeping.  That means my harddrive, disc drives, pci cards, and anything else is not causing the problem.

            Now, Ive ruled out that the CMOS battery died.  What could be the problem?  How could this have happened in less than 24 hours after a successful boot?

            BC_Programmer


              Mastermind
            • Typing is no substitute for thinking.
            • Thanked: 1140
              • Yes
              • Yes
              • BC-Programming.com
            • Certifications: List
            • Computer: Specs
            • Experience: Beginner
            • OS: Windows 11
            Re: 1-3-3-1 Phoenix BIOS Beep Code problem
            « Reply #7 on: October 05, 2008, 09:41:48 PM »
            have you tried different RAM? just because it works every once in a while doesn't mean it works 100% of the time.
            I was trying to dereference Null Pointers before it was cool.

            XRaptor

              Topic Starter


              Greenhorn

              Re: 1-3-3-1 Phoenix BIOS Beep Code problem
              « Reply #8 on: October 06, 2008, 01:03:25 AM »
              have you tried different RAM? just because it works every once in a while doesn't mean it works 100% of the time.

              I have tried:

              1) The computer's original RAM (256mb + 512mb Kingston)
              2) Combinations of original RAM and my extra 512mb
              3) A lone 128mb stick
              4) No RAM at all

              That means I have tried 3 different sizes and types of RAM, in every combination possible.  Each and every time, my computer has not booted.  And I keep hearing that 1-3-3-1 beep code.

              Why does it signal a Autosize DRAM error when THREE different types of RAM do not work?  Is there any way to know for certain that it's my RAM thats causing the issue?  What if its my motherboard? 

              If it was my motherboard, how could it have been able to run Windows and all the hardware associated to it for over 12 hours straight, including the installation/running of Avast and two successful reboots?  It just doesnt make sense at all...   

              street1 (RIP)

              • R.I.P.


              • Egghead

              • I Triple Dog Dare You!!! LOL
              • Thanked: 14
                • Obituary
              • Experience: Beginner
              • OS: Windows XP
              Re: 1-3-3-1 Phoenix BIOS Beep Code problem
              « Reply #9 on: October 06, 2008, 03:29:45 AM »
              If you have the original stick of memory in the primary slot you
              may have a crack in the motherboard.

              Try loosening all the motherboard screws slightly move the motherboard  around then tighten the motherboard screws gently do not over tighten.
              Sorry,The USA has ruined the language The United Kingdom loaned us. We do our best not to type gibberish. I Hope you can forgive us.

              goodgoing



                Newbie

                • Experience: Beginner
                • OS: Unknown
                Re: 1-3-3-1 Phoenix BIOS Beep Code problem
                « Reply #10 on: August 13, 2012, 06:58:15 AM »
                I found on this website a page that lists all the problems that it coud be.  www.computerhope.com/beep.htm

                Computer_Commando



                  Hacker
                • Thanked: 494
                • Certifications: List
                • Computer: Specs
                • Experience: Expert
                • OS: Windows 10
                Re: 1-3-3-1 Phoenix BIOS Beep Code problem
                « Reply #11 on: August 13, 2012, 09:07:06 AM »
                You're responding to a thread that's almost 4 years old & your solution is offered in the 1st post, which you obviously did not read.