What does Windows error code 593 (ERROR_VDM_HARD_ERROR) mean?

ERROR_VDM_HARD_ERROR

What this result means

ERROR_VDM_HARD_ERROR is a Windows system result. The failure belongs to the legacy NTVDM compatibility environment. It can represent an unrecoverable emulation, device, executable-format, or application fault that cannot be handled as an ordinary DOS error.

Likely causes

• the legacy application executed unsupported behavior or accessed unavailable hardware
• the virtual DOS environment or its configuration files are damaged
• a 16-bit module, driver, or memory manager is incompatible
• the workload is being attempted on a Windows edition or architecture without supported NTVDM capability

Where this code is usually encountered

• A DOS or 16-bit virtual machine reports a hardware-style fault to the host.
• An emulator maps a guest device or instruction failure to the VDM hard-error path.
• Legacy software assumes direct hardware access unavailable on modern Windows.

Useful evidence

• guest application and emulator version
• the VDM error text, virtual device, and instruction context
• host architecture and Windows edition
• whether the same image works in a dedicated supported emulator

Troubleshooting steps

1. Confirm that the result originates from a virtual DOS environment rather than a native device driver.
2. Reproduce with optional virtual devices and compatibility hooks disabled.
3. Capture the guest state immediately before the error, including loaded TSRs and memory managers.
4. Move the workload to a supported VM or emulator and compare virtual hardware configuration.

Guidance for developers

Modern applications should not depend on VDM behavior. Emulator developers should surface the underlying guest exception or virtual-device failure instead of collapsing every problem into a generic hard error.

Guidance for administrators

Host hardware replacement is rarely justified by this code alone. Preserve the legacy environment and migrate it as a unit to a supported virtualization solution.

How to interpret it correctly

Despite the wording, this does not by itself prove a physical host-hardware failure; “hard error” belongs to the compatibility subsystem’s reporting model.

Example failure pattern

A typical case reproduces only with a particular TSR, virtual device, memory manager, or direct-I/O instruction in the guest. Removing components one at a time from the legacy boot sequence is more informative than changing modern Windows drivers unrelated to the emulated device.

Retry and recovery policy

Restarting the isolated virtual machine is acceptable after preserving guest state. Repeated host restarts add little; migrate the legacy image or correct the emulator configuration when the same guest action consistently triggers the error.

References

• Microsoft: System error codes 500–999
• Microsoft: System error codes