KeWaitForMultipleObjects crash for Count > MAXIMUM_WAIT_OBJECTS.
https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0xc--maximum-wait-objects-exceeded
What to do if someone have more then MAXIMUM_WAIT_OBJECTS?
xxxxx@gmail.com wrote:
KeWaitForMultipleObjects crash for Count > MAXIMUM_WAIT_OBJECTS.
https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0xc--maximum-wait-objects-exceededWhat to do if someone have more then MAXIMUM_WAIT_OBJECTS?
I guess you redesign your driver. Is this a theoretical question?Â
Because it’s hard to imagine a real circumstance where you would need to
wait on more than 64 objects.
You could, I suppose, use a multi-layered structure, where you have one
thread wait on the first 64 and the second thread wait on the next 64,
and have each of them trigger some master thread.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
One of my filter driver is giving me this trouble. If I have more than 64 volumes, my filter driver crashes. The count becomes > MAXIMU_WAIT_OBJECTS, since my count is no of volumes.
Definitely, I suppose I need to redesign it.
So you have to rethink your design. Divide and conquer.
Mark Roddy
On Tue, Dec 19, 2017 at 12:27 PM, xxxxx@gmail.com > wrote:
> One of my filter driver is giving me this trouble. If I have more than 64
> volumes, my filter driver crashes. The count becomes > MAXIMU_WAIT_OBJECTS,
> since my count is no of volumes.
> Definitely, I suppose I need to redesign it.
>
> —
> NTDEV is sponsored by OSR
>
> Visit the list online at: http:> showlists.cfm?list=ntdev>
>
> MONTHLY seminars on crash dump analysis, WDF, Windows internals and
> software drivers!
> Details at http:
>
> To unsubscribe, visit the List Server section of OSR Online at <
> http://www.osronline.com/page.cfm?name=ListServer>
></http:></http:>
Read KeWaitForMultipleObjects documentation, WaitBlockArray argument.