URGENT- flashed BIOS, now compy has major problems.

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • impostal22
    disgruntled...
    • Apr 2003
    • 1623

    #1

    URGENT- flashed BIOS, now compy has major problems.

    ok..so i reformatted my sister's computer and reinstalled XP onto it. then i installed the mobo drivers, and saw the flash utility, i installed that and decided to check the net for an updated version of BIOS. there was one, so i flashed it. rebooted, seemed to be fine. then i tried going on the internet and the compy froze, so i rebooted and it sat beeping at me...every 3 seconds or so it would beep. so i turned the power off completely and hit the power button again. then it booted, saying the processor was only running at like 1.2ghz when it's a 2.something ghz processor. it boots ok..but freezes again so i hit the reset button, same thing happens. it sits and beeps at me. i followed the overly-easy directions of the BIOS flash, and now i get this. why is the computer beeping like it is, and saying the processor is so much slower than it is? how can i fix this? HELP!
  • Tunaman
    Specialized AGD Tech

    • Dec 2000
    • 8643

    #2
    Check the bios settings for CPU speed and FSB speed. I betcha one is set wrong.
    Email me for low prices on ALL AGD Products and more. [email protected]
    Tunamart

    Comment

    • impostal22
      disgruntled...
      • Apr 2003
      • 1623

      #3
      ya...and how do i know exactly what each is supposed to be? would that be the cause of the beeping as well? and why would flashing bios set that wrong? prior to flashing, the settings were correct and i had no problems booting.

      Comment

      • MantisMag
        Dim Sum
        • Dec 2001
        • 1895

        #4
        people who don't know what they're doing should leave things alone. in order to do anything you need to know the model of both your mobo and cpu. look up what the beeping means. sometimes the beeping comes in patterns that mean something. there might also be lights on the mobo to tell you what's wrong. look up what your fsb and multiplier should be set to. flashing the bios most likely reset all the settings on your mobo and now some of them are wrong.

        Comment

        • impostal22
          disgruntled...
          • Apr 2003
          • 1623

          #5
          Originally posted by MantisMag
          people who don't know what they're doing should leave things alone. in order to do anything you need to know the model of both your mobo and cpu. look up what the beeping means. sometimes the beeping comes in patterns that mean something. there might also be lights on the mobo to tell you what's wrong. look up what your fsb and multiplier should be set to. flashing the bios most likely reset all the settings on your mobo and now some of them are wrong.
          thanks for not being too condescending.

          Comment

          • Fixion
            Registered User
            • Aug 2003
            • 815

            #6
            Originally posted by Tunaman
            Check the bios settings for CPU speed and FSB speed. I betcha one is set wrong.
            Exactly the problem. A bios flash always resets the settings (unless your fsb and multiplyer are set by jumpers, and your multiplyer is probably locked so that doesn't matter).

            As for the other problems. What motherboard do you have? Some have multipule revisions, and the revisions don't always take the same bios (they are incompatible in some way). You might have flashed the wrong bios onto it. I'd flash the old bios back (if you saved it).

            people who don't know what they're doing should leave things alone. in order to do anything you need to know the model of both your mobo and cpu. look up what the beeping means. sometimes the beeping comes in patterns that mean something. there might also be lights on the mobo to tell you what's wrong. look up what your fsb and multiplier should be set to. flashing the bios most likely reset all the settings on your mobo and now some of them are wrong.
            Beep codes are given at boot, when the computer can't boot for some reason. I don't know of any motherboard that would give beepcodes after boot.
            Last edited by Fixion; 05-19-2004, 12:01 AM.
            .

            Comment

            • impostal22
              disgruntled...
              • Apr 2003
              • 1623

              #7
              As for the other problems. What motherboard do you have? Some have multipule revisions, and the revisions don't always take the same bios (they are incompatible in some way). You might have flashed the wrong bios onto it. I'd flash the old bios back (if you saved it).
              it's the asus ASUS A7N8X-X nVidia nForce-2 400 FSB...i know it's cheap, but it's not my computer either.

              the CPU is the AMD Athlon XP 2800+ with 512K L2 cache...

              i used a utility on the mobo's driver cd to flash bios. it found various new versions of bios that (i assume) were compatible with my mobo, then i picked the latest one and installed it.

              how do i figure out what settings need changed back and what they need changed back to? this is obviously my first time flashing BIOS, so your help is appreciated.

              Comment

              • impostal22
                disgruntled...
                • Apr 2003
                • 1623

                #8
                ok........so i reset the CPU settings to the correct ones (that's the only thing i changed). it booted...but then shortly after booting i got a blue screen saying....

                IRQL_NOT_LESS_OR_EQUAL

                some helpful information here...

                then...

                STOP 0x0000000A (0x0F000A0F, 0x000000FF, 0x00000000, 0x804ECABB)

                Beginning dump of physical memory.

                Comment

                • Buff
                  Registered User
                  • Apr 2002
                  • 414

                  #9
                  uhm, not sure what the exact setting are supposed to be, but try to set exactly as I say:
                  under advanced chipset features:
                  CPU external freq---200mhz (higher then supposed, but will work)
                  cpu ratio/multiplier--10.5 =cpu speed 2100mhz
                  memory freq -------100%
                  system performance-user defined
                  cpu interface-------Optimal
                  Memory timings-----user defined
                  set ram timings, from top to bottom
                  11-3-3-2.5
                  AGP Vddq-----------1.6V
                  AGP aperature------64mb or 128mb
                  cpu vcore setting----menu
                  Vcore/cpu voltage--- 1.6V
                  Vdimm/ ram voltage--2.8V

                  follow all that to the letter and it should work.
                  if it dosn't, I'll give u a ne set of settings.
                  by the way, I have the A7N8X, not my preference.......

                  emag block body-chrome rail-stock frame-
                  classic valve-32 carbon fiber 12"-
                  chrome palmer stab
                  My Feedback

                  Comment

                  • Buff
                    Registered User
                    • Apr 2002
                    • 414

                    #10
                    o, that error u got means ur ram aint holding up, or sum settings are wrong.

                    emag block body-chrome rail-stock frame-
                    classic valve-32 carbon fiber 12"-
                    chrome palmer stab
                    My Feedback

                    Comment

                    • impostal22
                      disgruntled...
                      • Apr 2003
                      • 1623

                      #11
                      Originally posted by Buff
                      o, that error u got means ur ram aint holding up, or sum settings are wrong.
                      what should the sum settings be...

                      Comment

                      • Buff
                        Registered User
                        • Apr 2002
                        • 414

                        #12
                        lol, no, i meant *some* settings are wrong.

                        look up^^^^^^, and set those. From there i can help u.
                        with those settings it will eliminate most probs, and any probs that come up will be fixable.

                        emag block body-chrome rail-stock frame-
                        classic valve-32 carbon fiber 12"-
                        chrome palmer stab
                        My Feedback

                        Comment

                        • impostal22
                          disgruntled...
                          • Apr 2003
                          • 1623

                          #13
                          ok about those settings you told me...

                          CPU external freq---200mhz (higher then supposed, but will work)
                          i set to 166 (dunno why, i heard that's what the xp2800+ is supposed to be)

                          cpu ratio/multiplier--10.5 =cpu speed 2100mhz
                          set to 12.5 to make it 2083, the processing speed of the 2800+

                          memory freq -------100%
                          there wasn't 100%...just auto and by speed...i picked auto

                          Memory timings-----user defined
                          set ram timings, from top to bottom
                          11-3-3-2.5
                          there's no way to alter those...at least i couldn't find one in this crappy version of BIOS

                          AGP Vddq-----------1.6V
                          couldn't even go that low...lowest was 1.65v

                          cpu vcore setting----menu
                          Vcore/cpu voltage--- 1.6V
                          i was too afraid to alter this

                          so now the compy boots fine and i have not YET had another blue screen, although it's only been up for about an hour...

                          my ram is ddr400...so should i set the cpu external frequency to 200 (and adjust the multiplier accordingly) to match the ram? or should i leave it at 166?

                          thanks for all your help, man.

                          Comment

                          • Buff
                            Registered User
                            • Apr 2002
                            • 414

                            #14
                            if ur ram is 400, set the external freq to 200, and the multiplier to 10.5, that will give u 2100mhz, close enough to 2083. Mine is a 1.83, I run it at 2.41ghz

                            to set ur ram timings, u have to set another option to user defined, then they can be changed. dont set the exteranl freq(FSB) to 200 until u get the ram timings set to 11-3-3-2.5, or it might throw a fit.

                            emag block body-chrome rail-stock frame-
                            classic valve-32 carbon fiber 12"-
                            chrome palmer stab
                            My Feedback

                            Comment

                            • impostal22
                              disgruntled...
                              • Apr 2003
                              • 1623

                              #15
                              Originally posted by Buff
                              if ur ram is 400, set the external freq to 200, and the multiplier to 10.5, that will give u 2100mhz, close enough to 2083. Mine is a 1.83, I run it at 2.41ghz

                              to set ur ram timings, u have to set another option to user defined, then they can be changed. dont set the exteranl freq(FSB) to 200 until u get the ram timings set to 11-3-3-2.5, or it might throw a fit.
                              ya..i couldn't find a user defined option for anything ram related...oh and why those timing settings?

                              Comment

                              Working...