| Previous | Next |
| DPC_WATCHDOG_TIMEOUT | AGP_INVALID_ACCESS |
MUP_FILE_SYSTEM
Multiple UNC Provider failure for MUP_FILE_SYSTEM
MUP_FILE_SYSTEM is bug check code 0x00000103. MUP routes UNC path opens to the appropriate network redirector. This bug check is about UNC provider selection and kernel file-system routing, not about a single remote server refusing a connection.
How to read it in a dump for MUP_FILE_SYSTEM
- Look for MUP, SMB redirector, WebDAV redirector, DFS, or third-party network provider drivers on the stack.
- The failing path can be create, referral, provider registration, cancellation, cleanup, or teardown.
- UNC prefix and provider ordering can be relevant.
What to check for MUP_FILE_SYSTEM
- Inspect installed network redirectors and file-system filters.
- Check whether the problem is limited to DFS, SMB, WebDAV, or a third-party provider path.
- Use verifier on redirector/filter drivers only with a controlled reproduction.
References for MUP_FILE_SYSTEM
Dump evidence for MUP_FILE_SYSTEM
For MUP_FILE_SYSTEM, preserve the complete dump, the four bug-check parameters, the exact Windows build, loaded-module list, and the event timeline immediately before the stop. AllStat summarizes the condition as “MUP_FILE_SYSTEM”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.
Analysis order for MUP_FILE_SYSTEM
- Run WinDbg
!analyze -v, then inspect the documented meaning of each MUP_FILE_SYSTEM parameter instead of relying only on the probably-caused-by line. - For MUP_FILE_SYSTEM, find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with mup / file / system.
- For MUP_FILE_SYSTEM, keep third-party filter, security, storage, graphics, and virtualization drivers in the module inventory; removing evidence before dump analysis can obscure the responsible path.
Do not repeatedly reboot a machine affected by MUP_FILE_SYSTEM before collecting the dump and event logs. For MUP_FILE_SYSTEM, recovery actions should follow the component identified by the stack and parameters, not merely the symbolic stop-code name.
Dump evidence for MUP_FILE_SYSTEM
For MUP_FILE_SYSTEM, preserve the complete dump, the four bug-check parameters, the exact Windows build, loaded-module list, and the event timeline immediately before the stop. AllStat summarizes the condition as “MUP_FILE_SYSTEM”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.
Analysis order for MUP_FILE_SYSTEM
- Run WinDbg
!analyze -v, then inspect the documented meaning of each MUP_FILE_SYSTEM parameter instead of relying only on the probably-caused-by line. - For MUP_FILE_SYSTEM, find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with mup / file / system.
- For MUP_FILE_SYSTEM, keep third-party filter, security, storage, graphics, and virtualization drivers in the module inventory; removing evidence before dump analysis can obscure the responsible path.
Do not repeatedly reboot a machine affected by MUP_FILE_SYSTEM before collecting the dump and event logs. For MUP_FILE_SYSTEM, recovery actions should follow the component identified by the stack and parameters, not merely the symbolic stop-code name.
Looking for a different code? Search another status or error code.