| Previous | Next |
| ERROR_FLOPPY_WRONG_CYLINDER | ERROR_FLOPPY_BAD_REGISTERS |
ERROR_FLOPPY_UNKNOWN_ERROR
The floppy disk controller reported an error that is not recognized by the floppy disk driver.
ERROR_FLOPPY_UNKNOWN_ERROR has value 1124 (0x464). It is a fallback mapping used when the floppy controller indicates failure but the driver cannot translate the returned status into a more specific known floppy error. The word “unknown” describes the driver’s interpretation, not proof that the failure is random.
Why this code needs raw context
The same Win32 value can hide different controller result bytes, emulator responses, or bridge-device statuses. A support log that records only 1124 discards the information most likely to identify whether the problem belongs to media, the drive mechanism, the controller, or a software emulation layer.
- uncommon controller status combinations not covered by the driver mapping
- faulty or partially compatible USB floppy bridges
- virtual controllers that return values outside the expected hardware model
- driver defects or firmware revisions with undocumented behavior
- electrical or mechanical faults that leave ambiguous result registers
Useful diagnostics
- the complete controller result phase or device-specific status bytes
- command issued, cylinder/head/sector, transfer size, and data rate
- driver, firmware, hypervisor, and USB bridge versions
- whether the same medium fails identically in a different drive
- whether a known-good disk also triggers the code on the same hardware
The two cross-tests separate the medium from the device path: a single disk failing everywhere favors media damage, while every disk failing on one controller favors hardware, firmware, or emulation.
Investigation approach
- reproduce with read-only commands and preserve the first raw status before reset
- compare the unknown result with documented controller or emulator status definitions
- test a known-good medium using the same geometry and density
- remove adapters or conversion layers one at a time when possible
- capture driver or hypervisor traces if the error exists only in a virtual environment
Repeated controller resets can erase the status that explains the original failure. Diagnostic software should snapshot registers and request parameters before attempting recovery.
Operational response
For ordinary replaceable disks, use another drive and medium after confirming the configuration. For unique data, stop broad retries, image all readable regions, and retain the hardware combination that produced each result. An emulator problem should be corrected at the image or virtual-controller boundary, not by modifying filesystem contents.
Driver developers should log the unmapped status and command so new hardware behavior can be added to the translation table. Returning 1124 without a detailed trace makes field diagnosis unnecessarily speculative.
How it differs from other floppy failures
ERROR_FLOPPY_ID_MARK_NOT_FOUND, ERROR_FLOPPY_WRONG_CYLINDER, and ERROR_FLOPPY_BAD_REGISTERS each identify a particular observed condition. Error 1124 is used when the controller reports failure but none of those specific interpretations fits.
Example
A VM imports an old floppy image and its emulated controller returns a result-byte combination the guest driver never expects. The guest reports 1124 for every read beyond track 39, while the raw image is complete. Matching the image geometry to the emulator resolves the issue without changing the archived data.
References
Looking for a different code? Search another status or error code.