Handling 'Unexpected Interrupt 0D' Errors Under NT?

Jersiais asks: "I am trying to get some command line stuff running on NT4 server with Take Control installed on an old 200MH Pentium II (Before anybody throws up, it's the test-it-&-wreck-it machine, not the real thing so there's no actual LAN there). Even on the real thing the compiler under command line has a tendency to blow up at random with 'Unexpected Interrupt 0D'. This only happens on the Pentium II, on the real (Workstation) thing it doesn't. I've found 3 different descriptions of Int 0D, none of which make any sense. Anybody any ideas how to get around it, or get rid of it? The compiler is 32-bit to interpreted intermediate and I have a RP calculator running as a test on the work system already, despite its use of soft interrupt IO."

Comments

First things first

[ObviousGuy]

What compiler?

What is crashing? The compiler? The command prompt?

What are you doing when it crashes?

Does this happen with other compilers? Other programs?

Crappy hardware

[cperciva]

Let's see... you have unexpected protection faults, you're running on antique hardware, and when you try the same code on a different machine, it works fine.

That sounds exactly like the symptoms of hardware which has exceeded its MTBF.