Slashdot Mirror

← Back to Stories (view on slashdot.org)

Handling 'Unexpected Interrupt 0D' Errors Under NT?

Posted by Cliff on from the low-level-serial-programming dept.

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."

6 of 59 comments (clear)

  1. Finally.. by Noodlenose · · Score: 5, Funny
    It had to happen one day:

    This is officially the first /. post I don't understand.

    At all.

    Damn..

  2. First things first by ObviousGuy · · Score: 5, Insightful

    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?

    --
    I have been pwned because my /. password was too easy to guess.
  3. Ralph Brown's interrupt list.. by Jon-o · · Score: 5, Informative

    I know next to nothing on the subject, but when I was tinkering about back in the good ole' DOS days, I came across this list of interrupts: http://www.delorie.com/djgpp/doc/rbinter/

    I expect most people have seen it. It lists the following fod 0d:

    0D INT 0D C - IRQ5 - FIXED DISK (PC,XT), LPT2 (AT), reserved (PS/2)
    0D INT 0D C - IRQ5 - Tandy 1000 60 Hz RAM REFRESH
    0D INT 0D - HP 95LX - INFRARED INTERRUPT
    0D INT 0D C - CPU-generated (80286+) - GENERAL PROTECTION VIOLATION

  4. Crappy hardware by cperciva · · Score: 4, Insightful

    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.

    --
    Tarsnap: Online backups for the truly paranoid
  5. 0D by adolf · · Score: 5, Informative

    It's not an NT error, but an Intel one, dating back to the Beginning of Time (or the 6MHz 286, anyway). The same errors are reported in the same way under OS/2, and probably a number of other operating systems - I seem to recall Win95 puking out similar nomenclature during at least one BSOD.

    Under OS/2, such screaching halts are known as "traps," instead of blue screens. And since OS/2 users were generally more knowledgable about computers then, than NT users are today, there's a lot of information available to help with fixing it.

    According to groups.google.com-archived message from 1993, 0D is a General Protection Fault.

    GPFs happen all the time with bunky hardware. Try re-seating (or just purchasing new) RAM, CPU, and anything else socketed that you can find.

    And if that doesn't work, toss the machine. Or give it away to someone with stubborn enough to fix it. Different boxes of similar ilk are available in the $50 range, these days - no need to spend any absurd amount of time with a diagnosis.

    --
    Kid-proof tablet..
  6. Re:What the hell... by realgone · · Score: 5, Funny
    Maybe the problem is that you don't know what you're doing.
    Either that or I'm a half-drunk asshole. Either answer wouldn't surprise me.
    We should also consider the possibility that you're half-drunk *because* you don't know what you're doing. I mean, come on -- you posted this at 1 a.m. and you *still* weren't fully hoisted yet? What were you drinking, Tequiza or something?

    Get with the program, people...