EXFAT_FILE_SYSTEM
Code: 0x12c (300)
As HRESULT:- S: 0 (Success)
- C: 0 (Microsoft-defined)
- N: 0 (Not an NTSTATUS value)
- Facility: 0x000 (FACILITY_NULL: Default)
- Code: 0x012c (300)
- Sev: 0 (STATUS_SEVERITY_SUCCESS)
- C: 0 (Microsoft-defined)
- Facility: 0x000 (Default)
- Code: 0x012c (300)
Parameters
| Parameter | Description |
|---|---|
| 1 | Specifies source file and line number information. The high 16 bits (the first four hexadecimal digits after the "0x") determine the source file by its identifier number. The low 16 bits determine the source line in the file where the bug check occurred. |
| 2 | If FppExceptionFilter is on the stack, this parameter specifies the address of the exception record. |
| 3 | If FppExceptionFilter is on the stack, this parameter specifies the address of the context record. |
| 4 | Reserved. |
Description
The EXFAT_FILE_SYSTEM bug check has a value of 0x0000012C. This bug check indicates that a problem occurred in the Extended File Allocation Table (exFAT) file system.
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
This bug check is caused by the file system as a last resort when its internal accounting is in an unsupportable state and to continue poses a large risk of data loss. The file system never causes this bug check when the on disk structures are corrupted, the disk sectors go bad, or a memory allocation fails. Bad sectors could lead to a bug check, for example, when a page fault occurs in kernel code or data and the memory manager cannot read the pages. However, for this bug check, the file system is not the cause.
Resolution
To debug this problem: Use the .cxr (Display Context Record) command together with Parameter 3, and then use kb (Display Stack Backtrace).
Article text from the Windows driver documentation (opens in a new tab), by Microsoft, under the CC BY 4.0 (opens in a new tab) licence.
Associated Modules
| Module | Code | Found in | Description |
|---|---|---|---|
| ESENT.dll | 0x12c | 8.11011 | %1 (%2) %3The database engine is initiating recovery steps. |
| EventCreate.exe | 0x12c | 78.11011 | %1 |
| KernelBase.dll | 0x12c | 78.1 | The oplock request is denied. |
| dxgkrnl.sys | 0x12c | 11 | Generic Monitor |
| kernel32.dll | 0x12c | 78.11011 | The oplock request is denied. |
| microsoft-windows-system-events.dll | 0x12c | 1011 | Microsoft-Windows-Kernel-AppCompat |
| ntdll.dll | 0x12c | 8.11011 | The file image hash is valid. |
| pmem.sys | 0x12c | 1011 | Persistent memory disk %1 is now in read-only mode. Use the Get-PhysicalDisk command to get the device’s health status. The Microsoft-Windows-PersistentMemory-PmemDisk/Operational event log may also contain more information. |
| pwrshmsg.dll | 0x12c | 78.11011 | Provider Health: %1. Details: %2 |
| webservices.dll | 0x12c | 78.11011 | The value '%1' could not be parsed as a qualified name. |
| 10 entries | |||