| Previous | Next |
| APP_TAGGING_INITIALIZATION_FAILED | FSRTL_EXTRA_CREATE_PARAMETER_VIOLATION |
DFSC_FILE_SYSTEM
DFS client file-system failure for DFSC_FILE_SYSTEM
DFSC_FILE_SYSTEM is bug check code 0x0000010B. This bug check is a DFS client-side counterpart to DFS namespace handling. It points to client referral/cache/path state, redirector interaction, or filters in the UNC namespace path.
How to read it in a dump
- Use the stack to distinguish DFS client, MUP, SMB redirector, WebDAV, and third-party file-system filters.
- The failing workload can be target failover, referral cache update, reconnect, cleanup, or namespace traversal.
- It is not enough to test the server; the client-side namespace path can be the failing component.
What to check
- Check DFS namespace targets, referral timeouts, SMB redirector events, and file-system filters.
- Reproduce with a specific UNC path and compare behavior when bypassing DFS to a direct target.
- Correlate with network transitions and offline/online state.
References
- Microsoft clustering / DFS documentation
- Microsoft Bug Check Code Reference
- Crash dump files and WinDbg
Dump evidence
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 “this result”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.
Analysis order
- Run WinDbg
!analyze -v, then inspect the documented meaning of each parameter instead of relying only on the probably-caused-by line. - find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with dfsc / 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 this result before collecting the dump and event logs. 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.