| Previous | Next |
| STATUS_NO_BROWSER_SERVERS_FOUND | STATUS_DRIVER_CANCEL_TIMEOUT |
STATUS_VDM_HARD_ERROR
Diagnose the 16-bit guest and NTVDM state together
STATUS_VDM_HARD_ERROR is explicitly an NTVDM hard-error status. NTVDM is the compatibility environment used for DOS and 16-bit Windows applications on supported 32-bit Windows systems. It is not included with 64-bit Windows. The process visible to modern diagnostic tools can therefore be ntvdm.exe while the meaningful workload is a 16-bit guest application inside it.
The message does not identify the guest instruction, DOS/Win16 component, device interaction, or compatibility transition that caused the hard error. A useful investigation must retain both layers. Microsoft process-creation documentation also notes that 16-bit applications are simulated by NTVDM rather than represented as ordinary individual processes, and creation flags can affect whether NTVDM is shared or created separately.
Record the 16-bit executable, NTVDM instance, command line, current directory, creation flags, console mode, and the first exception or compatibility event before the hard error. Reproduce with a separate VDM where applicable to distinguish corruption/state shared inside an NTVDM instance from an application-specific failure. Do not replace the status with “ntvdm.exe crashed” in logs; that loses the guest identity needed to find the real trigger.
What to inspect
- Identify the exact DOS/Win16 program hosted by the failing NTVDM instance.
- Capture earlier segment, console, or exception events; the hard error is often too late to explain the initiating condition by itself.
- Compare shared versus separate VDM execution when process-creation policy allows it.
References
- Microsoft: NTVDM and 16-bit app support
- Microsoft: Process creation flags
- Microsoft: Legacy Console Mode
- Microsoft: Windows console changes
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.