Bug Check 0x103: MUP_FILE_SYSTEM
The MUP_FILE_SYSTEM bug check has a value of 0x00000103. This bug check indicates that the multiple UNC provider (MUP) has encountered invalid or unexpected data. As a result, the MUP cannot channel a remote file system request to a network redirector, the Universal Naming Convention (UNC) provider.
Important Info If You Have Received a STOP Code
If you received a blue screen error, or stop code, the computer has shut down abruptly to protect itself from data loss. A hardware device, its driver, or related software might have caused this error. If your copy of Windows came with your computer, call the manufacturer of your computer. If you purchased Windows separately from your computer, Microsoft provides support. To find contact info for Microsoft or your computer manufacturer, Contact Support.
If you have experience with computers and want to try to recover from this error, follow the steps provided in the Microsoft article Resolving STOP (Blue Screen) Errors in Windows.
These actions might prevent an error like this from happening again:
- Download and install updates and device drivers for your computer from Windows Update.
- Scan your computer for computer viruses.
- Check your hard disk for errors.
MUP_FILE_SYSTEM Parameters
These bug check parameters are displayed on the blue screen. Parameter 1 identifies the type of violation.
| Parameter 1 | Parameter 2 | Parameter 3 | Parameter 4 | Cause of error |
|---|---|---|---|---|
|
0x1 |
The address of the pending IRP. |
The address of the file object whose file context could not be found. |
The address of the device object. |
The MUP could not locate the file context that corresponds to a file object. 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 likely cause of this bug check is a filter driver error. |
|
0x2 |
The address of the expected file context. |
The address that was actually retrieved from the file object. |
Reserved |
A file context is known to exist for the file object, but was not what was expected (for example, it might be NULL). |
|
0x3 |
The address of the IRP context. |
The IRP completion status code. |
The driver object of the UNC provider that completed the IRP (might be NULL). |
The IRP completion status was unexpected or invalid. This bug check occurs only when you are using a Checked Build of Windows and should only be caused by file system filter drivers that are attached to legacy network redirectors. Legacy redirectors use FsRtlRegisterUncProvider to register with MUP. This bug check detects filter drivers that return an NTSTATUS that is not STATUS_SUCCESS in IRP_MJ_CLEANUP or IRP_MJ_CLOSE requests. |
|
0x4 |
Address of the IRP |
Address of the file object |
The file context for the file object |
An I/O operation was started on a file object before the create request for the file object was completed. |
Remarks
The MUP maintains context information on a per-file object basis for all file objects it handles.
Send comments about this topic to Microsoft
Build date: 4/9/2013
