Mac Error Codes (1 to 32767)
This should give you a place to start with cryptic error codes generated by the Mac OS itself.
NOTE: THESE ARE NOT PARIS ERRORS, THEY ARE ACTUALLY MAC OS9 ERRORS
01 Bus Error
This means the computer tried to access memory that doesn't exist. You can get this error on almost any Macintosh. If one of these computers tried to access one or more bytes beyond
the total number of bytes in RAM, you see a bus error. You should never see this error on a Macintosh Plus or SE, because address references that are out of bounds "roll over". This
means if one of these computers tries to access one byte beyond the total bytes in RAM, it actually accesses the first byte in memory. If you see this error on a Macintosh Plus or SE,
it's reporting the wrong error or having hardware problems.
02 Address Error
The Motorola 68000 microprocessor can access memory in increments of one byte (8 bits), one word (16 bits), or one long word (32 bits). The microprocessor can access a byte of
information at an odd or even memory address. But it must access a word or long word at an even memory address. So, when the microprocessor attempts to read or write a word or long
word at an odd address, you see this error. Since that's a 50/50 proposition when running random code, this one shows up quite often.
03 Illegal Instruction
The computer has a specific vocabulary of machine language instructions it can understand. If a computer tries to execute an instruction that isn't in its vocabulary, you see this error code.
It's less likely than error 02, but still very common.
04 Zero Divide Error
This error results if the microprocessor divides two numbers, and the divisor is zero. Sometimes a programmer puts these in as debugging aids, and then forgets to take them out.
05 Range Check Error
Programmers can use an instruction in the Motorola 68000 to check if a number is within a certain range. This error indicates that the number tested isn't in the specified range.
06 Overflow Error
Each number stored in a computer is given a certain amount of space. The larger the number, the more space is needed to represent the number. An overflow condition results if a
generated number is too big for its allotted space. A Motorola 68000 instruction tests for an overflow condition, and displays this error if it detects an overflow.
07 Privilege Violation
The Motorola 68000 runs in Supervisor or User mode. The Macintosh should always be in Supervisor mode, but sometimes is placed in User mode. Some of the instructions can only be
executed in Supervisor mode. If the computer attempts one of these instructions while in User mode, a Privilege Violation error results.
08 Trace Mode Error
A programmer can use a runtime debugger while in Trace mode. This allows tracing through a program one instruction at a time. You see this error if a debugger isn't installed and the
68000 is accidentally placed in Trace mode.
09 Line 1010 Trap and
10 Line 1111 Trap
There are many routines in the Macintosh ROM that can be called by placing instructions in a program that aren't in the 68000's vocabulary. When the 68000 encounters such an
instruction, it looks it up in the instruction table. This table gives the location of routines paired with each instruction. If it finds an entry in the table for the instruction, it branches to the
routine. If there's no entry for the instruction, you see one of these errors.
Error Type 10
This error occurs when a Mac OS¹s table of instructions does not match the instructions it is receiving. More understandably, it occurs when a routine is called to perform a particular
function, and that routine does not exist to catch it. Type 10 is just an error trap to prevent further instructions and routines from possibly failing and causing more problems.
Error Type 11
This error occurs mainly on Power Macintosh computers, depending on various factors. It is the result of programming errors. It represents any error (such as a bus error) in native
code; it occurs on a Power Macintosh computer when a program crashes. Generally, this occurs most often with programs meant to run with 68K Macintoshes ‹ the PowerPC chip¹s
68K emulator basically took a dive. If the error can be duplicated with extensions off, it is usually either a problem with the program, or a compatibility issue between the program and
the Mac OS version and/or its hardware configuration.
In more clear explanation, Power Macs try to emulate 68K processing just like your PC or Mac¹s Super Nintendo emulator tries to emulate that processor. If the emulator is written
poorly by it¹s programmer, what happens? Exactly. It crashes. This is usually a program error, as stated, but can also be an OS-related problem.
Troubleshooting Errors Type 10 and 11
- 1.Restart the computer. The issue could have been temporary, and rebooting may solve this.
- 2.Trash the preferences associated with the application, then reconfigure the application. Trashing Finder preferences is a recommendation from Apple.
- 3.Rebuild the desktop.
- 4.Try to duplicate the error by disabling all extensions and control panels except those that would be necessary to attempt to duplicate the error.
- 5.Zap the PRAM
- 6.It may be a software problem (with the program that seems to be causing this). Contact the software vendor.
- 7.If nothing else works, try performing a clean install of the OS. The customer should talk to Apple at this point.
- 8.Update the version of the involved software and/or the Mac OS. There might be an incompatibility issue, in which case the customer needs to talk to Apple or the program vendor. If the problem continues, particularly in the Finder, it is probably a hardware-related issue.
12 Unimplemented Core Routine
A programmer might set breakpoints in parts of a program to inspect for errors. This requires using a debugger. If a debugger isn't installed when a breakpoint occurs, you see this error
code.
13 Uninstalled Interrupt
The Macintosh uses an interrupt to identify when devices like keyboards and disk drives need service. Routines must be available in memory to tell the computer how to service the
device. If those routines aren't available, you see this error.
14 IO Core Error
15 Segment Loader Error
Macintosh programs are broken up into segments, and each program will always have at least one segment. Multiple segments allow loading parts of the program into memory to provide
more room for data in internal RAM. The segment loader is responsible for loading a needed segment into RAM. If the segment loader can't do this, you'll see this error.
16 Floating point error
This is simply an error involving the FPU (floating point unit)
17, 18, 19, 20, 21, 22, 23, and 24 - Missing Packages 0-7
The Macintosh uses packages to do specific tasks. Some of the packages are International Utilities, Binary-Decimal Conversion, Standard File Utilities, and Disk Initialization. These
packages are located in the System file. If you get these errors, you probably have a damaged System file. Error codes 15, 16, 26, 27, 30, and 31 also come up when the System file is
damaged. Try replacing the System file.
25 Memory Full Error
You've probably run out of RAM. But you can get this error when an earlier error causes the Macintosh to falsely detect an out-of-memory condition.
26 Bad Program Launch
The Macintosh couldn't execute the application opened.
27 File system map has been trashed
28 Stack Ran into Heap
This is similar to the Memory Full error. It's a good idea to save your work frequently, and keep current backups of your hard disk data. When a system crash does occur, you'll lose less
data if you've taken these precautions.
30 dsReinsert - request user to reinsert off-line volume
31 dsNotThe1 - not the disk I wanted (obsolete)
33 negZcbFreeErr - ZcbFree has gone negative
40 dsGreeting - welcome to Macintosh greeting
41 dsFinderErr - can't load the Finder error
42 shutDownAlert - handled like a shutdown error (obsolete)
43 dsSystemFileErr - can't find System file to open (obsolete)
51 dsBadSlotInt - unserviceable slot interrupt
81 dsBadSANEopcode - bad opcode given to SANE Pack4
84 menuPrgErr - happens when a menu is purged
85 dsMBarNFnd - SysErr -- cannot find MBDF
86 dsHMenuFindErr - SysErr -- recursively defined HMenus
87 dsWDEFnFnd - Could not load WDEF
88 dsCDEFnFnd - Could not load CDEF
89 dsMDEFnFnd - Could not load MDEF
98 dsNoPatch - Can't patch for particular Model Mac
99 dsBadPatch - Can't load patch resource
101 dsParityErr - memory parity error
102 dsOldSystem - System is too old for this ROM
103 ds32BitMode - booting in 32-bit on a 24-bit sys
20000 dsShutDownOrRestart - user choice between ShutDown and Restart
20001 dsSwitchOffOrRestart - user choice between switching off and Restart
20002 dsForcedQuit - allow the user to ExitToShell, return if Cancel
32767 dsSysErr - general system error (catch-all used in DSAT)
Back to BugsTroubleshooting Bugs and Troubleshooting
