Bios Bleeps

[Tee_111]

Found this from another Forum,


Below is a table of the most common AMI, Phoenix and Award BIOS beep codes.

AMI (American Megatrends International) BIOS Beep Codes.
AMI BIOS uses beeps of the same length and pitch. The error is displayed as a number of beeps. For example, 4 beeps indicated a timer failure.
BEEP CODE MEANING POSSIBLE CAUSE
1 Beep (No video) Memory refresh failure Bad memory
2 Beeps Memory parity error Bad memory
3 Beeps Base 64K mem failure Bad memory
4 Beeps Timer not operational Bad motherboard
5 Beeps Processor error Bad processor
6 Beeps 8042 Gate A20 failure Bad CPU or Motherboard
7 Beeps Processor exception Bad processor
8 Beeps Video memory error Bad video card or memory
9 Beeps ROM checksum error Bad BIOS
10 Beeps CMOS checksum error Bad motherboard
11 Beeps Cache memory bad Bad CPU or motherboard



Award BIOS Beep Codes
Award BIOS uses beeps of varying duration. A long beep will typically last for 2 seconds while a short beep will last only 1 second. Award BIOS also uses beeps of different frequency to indicate critical errors. If an Award BIOS detects that the CPU is overheating it may play a high pitched repeating beep while the computer is running.
BEEP CODE MEANING POSSIBLE CAUSE
1 Long, 2 Short Video adapter failure Bad video adapter
Repeating (Endless loop) Memory error Bad memory or bad connection
1 Long, 3 Short Video adapter failure Bad video adapter or memory
High freq. beeps (while running) CPU is overheating CPU fan failure
Repeating High, Low beeps CPU failure Bad processor



Phoenix BIOS Beep Codes
Phoenix BIOS uses beep code patterns to indicate problems. In the table below the '-' indicates a brief pause between beeps.
Example: 1 - 1 - 2 would sound like BEEP <pause> BEEP <pause> BEEP BEEP

BEEP CODE MEANING POSSIBLE CAUSE
1 - 1 - 2 CPU / motherboard failure Bad CPU / motherboard
1 - 1 - 3 CMOS read/write failure Bad motherboard
1 - 1 - 4 BIOS ROM failure Bad BIOS chip
1 - 2 - 1 Timer failure Bad motherboard
1 - 2 - 2 DMA failure Bad motherboard
1 - 2 - 3 DMA failure Bad motherboard
1 - 3 - 1 Memory refresh failure Bad memory
1 - 3 - 2 64K memory failure Bad memory
1 - 3 - 3 64K memory failure Bad memory
1 - 3 - 4 64K memory failure Bad memory
1 - 4 - 1 Address line failure Bad memory
1 - 4 - 2 Parity error Bad memory
1 - 4 - 3 Timer failure Bad motherboard
1 - 4 - 4 NMI port failure Bad motherboard
2 - 1 - 1 64K memory failure Bad memory
2 - 1 - 2 64K memory failure Bad memory
2 - 1 - 3 64K memory failure Bad memory
2 - 1 - 4 64K memory failure Bad memory
2 - 2 - 1 64K memory failure Bad memory
2 - 2 - 2 64K memory failure Bad memory
2 - 2 - 3 64K memory failure Bad memory
2 - 2 - 4 64K memory failure Bad memory
2 - 3 - 1 64K memory failure Bad memory
2 - 3 - 2 64K memory failure Bad memory
2 - 3 - 3 64K memory failure Bad memory
2 - 3 - 4 64K memory failure Bad memory
2 - 4 - 1 64K memory failure Bad memory
2 - 4 - 2 64K memory failure Bad memory
2 - 4 - 4 64K memory failure Bad memory
2 - 4 - 4 64K memory failure Bad memory
3 - 1 - 1 Slave DMA failure Bad motherboard
3 - 1 - 2 Master DMA failure Bad motherboard
3 - 1 - 3 Interrupt controller failure Bad motherboard
3 - 1 -4 Slave IC failure Bad motherboard
3 - 2 -2 Interrupt Controller failure Bad motherboard
3 - 2 - 3 <RESERVED>
3 - 2 - 4 Keyboard control failure Bad motherboard
3 - 3 - 1 CMOS batter failure Bad CMOS battery
3 - 3 - 2 CMOS configuration error Incorrect setting
3 - 3 - 3 <RESERVED>
3 - 3 - 4 Video memory failure Bad video card or memory
3 - 4 - 1 Video init failure Bad video card or memory
4 - 2 - 1 Timer failure Bad motherboard
4 - 2 - 2 CMOS shutdown failure Bad motherboard
4 - 2 - 3 Gate A20 failure Bad motherboard
4 - 2 - 4 Unexpected interrupt Bad processor
4 - 3 - 1 RAM test failure Bad memory
4 - 3 - 3 Timer failure Bad motherboard
4 - 3 - 4 RTC failure Bad motherboard
4 - 4 - 1 Serial port failure Bad motherboard
4 - 4 - 2 Parallel port failure Bad motherboard
4 - 4 - 3 Coprocessor failure Bad motherboard or CPU.
9 - 2 - 1 Video adapter incompatibility Use a different brand of video card
Useful sites
Bios Central

[Tee_111]

Windows Stop Errors or Blue screen of death, (BSOD) are generated when windows experiences a fault from which it cannot recover. They are a feature of all Microsoft NT based operating systems e.g. NT, Windows 2000 and Windows XP.
The purpose of the stop error is to help you to troubleshoot problems with your system. The stop error is usually written in hex, for example 0x0000000A this can also be shortened to 0xA.

Causes of Stop Errors

Many things can cause stop errors, hardware and software, fortunately the Stop error describes the error and can be used to determine the cause. The probability of these errors also increases when you overclock your PC.
Below is a list of Stop errors, it is in no way a definitive list but hopefully deals with the more common stop errors.

0x0000000A: IRQL_NOT_LESS_OR_EQUAL

When people see this error, they see the IRQ part and assume that this must be caused by an IRQ conflict. This is not the case. It is caused when a kernel mode process or, more commonly, a driver attempts to access memory that it shouldn’t. If you receive this error, you should be thinking about the drivers you have installed. Are they certified to work by Microsoft?

0x0000007B: INACCESSIBLE_BOOT_DEVICE

This one is more self-explanatory. Windows cannot boot from the selected device. You will need to check that the drivers for your hard disk controller are loaded if you’re are using an onboard or external raid controller or if you are using a SCSI card. If you cannot boot the PC, move the hard disk to a standard IDE controller, boot and then install the correct drivers.

0x000000C2: BAD_POOL_CALLER

Again a kernel mode process or driver performed an illegal memory operation. Check for any recently installed drivers, which could be causing the problem.

0x00000050: PAGE_FAULT_IN_NONPAGED_AREA

A hardware or software component attempted to access a memory address which does not exist or the data it was attempting to access does not exist. This can also be caused by defective memory and can also be caused by pushing the memory too far when overclocking.

0x00000076: PROCESS_HAS_LOCKED_PAGES and
0x000000CB: DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS

This is also caused by drivers. A driver uses allocated memory but doesn’t free up the memory correctly after its operation.

0xC0000218: UNKNOWN_HARD_ERROR

A registry hive could not be loaded. You will need to restore the registry. This can happen if the registry data on your hard disk gets corrupted or if when loading the registry into memory it gets corrupted. This is usually hardware related.

0x0000001E: KMODE_EXCEPTION_NOT_HANDLED

This Stop message indicates that a kernel-mode process tried to execute an incorrect or unknown processor instruction. This error handler is a default error handler that catches errors not associated with other specific error handlers. This can be caused by drivers or possibly a hardware problem.

What to do after a stop error?

There are several options after you receive a stop error, depending on which operating system you use and how well prepared you are. A lot of the time you may be able to let the pc reboot as normal and everything will be fine, sometimes it won’t. When you receive a stop error, switch off your pc when it reboots and consider your options. These are the options:

Last known good configuration (NT/Windows 2000/Windows XP)

This is a “one shot” method. If immediately after you receive the stop error you select last known good configuration from the advanced start up options, windows will use a copy of the registry from the previous reboot. This only works once, if you reboot without it the old version of the registry will be overwritten with the version you were using when the blue screen occurred. The disadvantage to this is that any applications or drivers you have installed since the last reboot will be lost.

intresting site with some more info http://aumha.org/win5/kbestop.php