The IRP completion status was unexpected or invalid. The driver object of the UNC provider that completed the IRP (might be NULL). The address that was actually retrieved from the file object.Ī file context is known to exist for the file object, but was not what was expected (for example, it might be NULL). The address of the expected file context. The likely cause of this bug check is a filter driver error. This typically indicates that the MUP is seeing an I/O request for a file object for which MUP did not see a corresponding IRP_MJ_CREATE request. The MUP could not locate the file context that corresponds to a file object. The address of the file object whose file context could not be found. Parameter 1 identifies the type of violation. If you are a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |