Problem
What caused my computer to panic with trap type 0x0000000E?
Panic trap type 0x0000000E is fairly common, and you need a way to debug what's happening.
Solution
For information about trap type 0x0000000E panics, see the following article, written by A.P. Lawrence, mentioned here with his permission:
http://www.aplawrence.com/Unixart/trape.shtmlNOTE: Third party software mentioned in this article is neither
supported nor endorsed by SCO.NOTE: If you are using ECC memory, the panic is unlikely to be due to bad
memory. An ECC memory module contains logic
to automatically correct single bit failures such that the OS is
unaware of those failures. In the event of a a multi-bit
error, the system would have surely received an NMI (Non Maskable
Interrupt) and would have ended up, most likely, printing the
following message: "FATAL:Parity error address unknown." See also
ta106009, "What are Traps, Interrupts and Exceptions?"ta106181, "Why did my UNIX kernel 'panic'?"