Computing.Net > Forums > OS/2 > TRAP 000d ERROR

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.

TRAP 000d ERROR

Reply to Message Icon

Name: J ROMA
Date: October 8, 1999 at 08:02:16 Pacific
Comment:

I AM RUNNING OS/2 2.1 AND HAVE AN TRAP 0000d ERROR. WHAT DOES IT MEAN AND HOW CAN I FIX IT?



Sponsored Link
Ads by Google

Response Number 1
Name: Karla
Date: October 8, 1999 at 18:19:10 Pacific
Reply:

A trap 000d is a general protection fault. This is like when a program allocates an array with 10 elements, then references the 11th (goes after unallocated memory).

To pinpoint the failing program, you can look at the registers. Usually when you get a trap you get a black screen with white text. The text are the contents of the registers at the time of the trap. Looking at the registers is a bit complex. Since you are running OS/2 2.1, I don't believe IBM will provide support. Here are some general guidelines that may help:

- Did the trap always happen or did it just start?
- If the trap just started, did you load anything recently? Have you tried removing it?
- Does the trap happen at bootup? If so, at what point? If it happens during the loading of device drivers (when you see the OS/2 logo on the screen), it could mean that you are having hardware failure. A trap 000d is almost always caused by software any almost never hardware. But twice I've seen a failing SCSI drive cause a Trap D on boot.
- Does the trap 000d happen only when you use a certain application? If so, have you contacted the vendor for that application for assistance?
- Do you have a second PC installed with the same levels of code? If so, does the problem happen on both computers?

Without more information, I really can't provide much help. Two very skilled IBM'ers wrote a RED book call the OS/2 Debugging Handbook, SG24-4640-00. (Red books are IBM technical references.) If you get ahold of the OS/2 Debugging Handbook and are used to diagnosing problems from hex dumps, you may find your answer.

If you are stuck, you can email me the following information and I will take a look at it (no promises though):
- The model and brand PC are you running OS/2 2.1 on. Plus what video chipset is in the PC (like Matrox, S3Trio V64+, etc)
- The version of OS/2 (result of the ver /r command) It will be 6.222 or something like that. OS/2 WARP V3 with fixpack 10 applied is 8.234.
- The CS:EIP and CSLIM register contents. (Like CS:EIP = 0053:000034a3
CSLIM = 00004fe1 )
- Description of when the trap occurs.

Good Luck.

KJS


0
Reply to Message Icon

Related Posts

See More







Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to OS/2 Forum Home


Sponsored links

Ads by Google


Results for: TRAP 000d ERROR

Trap 000d www.computing.net/answers/os2/trap-000d/2249.html

trap 000d OS/2 Warp 4 www.computing.net/answers/os2/trap-000d-os2-warp-4/2111.html

Trap 000D / 000E Problem www.computing.net/answers/os2/trap-000d-000e-problem/1208.html