Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

System crashes with DRIVER_VERIFIER_IOMANAGER_VIOLATION in usbstor.sys


View products that this article applies to.

Symptoms

If you enable driver verifier on usbstor.sys, hibernate the system and then resume from hibernation, you may experience a system crash with bug code DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9) and the first argument equal to 228. The memory dump will point to usbstor.sys as the faulting module, specifically in the USBSTOR_FdoSetPowerD0Completion routine.


↑ Back to the top


Cause

Code 228 indicates that a driver's completion routine has not marked the IRP pending if the PendingReturned field was set in the IRP passed to it. This may cause the operating system to hang, especially if an error is returned by the stack.


↑ Back to the top


Resolution

This issue in usbstor.sys will be fixed in the next version of Windows


↑ Back to the top


Keywords: kb

↑ Back to the top

Article Info
Article ID : 2730127
Revision : 1
Created on : 1/7/2017
Published on : 7/3/2012
Exists online : False
Views : 414