Probably not a best question to ask, but: What's the most spooky/evil NTSTATUS code? All NTSTATUS codes can be found in ntstatus.h. So far I have STATUS_DISK_CORRUPT_ERROR which translates to
The file system structure on the disk is corrupt and unusable.
, STATUS_FT_READ_RECOVERY_FROM_BACKUP, which translates to
To satisfy a read request, the NT fault-tolerant file system successfully read the requested data from a redundant copy.
This was done because the file system encountered a failure on a member of the fault-tolerant volume, but was unable to reassign the failing area of the device.
, STATUS_FIRMWARE_UPDATED (of course when no BIOS has been updated):
Windows has detected that the system firmware (BIOS) was updated [previous firmware date = %2, current firmware date %3].
and of course STATUS_ACCESS_VIOLATION:
The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
I tried searching following keywords: unfixable, corrupt, critical, failure, fault.
The file system structure on the disk is corrupt and unusable.
, STATUS_FT_READ_RECOVERY_FROM_BACKUP, which translates to
To satisfy a read request, the NT fault-tolerant file system successfully read the requested data from a redundant copy.
This was done because the file system encountered a failure on a member of the fault-tolerant volume, but was unable to reassign the failing area of the device.
, STATUS_FIRMWARE_UPDATED (of course when no BIOS has been updated):
Windows has detected that the system firmware (BIOS) was updated [previous firmware date = %2, current firmware date %3].
and of course STATUS_ACCESS_VIOLATION:
The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
I tried searching following keywords: unfixable, corrupt, critical, failure, fault.
