4100 MT (250-5160) Error Messages Faxback Doc # 2822 When an error occurs after the video has been initialized, a description of the err appears on the screen followed by this prompt: Press to continue, or to run System Setup. At the prompt, you can press and continue normal processing, press and rerun System Setup, or turn off the system and perform necessary adjustments or replacements indicated by the error message. A number, in the format xx,yy appears in front of the message. xx indicates the problem component (see table below), and yy represents the test that failed Error Message Classes ┌──────────────────────────────────────────┐ │Class Description │ ├──────────────────────────────────────────┤ │01 Microprocessor │ │03-04, System board │ │14-15 │ │05, 08 Memory │ │06 Video │ │09 Cache memory │ │10 Software │ │11 CMOS data storage │ │12 Hard and floppy disk drives │ │13 Serial, parallel, and other │ │ communication ports │ │18 Personality module (Bravo LP only)│ └──────────────────────────────────────────┘ The following list describes the type of problem indicated by the error number. You can use this information to get more detail on the problem described in the message. 01.01-Protected mode cannot be enabled because it failed as the system sized extended memory. 03.01-The system halted because it detected a parity error. If the error occurred in memory below 1 MB, the message includes the segment where the error occurred. 03.02-The system halted because, while running, it detected an I/O channel check error. 03.10-The mask bits in interrupt controller 1 did not retain the data written to them. 03.11-The mask bits in interrupt controller 2 did not retain the data written to them. 03.12-The interrupt controller did not respond to an interrupt. 03.13-The system could no clear NMI control bits. 03.16-The system Setup configuration CMOS update-in-progress flag was stuck. 05.01-The move-shadow-RAM test failed. Shadow RAM did not store data correctly. 05.02-A memory verify error occurred during test of memory below 1MB. 05.03-A memory parity error occurred during test of memory below 1MB. 05.04-A memory verify error occurred during test of memory above 1MB. 05.05-A parity error was detected while testing memory above 1MB 05.06-The system detected a memory address error while testing for shorts and opens. 06.01-The primary video switch was set to color when a monochrome monitor was attached 06.02-The primary video switch was set to monochrome when a color monitor was attached. 06.03-System Setup was configured for a monochrome or CGA monitor when an EGA or VGA monitor was attached. 09.07-The testing of external cache memory failed because the test pattern did not verify. 09.08-The testing of external cache memory failed because the test pattern did not change. 09.09-The testing of the internal or external cache memory failed because the cache would not zero out. 09.10-The system did not have enough memory to test cache memory. The system needs at least 2MB for the cache test. 10.01-The system could not find a device with an operating system that would enable it to boot. 11.01-A battery failure caused the loss of CMOS data. 11.02-CMOS data failed the data path test. 11.03-The system set the factory-default CMOS configuration. 11.04-AT-compatible CMOS data had a bad checksum. 11.05-AST CMOS data had a bad checksum. 11.06-CMOS diagnostic byte memory size status was bad. 11.07-CMOS diagnostic byte equipment configuration status was bad. 11.08-The hours value stored in the System Setup Configuration CMOS was incorrect (above 23). If the error could not be corrected in System Setup, the system board has failed. 11.09-The minutes value stored in the System Setup Configuration CMOS was incorrect (above 59). If the error could not be corrected in System Setup, the system board has failed. 11.10-The floppy-drive configuration in System Setup did not match the drive. 11.11-The user password checksum is incorrect. Replace the battery. 11.12-The admin password checksum is incorrect. Replace the battery. 11.13-The serial number of asset-management tag in CMOS is invalid. Run the system-configuration utility to restore the data. 12.01-The system could not reset the hard drive while trying to load the operating system from it. 12.02-The hard drive timed out a the system tried to load the operating system from it. 12.03-The system could not reset the floppy drive while trying to load the operating system from it. 12.04-The hard drive timed out while waiting for the hard-drive controller to become available. The hard-drive signal and power cables might not be properly connected. 12.05-The hard-drive controller failed its internal diagnostics. The hard-drive signal and power cables might not be properly connected. 12.06-The system timed out while waiting for a hard drive to become ready. 12.07-The system timed out while sensing the hard-drive parameters. The system was waiting for a response from the hard drive after a reset command. 12.08-The system could not verify the existence of a hard drive while writing and reading the sector-count register during autosensing. 12.09-The system tried to autosense the hard-drive once more by writing and reading the sector-count register. Again, the system could not verify the existence of a hard drive. 12.10-The system timed out while attempting to autosense the hard-drive parameters. The system was waiting for a response by the hard drive to a recalibrate command. 12.11-The heads parameter returned from the drive was larger than what the BIOS can support. The IOS rounded the parameter down so it can support the drive; however, this process left unused disk space. Some drives may have alternate drive geometries that will fit. Enter these with the user-defined selection in the hard-drive-type fields in System Setup. 12.12-The sectors-per-track parameter returned from the drive was larger than what the BIOS can support. The BIOS rounded the parameter down so it can support the drive; however, this process left unused disk space. Some drives may have alternate drive geometries that will fit. Enter these with the user-defined selection in the hard-drive- type fields in System Setup. 12.13-The cylinders parameter returned from the drive was larger than what the BIOS can support. The BIOS rounded the parameter down so it can support the drive; however, this process left unused drive space. Some drives may have alternate drive geometries that will fit. Enter these with the user-defined selection in the hard-drive- type fields in System Setup. 12.14-The system timed out while attempting to autosense the hard drive parameters. The system was waiting for a response by the hard drive to an identify-drive command. 12.15-Floppy drive was not present. 12.16-Floppy-drive change line did not clear. 12.17-Floppy-drive controller did not respond to a request to send a specify command. 12.18-Floppy-drive seek attempt failed. 12.19-The floppy-drive controller did not accept a command. 12.20-A command to the floppy-drive controller timed out. 12.21-A command to the floppy-drive controller failed because of a DMA problem. 12.22-The system could not recalibrate a floppy drive successfully. 12.23-The floppy-drive controller could not seek. 12.24-The system received an "incorrect command" response after sending a valid command to the floppy-drive controller. 12.25-The floppy-drive controller did not find a valid sector ID. 12.26-An invalid CRC detected during a floppy-drive I/O operation. 12.27-The floppy-drive controller overran the DMA. 12.28-The floppy disk was write protected. 12.29-The system could not find an address ark on the floppy disk. 12.30-The floppy-drive controller reported a miscellaneous error. 12.31-The system timed out waiting for a floppy-drive controller seek, recalibrate, or reset commands to complete (no interrupt). 12.32-The floppy-drive controller failed to respond when trying to sense status after a seek, recalibrate, or reset command. 12.33-The floppy-drive controller responded with more than the correct number of status bytes after a seek, recalibrate, or reset command. 12.34-The floppy-drive controller failed to respond to a status request after a seek, recalibrate, or reset command. 12.35-The floppy-drive controller responded to a sense command with an incorrect number of bytes after a seek, recalibrate, or reset command. 12.36-The floppy-drive controller failed during a seek command. 12.37-The floppy-drive controller failed during a read-ID command. 12.38-A floppy-drive controller command went beyond the end of the media. 12.39-The system could not read the ID on track 0 because the disk was not formatted properly, or the drive type or transfer rate did not match. 12.40-The system timed out while waiting for results from the floppy-drive controller. 12.41-A floppy-drive DMA boundary error occurred. 12.42-A command to the floppy-drive controller timed out. 12.43-The system did not support the requested hard-drive function. 12.44-The hard drive did not become ready after a reset command. 12.45-The requested hard-disk transfer was too long (over 65,536 bytes). 12.46-The system timed out while waiting for the hard-drive controller to become ready. 12.47-The hard-drive controller did not request data as expected after it was sent a command. 12.48-The hard-drive controller did not request more data after it received a command and some data. 12.49-The system timed out while waiting for an interrupt from the hard -drive controller. 12.50-The hard disk attempted to seek. 12.51-The hard-drive controller failed because of an unclassified error. 12.52-The system timed out waiting for the hard disk to become ready. 12.53-Hard-drive initialization failed during a set-parameter command. The hard-drive controller indicated that the drive was ready when it was actually busy. 12.54-A hard-drive write-fault error occurred. 12.55-The system received a drive not ready error while initializing the hard-drive with the set-parameter command. 12.56-The system received a seek fail error while initializing the hard drive with the set-parameter command. 12.57-The system received an ECC error while initializing the hard drive with the set-parameter command. 12.58-The system received an unspecified error while initializing the hard drive with the set-parameter command. 12.59-The hard-drive controller was not ready before an attempt to send a drive diagnostics command. 12.60-The hard-drive controller was not ready during an attempt to send a drive-diagnostics command. 12.61-The hard-dive controller returned an error from a drive diagnostics command. 12.62-The hard drive was not ready after being sent a set-parameter command. 12.63-The hard-drive controller failed to respond to a recalibrate command. 12.64-The requested hard disk did not exist. 13.01-There was a conflict in serial port addresses. 13.02-There was a conflict in parallel port addressed. 13.03-There was a conflict in LAN module ROM indication. 13.04-The keyboard did not respond to a reset request, probably because the test was obsolete. 13.05-The keyboard did not respond to a reset request because it did not receive an ACK signal. 13.06-The keyboard did not respond to a reset request because the status byte returned from the keyboard after self-test was not 0AAh. 13.07-A key was stuck on the keyboard. Error may have occurred because the user pressed a key during the boot process. 13.08-The parameters autosensed during boot are different from those sensed the last time the system was booted. This message may appear if boards were added or removed since the last time the system ran or because CMOS failed. If the CMOS failed, other messages appear on the screen. 18.01-The personality module code in BIOS did not match the module that is installed in the system. (ALL-08/24/94)