home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 36 Tips
/
36-Tips.zip
/
AU0002.FAX
< prev
next >
Wrap
Text File
|
1994-11-30
|
2KB
|
59 lines
Causes of Trap0002 2/28/94
TRAP0002 (MEMORY FAILURE) ERRORS RUNNING OS/2 VERSION 2.X
DESCRIPTION OF SYMPTOMS:
Getting TRAP0002 (Memory Failure) error running OS/2 Version 2.0.
SUMMARY OF RESOLUTION:
The four possible causes of a TRAP0002 error are:
110 Error - System Board Memory Parity Error
111 Error - Memory Expansion Adapter Parity Error
112 Error - Watchdog Timer Error (Could be Hardware or
Software)
113 Error - DMA Arbitration Error (Could be Hardware or
Software)
DETAILS OF RESOLUTION:
1. Run CHKDSK C: /f to correct corrupt files where 'C' is the drive
being verified. (CHKDSK should be run on all drives.) Refer to
documentation for correct procedure if running fault tolerance
or local security.
2. The most common type of TRAP0002 error is caused by memory,
but it may on some occasions be caused by a system board or a
micro channel adapter failure.
3. Mismatched memory simms from different manufactures or
different classes can cause a TRAP0002 error. For example,
1x9 bit simms cannot be mixed with 1x3 bit simms.
4. Some timing problems may occur because OS/2 Version 2.0 is a
32 bit operating system that takes data in 32 bit words. DOS
and other operating systems do not stress the memory as OS/2
does. DOS is a single task operating system while OS/2 is
multi-tasking. This feature stresses the memory in an OS/2
environment more than in a DOS environment.
5. TRAP0002 errors can also be caused by two hardware devices
accessing the same Direct Memory Access (DMA), channels, or
by interrupt conflicts. Contact the hardware supplier for
correct adapter setup.
Last Updated: 2/25/94
12/31/99