| Previous | Next |
| ERROR_FLOPPY_UNKNOWN_ERROR | ERROR_DISK_RECALIBRATE_FAILED |
ERROR_FLOPPY_BAD_REGISTERS
The floppy disk controller returned inconsistent results in its registers.
ERROR_FLOPPY_BAD_REGISTERS is Win32 error 1125 (0x465). The floppy driver received a controller result phase, but the register values did not form a coherent outcome for the command that had been issued. This points toward controller communication, emulation, or hardware-state corruption rather than a normal filesystem error.
What “inconsistent” means in practice
A floppy controller returns several status and position values after an operation. The driver expects combinations that agree about completion, selected head, cylinder, and error state. Code 1125 is used when those values contradict one another or cannot safely describe the completed request.
- unstable controller or bus communication
- a drive or cable fault that disrupts the command/result sequence
- virtual floppy emulation with incorrect register behavior
- driver timing problems around interrupts, DMA, reset, or result-byte reads
- hardware that is only partially compatible with the expected controller model
Evidence that should not be lost
- all result registers in the order read, not merely the final Win32 code
- the command bytes and requested cylinder/head/sector
- interrupt, DMA, reset, and timeout events around the command
- controller identity, bus path, firmware, driver, and hypervisor versions
- whether the inconsistency repeats with a known-good disk and a no-data command
Because a reset changes controller state, collect the register snapshot first. A log generated only after automatic recovery may show a clean controller and conceal the contradictory values that triggered 1125.
Diagnostic steps
- compare the exact result pattern with the controller specification or emulator contract
- test the same medium in another drive and the same drive with known-good media
- disable optional acceleration or unusual DMA settings in a controlled test
- check whether failures follow host load or virtual-machine timing
- use a driver trace or kernel debugger when the result-reading sequence itself is suspect
Filesystem tools are not the first diagnostic layer. Until the controller returns a trustworthy sector result, higher-level metadata repair cannot establish that the bytes being examined came from the requested location.
Recovery guidance
A single controlled reset and reopen may recover from transient controller state, but repeated resets without capturing status are poor diagnostics. Persistent failures call for a different drive, controller, bridge, or emulator. Preserve unique media and avoid write commands until the path is reliable.
Software should classify this as a device-path integrity problem and include the operation coordinates. A generic “retry later” message is insufficient when the controller may be returning data for the wrong location.
Distinction from ERROR_FLOPPY_UNKNOWN_ERROR
ERROR_FLOPPY_UNKNOWN_ERROR means the controller error could not be mapped to a recognized category. ERROR_FLOPPY_BAD_REGISTERS specifically says the returned register set was self-contradictory or invalid for the command outcome.
Example
Under heavy host load, a virtual floppy controller reports a successful seek but returns a result cylinder that does not match either the command or the selected track. The guest raises 1125. Capturing the register sequence demonstrates an emulator timing defect; replacing the disk image would not solve it.
References
Looking for a different code? Search another status or error code.