BSOD 55 (FLOPPY_INTERNAL_ERROR): causes and diagnosis

Status / error code:		Category:

Constant name:
Source:		Operating System:
Description: Windows stopped because the legacy floppy driver reported internal state corruption.

Could be also:
Constant	Type	OS
ERROR_DEV_NOT_EXIST	Win32 error	Windows
ENOANO	errno	Linux
ENOBUFS	errno	Mac
EBADSLT	errno	Solaris

Previous	Next
DEVICE_REFERENCE_COUNT_NOT_ZERO	SERIAL_DRIVER_INTERNAL

FLOPPY_INTERNAL_ERROR

Legacy floppy driver internal failure for FLOPPY_INTERNAL_ERROR

FLOPPY_INTERNAL_ERROR is bug check code 0x00000037. This bug check belongs to the old floppy storage path. It is most useful when a dump or boot trace still shows the floppy controller driver, emulated floppy hardware, or firmware-provided legacy disk device state.

How to read it in a dump

Treat it as a storage-driver or legacy-device crash, not as a generic disk-full condition.
On virtual machines, check whether a virtual floppy device is still presented to the guest.
The driver stack and device object are more useful than the symbolic name alone.

What to check

Remove unused virtual floppy devices from VM settings.
Check boot-start storage drivers and firmware settings if the crash happens during startup.
Use the dump stack to decide whether the failure is a real controller path, an emulator, or stale legacy configuration.

References

Dump evidence

Preserve the complete dump, the four bug-check parameters, the exact Windows build, loaded-module list, and the event timeline immediately before the stop. AllStat summarizes the condition as “this result”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.

Analysis order

Run WinDbg !analyze -v, then inspect the documented meaning of each parameter instead of relying only on the probably-caused-by line.
find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with floppy / internal.
keep third-party filter, security, storage, graphics, and virtualization drivers in the module inventory; removing evidence before dump analysis can obscure the responsible path.

Do not repeatedly reboot a machine affected by this result before collecting the dump and event logs. Recovery actions should follow the component identified by the stack and parameters, not merely the symbolic stop-code name.

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