55
T r o u b l e s h o o t i n g
POWER ON SELF TEST MESSAGES
The following is an alphabetic list of error-and-status
messages that Phoenix BIOS and/or your operating
system can generate and an explanation of each message.
Error messages are marked with an *. If an error message
is displayed that is not in this list, write it down and
check your operating system documentation both on
screen and in the manual. If you can find no reference
to the message and its meaning is not clear, contact
your support representative for assistance.
nnnn Cache SRAM Passed
Where nnnn is the amount of system cache in kilobytes
success-fully tested by the Power On Self Test. (This can
only appear if you have an SRAM PC Card installed.)
*Diskette drive A error or Diskette drive B error
Drive A: or B: is present but fails the BIOS Power On Self
Test diskette tests. Check to see that the drive is defined
with the proper diskette type in the Setup Utility,
(See
BIOS Setup Utility on page 25 for more information)
and
that the diskette drive is installed correctly. If the disk
drive is properly defined and installed, avoid using it and
contact your support representative.
*Extended RAM Failed at offset: nnnn
Extended memory not working or not configured prop-
erly. If you have an installed memory upgrade module,
verify that the module is properly installed. If it is prop-
erly installed, you may want to check your Windows
Setup to be sure it is not using unavailable memory
until you can contact your support representative.
nnnn Extended RAM Passed
Where nnnn is the amount of memory in kilobytes
successfully tested.
*Failing Bits: nnnn The hex number nnnn
This is a map of the bits at the memory address (in
System, Extended, or Shadow memory) which failed the
memory test. Each 1 (one) in the map indicates a failed
bit. This is a serious fault that may cause you to lose data
if you continue. Contact your support representative.
*Fixed Disk x Failure or Fixed Disk Controller
Failure (where x = 1-4)
The fixed disk is not working or not configured properly.
This may mean that the hard drive type identified in
your setup utility does not agree with the type detected
by the Power On Self Test. Run the setup utility to check
for the hard drive type settings and correct them if
necessary. If the settings are OK and the message appears
when you restart the system, there may be a serious fault
which might cause you to lose data if you continue.
Contact your support representative.
*Incorrect Drive A type – run SETUP
Type of floppy drive A: not correctly identified in Setup.
This means that the floppy disk drive type identified in
your setup utility does not agree with the type detected
by the Power On Self Test. Run the setup utility to
correct the inconsistency.
*Incorrect Drive B type – run SETUP
Type of floppy drive B: not correctly identified in Setup.
This means that the floppy disk drive type identified in
your setup utility does not agree with the type detected
by the Power On Self Test. Run the setup utility to
correct the inconsistency.
*Invalid NVRAM media type
Problem with NVRAM access. In the unlikely case that
you see this message you may have some display prob-
lems. You can continue operating but should contact
your support representative for more information.
*Keyboard controller error
The keyboard controller test failed. You may have to
replace your keyboard or keyboard controller but may
be able to use an external keyboard until then. Contact
your support representative.
*Keyboard error
Keyboard not working. You may have to replace your
keyboard or keyboard controller but may be able to
use an external keyboard until then. Contact your
support representative.
*Keyboard error nn
BIOS discovered a stuck key and displays the scan code
for the stuck key. You may have to replace your keyboard
but may be able to use an external keyboard until then.
Contact your support representative.
*Monitor type does not match CMOS – Run SETUP
Monitor type not correctly identified in Setup. This error
probably means your BIOS is corrupted, run the setup
utility and set all settings to the default conditions. If you
still get this error, contact your support representative.
*Operating system not found
Operating system cannot be located on either drive A: or
drive C: Enter the setup utility and see if both the fixed
disk, and drive A: are properly identified and that the
boot sequence is set correctly. Unless you have changed
your installation greatly, the operating system should be
on drive C:. If the setup utility is correctly set, your hard
drive may be corrupted.
*Parity Check 1 nnnn
Parity error found in the system bus. BIOS attempts
to locate the address and display it on the screen. If it
cannot locate the address, it displays ????. This is a
potentially data destroying failure. Contact your
support representative.
falcon.book Page 55 Friday, August 4, 2006 11:12 AM
Summary of Contents for A3110 - LifeBook Notebook Computer
Page 1: ...Fujitsu LifeBook A3110 Notebook User s Guide falcon book Page 1 Friday August 4 2006 11 12 AM ...
Page 2: ...falcon book Page 2 Friday August 4 2006 11 12 AM ...
Page 9: ...1 Preface falcon book Page 1 Friday August 4 2006 11 12 AM ...
Page 13: ...3 2 Getting to Know Your LifeBook Notebook falcon book Page 3 Friday August 4 2006 11 12 AM ...
Page 31: ...21 3 Getting Started falcon book Page 21 Friday August 4 2006 11 12 AM ...
Page 39: ...29 4 User Installable Features falcon book Page 29 Friday August 4 2006 11 12 AM ...
Page 55: ...45 5 Troubleshooting falcon book Page 45 Friday August 4 2006 11 12 AM ...
Page 71: ...61 6 Care and Maintenance falcon book Page 61 Friday August 4 2006 11 12 AM ...
Page 77: ...67 7 System Specifications falcon book Page 67 Friday August 4 2006 11 12 AM ...
Page 83: ...73 8 Glossary falcon book Page 73 Friday August 4 2006 11 12 AM ...
Page 123: ...falcon book Page 113 Friday August 4 2006 11 12 AM ...
Page 124: ...falcon book Page 114 Friday August 4 2006 11 12 AM ...
Page 125: ...falcon book Page 115 Friday August 4 2006 11 12 AM ...
Page 126: ...falcon book Page 116 Friday August 4 2006 11 12 AM ...
Page 127: ...falcon book Page 117 Friday August 4 2006 11 12 AM ...
Page 128: ...falcon book Page 118 Friday August 4 2006 11 12 AM ...