Attempt to use an invalid printer change notification handle

A handle that was not opened with the FindFirstPrinterChangeNotification Microsoft Win32 API function was passed as a printer change notification handle.

The sample debugger output below illustrates the following troubleshooting steps:

• To see the stack trace of the routine that attempted this action, use the �k' command in the debugger.
  
  
• Identify the routine by locating the function call in the stack trace that references the handle identified by Parameter 1.
  
  

After you identify the routine that references the handle, find this routine in the source code and determine why an invalid handle was used.

�

Copy Code

======================================= VERIFIER STOP 0000A008 : pid 0x1268: Attempt to use an invalid printer change notification handle 00001237 : Printer change notification handle being accessed. 00000000 : Not used. 00000000 : Not used. 00000000 : Not used. ======================================= 0:000> k ChildEBP RetAddr 0020f5f8 7332385b ntdll!DbgBreakPoint 0020f7fc 71366481 vrfcore!VerifierStopMessageEx+0x4bd 0020f834 7136839d vfprint!CResourceUsageMgr<void *,CHandleTracker_t<void *> >::ClosedHandl eCheck+0xc7 0020f8d8 0014335f vfprint!VfHookFindClosePrinterChangeNotification+0x111 0020f8e4 00142edc UnitTestvfPrint!CloseANonExistingNotificationHandle+0xf * The routine that uses invalid printer change notification handle

Parameter 1 - Printer change notification handle being accessed.

Parameter 2 - Not used.

Parameter 3 - Not used.

Parameter 4 - Not used.

Test Layer:�PrintAPI

Stop code:�0000A008

Severity:�Error

One-time error:�no

Error report:�Break

Log to file:�yes

Create backtrace:�yes