GPF: RQL_NOT_LESS_OR_EQUAL - what is this?

[Frank Dreyfus]

I am getting a protection error "RQL_NOT_LESS_OR_EQUAL" that forces me to
reboot.

I searched for this in the KB but came up empty.

Is there any info on what causes this?

Thanks, Frank

[tweak2x]

this is usually caused by your video card. It also can mean that your IRQ's
are conflicting. Do you own a Nvidia card?

"Frank Dreyfus" <fdre...@nyw.com> wrote in message
news:Xns929D6D5F62111ad...@207.46.239.39...

[Frank Dreyfus]

"tweak2x" <twe...@carolina.rr.com> wrote in
news:OYuAaV7aCHA.2004@tkmsftngp12:

> this is usually caused by your video card. It also can mean that your
> IRQ's are conflicting. Do you own a Nvidia card?

That makes sense since I just replaced my graphics card. The new one is a
Trident Blade 3D w/8mb. It's made by Jaton Corp.

It is an inexpensive card.

Thanks, Frank

[tweak2x]

have you downloaded the latest drivers from the manufacturers website? and
have you red the manuals about the card? perhaps it dosnt like being close
to a sound card due to static or such.

"Frank Dreyfus" <fdre...@nyw.com> wrote in message

news:Xns929D78338D1EFad...@207.46.239.39...

[Alexander Grigoriev]

It doesn't have anything with IRQ! It is IRQL (IRQ level), not IRQ!

IRQL_LESS_OR_EQUAL bugcheck occurs when one of IRQL restrictions is
violated. It occurs because a driver doesn't conform to the kernel
environment rules. For example, it tries to wait for a waitable object while
on DISPATCH level, or touches a non-present page on DISPATCH_LEVEL.

There are the following IRQ levels:

PASSIVE_LEVEL (0) - all preemptible application and kernel threads run on
this level. A page fault is allowed to occur, it will bring the memory page
back from the pagefile. It means, that the thread can touch pageable
(virtual) memory. The thread can wait for a waitable object. The thread can
yield execution to another thread (or be preempted by a scheduler).

APC_LEVEL - (1 - Asynchronous Procedure Call level) the threads have
sometimes run on it, when the APC is delivered to a thread. A page fault is
allowed.

DISPATCH_LEVEL (2) - DPC (deferred procedure calls) are delivered on this
level. The execution is NON preemptible. Page faults NOT allowed. Pageable
memory CANNOT be touched. Waitable objects CANNOT be waited, but can be
checked and signalled. For synchronization, the software running on
DISPATCH_LEVEL can use so called spinlocks.

DIRQL (all levels from 3 to 31) - ISR (interrupt service routine) level. A
hardware interrupt with higher level can occur when an ISR for lower level
is running. More restrictions: simple spinlock cannot be used, only special
interrupt spinlocks. Waitable objects CANNOT even be signalled.

"tweak2x" <twe...@carolina.rr.com> wrote in message
news:OYuAaV7aCHA.2004@tkmsftngp12...