Compaq.com United States

Maintenance & Service Guide
Presario 3500 Series Personal Computers

MSG Index | Home  |   Preface    |   Product Description   |   Troubleshooting   |   Illustrated Parts   |    Removal & Replacement
Jumpers & Switches   |   Specifications   |   Connector Pins    |   Power Cord Requirements


POST (Power On Self Test) Error Messages

An error message displays if the POST encounters a problem. This self-test will run automatically each time the system is powered on. The self-test will check all assemblies within the computer and report any errors found.

Click on the desired error code for the probable cause of the error and a recommended course of action.

CMOS Battery Has Failed CMOS Checksum Error Disk Boot Failure
Diskette Drives or Types Mismatch Error Display Switch Is Set Incorrectly Display Type Has Changed Since Last Boot
Error Encountered Initializing Hard Drive Error Initializing Hard Disk Controller Floppy Disk CNTRLR Error or No CNTRLR Present
Keyboard Error or No Keyboard Present Memory Address Error at nnn Memory Parity Error at nnn
Memory Size Has Changed Since Last Boot Memory Verify Error at nnn Offending Address Not Found
Offending Segment: Press A Key to Reboot Press F1 to Disable NM1, F2 to Reboot
RAM Parity Error System Halted Floppy Disk(s) Fail (80)
Floppy Disk(s) Fail (40) Hard Disk(s) Fail (80) Hard Disk(s) Fail (40)
Hard Disk(s) Fail (20) Hard Disk(s) Fail (10) Hard Disk(s) Fail (08)
BIOS ROM Checksum Error Memory Test Fail

¡@

CMOS Battery Has Failed

Probable Cause / Solution
CMOS battery is no longer functional. It should be replaced.

Back to Top

CMOS Checksum Error

Probable Cause / Solution
Checksum of CMOS is incorrect. This can indicate that CMOS has become corrupt. This error may have been caused by a weak battery. Check the battery and replace if necessary.

Back to Top

Disk Boot Failure

Probable Cause / Solution
No boot device was found. This could mean that either a boot drive was not detected or the drive does not contain proper system boot files. Insert a system disk into Drive A: and press Enter. If you assumed the system would boot from the hard drive, make sure the controller is inserted correctly and all cables are properly attached. Also be sure the disk is formatted as a boot device. Then reboot the system.

Back to Top

Diskette Drives or Types Mismatch Error

Probable Cause / Solution
Type of diskette drive installed in the system is different from the CMOS definition. Run SETUP to reconfigure the drive type correctly.

Back to Top

Display Switch Is Set Incorrectly

Probable Cause / Solution
Display switch on the motherboard can be set to either monochrome or color. This indicates the switch is set to a different setting than indicated in SETUP. Determine which setting is correct, and then either turn off the system and change the jumper, or enter SETUP and change the Video selection.

Back to Top

Display Type Has Changed Since Last Boot

Probable Cause / Solution
Since last powering off the system, the display adapter has been changed. You must configure the system for the new display type.

Back to Top

Error Encountered Initializing Hard Drive

Probable Cause / Solution
Hard drive cannot be initialized. Be sure the adapter is installed correctly and all cables are correctly and firmly attached. Also be sure the correct hard drive type is selected in SETUP.

Back to Top

Error Initializing Hard Disk Controller

Probable Cause / Solution
Cannot initialize controller. Make sure the cord is correctly and firmly installed in the bus. Be sure the correct hard drive type is selected in SETUP. Also check to see if any jumper needs to be set correctly on the hard drive.

Back to Top

Floppy Disk CNTRLR Error or No CNTRLR Present

Probable Cause / Solution
Cannot find or initialize the floppy drive controller. Make sure the controller is installed correctly and firmly. If there are no floppy drives installed, be sure the Diskette Drive selection in SETUP is set to None.

Back to Top

Keyboard Error or No Keyboard Present

Probable Cause / Solution
Cannot initialize the keyboard. Make sure the keyboard is attached correctly and no keys are being pressed during the boot.
If you are purposely configuring the system without a keyboard, set the error halt condition in SETUP to All, But Keyboard. This will cause the BIOS to ignore the missing keyboard and continue the boot.

Back to Top

Memory Address Error at nnn

Probable Cause / Solution
Indicates a memory address error at a specific location. You can use this location along with the memory map for your system to find and replace the bad memory chips.

Back to Top

Memory Parity Error at nnn

Probable Cause / Solution
Indicates a memory address error at a specific location. You can use this location along with the memory map for your system to find and replace the bad memory chips.

Back to Top

Memory Size Has Changed Since Last Boot

Probable Cause / Solution
Press F1 to reconfigure.

Back to Top

Memory Verify Error at nnn

Probable Cause / Solution
Indicates an error verifying a value already written to memory. Use the location along with your system's memory map to locate the bad chip.

Back to Top

Offending Address Not Found

Probable Cause / Solution
This message is used in conjunction with the I/O channel check and RAM parity error messages when the segment that has caused the problem cannot be isolated.

Back to Top

Offending Segment:

Probable Cause / Solution
This message is used in conjunction with the I/O channel check and RAM parity error messages when the segment that has caused the problem cannot be isolated.

Back to Top

Press A Key to Reboot

Probable Cause / Solution
This will be displayed at the bottom screen when an error occurs that requires you to reboot. Press any key and the system will reboot.

Back to Top

Press F1 to Disable NM1, F2 to Reboot

Probable Cause / Solution
When BIOS detects a non-maskable interrupt condition during boot, this will allow you to disable the NMI and continue to boot, or you can reboot the system with the NMI enabled.

Back to Top

RAM Parity Error

Probable Cause / Solution
Indicates a parity error in random access memory.

Back to Top

System Halted

Probable Cause / Solution
Indicates the present boot attempt has been aborted and the system must be rebooted. Press and hold down the Ctrl and Alt keys and press Del.

Back to Top

Floppy Disk(s) Fail (80)

Probable Cause / Solution
Unable to reset floppy subsystem.

Back to Top

Floppy Disk(s) Fail (40)

Probable Cause / Solution
Floppy type mismatch.

Back to Top

Hard Disk(s) Fail (80)

Probable Cause / Solution
HDD reset failed.

Back to Top

Hard Disk(s) Fail (40)

Probable Cause / Solution
HDD controller diagnostics failed.

Back to Top

Hard Disk(s) Fail (20)

Probable Cause / Solution
HDD initialization error.

Back to Top

Hard Disk(s) Fail (10)

Probable Cause / Solution
Unable to recalibrate fixed disk.

Back to Top

Hard Disk(s) Fail (08)

Probable Cause / Solution
Sector verify failed.

Back to Top

BIOS ROM Checksum Error

Probable Cause / Solution
The checksum of ROM address F0000H-FFFFFH is bad.

Back to Top

Memory Test Fail

Probable Cause / Solution
BIOS detects an on-board memory error.

Back to Top

 

 Compaq Home Showroom Service Worldwide Compaq.com
Comments?
Copyright
Revised: 19 Nov. 1999