Initialization failure after rom update

AMI BIOS beep codes Below are the AMI BIOS Beep codes that can occur. However, because of the wide variety of different computer manufacturers with this BIOS, the beep codes may vary.
Beep Code Descriptions 1 short DRAM refresh failure 2 short Parity circuit failure 3 short Base 64K RAM failure 4 short System timer failure 5 short Process failure 6 short Keyboard controller Gate A20 error 7 short Virtual mode exception error 8 short Display memory Read/Write test failure 9 short ROM BIOS checksum failure 10 short CMOS shutdown Read/Write error 11 short Cache Memory error 1 long, 3 short Conventional/Extended memory failure 1 long, 8 short Display/Retrace test failed Award BIOS Beep codes that can occur. However, because of the wide variety of different computer manufacturers with this BIOS, the beep codes may vary. Beep Code Description 1 long, 2 short Indicates a video error has occurred and the BIOS cannot initialize the video screen to display any additional information Any other beep(s) RAM problem. If any other correctable hardware issues is found the BIOS displays a message. No Power, Loose Card, or Short.1 Short BeepNormal POST, computer is ok.2 Short BeepPOST error, review screen for error code.Continuous BeepNo Power, Loose Card, or Short.Repeating Short BeepNo Power, Loose Card, or Short.One Long and one Short BeepMotherboard issue.One Long and Two Short BeepsVideo (Mono/CGA Display Circuitry) issue.One Long and Three Short Beeps.Video (EGA) Display Circuitry.Three Long BeepsKeyboard or Keyboard card error.One Beep, Blank or Incorrect DisplayVideo Display Circuitry. Phoenix BIOS Q3.07 OR 4.X Beep Code Description and what to check 1-1-1-3 Verify Real Mode. 1-1-2-1 Get CPU Type. 1-1-2-3 Initialize system hardware. 1-1-3-1 Initialize chipset registers with initial POST values. 1-1-3-2 Set in POST flag. 1-1-3-3 Initialize CPU registers. 1-1-4-1 Initialize cache to initial POST values. 1-1-4-3 Initialize I/O. 1-2-1-1 Initialize Power Management. 1-2-1-2 Load alternate registers with initial POST values. 1-2-1-3 Jump to UserPatch0. 1-2-2-1 Initialize keyboard controller. 1-2-2-3 BIOS ROM checksum. 1-2-3-1 8254 timer initialization. 1-2-3-3 8237 DMA controller initialization. 1-2-4-1 Reset Programmable Interrupt Controller. 1-3-1-1 Test DRAM refresh. 1-3-1-3 Test 8742 Keyboard Controller. 1-3-2-1 Set ES segment to register to 4 GB. 1-3-3-1 28 Autosize DRAM. 1-3-3-3 Clear 512K base RAM. 1-3-4-1 Test 512 base address lines. 1-3-4-3 Test 512K base memory. 1-4-1-3 Test CPU bus-clock frequency. 1-4-2-4 Reinitialize the chipset. 1-4-3-1 Shadow system BIOS ROM. 1-4-3-2 Reinitialize the cache. 1-4-3-3 Autosize cache. 1-4-4-1 Configure advanced chipset registers. 1-4-4-2 Load alternate registers with CMOS values. 2-1-1-1 Set Initial CPU speed. 2-1-1-3 Initialize interrupt vectors. 2-1-2-1 Initialize BIOS interrupts. 2-1-2-3 Check ROM copyright notice. 2-1-2-4 Initialize manager for PCI Options ROMs. 2-1-3-1 Check video configuration against CMOS. 2-1-3-2 Initialize PCI bus and devices. 2-1-3-3 Initialize all video adapters in system. 2-1-4-1 Shadow video BIOS ROM. 2-1-4-3 Display copyright notice. 2-2-1-1 Display CPU Type and speed. 2-2-1-3 Test keyboard. 2-2-2-1 Set key click if enabled. 2-2-2-3 56 Enable keyboard. 2-2-3-1 Test for unexpected interrupts. 2-2-3-3 Display prompt Press F2 to enter SETUP. 2-2-4-1 Test RAM between 512 and 640k. 2-3-1-1 Test expanded memory. 2-3-1-3 Test extended memory address lines. 2-3-2-1 Jump to UserPatch1. 2-3-2-3 Configure advanced cache registers. 2-3-3-1 Enable external and CPU caches. 2-3-3-3 Display external cache size. 2-3-4-1 Display shadow message. 2-3-4-3 Display non-disposable segments. 2-4-1-1 Display error messages. 2-4-1-3 Check for configuration errors. 2-4-2-1 Test real-time clock. 2-4-2-3 Check for keyboard errors 2-4-4-1 Set up hardware interrupts vectors. 2-4-4-3 Test coprocessor if present. 3-1-1-1 Disable onboard I/O ports. 3-1-1-3 Detect and install external RS232 ports. 3-1-2-1 Detect and install external parallel ports. 3-1-2-3 Re-initialize onboard I/O ports. 3-1-3-1 Initialize BIOS Data Area. 3-1-3-3 Initialize Extended BIOS Data Area. 3-1-4-1 Initialize floppy controller. 3-2-1-1 Initialize hard disk controller. 3-2-1-2 Initialize local bus hard disk controller. 3-2-1-3 Jump to UserPatch2. 3-2-2-1 Disable A20 address line. 3-2-2-3 Clear huge ES segment register. 3-2-3-1 Search for option ROMs. 3-2-3-3 Shadow option ROMs. 3-2-4-1 Set up Power Management. 3-2-4-3 Enable hardware interrupts. 3-3-1-1 Set time of day. 3-3-1-3 Check key lock. 3-3-3-1 Erase F2 prompt. 3-3-3-3 Scan for F2 key stroke. 3-3-4-1 Enter SETUP. 3-3-4-3 Clear in POST flag. 3-4-1-1 Check for errors 3-4-1-3 POST done - prepare to boot operating system. 3-4-2-1 One beep. 3-4-2-3 Check password (optional). 3-4-3-1 Clear global descriptor table. 3-4-4-1 Clear parity checkers. 3-4-4-3 Clear screen (optional). 3-4-4-4 Check virus and backup reminders. 4-1-1-1 Try to boot with INT 19. 4-2-1-1 Interrupt handler error. 4-2-1-3 Unknown interrupt error. 4-2-2-1 Pending interrupt error. 4-2-2-3 Initialize option ROM error. 4-2-3-1 Shutdown error. 4-2-3-3 Extended Block Move. 4-2-4-1 Shutdown 10 error. 4-3-1-3 Initialize the chipset. 4-3-1-4 Initialize refresh counter. 4-3-2-1 Check for Forced Flash. 4-3-2-2 Check HW status of ROM. 4-3-2-3 BIOS ROM is OK. 4-3-2-4 Do a complete RAM test. 4-3-3-1 Do OEM initialization. 4-3-3-2 Initialize interrupt controller. 4-3-3-3 Read in bootstrap code. 4-3-3-4 Initialize all vectors. 4-3-4-1 Boot the Flash program. 4-3-4-2 Initialize the boot device. 4-3-4-3 Boot code was read OK.


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

Yu will need to determine which BIOS you have a see below
The computer beeps several times
If you hear several beeps from the PC speaker, it means that the computer failed its power-on self test (POST) because a problem was detected. The POST is a procedure that tests several components such as power, BIOS, CPU, memory, and video. Only if all those tests pass, the computer will then allow the operating system to load. But if one or more of these tests fail, beeps indicate a problem and the boot process is halted. These errors are a little more difficult to troubleshoot.
To diagnose the problem, listen to the beeps carefully and write down the sequence. Is it one long beep? Is it several short beeps? How many? Once you have the beep sequence documented, you need to find out what it means. What BIOS do you have? When you first turn on the PC, look at the top of the first screen to find out. Common BIOS types are Award, Phoenix, and AMI.
Award:
1-2-2 Indicates a video error has occurred and the BIOS cannot initialize the video screen to display any additional information Any other beeps Most likely a RAM problemYou can find more detailed information about Award error messages on Award's web site.
Phoenix:
1-2-2 Indicates a video error has occurred and the BIOS cannot initialize the video screen to display any additional information 1-2-2-3 BIOS ROM Checksum 1-3-1-1 Test DRAM Refresh 1-3-1-3 Test Keyboard Controller 1-3-4-1 RAM Failure 1-3-4-3 RAM Failure 2-1-2-3 Check ROM Copyright Notice 2-2-3-1 Test for unexpected interrupts 1-3-4-3 RAM FailureYou can find more detailed information about Phoenix error messages on Phoenix's web site.
AMI:
1 beep Refresh failure 2 beeps Parity error 3 beeps Base 64K memory failure 4 beeps Timer not operational 5 beeps Processor error 6 beeps 8042 - gate A20 failure 7 beeps Processor exception interrupt error 8 beeps Display memory read/write failure 9 beeps ROM checksum error 10 beeps CMOS shutdown register read/write error 11 beeps Cache memory badYou can find more detailed information about AMI error messages on AMI's web site.
If you get beep errors, you should try to think what happened right before they started. Did you add a new piece of hardware? If so, it might be faulty or not installed right. Remove it, then try again. If everything is fine without the hardware, try to reinstall and configure the hardware again. If that does not help, try exchanging it and see if that corrects the problem. If the error persists, narrow it down systematically. Remove everything but the CPU, memory, keyboard, and video card, then boot again. Does the error still occur? If not, then add one piece of hardware and try again. Repeat until one new component causes the error and you now know who the culprit is. If yes, then reseat your CPU, memory and video card and try again. If the error still happens, try replacing the CPU, video card and memory one by one to see if one of them is the troublemaker. If that does not help, you could have a bad motherboard. Check the motherboard carefully for any signs of damage. Also check for shorts, a metallic object could have found its way onto the motherboard, or the motherboard is not installed correctly and touches the case somewhere.
Page 1: Computer boot problems
Page 2: This page
Page 3: System hanging after POST
Page 4: POST running OK but Windows not starting

Good luck

Please rate FIXYA

Thanks

Hi.

Solving your problem is just as easy as 2 hour work. not more..

By the time you were having the restarting problems.. all you had to do was to boot from usb cd-rom using Hirenes boot cd 10.

It starts a small intergrated windows. then you would have to go to a menu to stop some un-named startup bugs that cause the restart when Explorer.exe is being executed by windows.

so now, if you have your backups safe, get instruction on the internet on how to make a bootable usb windows vista or 7 Setup. windows seven comes with many drivers for new laptops.

Boot your computer from USB flash disk, run the windows 7 setup and enjoy..

hope this information helps you because it helped me with Acer One netbook..

good luck

not_you

Have you tried to assign another drive letter to the to the ROM drives. The link below will help you do this.

http://www.fixya.com/support/r4176803-change_drive_letter_in_windows_vista

Let me know if you have any more problems or questions

Issken
http://www.fixya.com/users/issken

Update Acer drivers. I lost 1 USB on my Acer. This resolved the issue. After fixing it change settings to allow automatic updates.

If this is a problem that just occurred and until now it has worked, my first step would be to check that the hardware, (the CD drive) is still functioning and that the software, (the drivers) are still installed and not corrupted. First go to the start button, then control panel, then performance and maintainance,go to system, and then hardware. Look for DVD/CD ROM drives, if you have more than one CD or DVD drive, point and left click on the plus symbol to the left of DVD/CD ROM Drives. Point and left click on the drive in question to highlight it then go to action, scroll down to properties and left click. This window should say that the device is working properly and also at the bottom of this window, under device usage it sould say "use this device, enable". If all of this seems to be working so far, the drive itself should be good.If there have been error messages, there is an option on the last window that opened to troubleshoot. Use it. If so far, everything looks good, now check that the drivers are good. Follow all of the above steps up until you open the device manager and point to the drive in question, go to action. This time scroll down to update driver and left click. A window will open that says " welcome to the hardware update wizard". Point and highlight the circle that says" no,not this time" regarding connecting to the internet to search for a driver. If this device has been working, the driver should still be on your hard drive. Follow the wizard prompts. If at the end of the wizard you are informed that a better match could not be found, then most likely the drivers are still good for this device. If after checking both the hardware and the software, you saw no errors and everything looked as though it were operating, the problem may be more than you can solve without some repair expertise.

The NIC is fine, however it hangs because it is searching the network for boot information. This NIC's boot timeout is a lot longer than most.

hy i have your solution.its simple. the problem is remote network data entry that start in the bios systems, produce by a virus call downloader.trojan or bootable Tj.exe, normally the bios has to read it and it gives the error " media test faliurecheck cables",ir you dont repaired quickly your laptop or desktop eventually will not boot the windows att all, this have to be kill before that happens, First of all clean your pc with Trojan Remover and then do just a simple task restart your desktop or laptop and do not let it initiate windows just press F2 at the bios and go to the Bios program and then go to the tab name Bios and press F9 that means "default bios systems" and everything will change in your bios and when your desktop or pc restart it will never show that message again and your bios will initiate with no problems and the virus that put that into your pc will no longer control your bios system.

Possible solution?

PROCEDURE
1. Initialize the system.
a) Enter the TEST mode.
b) Select "3:ROM UPDATE" and press SET button.
c) Next, select "5:SYSTEM INITIAL" and press SET button.
d) The following message appears.
SYSTEM INITIALIZE
START ...
PUSH OK KEY?
e) Press SET button and System is initialized.
"SUCCESS !" appears on the monitor.
2. Write firmware.
Update the firmware version"
Write the firmware.
If the TEST mode boots automatically, change "USB TCC ON" to "USB TCC OFF".

I have looked at different sites and found some informations. The only way for you is an EUU (End User Update) but Toshiba doesn't offer an EUU for the e350 until now, perhaps Toshiba installed a OS with all available EUUs yet and is waiting for an EUU from MS.