Hello,

I have a driver than runs on ksproxy for my hardware device. The driver
works but I have intermittent issues on enable/disable of the driver which
will generate the IRQL_NOT_LESS_OR_EQUAL exception and kill the machine. The
driver was made with DriverStudio's tool derived from their KsDevice. I'm
trying to track down whether it's something I've done (with bad use of spin
locks perhaps) or if it's something in the DriverStudio framework. Has
anyone had similar issues or have some suggestions for tools/techniques to
nail down the issue. I'm using SoftIce as my debugger right now but the
error doesn't happen in my functions, that I've been able to trap.

It seems to happen (at least on enabling the driver) after I receive an
IRP_MN_QUERY_DEVICE_RELATIONS which I don't handle directly.

Thanks for any help!

Re: Debugging IRQL_NOT_LESS_OR_EQUAL by Ivan

Ivan
Mon Nov 21 18:20:07 CST 2005

You'll have to get the debugger to show you the call stack that led to the
crash. It will help you.

"El-Korik" <ElKorik@discussions.microsoft.com> wrote in message
news:40644BAC-CA9C-4EFE-8215-B33BC35CBFE4@microsoft.com...
> Hello,
>
> I have a driver than runs on ksproxy for my hardware device. The driver
> works but I have intermittent issues on enable/disable of the driver which
> will generate the IRQL_NOT_LESS_OR_EQUAL exception and kill the machine.
> The
> driver was made with DriverStudio's tool derived from their KsDevice. I'm
> trying to track down whether it's something I've done (with bad use of
> spin
> locks perhaps) or if it's something in the DriverStudio framework. Has
> anyone had similar issues or have some suggestions for tools/techniques to
> nail down the issue. I'm using SoftIce as my debugger right now but the
> error doesn't happen in my functions, that I've been able to trap.
>
> It seems to happen (at least on enabling the driver) after I receive an
> IRP_MN_QUERY_DEVICE_RELATIONS which I don't handle directly.
>
> Thanks for any help!