OSRLogo
OSRLogoOSRLogoOSRLogo x Seminar Ad
OSRLogo
x

Everything Windows Driver Development

x
x
x
GoToHomePage xLoginx
 
 

    Thu, 20 Sep 2018     118014 members

   Login
   Join


 
 
Contents
  Online Dump Analyzer
OSR Dev Blog
The NT Insider
Downloads
ListServer / Forum
Driver Jobs
  Express Links
  · The NT Insider Digital Edition - May-June 2016 Now Available!
  · Windows 8.1 Update: VS Express Now Supported
  · HCK Client install on Windows N versions
  · There's a WDFSTRING?
  · When CAN You Call WdfIoQueueP...ously

Must Succeed Pool...DEAD!

When allocating pool, do not specify pool type NonPagedPoolMustSucceed. In XP, this pool type has been declared reserved, and can legally be used only to support the boot-up process. Attempts to use Must Succeed pool on XP will be "caught" by Driver Verifier.

Start updating your drivers now. Must Succeed pool is out. If you get a failure, you can either retry or fail the operating you're trying to perform in your driver. Yeah, I know it's annoying. But my sources tell me people were using this feature gratuitously, leading to unnecessary O/S bug checks. What's that you guys say about "one bad apple"?

Related Articles
Who Owns Which Pool Tag
No Pool Tagging for Special Pool
Permanent Pool Overrun Checking Starting With XP SP2
ExAllocatePoolWithQuota Raises Exceptions
Pool and Memory Events

User Comments
Rate this article and give us feedback. Do you find anything missing? Share your opinion with the community!
Post Your Comment

Post Your Comments.
Print this article.
Email this article.
bottom nav links