Article View: comp.os.ms-windows.nt.misc
Article #209Re: NT Blue Screen
From: Dan Guisinger
Date: Sat, 18 Jul 1998 00:00
Date: Sat, 18 Jul 1998 00:00
38 lines
2864 bytes
2864 bytes
Its the driver. A few things have happened here, but I'll try to explain it. The IRQL (Interrupt Request Level) is a way of prioritizing events that happen in the kernel. A TRAP is an interrupt request, and a KMODE_EXCEPTION is a fault cased by software error (like accessing non-existing memory). The trap and the exception were unhandled, and the process was at too high of an IRQL to recover (a higher IRQL can not be interrupted, and virtual memory might not have been accessable or something like that). It appears it might be using Paged memory when it can't pull it from disk (As it triggers the EXCEPTION, it can't handle it, as it can't interrupt the process). Now, if you wrote the driver, switch it to NonPaged memory. If you know the person who wrote it, have them do it. Otherwise, if its a commercial driver, COMPLAIN. Make Noise. That is a *BIG* programming mistake. -Dan Guisinger Quantum Warp Laboratories Trinity Operating System Development Team Damien Spanjer wrote in message <01bdb2bb$8358b820$8d1c12cb@damien.netwit.net.au>... >I'm having trouble with my NT 4 Workstation. I am constantly getting blue >screens with the following STOP error messages: > >UNEXPECTED_KERNEL_MODE_TRAP >KMODE_EXCEPTION_NOT_HANDLED >IRQL_NOT_LESS_OR_EQUAL > >Can anyone tell me what they mean? > >I've checked most of the hardware for errors. The only thing left is the >CPU. Could it be faulty? > >Any info regarding this problem would be greatly appreciated. Thanks in >advance. :) >
Technical Details
Message-ID:
<6orq0t$rkq$1@ash.prod.itd.earthlink.net>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<01bdb2bb$8358b820$8d1c12cb@damien.netwit.net.au>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 10de39,c9f47c975f077dbe,start X-Google-Attributes: gid10de39,public X-Google-Thread: fb9cd,c9f47c975f077dbe,start X-Google-Attributes: gidfb9cd,public X-Google-Thread: 104ed6,c9f47c975f077dbe,start X-Google-Attributes: gid104ed6,public X-Google-Thread: fdb6e,c9f47c975f077dbe,start X-Google-Attributes: gidfdb6e,public X-Google-Thread: 115e93,c9f47c975f077dbe,start X-Google-Attributes: gid115e93,public X-Google-Thread: 1018aa,c9f47c975f077dbe,start X-Google-Attributes: gid1018aa,public X-Google-Thread: 10e551,c9f47c975f077dbe,start X-Google-Attributes: gid10e551,public X-Google-Thread: 10eb20,c9f47c975f077dbe,start X-Google-Attributes: gid10eb20,public From: "Dan Guisinger" <danrg@sprintmail.com.---> Subject: Re: NT Blue Screen Date: 1998/07/18 Message-ID: <6orq0t$rkq$1@ash.prod.itd.earthlink.net> X-Deja-AN: 372798536 References: <01bdb2bb$8358b820$8d1c12cb@damien.netwit.net.au> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Organization: EarthLink Network, Inc. Newsgroups: comp.os.ms-windows.nt.misc,comp.os.ms-windows.nt.setup.hardware,comp.os.ms-windows.programmer.nt.kernel-mode,cz.comp.windows.nt,dk.edb.ms-windows.nt,microsoft.public.windowsnt.misc,thenet.support.windowsnt,tnn.os.windows-nt,utexas.comp.windows-nt