Bios signals three long, 1 short. BIOS signals from Award. The most common BIOS beeps
American Megatrends, Inc. (AMI)
The checkpoints of the POST procedures performed in AMIBIOS were redesigned and supplemented in 1995 and have not undergone significant changes to date. The first description of POST codes or as AMI calls them - "check points" in their current form appeared in connection with the release of the V6.24 kernel, 07/15/95. Some changes have been made to AMIBIOS V7.0, which are reflected in this document.
Features of performing AMIBIOS startup procedures
If during the startup process the data 55h, AAh appears in the diagnostic port, you should not compare this information with POST codes - we are dealing with a typical test sequence, the task of which is to check the integrity of the data bus.
At the start stage, the output to the diagnostic port of data is specific to each platform. In some implementations, the first code rendered is associated with actions, which AMI calls chipset specific stuff. This procedure is accompanied by outputting the CCh value to port 80h and performing a number of steps to configure the registers system logic. As a rule, the CCh code appears in cases where system logic from Intel is used, built on the basis of the PIIX controller - these are TX, LX, BX chipsets.
Some on-board I/O chips contain an RTC and a keyboard controller, which are disabled at startup. The purpose of the BIOS is to initialize these board resources for further use. In this case, the first startup procedure associated with setting up the keyboard controller is accompanied by the output of the value 10h, then the RTC is initialized, as evidenced by the appearance of the DDh code in the diagnostic port. It should be noted that the failure of at least one of these resources will result in a non-start of the system board as a whole at the very first stage of POST execution.
On a number of boards, the initialization process begins with the CPU switching to protected mode. In this case, following the first rendered code 43h, the POST execution continues as described in the AMIBIOS documentation - control is transferred to point D0h.
Unpacked initialization procedure codes
Uncompressed Init Code Check Points
Error code | Description of the error |
---|---|
E.E. | In modern AMIBIOS implementations, the first code rendered is associated with accessing the device from which it is possible to boot to restore the BIOS |
CC | Initializing system logic registers CD Flash ROM type not recognized |
C.E. | Checksum mismatch in the starting BIOS CF Error in accessing the spare Flash ROM chip |
DD | Early initialization of the RTC, which is integrated into the SIO chip |
D0 | Disable non-maskable NMI interrupt. Working out the time delay for attenuation of transient processes. Checking the Boot Block checksum, stopping if there is a mismatch |
D1 | Perform memory regeneration procedure and Basic Assurance Test. Switching to 4 GB memory addressing mode |
D3 | Determination of capacity and primary memory test |
D4 | Return to real memory addressing mode. Early initialization of the chip set. Stack Installation |
D5 | Transferring the POST module from Flash ROM to the transit memory area |
D6 | If the checksum does not match or CTRL+Home, a transition to the procedure is performed Flash recovery ROM (Code E0) |
D7 | Transferring control to a utility program that unpacks the system BIOS |
D8 | Complete unpacking of the system BIOS |
D9 | Transferring system BIOS control to Shadow RAM |
D.A. | Reading information from SPD (Serial Presence Detect) DIMM DB modules Setting MTRR registers central processor |
DC | The memory controller is programmed according to the data received from the SPD DE Configuration error system memory. Fatal error |
DF | System memory configuration error. Beep 10 Early |
11 | Return from STR (Suspend to RAM) state |
12 | Restoring access to SMRAM (System Management RAM) |
13 | Memory regeneration restoration |
14 | Finding and initializing VGA BIOS |
Flash ROM rewrite procedure codes
Boot Block Recovery Codes
Error code | Description of the error |
---|---|
E0 | Preparations are being made to intercept INT19 and the ability to start the system in simplified mode is checked. |
E1 | Setting interrupt vectors |
E3 | Recovering CMOS contents, searching and initializing BIOS |
E2 | Preparing interrupt controllers and direct memory access |
E6 | Enable system timer and FDC interrupts |
E.C. | Reinitializing the IRQ and DMA ED controllers Initializing the disk drive |
E.E. | Reading boot sector from floppy disk EF Disk operation error |
F0 | Finding the AMIBOOT.ROM file |
F1 | IN root directory file AMIBOOT.ROM not found F2 Read FAT |
F3 | Reading AMIBOOT.ROM |
F4 | The size of the AMIBOOT.ROM file does not match the size of the Flash ROM |
F5 | Disabling Internal Cache |
FB | Flash ROM Type Definition |
F.C. | Erasing the main Flash ROM block |
FD | Programming the main Flash ROM block |
FF | Restart BIOS |
Unpacked system BIOS codes executed in ShadowRAM
Runtime code is uncompressed in F000 shadow RAM
Error code | Description of the error |
---|---|
03 | Disable non-maskable NMI interrupt. Reset type definition |
05 | Stack initialization. Disable memory caching and USB controller |
06 | Executing a utility program in RAM |
07 | Processor recognition and APIC initialization |
08 | Checking the CMOS checksum |
09 | Checking the execution of the End/Ins keys |
0A | Battery failure check |
0B | Clearing the keyboard controller buffer registers |
0C | A test command is sent to the keyboard controller |
0E | Finding additional devices supported by the keyboard controller |
0F | Initializing the keyboard |
10 | A reset command is sent to the keyboard |
11 | If the End or Ins key is pressed, the CMOS 12 is reset. Placing the DMA controllers in a passive state. |
13 | Chipset initialization and L2 cache |
14 | Checking the system timer |
19 | DRAM regeneration request generation test running |
1A | Checking the duration of the regeneration cycle |
20 | Initializing Output Devices |
23 | The keyboard controller input port is read. Keylock Switch and Manufacture Test Switch are interrogated |
24 | Preparing to initialize the interrupt vector table |
25 | Interrupt vector initialization complete |
26 | The status of the Turbo Switch jumper is polled through the keyboard controller input port |
27 | Primary initialization of the USB controller. Updating the microcode of the starting processor |
28 | Preparing to install video mode |
29 | Initializing the LCD panel |
2A | Search for devices supported by additional ROMs |
2B | Initializing VGA BIOS, checking its checksum |
2C | Executing VGA BIOS |
2D | Matching INT 10h and INT 42h |
2E | Search for CGA video adapters |
2F | CGA adapter video memory test |
30 | Test of CGA adapter scan generation circuits |
31 | Error in video memory or scanning circuits. Finding an alternative CGA video adapter |
32 | Test of video memory of an alternative CGA video adapter and scan circuits |
33 | Poll the status of the Mono/Color jumper |
34 | Setting text mode 80x25 |
37 | Video mode is set. Screen cleared |
38 | Initialization of on-board devices |
39 | Displaying error messages from the previous step |
3A | Display "Hit DEL" message to enter CMOS Setup |
3B | Start preparing for a memory test in protected mode |
40 | Preparing GDT and IDT descriptor tables |
42 | Switching to protected mode |
43 | The processor is in protected mode. Interrupts enabled |
44 | Preparing to test the A20 line |
45 | A20 line test |
46 | RAM size determination completed |
47 | Test data recorded in Conventional Memory |
48 | Rechecking Conventional Memory |
49 | Extended Memory Test |
4B | Memory reset |
4C | Indication of the zeroing process |
4D | Recording in CMOS the resulting sizes Conventional and Extended memory 4E Indication of the actual amount of system memory |
4F | Extended Conventional Memory test running |
50 | Conventional Memory size correction |
51 | Extended Memory test |
52 | Conventional Memory and Extended Memory volumes saved |
53 | Delayed parity error handling |
54 | Disable parity and non-maskable interrupt processing |
57 | Initializing the memory region for POST Memory Manager |
58 | You are prompted to enter CMOS Setup |
59 | Returning the processor to real mode |
60 | Checking page DMA registers |
62 | Test of address registers and forwarding length of DMA#1 controller |
63 | Test of address registers and forwarding length of DMA#2 controller |
65 | Programming DMA controllers |
66 | Clearing the Write Request and Mask Set POST registers |
67 | Programming Interrupt Controllers |
7F | Resolving NMI request from additional sources |
80 | Sets the interrupt servicing mode from the PS/2 port |
81 | Keyboard interface test for reset errors |
82 | Setting the keyboard controller operating mode |
83 | Checking Keylock Status |
84 | Memory capacity verification |
85 | Displaying Error Messages |
86 | Configuring the system for Setup operation |
87 | Unboxing CMOS programs Setup in Conventional Memory. |
88 | Setup program completed by user |
89 | Completed state recovery after Setup operation |
8B | Reserving memory for an additional BIOS variable block |
8C | Programming Configuration Registers |
8D | Primary initialization of HDD and FDD controllers |
8F | Reinitializing the FDD Controller |
91 | Configuring the HDD Controller |
95 | Performing a ROM Scan to look for additional BIOSes |
96 | Additional configuration of system resources |
97 | Verifying the signature and checksum of the optional BIOS |
98 | Setting up System Management RAM |
99 | Setting the timer counter and parallel port variables 9A Generating a list of serial ports |
9B | Preparing an area in memory for a coprocessor test |
9C | Initializing the coprocessor |
9D | Coprocessor information is stored in CMOS RAM |
9E | Keyboard Type Identification |
9F | Search for additional input devices |
A0 | Formation of MTRR registers (Memory Type Range Registers) |
A2 | Error messages from previous initialization steps |
A3 | Setting the keyboard auto-repeat timing |
A4 | Defragmenting unused RAM regions |
A5 | Setting the video mode |
A6 | Cleaning the screen |
A7 | Transferring BIOS executable code to Shadow RAM area |
A8 | Initializing additional BIOS in segment E000h |
A9 | Returning control to the system BIOS AA Initializing the USB bus |
AB | Preparing the INT13 module to serve disk services |
A.C. | Building AIOPIC tables to support multiprocessor AD systems Preparing the INT10 module to serve video services |
A.E. | DMI Initialization |
B0 | System Configuration Table Output B1 ACPI BIOS Initialization |
00 | Software interrupt INT19h – Boot Sector loading |
Features of the Device Initialization Manager
In addition to the above POST codes, messages about events during the execution of Device Initialization Manager (DIM) are output to the diagnostic port. There are several control points that indicate the initialization status of system or local buses.
The information is displayed in word format, the low byte of which coincides with the system POST code, and the high byte indicates the type of initialization procedure being performed. The most significant tetrad in the high byte indicates the type of procedure being executed, and the low tetrad determines the bus topology for its application.
Senior tetrad
Junior tetrad
If a system memory configuration error is detected, the DE code, DF code, and configuration error code are output to port 80h sequentially in an endless loop, which can take the following values:
2. Award BIOS V4.51PG Elite
AwardBIOS V4.51PG Elite
The dynamically developing company Award Software in 1995 proposed a new solution in the field of low-level software- AwardBIOS "Elite", better known as V4.50PG. The control point maintenance mode has not changed either in the widespread version V4.51 or in the rare version V4.60. The suffixes P and G denote support for the PnP mechanism and support for energy saving functions (Green Function), respectively.
Performing a POST in Shadow RAM
Error code | Description of the error |
---|---|
03 | Disable NMI, PIE (Periodic Interrupt Enable), AIE (Alarm Interrupt Enable), UIE (Update Interrupt Enable). Prohibition of generation of programmable frequency SQWV |
04 | Checking the generation of requests for DRAM regeneration |
05 | |
06 | Test the memory area starting at address F000h, where BIOS 07 is located Checking the functioning of CMOS and battery power |
BE | Programming the configuration registers of the South and North Bridges |
09 | Initializing the L2 Cache and Advanced Cache Control Registers on the Cyrix Processor |
0A | Generation of interrupt vector table. Configuring Power Management Resources and Setting the SMI Vector |
0B | Checking the CMOS checksum. Scanning PCI bus devices. Processor microcode update |
0C | Initializing the Keyboard Controller |
0D | Finding and initializing the video adapter. Setting up IOAPIC. Clock measurements, FSB setting |
0E | MPC initialization. Video memory test. Displaying the Award Logo |
0F | Checking the first DMA 8237 controller. Keyboard detection and internal test. BIOS checksum verification |
10 | Checking the second DMA 8237 controller |
11 | Checking DMA controller page registers |
14 | Test of system timer channel 2 15 Test of the request masking register of the 1st interrupt controller |
16 | Test of the request masking register of the 2nd interrupt controller 19 Checking the passivity of the NMI non-maskable interrupt request |
30 | Determination of the volume of Base Memory and Extended Memory. APIC setup. Software control Write Allocation mode |
Error code | Description of the error |
---|---|
31 | Basic on-screen test random access memory. USB initialization |
32 | The Plug and Play BIOS Extension splash screen appears. Setting up Super I/O resources. Programmable Onboard Audio Device |
39 | Programming the clock generator via the I2C bus |
3C | Setting the software flag to allow entry into Setup |
3D | Initializing PS/2 mouse |
3E | Initializing the External Cache controller and enabling Cache BF Setting up the chipset configuration registers |
41 | Initializing the floppy disk subsystem |
42 | Disable IRQ12 if PS/2 mouse is missing. The hard drive controller is being soft reset. Scanning other IDE devices |
43 | |
45 | Initializing the FPU coprocessor |
4E | Error message display |
4F | Password Request |
50 | Restoring a previously stored CMOS state in RAM |
51 | Resolution of 32 bit access to HDD. Configuring ISA/PnP Resources |
52 | Initializing additional BIOS. Setting the values of PIIX configuration registers. Formation of NMI and SMI |
53 | |
60 | Installing BOOT Sector antivirus protection |
61 | Final steps to initialize the chip set |
62 | Reading keyboard ID. Setting its parameters |
63 | Correction of ESCD, DMI blocks. Clearing RAM |
FF | Transferring control to the bootloader. BIOS executes INT 19h command |
3. Award BIOS V6.0 Medallion
AwardBIOS V6.0 Medallion
The first mention of Award Medallion BIOS, Version 6.0 dates back to May 12, 1999. The structure of the new product remains unchanged, retaining the early (Early), late (Late) and final (System) phases of hardware initialization. Significant changes affected the POST execution algorithms, which was reflected in the new encoding of checkpoints, significantly expanding their scope of application. However, in the new BIOS there was no place for outdated technologies such as EISA, and for this reason a number of POST codes were abolished.
Executing startup POST procedures from ROM
At the early initialization stage program code BIOS is executed from the Boot Block in Flash ROM, and is accompanied by the output of control points 91h...FFh to the diagnostic port
Error code | Description of the error |
---|---|
91 | Selecting a startup script for the CF platform Determining the processor type |
C0 | External Cache prohibition. Internal Cache prohibition. Shadow RAM ban. Programming the DMA controller, interrupt controller, timer, RTC C1 block Determining the memory type, total volume and placement on 0C lines Checking checksums |
C3 | Checking the first 256K DRAM for the Temporary Area organization. Unpacking BIOS in Temporary Area |
C5 | If the checksums match, the POST code being executed is transferred to Shadow. Otherwise, control is transferred to the BIOS recovery procedure |
B0 | Initializing North Bridge |
A0-AF | Hardware-dependent system logic initialization procedure E0-EF Error during system logic initialization process |
BIOS recovery
Performing a POST in Shadow RAM
Late initialization is performed in RAM and continues until the user menu is called - CMOS Setup. This POST phase is characterized by the use of memory segment E000h, in which the passage of checkpoints from 01h to 7Fh is processed.
Error code | Description of the error |
---|---|
01 | Unpacking XGROUP at physical address 1000:0000h |
03 | Early |
05 | Installation initial values variables that specify image attributes. Checking the CMOS Status Flag |
07 | Checking and initializing the keyboard controller |
08 | Determining the interface type of the connected keyboard |
0A | The procedure for autodetection of keyboard and mouse. Final settings of the keyboard controller using PCI space registers |
0E | Testing memory segment F000h |
10 | Determining the type of FlashROM installed |
12 | CMOS test |
14 | Chipset register initialization procedure |
16 | Primary initialization of the on-board frequency synthesizer |
18 | Definitions installed processor and the volume of its Cache L1 and L2 1B Generation of the interrupt vector table |
1C | |
1D | Initial setup of the Power Management system |
1F | Loading the keyboard matrix from the XGROUP external module |
21 | Initializing the Hardware Power Management subsystem |
23 | Coprocessor testing. Determining the FDD drive type. Preparatory stage for creating a resource map of PnP devices |
24 | Processor microcode update procedure. Resource distribution map update |
25 | Initialization and scanning of the PCI bus |
26 | Configuring the logic that serves the VID (Voltage Identification Device) lines. Initialization on-board system voltage and temperature monitoring |
27 | Reinitializing the Keyboard Controller |
29 | Initialization of the APIC included in the central processor. Measuring the frequency at which the processor operates. Setting up system logic registers. Initializing the IDE Controller |
2A | |
2B | Search VGA BIOS |
2D | Displaying processor information |
33 | Performing a Reset on a connected keyboard |
35 | Checking the first channel of the 8237 DMA controller |
37 | Checking the second channel of the DMA 8237 controller |
39 | Testing DMA page registers |
3C | Setting up the Programmable Interval Timer (8254) controller |
3E | Initializing the 8259 Master Controller |
40 | Initialization of Slave controller 8259 |
43 | Preparing the interrupt controller for operation. Interrupts are disabled, they are enabled later, after a memory test |
45 | Checking the Passivity of a Non-Maskable Interrupt (NMI) Request |
47 | Performing ISA/EISA tests |
49 | Determining the amount of basic and extended memory. Software control of Writes Allocation mode by adjusting AMD K5 registers |
4E | Testing memory within the first megabyte and visualizing the results on the display screen. Initializing caching schemes for single and multiprocessor systems, setting up Cyrix M1 processor registers |
50 | USB initialization |
52 | Testing of all available system memory, including the region for the built-in video controller (Shared Memory). Visualization of results on the display screen |
53 | Resetting your login password |
55 | Visualization of the number of detected processors |
57 | Initial initialization of ISA PnP devices, each of which is assigned a CSN (Card Select Number). Rendering of the EPA logo |
59 | Initializing the anti-virus support system |
5B | Starting the BIOS update procedure from the drive to floppy disks 5D Initialization of on-board SIO and Audio controllers |
60 | Access to CMOS Setup is open |
63 | Initializing PS/2 Mouse |
65 | Initializing USB Mouse |
67 | Use of IRQ12 by PCI devices if there is no PS/2 Mouse in the system 69 Full initialization of the L2 cache controller |
6B | Chipset initialization according to CMOS Setup |
6D | Configuring Resources for ISA PnP Devices in SIO 6F Configuration Mode Initializing the Floppy Disk Subsystem |
73 | Preliminary steps to initialize the hard drive subsystem. On some platforms - poll ALT+F2 to launch AwardFlash |
75 | Finding and initializing IDE devices |
77 | Initializing serial and parallel ports |
7A | Software reset of the coprocessor, writing the control word to the FPU register CW 7C Installing protection against unauthorized writing to hard drives |
7F | Display error messages. Maintaining the DEL and F1 keys |
Preparing tables, arrays and structures for starting the operating system
Starting with code 82h, POST configures the system according to the CMOS settings. Its final phase is executed from the Shadow RAM area (segment E800h) and ends with the transfer of control to the operating system - code FFh.
Error code | Description of the error |
---|---|
82 | Allocates an area in system memory for power management |
83 | Recovering data from a temporary storage stack in CMOS |
84 | Displaying the message “Initializing Plug and Play Cards...” |
85 | USB initialization complete |
86 | Reserved, Carry Flag clearing |
87 | Building SYSID tables in the DMI area |
88 | Reserved, Carry Flag clearing |
89 | Generating ACPI Service Tables |
8A | Reserved, Carry Flag clearing |
8B | Finding and initializing the BIOS of additional devices |
8C | Reserved, Carry Flag clearing |
8D | Initializing parity bit maintenance routines |
8E | Reserved, Carry Flag clearing |
8F | IRQ12 resolution for mouse hot plugging 90 Reserved, clear Carry Flag |
91 | Initializing Legacy platform resources |
92 | Reserved, Carry Flag clearing |
93 | Presumably not used |
94 | Final steps to initialize the main set of logic before loading the operating system. The power management system completes initialization. The BIOS startup screen is removed and the resource allocation table is displayed. AMD K6® family processors have specific settings. Microcode update for family processors Intel Pentium® II and higher |
95 | Setting the automatic transition to winter/summer time. Programming the keyboard controller for the auto-repeat frequency |
96 | In multiprocessor systems, final system settings are performed and service tables and fields are created. For Cyrix family processors, additional register settings are performed. Building the ESCD "Extended System Configuration Data" table. Setting the DOS Time counter in accordance with Real Time Clock. Boot device partitions are saved for further use by built-in antivirus tools: Trend AntiVirus or Paragon Anti-Virus Protection. The system speaker emits a POST completion signal. The MSIRQ table is built and saved |
A number of processes occurring in the Award Medallion BIOS are designated by special groups of control points. These include:
System Event codes - control points system events.
Power Management Debug codes are checkpoints that occur during the execution of APM or ACPI services.
System Error codes - messages about fatal errors.
Debug codes for MP system - initialization points for multiprocessor platforms.
Features of accelerated POST passage
To reduce system boot time, the user in CMOS Setup can select the option " Quick Power On Self Test". In this case, the POST will be accelerated by refusing to perform some procedures (Quick Boot).
The Quick Boot operating pattern replaces the late and final POST phases and does not affect the operation of the boot block. Award Software offers a codification of the executable expedited POST procedures that differs from the standard one. Quick Boot begins with the output of checkpoint 65h to the diagnostic port and ends with POST code 80h. Control is then transferred to the operating system, displaying the usual Award BIOS code FFh.
Error code | Description of the error |
---|---|
65 | Early initialization of the SIO controller, software reset of the video controller. Setting up the keyboard controller, testing the keyboard and mouse. Initializing the sound controller. Checking the integrity of BIOS structures. Unpacking Flash ROM maintenance procedures. Initializing the onboard frequency synthesizer |
66 | Initializes the L1/L2 cache according to the results obtained from the CPUID command. Generation of a vector table consisting of pointers to interrupt handling routines. Initializing Power Management Hardware |
67 | Checking CMOS and battery power plausibility. Configuring chipset registers according to CMOS settings. Initializing the keyboard controller as part of the chipset. Formation of BIOS Data Area Variables |
68 | Initializing the video system |
69 | Configuring i8259 interrupt controller |
6A | An accelerated one-pass RAM test is performed using a special algorithm |
6B | Visualization of the number of detected processors, the EPA logo and a prompt to launch the AwardFlash utility. Configuring embedded I/O controller resources in configuration mode |
70 | Invitations to enter Setup. Initializing PS/2 and USB Mouse |
71 | Initializing the cache controller |
72 | Setting up system logic configuration registers. Formation of the Plug and list Play devices. Initializing the FDD controller |
73 | Initializing the HDD controller |
74 | Initializing the coprocessor |
75 | If specified by the user in CMOS Setup, the IDE HDD is write protected. |
77 | Request for a password and display the message: “Press F1 to continue, DEL to enter Setup” |
78 | Initializing BIOS for additional devices on ISA and PCI buses |
79 | Initializing Legacy platform resources |
7A | Generating the root table RSDT and device tables DSDT, FADT, etc. |
7D | Finding information about boot device partitions |
7E | Configuring BIOS services before booting the operating system |
7F | Setting the NumLock flag according to CMOS SetUp |
80 | Transferring control to the operating system |
Performing a POST in Power Saving Mode
One of the platform states, when the contents of RAM are stored on the hard disk, is called Hibernate. In the ACPI specification ("Advanced Configuration and Power Interface Specification", Revision 2.0a dated 03/31/2002) it is defined as the S4 (Non-Volatile Sleep) power saving mode. Returning to full functioning requires a special way of completing POST.
The ACPI S4 operating scheme, as with the accelerated start, replaces the late and final phases of POST. An essential point is checking the startup script in the boot block. Depending on what ACPI state the system is in after the hardware Reset signal, a decision is made to exit state S4, which begins with the output of test point 90h to the diagnostic port and ends with POST code 9Fh.
Error code | Description of the error |
---|---|
90 | Early initialization of the SIO controller, software reset of the video controller. Setting up the keyboard controller, testing the keyboard and mouse |
91 | CMOS and Battery Validation Check |
92 | Initialization of system logic registers and on-board frequency synthesizer |
93 | Initializing the cache using CPUID information |
94 | Generation of a vector table consisting of pointers to interrupt handling routines. Initializing Power Management Hardware |
95 | PCI bus scanning |
96 | Initializing the embedded keyboard controller |
97 | Initializing the video system |
98 | VGA adapter message output |
99 | Checking the first channel of the DMA8237 controller by writing and test reading the base address and forwarding block length registers 9A Configuring the i8259 interrupt controller |
9B | Initializing PS/2 and USB Mouse. Unpacking ACPI code. Initializing the cache controller |
9C | Setting up system logic configuration registers. Formation of a list of Plug and Play devices. Initialization of FDD and HDD controllers |
9D | The PM region is not reserved in system memory if it is created in Shadow RAM or SMRAM. In some cases, a repeated, final initialization of the USB bus is required, performed when the cache memory L1 |
9E | Setting up Power Management, which is part of the system logic. Initialization of SMI generation circuits and installation of the SMI vector. Programming resources responsible for monitoring PM system events |
9F | The disable and enable operation clears the L1/L2 cache and restores its current size. The power saving mode control settings specified in CMOS Setup are saved in PM RAM. For mobile platforms, a check is made to return to full operation after turning off all supply voltages (Zero Volt Suspend mode) |
4. Phoenix BIOS 4.0 Release 6.0
Phoenix Technologies, Ltd.
One of the leaders in low-level software development, Phoenix Technologies, has released a new version of PhoenixBIOS 4.0 to coincide with the release of Windows95. Support for the Intel Pentium processor family is reflected in the names of the intermediate revisions. One of the latest - Release 6.0 - formed the basis for all released BIOS. With the advent of Release 6.1, there were no significant changes in the execution of POST procedures, and, therefore, this did not affect the indication of checkpoints.
A distinctive feature of PhoenixBIOS is that if during the POST execution errors occur when testing 512 KB of main memory (codes 2Ch, 2Eh, 30h), additional information is output to port 80h in word format, the bits of which identify the failed address line or data cell. For example, the code "2C 0002" means that a memory fault has been detected on address line 1. The code "2E 1020" in this case will mean that a fault has been detected on data lines 12 and 5 in the low byte of the memory data bus. On 386SX systems that use a sixteen-bit data bus, an error cannot occur during code execution step 30h
The POST code output to the diagnostic port is accompanied by an audio signal output to the system speaker. The sound signal generation scheme is as follows:
- The eight-bit code is converted into four two-bit groups
- The value of each group increases by one
- Based on the received value, a short sound signal is generated (for example: code 16h = 00 01 01 10 = 1-2-2-3)
Executing startup POST procedures from ROM
Error code | Description of the error |
---|---|
01 | Initializing the Baseboard Management Controller (BMC) |
02 | Checking the current processor operating mode |
03 | Disabling non-maskable interrupts |
04 | The type of installed processor is determined |
06 | Initial settings of the PIC and DMA registers |
07 | The memory area designated for the BIOS copy is reset to zero |
08 | Early initialization of system logic registers |
09 | Setting the POST software flag |
0A | Initializing processor software resources |
0B | Internal Cache permission |
0E | Initializing Super I/O Resources |
0C | Initialize L1/L2 cache according to CMOS values |
0F | Initializing the IDE |
10 | Initializing the Power Management subsystem |
11 | Setting Alternate Register Values |
12 | The value of the MSW (Machine Status Word) register is being set. |
13 | Early provisioning of PCI devices |
14 | Initializing the Keyboard Controller |
16 | Checking the ROM BIOS checksum |
17 | Determining L1/L2 cache size |
18 | Initializing the 8254 system timer |
1A | Initializing the DMA Controller |
1C | Resetting programmable interrupt controller values |
20 | Checking the generation of DRAM regeneration requests |
22 | Checking the operation of the keyboard controller |
24 | Installing a selector for servicing a flat 4Gb memory model |
26 | A20 line resolution |
28 | Determining the total amount of installed memory |
29 | Initializing POST Memory Manager (PMM) |
2A | Resetting 640Kb of main memory |
2C | Testing address lines |
2E | Failure on one of the data lines in the low byte of the memory data bus |
2F | Selecting a cache memory protocol |
30 | Available system memory test |
32 | Determining CPU clock parameters and bus frequency |
Error code | Description of the error |
---|---|
33 | Initializing Phoenix Dispatch Manager |
34 | Prohibiting Power Off Using ATX Power Button |
35 | Settings of system logic registers that control the formation of timing characteristics of access to memory, input/output ports, system and local buses |
36 | A restart is performed if the transition to the next POST procedure fails. The sequence of procedures is managed by Watch Dog Service |
37 | The process of setting up system logic registers is completed. |
38 | The contents of the BIOS Runtime module are unpacked and rewritten into the area intended for Shadow RAM |
39 | Reinitializing the Cache Controller |
3A | L2 cache resize |
3B | Initializing BIOS Execution Trace |
3C | Additional configuration of logic registers to configure PCI-PCI bridges and support for distributed PCI buses |
3D | The system logic registers are configured in accordance with the CMOS Setup settings |
3E | Read Hardware Configuration |
3E | Checking the ROM Pilot system connection |
40 | Determining CPU clock parameters |
41 | Initializing ROM Pilot - remote boot control |
42 | |
44 | Set BIOS Interrupt |
45 | Initializing devices before enabling the PnP mechanism |
46 | The BIOS checksum is calculated using a special algorithm |
47 | Initializing I2O I/O controllers |
48 | Search for video adapter |
49 | PCI Initialization |
4A | Initializing system video adapters |
4B | Quiet Boot is running - a shortened system startup sequence used to speed up POST. |
4C | VGA BIOS contents are rewritten to the transit area |
4E | Visualization of BIOS text string Copyright |
4F | Reserving memory for the boot device selection menu |
50 | The processor type and its clock frequency are visualized |
51 | Initializing the EISA controller and devices |
52 | Keyboard Controller Programming |
54 | Mode activated soundtrack keys |
55 | |
58 | Finding unserviced interrupt requests |
59 | Initializing the POST Display Service (PDS) procedure 5A Displaying the message “Press F2 to enter SETUP” |
5B | Disable CPU Internal Cache |
5C | Conventional Memory Check |
5E | Detect Base Address |
60 | Extended Memory Check |
62 | Checking Extended Memory Address Lines |
64 | Transferring control to an executable block generated by the motherboard manufacturer (Patch1) |
66 | Configuring cache control registers |
67 | Minimal initialization of APIC controllers |
68 | L1/L2 cache resolution |
69 | Preparing System Management Mode RAM |
6A | External Cache volume is visualized |
6B | Setting CMOS Setup Defaults |
6C | Visualization of Shadow RAM usage information |
6E | Visualization of information about Upper Memory Blocks (UMB) |
70 | Displaying Error Messages |
72 | Checking the current system configuration and CMOS information |
76 | Checking Keyboard Error Information |
7A | Checking the status of software (System Password) or hardware (Key Lock Switch) keyboard locking tools |
7C | Setting hardware interrupt vectors |
7D | Initializing the power tracking system |
7E | Initializing the coprocessor |
80 | On-board SIO I/O controller is prohibited |
81 | Preparing to boot the operating system |
82 | Finding and identifying RS232 ports |
83 | Configuring external IDE controllers |
84 | Finding and identifying parallel ports |
85 | Initializing ISA PnP Devices |
86 | On-board resources of the SIO controller are configured in accordance with the CMOS Setup settings |
87 | Configuring MCD (Motherboard Configurable Devices) |
88 | The values of the variable block in the BIOS Data Area are set |
89 | Allows generation of a non-maskable interrupt |
8A | Setting the values of variables located in the Extended BIOS Data Area |
8B | Checking PS/2 Mouse connection diagrams |
8C | Initializing the drive controller |
8F | Determining the number of connected ATA devices |
90 | Initializing and configuring hard drive controllers |
91 | Setting temporary parameters for hard drive operation in PIO mode |
92 | Transferring control to an executable block generated by the motherboard manufacturer (Patch2) |
93 | Building a multiprocessor system configuration table |
95 | Selecting CD-ROM Maintenance Procedure |
96 | Return to Real Mode |
97 | Building MP Configuration Table |
98 | ROM Scan in progress |
99 | Checking the status of the SMART parameter 9A The contents of the ROM are written to RAM |
9C | Setting up the Power Management subsystem |
9D | Initializing resources to protect against unauthorized access |
9E | Hardware interrupts are enabled |
9F | The number of IDE and SCSI drives is determined |
A0 | Setting DOS Time based on RTC state A1 The purpose of this code is unknown A2 Checking the Key Lock state |
A4 | Keyboard Auto-Repeat Characteristics Settings |
A8 | The "Press F2 to enter Setup" message is removed from the screen |
A.A. | Checked availability of SCAN F2 key code in input buffer AC Setup program starts |
A.E. | The restart flag executed by CTRL+ALT+DEL B0 is cleared. The message "Press F1 to resume, F2 to Setup" is generated. |
B1 | POST progress flag is cleared B2 POST completed |
B4 | Sound signal before booting |
B5 | Quiet Boot phase completed |
B6 | Password check if this mode included in Setup B7 ACPI BIOS Initialization |
B9 | Searching for boot devices on the USB bus BA Initializing DMI parameters |
BB | Repeating the ROM Scan procedure |
B.C. | The RAM parity error latching trigger is reset. |
BD | A menu is displayed for selecting a boot device BE Clearing the screen before loading the operating system BF Activating anti-virus support |
C0 | The software interrupt processing procedure INT 19h is launched - the Boot Sector loader. The interrupt service routine sequentially attempts to load the Boot Sector by polling disk devices in the order prescribed by Setup |
C1 | Initialization of fault maintenance routine (PEM) C2 Calling service routines for error logging |
C3 | Visualization of error messages in the order they were received C4 Setting initial state flags |
C5 | Initializing an extended block of CMOS RAM cells |
C6 | Initial initialization of the docking station |
C7 | Lazy dock initialization |
C8 | Execution of test procedures included in the Boot Block to determine the integrity of BIOS structures |
C9 | Checking the integrity of structures and/or modules external to the system BIOS |
C.A. | Running Console Redirect to serve a remote CB keyboard Emulate disk devices in RAM/ROM |
CC | Run Console Redirect to serve video CDs Support PCMCIA communications |
C.E. | Setting up the Light Pen Controller |
Fatal Error Messages
D0 Error caused by an exceptional situation (Exception error) D2 Calling an interrupt handling procedure from an unidentified source D4 Error associated with a violation of the protocol for issuing and clearing interrupt requests D6 Exiting protected mode with software reset generation D7 To save the state of the video adapter, more is required amount of memory than is available in SMRAM D8 Error during software generation of the processor reset pulse DA Loss of control when returning to Real Mode DC Exit from protected mode with software reset generation without re-initializing the interrupt controller DD Error when testing extended memory DE Keyboard controller error DF Line control error A20 19
Executing Procedures from Boot Block
Error code | Description of the error |
---|---|
E0 | Setting up E1 chipset configuration registers Initializing the North and South bridges |
E2 | Initializing the CPU |
E3 | Initializing the system timer |
E4 | Initializing Super I/O Resources |
E5 | Checking the status of Recovery Jumper, the installation of which forces the BIOS Recovery mode to start |
E6 | BIOS checksum verification |
E7 | Control is transferred to the BIOS if its checksum is calculated correctly E8 Initialize MPS support |
E9 | Transition to a flat 4Gb memory model |
E.A. | Initialization of non-standard equipment |
E.B. | Configuring the interrupt controller and direct memory access |
E.C. | By writing and control readings using a special algorithm, the memory type is determined: FPM, EDO, SDRAM, and the Host Bridge configuration registers are configured in accordance with the result |
ED | By means of records and control readings using a special algorithm, the volume of memory banks and placement in rows are determined. In accordance with the result, the Host Bridge configuration registers (DRAM Row Boundary) are configured |
E.E. | The contents of the Boot Block are copied to Shadow RAM EF Preparing SMM RAM for the SMI handler |
F0 | Memory test |
F1 | Initializing interrupt vectors |
F2 | Initializing Real Time Clock |
F3 | Initializing the video subsystem |
F4 | Generating a beep before booting |
F5 | Loading the operating system stored in Flash ROM |
F6 | Return to Real Mode |
F7 | Boot to Full DOS |
F8 | Initializing the USB controller |
FA…FF | Codes for interaction with the PhDebug procedure |
5. Insyde BIOS Mobile Pro
Insyde Software Corp.
Market Insider mobile systems has firmly established itself where loyalty to tradition and a conservative approach to building a BIOS are required. Having inherited the source code from SystemSoft, the company is constantly working to improve it. The latest revision of MobilePRO is actively used in Mitac and Clevo laptops, the documentation for which formed the basis of the Error Codes table - this is what Insyde Software calls POST checkpoints.
Boot block checkpoints
Despite the fact that Insyde Software created its first BIOS in 1992, the established model of the boot block - or Boot Loader, as the creators themselves called it - was finally formed only by the end of 1995. From this moment on, the starting procedure was numbered by version and creation date.
The most significant point from the point of view of a service engineer examining the process of booting a computer system with InsydeBIOS is the diagnostic code display device. Although, as a rule, Boot Loader uses Manufacture's Diagnostic Port 80h, standard in such cases, in some cases, test point output is performed only on the PIO Port (Parallel Input/Output port for diagnostic purpose), which is nothing more than a parallel port 378h There are implementations in which diagnostic codes sent to port 80h are duplicated to the parallel port.
Error code | Description of the error |
---|---|
00 | Starting point for boot block execution 01 Inhibit line A20 (not used) |
02 | CPU microcode update |
03 | Testing RAM |
04 | Transferring the boot block to RAM |
05 | Executing a boot block from RAM |
06 | Forcing the Flash ROM recovery procedure |
07 | Transferring the system BIOS to RAM |
08 | System BIOS checksum verification |
09 | Running the POST procedure |
0A | Starting the Flash ROM recovery procedure from an FDD drive |
0B | Initializing the frequency synthesizer |
0C | Completing the BIOS recovery procedure |
0D | Alternative procedure for recovering Flash ROM from FDD |
0F | Stopping if a fatal error occurs |
BB | LPC SIO early initialization |
CC | Starting point for starting Flash ROM recovery |
88 | Enabling ACPI Features |
99 | Error when exiting STR mode |
60 | Switching to Big Real Mode |
61 | Initialization of SM Bus. SPD data is stored in CMOS A0 Read and parse SPD fields previously stored in CMOS A1 Memory controller initialization |
A2 | Defining logical banks of a DIMM |
A3 | Programming DRB registers (DRAM Row Boundary) |
A4 | Programming DRA Registers (DRAM Row Attributes) |
A.E. | DIMMs have been detected in the system that differ in their Error Correcting Codes (ECC) functions. |
A.F. | Primary initialization of memory controller registers mapped to memory space |
E1 | The boot procedure fails if the DIMM is not equipped with an SPD chip |
E2 | DIMM type does not match system requirements |
E.A. | The minimum time between activating DIMM strings and entering the regeneration state does not meet system requirements |
E.C. | Register modules are not supported ED Checking CAS Latency modes |
E.E. | DIMM organization not supported by motherboard |
Executing POSTs from RAM
The most modern solutions InsydeBIOS use 16-bit checkpoint mapping. This is done using ports 80h and 81h, the latter of which is intended to extend standard diagnostics.
The study of control points is made difficult by their irregular construction, when processes of different meaning are accompanied by the same codes. In dual diagnostic systems, there are differences of a different order: some POST codes are displayed only in one of the ports without the usual duplication in such cases.
Error code | Description of the error |
---|---|
10 | Cache initialization, CMOS check |
11 | Line A20 banned. Setting registers for 8259 controllers. |
12 | Determining the boot method |
13 | Initializing the Memory Controller |
14 | Searching for a video adapter connected to the ISA bus |
15 | Setting System Timer Values |
16 | Setting system logic registers using CMOS |
17 | Calculating the total amount of RAM |
18 | Testing the low page of Conventional Memory |
19 | Verifying the checksum of the Flash ROM image |
1A | Resetting the Interrupt Controller Registers |
1B | Initializing the video adapter |
1C | Initializing a subset of video adapter registers compatible with the 6845 software model |
1D | Initializing the EGA adapter |
1E | Initializing the CGA adapter |
1F | DMA controller page register test |
20 | Checking the keyboard controller |
21 | Initializing the Keyboard Controller |
22 | Comparison of the resulting amount of RAM with the value in CMOS |
23 | Checking battery backup and Extended CMOS |
24 | Testing DMA Controller Registers |
25 | Setting DMA controller parameters |
26 | Formation of the interrupt vector table |
27 | Accelerated determination of the amount of installed memory |
28 | Protected Mode |
29 | System memory test completed |
2A | Exiting Protected Mode |
2B | Transferring the Setup procedure to RAM |
2C | Starting the video initialization procedure |
2D | Re-search for CGA adapter |
2E | Re-search for EGA/VGA adapter |
2F | Displaying VGA BIOS messages |
30 | Custom Keyboard Controller Initialization Routine |
31 | Checking the connected keyboard |
32 | Checking the passage of a request from the keyboard |
33 | Checking the Keyboard Status Register |
34 | Test and reset system memory |
35 | Protected Mode |
36 | Extended memory test completed |
37 | Exiting Protected Mode |
38 | A20 line ban |
39 | Initializing Cache Controller 3A Checking the System Timer |
3B | Setting the DOS Time counter according to Real Time Clock |
3C | Initializing the hardware interrupt table |
3D | Finding and initializing manipulators and pointers |
3E | Setting the status of the NumLock key |
3F | Initializing serial and parallel ports |
40 | Configuring Serial and Parallel Ports |
41 | Initializing the FDD controller |
42 | Initializing the HDD controller |
43 | Initializing Power Management for the USB Bus |
44 | Finding and initializing additional BIOS |
45 | Resetting the NumLock key status |
46 | Checking coprocessor functionality |
47 | Initializing PCMCIA |
48 | Preparing to start the operating system |
49 | Transferring control to executable Bootstrap code |
50 | ACPI initialization |
51 | Initializing Power Management |
52 | Initializing the USB Bus Controller |
Hearing a BIOS signal (1 long beep), the user usually becomes wary. After all, as you know, in most BIOSes the message about the successful completion of hardware testing sounds somewhat different, although it is similar - one signal, but a short one. Is there any cause for concern in this case? Practice shows that in most cases - Yes.
First of all, it is worth defining the concept of “long signal”. In many cases, one continuous sound can be considered long. If you hear a similar sound and you have an Award BIOS installed, then this means that the power supply is faulty. When Phoenix BIOS In such a situation, there is a malfunction of the CPU cooler fan. In the Compaq BIOS, this type of sound indicates a problem with the RAM.
However, most often the user may encounter a slightly different situation, when there is only a long but time-limited signal. This type of signal is used by many BIOS manufacturers to encode error messages.
However, one long BIOS beep is a sound that is often used for more than just signaling errors. For example, you can find BIOS version famous manufacturer American Megatrends, in which the BIOS signal 1 long beep is used to notify about the normal completion of tests instead of the usually used short beep. A similar approach is also used in the Mylex 386 BIOS. This factor should also be kept in mind, especially if you are dealing with specific computer for the first time.
In AST BIOS, one long squeak has a completely different meaning, namely, an error detected when testing the first channel of the DMA controller. Typically, this situation means the microcontroller is faulty, which may result in the need to replace the entire motherboard.
In IBM BIOS, a similar BIOS signal, one long beep, also has its own meaning - this is a malfunction of the video system. You can try to fix this problematic situation yourself by checking that the video card is securely installed in the motherboard expansion slot.
A fairly common situation is the problem when, when turning on the computer, the user hears one long and two short BIOS beeps from the system speaker. In this case, the operating system does not load at all, and the user sees a black screen in front of him (sometimes messages indicating a problem may appear, but, as a rule, they are absent). Read on to learn how to interpret this sequence of signals and what to do to correct the situation.
One long, two short BIOS beeps: what does this mean?
Let's start with theoretical information. When you turn on your desktop computer or laptop, all hardware is checked. The primary one is responsible for this. BIOS system(or its modernized version UEFI). For each such system, the use of strictly certain sequences signals that may indicate either that the test was completed successfully, or that problems were found in the operation or initialization of the equipment. In general, to figure out what the problem is, you need to contact technical documentation primary system or at least read what different sequences and combinations mean.
In general, if the user hears one long and two short beeps from the BIOS of ASUS or any other developer of the primary system, we can immediately conclude that something is wrong with the installed hardware. Unfortunately, the system does not provide notifications about faulty components.
The only situation is a message about the absence of a connected keyboard. But this mostly applies exclusively to stationary terminals, since on laptops such a message can only appear if the built-in keyboard has become unusable. Connect any other external keyboard, for example, via USB and check how the system boots.
One long, two short BIOS beeps: what to do first?
The issuance of such a sequence of signals may not always be associated specifically with physical damage installed equipment. It is quite possible that somewhere on the motherboard the contacts have simply come loose or become clogged. All components may be in perfect order, but dust or contamination of the inside of the computer can lead to the fact that some elements of the filling are simply not detected.
In the simplest case, if you receive one long and two short signals from the BIOS, you should immediately turn off the computer and completely disconnect it from the power supply. After this, you need to pause so that the residual currents disappear (ten minutes will be enough), then remove the side cover of the desktop PC case from the side accessing the motherboard and perform a basic dust removal. A regular vacuum cleaner with the minimum suction power set is suitable for this. When cleaning, you need to be very careful not to damage the components installed on the motherboard and the motherboard itself, otherwise the entire computer system will stop working. And replacing a motherboard is clearly not a cheap pleasure.
Problems with the graphics chip
Basically, most situations when the user hears one long and two short BIOS beeps are usually attributed to problems with the graphics adapter, since it is the adapter that is responsible for displaying the image on the screen, and if it malfunctions, problems arise with the inability to start the operating system.
In different BIOS versions (and from different developers), this sequence of signals may indicate different failures. For example, IBM BIOS issues such signals only if the computer is equipped with Mono/CGA video cards. But since such chips are practically not found today, such situations are very rare.
In the case of AST BIOS, such a sequence is issued only if problems are observed with frame scanning.
Compaq BIOS gives one long and two short beeps if initialization of the graphics adapter is not possible at all. The same situation is observed with the primary systems Award and Quadtel.
The only way to fix the problem is physically. To do this, you need to remove the video card from the corresponding slot on the motherboard and first check its functionality on another computer. If it works as expected, the slot itself may need to be cleaned. You can also try inserting it into a different connector. If the card does not work, it will have to be replaced.
Possible problems with RAM
But problems are not always related specifically to graphics adapters. For example, AMI BIOS generates one long and two short signals if problems with RAM are detected (for a video card, a sequence of pulses in combination 1-3 is used).
In this case, the memory sticks should be removed one at a time when the power is turned off, turning on the computer after each removal and checking the functionality of the system. When the damaged strip is found and the system boots in normal mode, you will simply have to replace it by installing similar equipment in its place. In this case, you should take into account which generation the RAM belongs to, and also pay attention to the characteristics of the motherboard itself in terms of ensuring that it supports the installed brackets both according to the standard and the maximum volume. Otherwise, you will not be able to use the maximum capacity, since the one determined by the motherboard may be much less.
What to do if the problem persists?
But let’s assume that it was not possible to get rid of the malfunctions using such simple methods. Let's take a situation where a Samsung laptop produces a similar combination. One long and two short BIOS signals are enough to determine problems with the hardware, but disassembling the device yourself is not always advisable.
In some cases, you can do much simpler, since the problem may be incorrect settings of the primary system. To get started, use reset parameters from the appropriate section, save the changes and check how the loading will proceed. If such actions do not give results, it may very well be that updating the BIOS will help. True, such actions must be performed competently, so as not to render the primary input/output system itself unusable.
A similar solution can be applied to stationary computer terminals. But this situation can mainly be associated with replacing hardware or installing new components, when an outdated version of the BIOS is unable to recognize modern devices. In this case, updating the firmware is the best option to fix the problem.
Instead of an afterword
It remains to add that the situation when a sequence in the form of one long and two short BIOS signals is output through the system speaker can, in principle, be corrected. Because the the real reason such behavior of the system is not explicitly indicated, you will have to perform the described actions exactly in the order in which they were given in the above material. It is advisable not to use reset and update immediately, but leave them as a last resort if the methods physical intervention will be powerless. However, first, clean up stationary unit from dust. This is the first remedy. With laptops the situation is more complicated, especially if the device is under warranty. If none of the above suggestions help, you will have to contact an authorized service center. And avoid contacting private sellers who do not have relevant repair experience. computer equipment. Then many more problems may appear.
Every time the computer boots, the system unit makes a beeping noise. Not everyone knows that this is a signal indicating the performance of the system unit. And only a few know how to decipher these signals from the system unit.
That's what we'll talk about. If you are reading this material, I recommend printing it out now. When you need decryption, you won’t be able to get online. :)
So what is the “system specialist” squeaking about? These signals are the result of testing the computer hardware (cooler, RAM, video card, etc.). Every time you boot your computer, it tests the hardware and reports the results with this particular squeak. The transcript of the system unit squeaks is below.
* One short squeak.
Explanation:
Everything is fine. The test was completed successfully. You can continue to work. It happens that some system units do not beep at all at this moment.
* There is not a squeak or image on the computer screen.
Explanation:
Malfunction in the power supply or processor.
Correction:
First, check to see if the power cord is plugged into the outlet. If everything is in order, try connecting a known working device to the surge protector (such a cord with a box in which there are many sockets, there is also a switch button, usually red). A phone charger will do, of course, with a phone connected to it. You need to check all the surge protector sockets. If the socket is working, the phone will charge. Next, we check whether the power supply starts when you press the computer start button. In this case, the cooler (fan) of the power supply should at least twitch. If there is movement, look for a new processor, otherwise, a new power supply. You also need to check the power cable of the motherboard. It may happen that he moved away.
* One long continuous squeak.
Explanation:
The power supply is faulty.
Correction:
Purchasing a new power supply.
* Two short squeaks.
Explanation:
Minor problems with BIOS settings.
Correction:
Go to BIOS and install optimal parameters. Exiting to the BIOS is usually done using the key. If you don't know what to change, then set the default values. To do this, press the button. To exit with saving - , . Some BIOS versions themselves highlight conflicting settings items by highlighting them. You can also reset the BIOS settings by removing the motherboard battery for a few seconds.
* Three long squeaks.
Explanation:
The keyboard is missing.
Correction:
Plug the keyboard into the PS/2 socket. If this does not help, you will have to change the keyboard.
* Three short squeaks.
Explanation:
RAM error.
Correction:
To do this, you need to check whether there are memory sticks on the motherboard. Don't laugh, it happens. Then you need to remove all the memory sticks, carefully sweep away the accumulated dust, and one by one stick the memory stick in and start the system unit. If the “system unit” beeps on some strip, this may mean that the strip is faulty.
* One long and one short squeak.
Explanation:
RAM is not working properly.
Correction:
Perhaps one or more memory sticks are conflicting with each other. You need to insert one memory stick at a time and try to start the computer.
* One long and two short squeaks.
Explanation:
The video adapter is not working properly.
Correction:
Correct settings in BIOS.
* One long and three short squeaks.
Explanation:
The video adapter does not work.
Correction:
Check the performance of the video card. To do this, you need another, known working video card. You can also try removing the card, removing dust from the slot, and sticking the card back in place. And don’t forget to check if the card has additional plugs for power. Power to such video cards must be supplied with a separate cord to which no device is connected. I also suggest checking whether the monitor is connected and working. Try to blow out the connector connecting the monitor to the computer.
* One long and eight short squeaks.
Explanation:
The video adapter is not working or the monitor is not connected.
Correction:
Same as written above.
* One long and nine short squeaks.
Explanation:
Error reading BIOS data.
Correction:
Try resetting the BIOS settings by removing the battery. If this does not help, then flash the BIOS. But this is another story, requiring a separate article. I'll try to write it soon.
* Four short squeaks.
Explanation:
The system timer does not work.
Correction:
You can try resetting the BIOS. But, unfortunately, it rarely helps. There is only one way out - replace or repair the motherboard.
* Five short squeaks.
Explanation:
The processor is not working properly.
Correction:
Try to clean the dust from the processor slot, make sure the heatsink is clean and the processor temperature is low.
* Six short squeaks.
Explanation:
The keyboard is faulty.
* Seven short squeaks.
Explanation:
Motherboard malfunctions.
Correction:
Have the motherboard repaired or purchase a new one.
* Eight short squeaks.
Explanation:
Problems with video memory.
Correction:
Take the video adapter for repair, or purchase a new one.
* Nine short squeaks.
Explanation:
Incorrect BIOS checksum.
Correction:
Usually it is suggested to reset the BIOS settings and allows you to continue working. If something happens, you can reset the BIOS by removing the battery.
* Ten short squeaks.
Explanation:
Error writing data to CMOS chip.
Correction:
This error may occur when flashing the BIOS. Therefore, we will describe this part in another article.
* Eleven short squeaks.
Explanation:
The cache memory is not working properly.
Correction:
Reset BIOS. If this does not help, we take the computer in for repair or install a new processor.
* Repeated long squeaks.
Explanation:
The RAM is faulty or incorrectly connected.
Correction:
Reconnecting memory sticks. Calculating the faulty one by connecting one by one and starting the computer. Cleaning from dust.
* Repeated short squeaks.
Explanation:
The power supply is not working properly.
Correction:
Checking the functionality of the power supply, checking the cords for breaks, checking the surge protector, and, last but not least, replacing the power supply.
That's all. If you have any questions, ask.
PS: To reset the BIOS, instead of removing the battery, you can use a special jumper. Its location can be found in the documentation for the motherboard.
Addition: BIOS signal encodings if the computer died.
AWARD BIOS Signals
Continuous signal. The power supply is faulty.
2 short. Minor errors found.
3 long. Keyboard controller error.
1 long + 1 short. Problems with RAM.
1 long + 2 short. Problem with the video card.
1 long + 3 short. An error occurred while initializing the keyboard.
1 long + 9 short. An error occurred while reading data from the microcircuit permanent memory.
1 long repeating. Memory modules are installed incorrectly.
1 short repeating. Problems with the power supply.
AMI BIOS signals
There are no signals. The power supply is faulty or not connected to the motherboard.
1 short. No errors found.
2 short. RAM parity error.
3 short. An error occurred during the operation of the first 64 KB of main memory.
4 short. The system timer is faulty.
5 short. The central processor is faulty.
6 short. The keyboard controller is faulty.
7 short. The motherboard is faulty.
8 short. The video memory is faulty.
9 short. BIOS chip contents checksum error.
10 short. Cannot write to CMOS memory.
11 short. The external cache memory (installed in the slots on the motherboard) is faulty.
1 long + 2 short. The video card is faulty.
1 long + 3 short. The video card is faulty.
1 long + 8 short. Problems with the video card or the monitor is not connected.
PHOENIX BIOS signals
1-1-3. CMOS data write/read error.
1-1-4. BIOS chip contents checksum error.
1-2-1. The motherboard is faulty.
1-2-2. DMA controller initialization error.
1-2-3. Error when trying to read/write to one of the DMA channels.
1-3-1. RAM regeneration error.
1-3-3. Error when testing the first 64 KB of RAM.
1-3-4. Error when testing the first 64 KB of RAM.
1-4-1. The motherboard is faulty.
1-4-2. RAM testing error.
1-4-3. System timer error.
1-4-4. Error accessing I/O port.
3-1-1. Error initializing the second DMA channel.
3-1-2. Error initializing the first DMA channel.
3-1-4. The motherboard is faulty.
3-2-4. Keyboard controller error.
3-3-4. Video memory testing error.
4-2-1. System timer error.
4-2-3. Line error A20. The keyboard controller is faulty.
4-2-4. Error when working in protected mode. The CPU may be faulty.
4-3-1. Error when testing RAM.
4-3-4. Real time clock error.
4-4-1. Serial port test failed. The error may be caused by a device using this port.
4-4-2. Error while testing parallel port. The error may be caused by a device using this port.
4-4-3. Error when testing the math coprocessor.
Compared to signals AMI audio Award signals BIOS are not so diverse, but in the vast majority of cases their set is quite enough to encode all possible motherboard errors. Distinctive features of Award BIOS are wide use long signal, as well as the use of such types of signals as continuous and constantly repeating sound signals.
Below is a list of Award beeps and their corresponding problem situations, as well as possible solutions.
- No signals
This may indicate a malfunction of both the power supply and the motherboard itself. In some cases, the system speaker of the motherboard may be faulty. To correct the situation, you can try checking the contact of the power cable coming from the power supply to the motherboard.
- One short
The user hears this signal most often. It means that the BIOS POST hardware check procedure was successful and the computer can continue booting.
- Two short
This message in Award BIOS is reserved for cases where the error is not serious and allows the computer to operate normally. A detailed text message about the essence of the error is displayed on the monitor screen. The user's further actions to resolve the error usually depend on the type of situation. For example, the error may be caused by a dead CMOS memory battery. In such a case, it must be replaced.
- Short repeating
The signal indicates a faulty power supply or damage to the power circuits. To correct the situation, you can try checking the contacts of the wires coming from the power supply to the motherboard.
- One long and one short
A message indicating a faulty RAM or no memory at all. If the latter option occurs, then the RAM modules must be installed, and if the memory is already present in the slots, then you can try to reinstall the RAM chips. If this does not help, then most likely the problem is a faulty memory module. Sometimes these signals can be generated when the video memory is faulty.
- Long repeating
An error similar to the previous one and indicating problems with RAM. This error Most often occurs when memory modules are installed incorrectly. To correct the situation, you should check whether the modules are installed correctly, and if not, then reinstall them.
- One long and two short
Similar beeps indicate a video card error. Often in such a situation, the problem is simply a poorly installed graphics accelerator card in the expansion slot, although the cause may also be a malfunction of the video card chip.
- Three long
This message means that the BIOS has detected a keyboard controller error. As in other cases, here you can try to check the connection between the keyboard and the system unit. In some cases, the signal disappears after restarting the computer again. If the keyboard works, but the signals still remain, then they can usually be turned off using special option BIOS.
- One long and three short
A sound message, like the previous one, indicating a keyboard error. But, unlike the previous error, in this case the signals indicate that the error manifests itself in a slightly different situation - the BIOS detected the keyboard, but was unable to access it.
- One long and nine short
The signals indicate a CMOS read-only memory error. This failure It can be either random, disappearing after rebooting the PC, or be a consequence of a malfunction of the CMOS memory chip, as well as incorrect flashing of the BIOS.
- Repeating signal with high and low frequencies
An error indicating a malfunction or incorrect installation of the central processor. To correct the situation, you should try to check the reliability or correct installation of the processor and its fastening in the socket.