EFS_FATAL_ERROR

Code: 0x1d7 (471)

As HRESULT:

S: 0 (Success)
C: 0 (Microsoft-defined)
N: 0 (Not an NTSTATUS value)
Facility: 0x000 (FACILITY_NULL: Default)
Code: 0x01d7 (471)

As NTSTATUS:

Sev: 0 (STATUS_SEVERITY_SUCCESS)
C: 0 (Microsoft-defined)
Facility: 0x000 (Default)
Code: 0x01d7 (471)

Parameters

Parameter	Description
1	Bug Check Subclass: 01 - Pre-offloading failure.
2	NTSTATUS return code of the operation.
3	The current IRP at the time of failure.
4	File encryption context at the time of failure.

Description

The EFS_FATAL_ERROR bug check has a value of 0x000001D7. It indicates that an EFS error condition has occurred such that cannot be handled without data loss or data corruption.

Important
This article is for programmers. If you're a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.

Cause

An EFS error condition has occurred such that cannot be handled without data loss or data corruption.

Resolution

The !analyze debug extension displays information about the bug check and can be helpful in determining the root cause.

Examine parameter 2 the NTSTATUS field to try and determine why NT_SUCCESS was not returned. This is the expected and only allowed value for file systems that call crypto pre-offloading.

Use the debugger !IRP command to investigate parameter 3 for a possible conflicting IRP code or other issues.

Associated Modules

Module	Code	Found in	Description
ESENT.dll	0x1d7	8.11011	%1 (%2) %3Unable to rollback operation #%4 on database %5. Error: %6. All future database updates will be rejected.
EventCreate.exe	0x1d7	78.11011	%1
kernel32.dll	0x1d7	11	The system does not support this version of the CimFS image.
webservices.dll	0x1d7	78.11011	The maximum allowed policy extensions of %1 for the document was exceeded.
4 entries