Bug Check 0x112: MSRPC_STATE_VIOLATION
The MSRPC_STATE_VIOLATION bug check has a value of 0x00000112. This indicates that the Msrpc.sys driver has initiated a bug check.
Important
This article is for programmers. If you're a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.
MSRPC_STATE_VIOLATION Parameters
Parameters 1 and 2 are the only parameters of interest. Parameter 1 indicates the state violation type; the value for Parameter 2 is determined by the value of Parameter 1.
| Parameter 1 | Parameter 2 | Cause of Error |
|---|---|---|
0x01 |
The exception code |
A non-continuable exception was continued by the caller. |
0x02 |
The error |
The advanced local procedure call (ALPC) returned an invalid error. |
0x03 |
The session to the server |
The caller unloaded the Microsoft remote procedure call (MSRPC) driver while it was still in use. It is likely that open binding handles remain. |
0x04 and 0x05 |
The session to the server |
An invalid close command was received from the ALPC. |
0x06 |
The binding handle |
An attempt was made to bind a remote procedure call (RPC) handle a second time. |
0x07 |
The binding handle |
An attempt was made to perform an operation on a binding handle that was not bound. |
0x08 |
The binding handle |
An attempt was made to set security information on a binding handle that was already bound. |
0x09 |
The binding handle |
An attempt was made to set an option on a binding handle that was already bound. |
0x0A |
The call object |
An attempt was made to cancel an invalid asynchronous remote procedure call. |
0x0B |
The call object |
An attempt was made to push on an asynchronous pipe call when it was not expected. |
0x0C and 0x0E |
The pipe object |
An attempt was made to push on an asynchronous pipe without waiting for notification. |
0x0F |
The pipe object |
An attempt was made to synchronously terminate a pipe a second time. |
0x15 |
The object closest to the error |
An RPC internal error occurred. |
0x16 |
Reserved |
Two causally ordered calls were issued in an order that cannot be enforced by the RPC. |
0x17 |
The call object |
A server manager routine did not unsubscribe from notifications prior to completing the call. |
0x18 |
The async handle |
An invalid operation on the asynchronous handle occurred. |
Cause
The most common cause of this bug check is that the caller of the Msrpc.sys driver violated the state semantics for such a call.