cofiredm.dll

Associated Error Codes

Below lists error codes and symbolic names found for this module.

CodeFound inDescription
0x61011The system file %1 was corrupted, which may have caused the application %2 to stop working. Windows was unable to repair this file (error code %3). Run the command "sfc /scannow" at an administrative command prompt to check for errors and to repair the file if necessary.
0x81011The system file %1 was corrupted, which may have caused the application %2 to stop working. Windows attempted to repair the file. A reboot is required to finish this repair.
0xa1011The system file %1 may be corrupted, but Windows could not determine if the file was actually damaged (error code %3). No repair action was taken. Run the command "sfc /scannow" at an administrative command prompt to check for errors and to repair the file if necessary.
0xb1011The system file %1 is corrupted, which may have caused the application %2 to stop working. Windows could not attempt to repair %1 because a previous repair operation was pended. Reboot the computer and run the command "sfc /scannow" at an administrative command prompt to check for errors and to repair the file if necessary.
0xc1011Windows detected that program file %1 is corrupted, causing application %2 to stop working. To restore the file, reinstall %3 version %4.
0xe1011The file %1 may be corrupted, which may have caused the application %2 to stop working. Windows did not attempt to repair %1 because it could not find its corresponding installer package.
0x500000011011Critical
0x500000021011Error
0x500000031011Warning
0x500000041011Information
0x900000011011Microsoft-Windows-CorruptedFileRecovery-Server
0x900000021011System
0x900000031011Microsoft-Windows-CorruptedFileRecovery-Server/Operational
0x910000011011Microsoft-Windows-CorruptedFileRecovery-Client
0x910000021011Microsoft-Windows-CorruptedFileRecovery-Client/Operational
0xb00000011011The file %1 may be corrupted, which may have caused the application %2 to stop working. Windows did not attempt to repair %1 because it is not a protected system file.
0xb00000021011The system file %1 is corrupted, which may have caused the application %2 to stop working. Windows will not attempt to repair %1 because too many corrupted files have been detected recently. Frequent corruptions may indicate a problem with the disk on this computer.
0xb00000031011The system file %1 may be corrupted, which may have caused the application %2 to stop working. Windows did not attempt to repair this file because the same file has been repaired too many times over a recent period of time.
0xb00000041011The system file %1 is corrupted, which may have caused the application %2 to stop working. Windows did not attempt to repair this file because a repair attempt is already underway for the same file.
0xb00000051011The system file %1 was reported as being corrupted but Windows determined that the file is not actually damaged. It may have been repaired already.
0xb00000071011The system file %1 was corrupted, which may have caused the application %2 to stop working. Windows successfully repaired the damaged file.
0xb00000091011The system file %1 may be corrupted, which may have caused the application %2 to stop working. Windows attempted to repair the file, but the operation was cancelled before it could be completed. Run the command "sfc /scannow" at an administrative command prompt to check for errors and to repair the file if necessary.
0xb000000d1011The program file %1 was reported as being possibly corrupted, causing application %2 to stop working. Windows performed additional diagnostics and determined that the file is not actually damaged.
0xb000000f1011Windows detected that program file %1 is corrupted, causing application %2 to stop working. Reinstalling %3 version %4 may repair the file. However, Windows is not launching a %3 reinstallation because too many product reinstalls have run recently.
0xb00000101011Windows detected that program file %1 is corrupted, causing application %2 to stop working. Reinstalling %3 version %4 may repair the file. However, Windows is not launching a %3 reinstallation because that product has already been reinstalled too many times recently.
0xb00000111011The program file %1 was reported as being possibly corrupted, causing application %2 to stop working. Windows performed additional diagnostics and determined that the file is not an executable image. To avoid potential user data loss, Windows will not attempt to repair the file.
0xb10000011011The system file %1 may be corrupted, which may have caused the application %2 to stop working. Windows could not repair this file automatically (error code %3). Run the command "sfc /scannow" at an administrative command prompt to check for errors and to repair the file if necessary.
0xb10000021011The system file %1 may be corrupted, which may have caused the application %2 to stop working. Windows attempted to repair the file, but the operation was disabled by group policy. Run the command "sfc /scannow" at an administrative command prompt to check for errors and to repair the file if necessary.
0xb10000031011The system file %1 is corrupted, which may have caused the application %2 to stop working. Windows could not attempt to repair %1 because the operation was disabled by group policy. Run the command "sfc /scannow" at an administrative command prompt to check for errors and to repair the file if necessary.
29 entries