What does NTSTATUS 0x4000001A (STATUS_LOG_HARD_ERROR) mean?

 
Previous Next
STATUS_WAS_LOCKED STATUS_ALREADY_WIN32

STATUS_LOG_HARD_ERROR

The message belongs to the Windows hard-error notification path

STATUS_LOG_HARD_ERROR is an informational status whose message template contains two insertion fields for an application-popup style message. The important diagnostic data is therefore the completed message and the component that raised the hard error; the numeric status alone omits the inserted title and detail text.

Windows exposes kernel hard-error mechanisms through IoRaiseHardError and IoRaiseInformationalHardError. The WDK describes them as ways to warn a user about device I/O failures or other informational hard errors. Thread hard-error mode also matters: IoSetThreadHardErrorMode can suppress display behavior for a thread, and the documented routines have different behavior when hard errors are disabled. These APIs describe the public mechanism; they do not prove that every occurrence of this NTSTATUS was emitted by one particular routine.

Preserve the insertion strings before converting or aggregating the event. If a log contains only 0x4000001A, inspect the event source, calling component, device or IRP context, and any surrounding application-popup or system events. Repeatedly retrying I/O is not a generic fix: the hard-error text may identify a physical device, media problem, or component-specific condition. Also avoid treating an informational severity bit as proof that the underlying incident is harmless.

What to inspect

  • Capture both formatted insertion strings and the originating component.
  • Check thread hard-error mode when expected user notification is absent.
  • Correlate with device, IRP, and System event evidence instead of classifying by severity alone.

References

Looking for a different code? Search another status or error code.