BSOD 104 (FILE_INITIALIZATION_FAILED): causes and diagnosis

Status / error code:		Category:

Constant name:
Source:		Operating System:
Description: File-system or file object initialization failed during early Windows startup.

Could be also:
Constant	Type	OS
ERROR_INVALID_AT_INTERRUPT_TIME	Win32 error	Windows
ECONNRESET	errno	Linux
ENOTRECOVERABLE	errno	Mac
EBADMSG	errno	Windows

Previous	Next
CONFIG_INITIALIZATION_FAILED	IO1_INITIALIZATION_FAILED

FILE_INITIALIZATION_FAILED

File subsystem initialization failure for FILE_INITIALIZATION_FAILED

FILE_INITIALIZATION_FAILED is bug check code 0x00000068. This bug check points at early file subsystem initialization: object namespaces, file-system drivers, boot volumes, filters, or file-object infrastructure did not become usable in time for startup.

How to read it in a dump

The failing stack should show whether storage, file system, filter manager, object manager, or cache manager is involved.
Do not reduce it to a single missing file unless the dump or boot logs prove that.
Boot-start filters and system file corruption are common evidence to check.

What to check

Check boot-start storage and file-system filters, system file integrity, and boot volume health.
Review recent filter-driver, antivirus, encryption, or backup product updates.
Use boot logging and crash dump analysis together.

References

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 file / initialization.
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.