What raises IRQL?

[Michael_Wade]

I am having a problem as when my xxxEvtDeviceControl is getting called it appears to be running at IRQL = 2, which I believe is dispatch level. But
the EvtDeviceControl is being called from a device property page. Why is the IRQL getting raised? Is it because it’s coming from the property page
provider? Thanks

[Peter_Viscarola_OSR]

(Aside: Why are you making this a new topic? We’re we already discussing this here: http://www.osronline.com/cf.cfm?PageURL=showThread.CFM?link=198441 ??)

Soooooo… as I said in reply to your previous question:

The simple answer is that the IRQL is elevated because you didn’t specify an
ExecutionLevel constraint. If you expected to be called at IRQL PASSIVE_LEVEL,
the way you ensure this will happen is by specifying the appropriate constraint.
Otherwise, the IRQL at which you’ll be called will be <= DISPATCH_LEVEL.

Doron also asked “What did you specify as your synchronization scope?”

Let’s start there…

Peter
OSR

[Michael_Wade]

I made a mistake. Sorry about that. I thought that I was having a memory access violation in that first post. And I posted the second before any
replies came through on my news server. Again, sorry.

On Wed, 26 Jan 2011 14:57:30 -0500 (EST), xxxxx@osr.com wrote:

(Aside: Why are you making this a new topic? We’re we already discussing this here: http://www.osronline.com/cf.cfm?PageURL=showThread.CFM?link=198441 ??)

Soooooo… as I said in reply to your previous question:

The simple answer is that the IRQL is elevated because you didn’t specify an
ExecutionLevel constraint. If you expected to be called at IRQL PASSIVE_LEVEL,
the way you ensure this will happen is by specifying the appropriate constraint.
Otherwise, the IRQL at which you’ll be called will be <= DISPATCH_LEVEL.

Doron also asked “What did you specify as your synchronization scope?”

Let’s start there…

Peter
OSR