This chapter describes the various error indications that will be encountered while running the tests on the Diagnostic menu. Where possible, the most likely cause of the failure is given as well.
Microprocessor Test A microprocessor failure will usually prevent the software from loading, and will require a hardware tool such as the POST-Probe to diagnose the problem. If this failure does appear, it indicates a problem with the CPU chip.
Register Test The Register Test will exercise the internal registers of the CPU. Failure is a defective CPU chip.
Arithmetic Test Indicates a bad CPU chip. Be aware that some revisions of the 80386 have an error on 32-bit divides, which will cause this test to fail but is not otherwise a problem if the system has been running properly.
Logical Test This tests the logical functions of the CPU chip, which should be replaced if the test fails.
NPU Tests Coprocessor Test Tests the general functionality of the NPU chip.
Not Installed The NPU chip was not detected by the software. This indicates a hard failure of the NPU chip, except in those few systems with no NPU installed. Verify with the System Configuration feature.
Register Test Tests the NPU registers and indicates failure of the chip.
Arithmetic Tests the floating-point calculations of the NPU. Failure indicates replacement of the chip.
RTC Errors RAM Data Failure There is a failing data bit in the memory associated with the Real Time Clock, located in the CMOS/RTC chip.
RAM Address Failure This indicates a failing address line in the memory associated with the RTC.
CRC Checksum Failure The CRC checksum does not equal the expected total.
CTC Errors Port B Test Failed This indicates a failure of the secondary port of the Clock Timer chip.
CTC Register Failed Testing the internal registers of the CTC chip.
CTC Timer Failed Indicates failure of the timer circuitry of the CTC chip.
DMA Errors Register Failure Indicates a defective DMA chip.
Page Register Failure Usually means a defective DMA chip, but some early PCs may fail due to an incompatibility with the test even though the chip is OK.
Keyboard Controller Errors Keyboard Controller Test Failed Indicates either a defective keyboard or a failing keyboard controller chip (8042). Use the Keyboard test to differentiate.
PS/2 Mouse Test Failed Tests the PS/2 mouse portion of an Enhanced Keyboard Controller. Failure may be the controller chip, mouse port socket or cable, or the mouse itself. To isolate the problem, run the test again with no mouse attached.
Interrupt Controller Errors Register Test Failed This indicates a defective PIC chip.
APM Errors (Advanced Power Management) Cycle Fan On Failed The failure could be the fan control circuit or the fan itself. If possible, the fan should be observed during the test to determine if it is responding to the command. Cycle Fan Off Failed The failure could be the fan control circuit or the fan itself. If possible, the fan should be observed during the test to determine if it is responding to the command.
Refresh Errors If a refresh error occurs while testing Base Memory, the memory controller or the PIT chip are the likely suspects.
Data Errors Indicates a failure of a memory chip. The segment, offset, expected data, received data and XOR are given. The XOR is all bits within the offset that failed.
Address Errors The failing address line will be indicated on the screen. This could be due to a bad trace or buffer circuit on the motherboard, or in some cases by a defective SIMM or DIMM.
Parity Errors Almost always a failure of the memory chip. The segment, offset, expected data, received data and XOR are provided.
Cache Memory A Cache Memory failure could be either the static RAM or the Cache Controller. The segment within the cache, the offset, expected data, received data and XOR are given. The XOR is all bits that failed within the given offset. The Cache Memory tests are functionally the same as those for Extended Memory, except that the cache is not flushed during the test.
Note: To properly perform the Expanded Memory tests, first perform a warm boot so that the EMM drivers are loaded.
Page Frame This error indicates that the page frame (block within Base Memory) could not be allocated. Try changing the page frame in the Expanded Memory software setup, since this area may be used by another device or program. Number of Pages This error indicates that the number of pages allocated by the Expanded Memory driver is incorrect. EMM Version If this error occurs, the expected version of the EMM driver could not be detected by the diagnostic. Handles and Allocation of Memory This error indicates the Expanded Memory driver is unable to allocate a memory block. Reduce the number of handles and try again. Map Memory to Physical Memory The EMM driver could not allocate a memory block. Either the memory block is being used or the EMM driver is failing. Compare Memory This error means there was a failure of the Compare performed on the data written to memory. Test the indicated area as Extended Memory. De-allocate Memory This error will occur if the EMM driver cannot de-allocate a block of memory, and indicates a failure of the EMM driver. Conform that the EMM driver has been loaded with a warm boot. Refresh Error There is either a failure in the refresh circuitry or the EMM driver is not addressing the correct location where data was written prior to this error occurring. Use the Extended Memory test to verify this error.
Extended Memory Errors Unlike expanded memory, the Extended Memory tests will NOT run if the EMM drivers are loaded. Always do a cold boot to Micro-Scopes own operating system before testing Extended Memory. All Extended Memory tests will state the Offset from 1 Megabyte, the Segment, the EXP (expected data), REC (received data) and an XOR (the failing bit). Use the Offset to determine the bank in which the failure occurred, the Segment to determine the 64K block within the bank, and the XOR to determine the specific bits that are failing. For example:
Offset = 0001 First megabyte beyond 1MB. Segment = 1000 Second 64K block in Offset. XOR = 10 Bit 4 is failing.
The actual memory segment may be affected by the computers paging layout. Refresh Error Either an intermittent error is occurring at the given location, or the refresh circuitry for the memory is failing. If this error occurs at different locations each time, the fault is in the refresh circuits. Parity The memory location indicated has a defective parity cell. Data Bit Error The Data Received does not match the Data Expected for the given location. The XOR will show the conflicting bit(s). A20 Line Not Open The keyboard controller would not allow the CPU to enter Protected Mode. Either the keyboard controller chip is malfunctioning or the A20 line is defective.
Note: Faster Tests Available
Extended Memory has long and short versions for the Bit test and the Grid test. The reason the long versions are so time-consuming is because of the need to flush the cache after each step to ensure that the test is looking at RAM rather than the cache. If the cache is disabled in CMOS, these same tests can be run from the Cache Memory Tests menu, but will take place in RAM since cache is disabled. In this way, the tests will be completed in a much shorter amount of time. The cache must be re-enabled once the tests are completed.
Many of the errors that might be found during these floppy tests can be caused either by the drive or by the floppy controller. Many more errors occur with the drives, because of their mechanical complexity and close tolerances. However, if there is a second floppy in the system and the error shows up on both drives, the most likely suspects are the controller or the floppy cable. Code 01: Invalid Function Error The command sent to the floppy drive was not accepted. The most likely cause is either the drive unit or the cable. Code 02: Address Mark Not Found The diagnostic could not find the Address Mark for the given sector. This is most likely from a defective or unformatted diskette. Retry the test with another freshly-formatted diskette. Code 03: Disk Write Protect This error should only occur during the Write Test or Format, and indicates that the drive is sending a write-protected signal to the controller. If the diskette is actually write-protected, this is functioning normally. If the diskette is not write-protected, there is a problem either with the drive or the controller. If the error occurs during a Read or Butterfly Seek test, it is most likely the controller at fault. Code 04: Sector Not Found This error could occur if the selected media type does not match the diskette in the drive, if the diskette is unformatted or has defective sectors, or if the floppy heads are out of alignment.
Note: To determine if a floppy drive is aligned properly, format a diskette in a known good drive, to use as a standard. If a drive can read diskettes that have been formatted on that drive, but fails when tested with the standard diskette, the drive is misaligned.
Code 05: Reset Failed The floppy drive will not reset before starting the format operation. This could be caused by the drive, the cable, or the controller.
Code 06: Disk Change This should occur if the door on the floppy drive is opened during the test. If the door was not deliberately opened, there is a probably a mechanical problem with the drive. If the door was deliberately opened during the test and this error did NOT occur, there is a problem either with the drive or the controller. Code 07: Drive Param Activity Failed This indicates either a failure in the floppy controller or improper media settings in the CMOS. Verify the media settings and try the test again. Code 08: DMA Overrun This error would occur if another device, such as a tape drive, was set to the same DMA channel as the floppy drive. If such a device was recently added to the system, the first thing to try would be removing the device and running the test again. Floppy drives use DMA channel 2, so no other devices should be set to this. If no other device is using the same channel, then the floppy drives control circuitry is failing. Code 09: Data Boundary Error This indicates that another device is using the same DMA channel as the floppy drive. See DMA Overrun above for solutions. Code 0A: Bad Sector Flag Bad sectors should be flagged and not accessed, even during the diagnostic tests. If this error occurs, it most likely indicates a failure in the controller. Code 0B: Bad Cylinder Detected This code could mean a faulty controller, a damaged diskette or a malfunctioning actuator arm in the floppy drive. Code 0C: Invalid Media This error should not occur with the Micro-Scope diagnostic regardless of the media placed in the drive. The fault could be with the drive, controller or cable. Code 0D: Invalid Number of Sectors This error could mean a malfunction of the drive, cable or controller, either on the system under test or on the one in which the diskette was formatted. Code 0E: Control Data Address Mark Retry the test with another freshly-formatted diskette. A second failure implicates the floppy head alignment or an electronic failure. Code 0F: DMA Arbitration Out of Range Could be hardware failure, but first check the setup of the system, and remove any recently installed devices to eliminate conflicts. Code 10: Uncorrectable CRC Error This is most likely a defective diskette. Replace the diskette with a known good sample. If the error re-occurs, clean the heads and try again. A third failure indicates a malfunction of the floppy drive. Code 11: ECC Corrected Data Error This is most likely a defective diskette. Replace the diskette with a known good sample. If the error re-occurs, clean the heads and try again. A third failure indicates a malfunction of the floppy drive. Code 20: Controller Failure Although this message occurs when the controller has failed to properly control the drives, the problem could be in the drive or the cable as well as the controller. Code 40: Seek Failed The floppy drive was not able to find the desired cylinder. The problem is most likely a defective floppy diskette, followed by a mis-aligned floppy drive or mechanical failure of the actuator arm. Least likely causes are a defective cable or controller. Code 80: Timeout Error This is most likely to happen if there is no diskette in the drive, or it is inserted incorrectly. Code AA: Drive Not Ready Indicates electronic failure in the drive, controller or cable. Code BB: Undefined Error Either the floppy controller or cable. Code CC: Write Fault A failure occurred while attempting to write to the drive. Source of the problem could be electronic or mechanical. Code E0: Status Register Error The floppy controller is not sending the proper signal to the BIOS during the floppys busy state. The fault is with either the controller or the cable. Code FF: Sense Operation Failed Most likely a defective diskette or the heads need cleaning. If these fail to resolve it, the problem is electronic failure in the drive.
This section lists the errors that could be encountered during the Fixed Disk diagnostic tests or during a drive format, along with suggestions for correction. Keep in mind that with IDE drives, the control circuitry is in the drive, not on the motherboard. Also, when errors occur because of incompatibility between drives, the error will sometimes disappear if the order of the drives is changed (swapping Master and Slave, or Primary and Secondary). Of course, the proper changes must then be made with jumpers and settings. Code 01: Invalid Function Error The command sent to the drive was not accepted. The most likely cause is either the drive unit or the cable. If the system is a PS/2, the BIOS will not support the direct format of the drive. Code 02: Address Mark Not Found The diagnostic could not find the Address Mark for the given sector. On MFM and RLL drives that do not use a voice-coil head actuator, it could mean the heads are misaligned. A low-level format will correct the problem. It could also mean that the drive type is not set in CMOS. On IDE drives, this error is a physical defect and the address should be added to the Bad Sector map before doing a low-level format. Code 03: Disk Write Protect This error should never occur while testing a hard drive, and would indicate electronic failure in the drive control circuitry. Code 04: Sector Not Found This can occur if the servo information on the platter for that sector is damaged or there is an electronic failure in the drive control circuitry. It could also be mis-aligned heads (MFM or RLL drives). A low-level format may be able to correct the problem. If the error occurs during a low-level format, it is a fatal error and the drive should be replaced. Code 05: Reset Failed Usually caused by electronic failure in the control circuitry. If there are two or more hard drives in the system, this error may indicate an incompatibility between a Master Drive and its Slave. Code 06: Disk Change This error should never occur during testing of a hard drive. Code 07: Drive Param Activity Failed Either the drive parameters are set incorrectly in CMOS or the controller does not correctly translate the parameters. Verify the settings and try the test again. Code 08: DMA Overrun This error would occur if another device is trying to use the same DMA channel as the disk drive or if the drive controller is failing. If a new device was recently added to the system, the first thing to try would be removing the device and running the test again. Code 09: Data Boundary Error This indicates that another device is using the same DMA channel as the fixed disk. See DMA Overrun above for solutions. Code 0A: Bad Sector Flag On the fixed disk, this is not an error. It shows that the flagged sector has already been added to the Bad Sector Map and is not being used by the system. If it is known that the sector is good, the flag can be removed by performing a low-level format without first setting this sector in the Bad Sector Map. Code 0B: Bad Cylinder Detected This error code should not occur during the Fixed Disk tests. Code 0C: Invalid Media This error code should not occur during the Fixed Disk tests. Code 0D: Invalid Number of Sectors This error indicates that the fixed drive is set incorrectly in CMOS or the controller is improperly jumpered. If these causes are eliminated, then an electronic failure exists in the drive, controller or cable. Code 0E: Control Data Address Mark The servo information is damaged or there is an electronic failure. If the error occurs in different locations of the drive, suspect electronic failure. If its at the same place each time, run a low-level format to map out the bad sector. If the error occurs during a low-level format, it is a fatal error and the drive should be replaced. Code 0F: DMA Arbitration Out of Range Could be hardware failure, but first check the setup of the system, and remove any recently installed devices to eliminate conflicts. Code 10: Uncorrectable CRC/ECC Error This is most likely a physical defect in the requested sector, which can be corrected by mapping during a low-level format. With MFM or RLL drives, it may indicate mis-alignment of the heads. Code 11: ECC Corrected Data Error The requested sector had an error that was within correctable limits for the ECC circuitry. If data integrity is of extreme importance, the sector can be marked bad during a low-level format. Code 20: Controller Failure Although this message occurs when the controller has failed to properly control the drives, the problem could be in the drive or the cable as well as the controller. If there are two or more drives, it may result from an incompatibility between a Master Drive and its Slave. Code 40: Seek Failed This could result from a physical defect on the platter, which can be corrected by a low-level format, or by a failure of the seeking circuitry of the drive. Code 80: Timeout Error This error will occur when the drive does not respond to the controller commands. Before replacing hardware, check the CMOS setup and the IRQ status for the drive and also check that the drive and controller jumpers are correctly configured. Before retesting, run the Controller Test to reset the drive. Code AA: Drive Not Ready Run the controller test to reset the drive. If the failure persists, it indicates electronic failure in the drive, controller or cable. Code BB: Undefined Error Either the fixed disk controller or cable. Code CC: Write Fault A failure occurred while attempting to write to the drive. Source of the problem could be electronic or mechanical. Code E0: Status Register Error The fixed disk controller is not sending the proper signal to the BIOS. The fault is with either the controller or the cable. Code FF: Sense Operation Failed This error should never be reported during the Fixed Disk tests. Controller Internal Diags Failed The controller circuitry is failing, or there is an incompatibility between two drives. Controller Write Buffer Failed This indicates a failure of the write buffer on the drive itself, not the controller. Controller Read Buffer Failed This indicates a failure of the read buffer on the drive itself, not the controller. Controller Compare Buffer Data Failed This indicates a failure of the fixed drives buffer circuitry, on the drive itself, not on the controller card. Controller Recalibrate Failed The drives heads failed to properly seek Track 0. Either the heads or Track 0 of the platter is damaged. Either is a fatal error for the drive. Controller Reset Failed The drive failed to respond to the reset command. This failure could occur in the drive, the controller or the cable.
Code 01: Unknown Unit The software driver does not recognize the CD-ROM drive. This can occur if attempting to access a drive which is not installed.
Code 02: Drive Not Ready The CD-ROM drive did not return a Ready signal. There are several possibilities: mechanical or electronic malfunction in the drive, controller or cable, incorrect hardware settings, or a corrupted or incorrectly configured software driver. Code 03: Unknown Command The software driver did not recognize a control command. Sometimes a defective controller, most often a corrupted driver. Code 04: CRC Error Usually a defect in the data area of the disc. If the error still occurs with a known good disc the CD-ROM should be cleaned. Continued failure after cleaning indicates a malfunction of the drive itself. Code 05: Bad Request Header Length The controller software was unable to execute a command due to an incorrect Request Header response. Code 06: Seek Error The drive was unable to seek the sector requested by the test. Code 07: Unknown Media The software driver did not recognize the media type. Retry with a known good disc (data disc, not music). Code 08: Sector Not Found The requested sectors ID was not found. It could result from a defective disc, dirty or misaligned head, or electronic failure. Code 0B: Read Fault Due to a failure of the Read circuitry in the drive. Code 0C: General Failure The driver cannot recognize or communicate with the CD-ROM drive. Code 0F: Invalid Disc Change This occurs when the door is opened and re-closed during the test. If the door was not disturbed, there may be a mechanical problem with the door or a bad electrical connection in the drive or the cable. Code 15: Invalid Drive Usually indicates an attempt to access a drive that is missing or incorrectly installed. Code FB: Dirty lens or dirty media. Try a new CD. If failure still occurs, clean lens in drive.
Code 01/02: Timeout Error The printer failed to respond. Check the cable and the printers Online status.
Code 08: I/O Error The printer command was unable to gain I/O access. Code 20: Out of Paper Error The printer is returning an Out-of Paper signal. Code F6: Print Test Aborted The Escape key was pressed during the test. Code FF: Printer Would Not Initialize Indicates the printer is not responding to commands. Multiple Errors A combination of two or more error codes were returned during the test.
UART Failure There was no response from the Universal Asynchronous Receiver/Transmitter chip. Use the System Information screen to verify that the port actually exists.
FIFO Failure The FIFO circuitry of the UART has failed, and the UART or Serial Controller card should be replaced.
Line Status Errors The following signals each describe one line of the serial port. If the port is functioning properly, each of these lines should report as Active at the conclusion of the Loopback Test. An error means that the given signal did not appear when expected, which could be due to the connector, the UART chip, or attempting an external test when no loopback plug is attached. It is important that the test is done with a loopback plug attached rather than an actual serial device. In describing the various signals, Terminal refers to the computer terminal (bus). Set or Device refers to the peripheral attached to the port. The number corresponds to the pin number of a 9-pin connector.
Note: RI/87307 TERI Flaw A ring indicator failure that appears only with the National Semiconductor 8730x series of Super I/O Controller chips, because these do not comply with design standards. The error does not appear to affect the function of current modem devices.
Negative Current Transmit Loop Only used in XT and earlier machines, to indicate data transfer. It has been replaced by the Transmit Data signal.
Misc. Serial Test Errors Overrun The Data Receive Register is full, but data is still being sent. Either the CS signal is not functioning or the sending device is malfunctioning. Parity Error Indicates that the attached devices are not set to the same parity. Framing Error One or more serial devices are not responding properly to the setting of the Start and Stop bits. Handshake The port failed to respond to the XON and XOFF software flow control signals. Break Detected A break was detected during data transmission. A mouse connected to the serial port is often a cause of these errors. Data Errors The Sent and Received data bytes were not the same.
Modem Status Errors When the Serial Port Test is run, it will also report the condition of the Modem Status Lines listed below. If the modem is not in use during the test, the four Inverted lines should be reported as Low, and the Delta lines should be reported as Inactive. Delta Clear To Send A Request to Send was acknowledged by the modem. Delta Data Set Ready The modem is ready to receive data. Delta Ring Indicator An incoming ring was detected. Delta Carrier Detect A carrier signal was detected. Inverted Clear to Send The CTS line has been toggled. Inverted Data Set Ready The DTS line has been toggled. Inverted Ring Indicator The Ring Indicator signal has been toggled. Inverted Carrier Detect The Carrier Detect circuitry was toggled.
Although the modem can be tested as a serial device as explained in the previous section, the Modem Connect Tests menu offers five sets of tests for more comprehensive testing of a host-based modem. These are the Modem test, Line test, Connect test, Send ASCII and Send File tests. The last three require the modem to communicate with a remote modem.
Modem Test The largest group of tests in this set is the Sync/Async Tests, which use the ATI Command Set to request information from the modem. These may vary from one manufacturer to the next, but the most common version is given here. Because the ATI commands can vary from one manufacturer to the next, error responses should be analyzed carefully and if possible compared against other modems of the same model. Another thing to watch for is whether the modem is connected to an active line, for instance to an ISP. In this case, errors can result from the receipt of signals not expected by the test. The Sync/Async Test is an off-line test, and the phone line should be disconnected if necessary to prevent spurious signals.
Sync/Async ATI 0 Manufacturers Product Code ATI 1 ROM Checksum ATI 2 RAM Checksum ATI 4 Current Settings. Includes: FAX INT Settings Baud Rate Parity Dial Settings Speed ATI 5 NVRAM Settings ATI 7 Configuration and Internal Product ID ATI 9 Plug-N-Play Status
Data Compression (ATXC) Tests the modems data compression circuitry. Fax Modem Test Checks the FAX functions of the modem. Internal Loopback Uses an internal loopback to test the modem I/O. Reset Modem Tests the Reset function of the modem.
Line Test This set monitors two functions of the modem.
If this test fails, first check the phone cable and its connections on both ends.
Note: This test expects a standard phone-company-supplied dial tone. Connecting to a private PBX can cause this test to fail, as well as risking damage to your modem.
On-line Tests These tests require entering a phone number that will connect to another modem. Connect Test This test confirms that the modem has connected to a remote site and received an acknowledgment. If the test fails, run the Line Test to help isolate the problem. If the Line Test passes and the Connect Test fails, check that the modems on both ends are in compatible modes and able to match transmission speeds.
Send ASCII Test This goes one step beyond the Connect Test, and sends a packet of ASCII data to the remote site. If the previous test passed and this one fails, there may be a resource conflict or marginal transmission capability.
Send File Test This test sends a file called Sample.txt to the remote site. This file can be printed out and checked visually for accurate transmission. If this fails where the ASCII test passed, suspect the data settings for either of the modems.
Following are the various lines of the parallel port that are toggled during the test. The first five are incoming signals (from the external device to the port) and will be listed as Inactive if the test is run in Internal mode. The others are outgoing and will be listed as Active at the conclusion of the Loopback test, if they are functioning properly.
Acknowledge The device received the data byte and is ready for another. Device Busy If this signal fails, the port will send data when the device is not ready to receive it. Paper End The printer is out of paper. Select The device indicates it has been selected to receive data. Select In Selects the device to receive data. Error Register The device uses this line to let the system know it has flagged an error. Strobe Enables the transfer of one byte of data. Data Bits 0-7 These are the parallel data lines. Auto Feed Notifies the printer to do auto-feed. If this signal fails, the printer will perform manual feed only. Initialize Printer This signal alerts the printer to perform its internal initialization routine. IRQ Enable Tells the system an interrupt will be generated when the external device returns an Ack signal.
The Status Latch Test and Interrupt Level Test must be run with an external loopback plug. If the test is run in internal mode, these tests will say Bypassed. If the test is run in External mode without a loopback plug in place, the tests will fail.
Data Latches Test Tests the port register that holds a data byte for transmission. Control Latch Test This register holds the Control byte, containing signals such as IRQ Enable and Initialize Printer. The failing signal will be displayed in the test status window. Status Latch Test Latches the incoming status lines, such as Device Busy, Ack and Paper Out. The failing signal will be displayed. If all fail, check to see if the test was run in external mode without a loopback plug. Interrupt Level Checks that the device responds with an interrupt. A failure could be the port or PIC circuitry but is more likely the device or cable.
Each of the failure codes listed below will be the result of a hardware failure on the NIC card. 1 = Register Test Failure onboard command registers are malfunctioning. 2 = EEPROM Test Failure EEPROM chip not responding. 3 = SRAM Test Failure Malfunction of onboard RAM. 4 = FIFO Test Failure FIFO stack not responding with correct data. 5 = Rcv RAM Buffer Failure Malfunction of the buffer for incoming data. 6 = Xmt RAM Buffer Failure Malfunction of the buffer holding data for output. 7 = NIC Node Address Failure The card did not respond with the correct MAC address. 8 = I/O Address Failure An incorrect address or the I/O ports are not functioning. 9 = Interrupt Failure The card did not respond with the expected interrupt. 10 = Not From a Windows DOS Box The test was attempting to run the Windows MS-DOS prompt. 11 = No Supported NIC Adapter The installed network card is not a type recognized by Micro-Scope. 13 = Port Self-Test Failure The card did not pass an internal diagnostic of its I/O ports. 14 = Internal Diagnostic Failure The card did not pass some part of its own internal diagnostic. 15 = Dump Data Bytes Failure The card did not comply with a command to dump its buffer contents. 16 = Configure Command Failure Did not respond to Configure command. 17 = Transmit Data Failure Unable to output data to the network cable. 18 = Receive Data Failure Unable to latch incoming data.
USB Controller Tests
Each of the following errors is the result of the USB Host Controller failing to respond correctly to one of the basic commands. These tests do not test attached devices and do not require any USB devices to be attached. 1 = Host Reset Failure Controller did not respond correctly to a Reset command. 2 = Host Restart Failure Controller did not respond to a Restart command after being stopped. 3 = Host Run/Stop Failure Either the Run command, Stop command or both were ineffective. 4 = Host Suspend Failure Controller unable to suspend operations. 5 = Host Resume Failure Controller unable to resume after a Suspend command.
Memory Failure A data mismatch within the video memory. The error message provides the offset, data expected, data received and XOR.
Display Attributes The attributes are displayed in the middle column, the attribute bits in the left column, and a description on the right. The attributes must be visually matched to the description. Display Character Set The entire ASCII character set should be displayed. Any errors are probably due to the video adapter card. Screen Alignment Check the horizontal and vertical grid lines to ensure that they remain parallel, especially toward the corners of the screen. Convergence Using the screen alignment test, change the background attribute with the up and down arrow keys. If a red or blue line appears at the edge of the screen, the colors of the electron gun do not converge properly. Text Modes The standard 8-character set should be displayed on each line, offset by one character from the line above it. Graphics Mode The display will show 16 labeled colors, allowing the color balance to be adjusted either by eye or by comparison with a standard color chart. Screen Paging The screen will initially show 25 lines of zeroes. Pressing any key (except Esc) will cycle the display through the digits 0-7.