16.135 bytes

Service Hints & Tips

Document ID: GSMH-3CACWX

This document is provided to IBM and our Business Partners to help sell and/or service IBM products. It is not to be distributed beyond that audience or used for any other purpose.

TP General - N45SL Symptom - To - FRU Index

Applicable to: World-Wide

Symptom-to-FRU Index:
The Symptom-to-FRU Index lists the symptoms and errors and the possible causes. The most likely cause is listed first.

Note:
Perform the FRU replacement or actions in the sequence shown in the FRU/Action columns. If a FRU did not solve the problem, put the original part back in the computer. Do not replace a non-defective part.

This index can also be used to help you decide which FRUs to have available when servicing a computer.

Note:
For IBM devices not supported by the N45 diagnostics, see the manual for that device.

Symptom/Error

FRU/Action

No access to A or C drive after POST.

1. Ensure boot sequence is not set to ¿Monitor.—

¿CHECKSUM ERROR! Bad image file.
ERROR occurred while reading file.—

1. Advanced Diagnostics diskette

¿Device error during erasing process.—

1. System Board

¿Device error during programming process.—

1. DC-to-DC board
2. System Board

¿DISK ERROR: Bad disk controller!—

1. Check disk drive cable connection.
2. Diskette Drive Cable

¿DISK ERROR: Cannot reset drive!—

1. Verify drive installation.
2. Diskette Drive
3. System Board

¿DISK ERROR: CRC error!—

1. Diskette
2. Diskette Drive Cable
3. Run Advanced Diagnostics to test drive.
4. Diskette Drive
5. System Board

¿DISK ERROR: Data Corrected!—

1. If this message occurs regularly, see ¿DISK ERROR: CRC error!—

¿DISK ERROR: Disk not bootable!—

1. Use a bootable diskette.
2. For a hard disk, reinstall the operating system.
3. Back up the hard disk, if possible, and run PREP to reinitialize the disk (see ¿Running PREP— ). Reformat disk and install operating system.
4. Hard Disk Drive

¿DISK ERROR: DMA overrun!—

1. Diskette Drive
2. System Board

¿DISK ERROR: Drive not ready!—

1. Remove and reinsert diskette.
2. Verify the correct drive was specified.
3. Diskette Drive

¿DISK ERROR: Invalid address mark!—

1. If the problem is a diskette:
a. Copy any readable files to another diskette and reformat faulty diskette. If bad sectors are reported, discard the faulty diskette.
b. Diskette
c. Diskette Drive
2. If the problem is a hard disk:
a. Back up the hard disk, if possible, and run PREP to reinitialize the disk (see ¿Running PREP—).
Reformat disk and install operating system.
b. Hard Disk Drive

¿DISK ERROR: Invalid data read!—

1. If the problem is a diskette: a. Copy any readable files to another diskette and reformat faulty diskette. If bad sectors are reported, discard the faulty
diskette.
b. Diskette
c. Diskette Drive
2. If the problem is a hard disk:
a. Back up the hard disk, if possible, and run PREP to reinitialize the disk (see ¿Running PREP—).
Reformat disk and install operating system.
b. Hard Disk Drive

¿DISK ERROR: Must run SETUP to boot from Winchester!—

1. Run Setup program to specify correct hard disk drive type.
2. System Board

¿DISK ERROR: No bootable partitions—

1. Retry the boot command syntax and verify a valid partition is selected using the DOS ¿FDISK— command.
2. Format partition and install operating system using the DOS FORMAT— command.

¿DISK ERROR: Sector not found!—

1. If the problem is a diskette:
a. Copy any readable files to another diskette and reformat faulty diskette. If bad sectors are reported, discard the faulty diskette.
b. Diskette
c. Diskette Drive
2. If the problem is a hard disk:
a. Back up the hard disk, if possible, and run PREP to reinitialize the disk (see ¿Running PREP—).
Reformat disk and install operating system.
b. Hard Disk Drive

¿DISK ERROR: Seek failure!—

1. Copy any readable files to another diskette and format the faulty diskette.
2. If bad sectors are reported, discard the faulty diskette.
3. Diskette
4. Diskette Drive
5. System Board

¿ERROR: Bad configuration information found in CMOS!—

1. Run Setup program to reconfigure.
2. Backup Battery
3. System Board

¿ERROR: Base memory size error: SETUP: XXXK ACTUAL:XXXK!—

1. Run Setup program to verify correct base memory size.
2. Run the Advanced Diagnostics Memory Test to check base memory.
3. System Board

¿ERROR: Can't locate input file.—

1. Correct Advanced Diagnostics diskette?
2. Advanced Diagnostics diskette

¿ERROR: CMOS memory failure!—

1. Run Setup program to verify configuration.
2. System Board

¿ERROR: CPU failure!—

1. System Board

¿ERROR: Divide by zero!—

1. Try another copy of the software, or have the customer contact the software manufacturer or dealer and report the problem. Unless this message occurs during the power-up sequence, the
problem is with the software.
2. Power-off computer, wait 15 seconds, then power-on computer. If the message reappears, replace system board.

¿ERROR: Extended memory size error! SETUP: XXXK ACTUAL: XXXXK—

1. Run Setup program to verify the extended RAM memory size matches the memory installed.
2. Check the memory module installation.
3. Run Advanced Diagnostics to test extended memory. If you cannot boot the computer, replace the system board and try again. If the tests identify an expansion memory module, replace it. If the tests identify a problem in the base memory, replace the system board.

¿ERROR: File too long for program buffers.—

1. Correct Advanced Diagnostics diskette?
2. Advanced Diagnostics diskette

¿ERROR: File too long for ROM size.—

1. Correct Advanced Diagnostics diskette?
2. Advanced Diagnostics diskette

¿ERROR: File too short to fill ROM.—

1. Correct Advanced Diagnostics diskette?
2. Advanced Diagnostics diskette

¿ERROR: Invalid command!—

1. Retry the command.
2. Try another copy of the software or have the customer contact the software manufacturer or dealer and report the problem.
3. System Board

¿ERROR: Keyboard not responding or not connected!—

1. Check keyboard connections.
2. Keyboard
3. System Board

¿ERROR: Memory parity failure!—

1. Run Advanced Diagnostics Memory Test to check base and extended memory.
2. Memory Module
3. System Board

¿ERROR occurred while reading Boot Sector.—

1. Advanced Diagnostics diskette

¿ERROR occurred while reading FAT table.—

1. Advanced Diagnostics diskette

¿ERROR occurred while reading root directory.—

1. Advanced Diagnostics diskette

¿ERROR: Please replace the backup battery!—

1. If backup battery was recently replaced, run Setup program to
configure computer.
2. Backup Battery
3. System Board

¿Error programming FLASH Device. Retrying.—

1. System Board

¿ERROR: RAM failure! Address: XXXX—

1. Inspect memory modules for proper installation.
2. Swap the installed memory modules with known good modules.
3. Memory Board
4. System Board

¿ERROR: RAM failure! SIMM module: XXXX—

1. Inspect the memory modules for proper installation.
2. Swap the installed memory modules with known good modules.
3. Memory Board
4. System Board

¿ERROR: ROM checksum failure!—

1. Power-off computer, wait 15 seconds, then power-on computer. If the message reappears, replace system board.

¿ERROR: System control processor failure!—

1. Power-off computer, wait 15 seconds, then power-on computer. If message reappears, replace system board.

¿ERROR: The image file is not for this machine.—

1. Correct Advanced Diagnostics diskette?
2. Advanced Diagnostics diskette

¿ERROR: Timer interrupt failure!—

1. Power-off computer, wait 15 seconds, then power-on computer. If message reappears, replace system board.

¿ERROR: Wild Hardware Interrupt.—

1. Power-off computer, wait 15 seconds, then power-on computer. Rerun the program.
2. If message reoccurs at the same place during operation of a program, it is probably software related. Have the customer contact the software manufacturer or dealer to report problem.
3. System Board

¿Fatal Error; Cannot Continue!—

1. Refer to first error message and follow instructions to resolve the problem.

¿File not found, try another diskette.—

1. Try another Advanced Diagnostics diskette.

¿FLASH Device failure! Device content has been corrupted.—

1. System Board

¿High ROM Checksum Error! Flash ROM needs to be reprogrammed—

1. BIOS within the Flash ROM is corrupt. The NEWBIOS command will automatically be executed. See ¿Updating Flash Memory—.

¿Low ROM Checksum Error! Flash ROM needs to be reprogrammed—

1. See ¿Updating Flash Memory—.

¿Non-maskable interrupt received!—

1. If a software problem is suspected, have the customer contact the software manufacturer or dealer and report the problem.
2. Run Advanced Diagnostics.
3. AC Adapter

¿No system—

1. Install the operating system. Refer to the operating systemdocumentation for instructions.
2. Retry the boot command syntax and verify a valid drive was selected.

¿Not a bootable partition—

1. Retry the boot command syntax and make certain a valid partition was selected.
2. Back up the hard disk, if possible, and run PREP to reinitialize the disk (see ¿Running PREP—). Reformat disk and install operating system.
3. Hard Disk Drive

¿Overflow!—

1. Power-off computer, wait 15 seconds, then power-on computer. If message reappears during power up, replace system board.
2. If a software problem is suspected, try another copy of the program, or have the customer contact the software manufacturer or dealer and report the problem.

¿Password Security Violation: System Shutdown—

1. Power-off computer, wait 15 seconds, then power-on the computer.
2. Retry the password. If password is unknown, clear the password
(see ¿Power-on Password—).

¿Program verify failure.—

1. System Board

¿Remove diskette and insert again, otherwise reboot.—

1. Try another Advanced Diagnostics diskette.
2. System Board

¿Retries exhausted, please remove diskette.—

1. Try another Advanced Diagnostics diskette.
2. System Board

¿Slush BIOS Checksum Error!—

1. System Board

¿Slush RAM Data Error!—

1. System Board

¿Slush Video Checksum Error!—

1. System Board

¿Wild Interrupt!—

1. Power-off computer, wait 15 seconds, then power-on computer. Rerun the program.
2. If the message reoccurs at the same place during the operation of a program, it is probably software related. Have the customer contact the software manufacturer or dealer to report problem.
3. If the message reoccurs randomly, run Advanced Diagnostics. Replace any faulty assemblies.

Search Keywords

Hint Category

Hardware Maintenance Information

Date Created

12-12-96

Last Updated

01-05-98

Revision Date

28-04-99

Brand

IBM ThinkPad

Product Family

Notebook N45

Machine Type

2614

Model

Various

TypeModel

Retain Tip (if applicable)

N/A

Reverse Doclinks
and Admin Purposes