KeWaitforSingleObject at DISPATCH_LEVEL.

NTDEV
1

Hi,

Is it valid to call KeWaitForSingleObject at DISPATCH_LEVEL for an event
which has been already signalled?. The timeout parameter is NULL.

In such a condition, with the Driver verifier enabled in WindowsXP, I get a
Bugcheck (C4), DRIVER_VERIFIER_DETECTED_VIOLATION with P1=3B, P2=2 and P3
= FF57FE30 P4=0.

The DDK documentation doesn’t say anything about the state of the event,
but says that at DISPATCH_LEVEL the timeout value should be NULL.

Thanks in Advance
Ram

2

No, it states you cannot wait for a non-zero wait length at DISPATCH. By
specifying a NULL you are saying wait until it is free, if it is not
currently signaled. This is different than a zero timeout where you
specify zero in the non-null timeout.

This has been covered throughout this list many times.

Pete

Peter Scott
xxxxx@KernelDrivers.com
www.KernelDrivers.com

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@securemicrotech.com
Sent: Friday, January 17, 2003 8:41 AM
To: NT Developers Interest List
Subject: [ntdev] KeWaitforSingleObject at DISPATCH_LEVEL.

Hi,

Is it valid to call KeWaitForSingleObject at DISPATCH_LEVEL for an
event
which has been already signalled?. The timeout parameter is NULL.

In such a condition, with the Driver verifier enabled in WindowsXP, I
get a
Bugcheck (C4), DRIVER_VERIFIER_DETECTED_VIOLATION with P1=3B, P2=2 and
P3
= FF57FE30 P4=0.

The DDK documentation doesn’t say anything about the state of the event,
but says that at DISPATCH_LEVEL the timeout value should be NULL.

Thanks in Advance
Ram

You are currently subscribed to ntdev as: xxxxx@kerneldrivers.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

3

I would try changing your pointer parameter to point to a LARGE_INTEGER that contains the value 0, since your NULL pointer is implying no-timeout, whereas you need to specify a timeout of zero (i.e. don’t wait).

Duane.

-----Original Message-----
From: xxxxx@securemicrotech.com
[mailto:xxxxx@securemicrotech.com]
Sent: Friday, January 17, 2003 10:41 AM
To: NT Developers Interest List
Subject: [ntdev] KeWaitforSingleObject at DISPATCH_LEVEL.

Hi,

Is it valid to call KeWaitForSingleObject at DISPATCH_LEVEL for an event
which has been already signalled?. The timeout parameter is NULL.

In such a condition, with the Driver verifier enabled in WindowsXP, I get a
Bugcheck (C4), DRIVER_VERIFIER_DETECTED_VIOLATION with P1=3B, P2=2 and P3
= FF57FE30 P4=0.

The DDK documentation doesn’t say anything about the state of the event,
but says that at DISPATCH_LEVEL the timeout value should be NULL.

Thanks in Advance
Ram

You are currently subscribed to ntdev as: xxxxx@infiniconsys.com
To unsubscribe send a blank email to xxxxx@lists.osr.com