| |
|
|
| |
|
| |
Description |
|
| |
|
|
| |
The Remote Proceedure Call driver MSRPC.SYS likely has a bug.
Some older versions of Windows may show the description as "MSRPC_STATE_VIOLATION". This is a fatal Windows error, typically called a Stop message, Bug Check, or more commonly the Blue Screen of Death (BSoD). The system is in a forced reboot state. Any unsaved work is likely lost.
|
|
| |
|
|
| |
Sample Screen |
|
| |
|
|
| |
|
A problem has been detected and Windows has been shut down to prevent damage to your computer.
The kernel mode RPC facility has detected that a state violation has occurred. If this is the first time you've seen this Stop error screen, restart your computer. If this screen appears again, follow these steps:
Check to make sure any new hardware or software is properly installed. If this is a new installation, ask your hardware or software manufacturer for any Windows updates you might need.
If problems continue, disable or remove any newly installed hardware or software. Disable BIOS memory options such as caching or shadowing. If you need to use Safe Mode to remove or disable components, restart your computer, press F8 to select Advanced Startup Options, and then select Safe Mode.
Technical Information:
*** STOP: 0x00000112
Beginning dump of physical memory
Physical memory dump complete.
Contact your system administrator or technical support group for further
assistance. |
|
|
| |
Text may appear differently depending on where the error occurs.
Additional technical information (hex values) specific to a machine are not shown. |
|
| |
|
|
| |
Key Facts |
|
| |
|
|
| |
Full Title |
|
The kernel mode RPC facility has detected that a state violation has occurred.
|
Stop Code |
|
0x00000112
|
Type |
|
Fatal
|
|
Windows |
|
Vista, 2008, 7, 8
|
Vendor |
|
Microsoft Corporation |
|
|
| |
|
|
| |
Solutions and Fixes |
|
| |
|
|
| |
|
Update or disable the MSRPC.SYS device driver. |
| |
|
|
FaultWire Staff
Posted: 2-Sep-2009 |
|
|
|
Install the latest Windows software updates. Don't forget to check for non-critical updates too!
To manually get updates, open Internet Explorer (you can't use a non-Microsoft browser for updates).
For IE 8 and later: Click on Safety, then Windows Update. Follow the instructions.
For IE 7 and older: Click on Tools, then Windows Update. Follow the instructions.
|
| |
|
|
FaultWire Staff
Posted: 5-Oct-2008 |
|
|
Also see our list of common Fatal Error Solutions. |
|
| |
|
|
| |
Forum Help |
|
| |
|
|
| |
 |
Check out what others say about this issue and review or add your own comments and solutions!
Go to Forums on topic. |
|
|
| |
|
|
| |
Technical Details |
|
| |
|
|
| |
| |
 The Msrpc.sys driver (Microsoft Remote Procedure Call) has initiated a bug check.
After the Stop code will be 1 or more hex values: {Parameter 1, Parameter 2, Parameter 3, Parameter 4}.
Parameter 1 specifies the cause of the issue.
| 0x00000001 |
A non-continuable exception was continued by the caller. |
| 0x00000002 |
The advanced local procedure call (ALPC) returned an invalid error. |
| 0x00000003 |
The caller unloaded the Microsoft remote procedure call (MSRPC) driver while it was still in use. It is likely that open binding handles remain. |
0x00000004
|
An invalid close command was received from the ALPC. |
| 0x00000005 |
An invalid close command was received from the ALPC. |
| 0x00000006 |
An attempt was made to bind a remote procedure call (RPC) handle a second time. |
| 0x00000007 |
An attempt was made to perform an operation on a binding handle that was not bound. |
| 0x00000008 |
An attempt was made to set security information on a binding handle that was already bound. |
| 0x00000009 |
An attempt was made to set an option on a binding handle that was already bound. |
0x0000000A
|
An attempt was made to cancel an invalid asynchronous remote procedure call. |
| 0x0000000B |
An attempt was made to push on an asynchronous pipe call when it was not expected. |
0x0000000C
|
An attempt was made to push on an asynchronous pipe without waiting for notification. |
| 0x0000000E |
An attempt was made to push on an asynchronous pipe without waiting for notification. |
| 0x0000000F |
An attempt was made to synchronously terminate a pipe a second time. |
| 0x00000015 |
An RPC internal error occurred. |
| 0x00000016 |
Two causally ordered calls were issued in an order that cannot be enforced by the RPC. |
| 0x00000017 |
A server manager routine did not unsubscribe from notifications prior to completing the call. |
| 0x00000018 |
An invalid operation on the asynchronous handle occurred. |
Parameter 2 depends on the value of Parameter 1.
|
|
|
| |
|
|
| |
Vendor Summary |
|
| |
|
|
| |
|
|
| |
|
|
| |
|
While BSoD fatal stop errors are identified by Microsoft Windows, they are often caused by
non-Microsoft applications, drivers and hardware issues. |
|
| |
|
|
| |
Research this Issue |
|
| |
|
|
| |
Getting search results...
|
|
| |
|
|
| |
Notes |
|
| |
|
|
| |
While we believe this information up to date and accurate, FAQware is not responsible for any inaccuracies. If you find something that is out of date or inaccurate, please let us know at
so we can correct it. |
|
| |
|
|
