Amiga problems: screen colors and their meaning (errors)

When you boot up your Amiga you are always greeted with a series of flashing screen colors. On most days the screen will change from dark gray to a couple lighter shades then white before marching on. On bad days, it flicks over to an actual color of the rainbow, each with its own heart-stopping meaning.

What do those colors mean? And what is the Amiga doing during the boot-up process in the first place?

The following is a collection of ancient and excellent information compiled from various sources.

During boot-up, the Amiga is going through a series of system checks and routines.

  1. Clear all chips of old data
  2. Disable DMA and interrupts during the selftest.
  3. Clear the screen.
  4. Check the hardware ….checks to see if 68000 processor is working.
  5. Change screen color.
  6. Do a checksum test on all ROMS.
  7. Change screen color.
  8. Beginning of system startup.
  9. Check RAM at $C0000 and move SYSBASE there
  10. Test All CHIP RAM.
  11. Change screen color.
  12. Check that software is being executed.
  13. Change screen color.
  14. Setup CHIP RAM to receive data.
  15. Link the libraries
  16. Check for additional memory and link it (FAST RAM)
  17. Turn the DMA and interrupts back on.
  18. Start a default task.
  19. Check for 68010, 68020, 68881 or other processor upgrades (accellerator / math co processor).
  20. Check to see if there is an exception or processor error
  21. If so do a system reset.

During this system test the Amiga is sending vital information to the screen with colors. If the system checks out ok, you will see the following sequence that you have seen so many times.

DARK GRAY:  The initial hardware tested OK. the 68000 is running and the registers are readable.
LIGHT GRAY: The software is coming in and seems OK.
WHITE: The initialization test have passed and the system is ready to boot.

The failure mode screen colors:

  • Turquoise (0x0CC) (A1000 only): RAM failure in the Kickstart WCS
  • Green (0x0F0) error in the lowest 256 bytes of Chip RAM. Possible causes, defective CIA-A IC or defective Agnus IC.
  • Yellow (0xFE5) an unexpected processor exception before the appropriate system failure message was prepared. This could mean defective hardware or an attempt to access a RAM address where no RAM exists.
  • Red (0xF00) invalid KickStart ROM checksum.
  • Magenta (0xF0F) single-task or cold-start initialization failed.

These problems could be caused by a number of things such as a loose chip or board.
The red screen may be caused by a loose Kickstart chip that can be fixed by pressing down on the ROM to check it is fitted correctly. Another cause could be a connection problems between the chip and socket that can be solved by straightening an bent pins.

Alternatively, the green screen could be caused by a loose memory board, SIMM, or a loose RAM chip on the memory board. If reattaching these chips do not solve the problem, try them on another Amiga.

Another listing of screen color interpretations:

REDKickstart ROM errorTwo ICs in A1200, A3000, A4000
BLUECustom chip problemDenise Paula Agnus
YELLOWAbove problems combined
LIGHT GREENCIA (U7/U300) problem
BLACKCIA (U7/U300) problemIf not booting
DARK GRAYHardware tested OK
LIGHT GRAYSoftware tested OK
LIGHT GRAYCIA (U8/U301) problemStops at gray, CIA defective
No videoR406 or R215 open R406=1 ohm R215=4.7 ohm
Video scrambledAgnus or Denise defective


The keyboard also has its own processor, RAM, and ROM. It also has a selftest that performed on power up in the following sequence.

  1. Performs checksum on ROM’s
  2. Checks 64 bytes of RAM.
  3. The timer is tested.
  4. Performs handshake with computer and gives results of self-test.

If the keyboard does not pass the test, it will tell you through the blinking of the caps lock light.

If the Amiga caps lock key LED blinks repeatedly at boot up, another series of error messages must be consulted:

  • One blink: keyboard ROM checksum error
  • Two blinks: RAM failure
  • Three blinks: watchdog timer failure
  • Four blinks: A short between two lines or the special control keys. 
  • READ THIS (please). Don’t panic if your keyboard flashes once when you switch on. THIS IS PERFECTLY NORMAL. Every Amiga in the entire universe does this.

If something is wrong with your system, you may see the following:

  • RED: Error was found in ROMS.
  • GREEN: Error found in the CHIP RAM.
  • BLUE: Error was found in the custom chips.
  • YELLOW: If 68000 found an error before the error trapping software (GURU) was running.

Guru Meditations

It’s not always obvious why your Amiga guru’s. With the codes below, you can break the meaning down to its basic components and get to the bottom of things.

Probably all Amiga owners have seen the guru at one time or another. The guru meditation is what your Amiga does when the low level error trapping routines catch an error before the computer crashes. When the higher-level routines detect the error you are given a requestor saying: ‘Software Failure. Task held. Finish ALL disk activity’, with two gadgets saying retry and cancel. Retry usually does nothing and cancel causes a guru.

The proper term for the guru is an alert. The alerts give you some useful information about why the Amiga crashed and what program caused the program to crash.


D: This indicates whether or not the software failure is recoverable or not (with the current OS none are really). A zero means that it is recoverable and any non-zero value means that it isn’t.

S: This (together with D) indicates the subsystem that generated the alert. The various subsystems are (DS):

00 .. Processor or none
01 .. Exec.Library
02 .. Graphics.Library
03 .. Layers.Library
04 .. Intuition.Library
05 .. Math.Library
06 .. Clist.Library
07 .. DOS.Library
08 .. RAM.Library
09 .. Icon.Library
10 .. Audio.device
11 .. Console.device
12 .. GamePort.device
13 .. Keyboard.device
14 .. Trackdisk.device
15 .. Timer.device
20 .. CIA.resource
21 .. Disk.resource
22 .. Misc.resource
0A .. Expansion.Library
30 .. Bootstrap
31 .. Workbench
32 .. Diskcopy

Ge: This indicates the general error. Basically telling you what went wrong. The various defined General Errors are (Ge):

01 .. No memory
02 .. Make Library
03 .. Open Library
04 .. Open Device
05 .. Open Resident
06 .. I/O Error
07 .. No Signal

Code: This gives more detail as to what went wrong. The value that appears here depends on the subsystem and general error.

TAddress: This is the Address of the task that caused the guru (where applicable).

Quite often the processor with trap an error. The operating system will then display a guru. These errors will only contain two digits (the right-most two digits in ‘Code’) and their meanings are:

00000000 Reset (SP). /Technically, these shouldn’t occur, but
00000001 Reset (PC). /they do pop up occassionally
00000002 Bus Error (memory doesn’t exist)
00000003 Address error (usually odd address access) A program probably made a jump to somewhere it shouldn’t have
00000004 Illegal instruction
00000005 Divide by zero. A program has attempted to divide a number by zero (a mathematical impossibility).
00000006 CHK instruction (Check register against boundaries)
00000007 TRAPV instruction (Trap on overflow)
00000008 Privilege violation. A program in user mode attempted to execute a privileged Instruction.
00000009 Trace (debugging)
0000000A Op Code 1010 (unimplemented instruction)
0000000B Op Code 1111 (unimplemented instruction)
0000000A & 0B A & F Line Emulation. Used with some coprocessors. Usually program is out of control.
00000018 .. Spurious interrupt.
00000019 to 1F .. Auto-Vector Interrupts – These should not happen as the OS uses them to detect what is going on with the hardware, but as with all others they do appear sometimes.
00000020 to 2F .. Trap Vectors – Usually a program is out of control.
00000030 to 3F .. These are reserved by Motorola. Any program causing these is probably out of control.
00000040 to FF .. User Interrupt Vectors – Usually a program is out of control.

Error messages

If you enter a command and comes back with an error message, typing WHY will display more
information about it. Use the FAULT command to display the error message that applies to a error

Typical error messages are:

103Insufficient free store .Free up some memory by quiting other programs
105Task table fullShutdown some programs
120Argument line invalid or too longCheck command arguments using `?`
121File is not an object moduleTry setting ‘e’ or ‘s’ protection flag.
122Invalid resident library during load
202Object in useExit program, unassign assign or close directory windows.
203Object already exists.
Cannot move the program as it exists elsewhere. Delete the original first
204Directory not foundRetype directory name
205Object not foundRetype file name
206Invalid window description
Re-enter correct window description for NEWCLI or NEWSHELL
209Packet request type unknown
210Stream name component invalid
211Invalid object lockRecheck filename
212Object not of required typeRecheck file
213Disk not validatedWait until disk is validated first.
214Disk write-protectedEnsure write tab is closed.
215Rename across devices attemptedUse copy instead
216Directory not emptyMust delete its contents first. Use DELETE ALL.
218Device (or volume) not mountedCheck device name and reinsert disk
219Seek failureCheck position in file
220Comment too bigUse shorter description in FILENOTE
221Disk fullDelete some files or use a new disk.
222File is protected from deletionEnable Delete flag with Protect
223File is write protectedEnable Write flag with Protect
224File is read protectedUse PROTECT to set ‘r’ flag.
225Not a valid DOS disk.Disk is unformatted or a protected game disk
226No disk in driveUse correct device name or insert disk
232No more entries in directoryDirectory is full, delete files or move files into new sub-dirs.


(just preserving your great information, thanks for this!) is onderdeel van TASK4 Studios
Web Analytics