0XC0000166

Fix STATUS_FLOPPY_WRONG_CYLINDER (0XC0000166) on Boot

Boot error on old floppy-based systems, often after hardware changes. Fix the drive geometry, update CMOS, or disable the floppy controller.

When this error hits

You're booting an older Windows NT 4.0 or Windows 2000 workstation, and instead of the usual progress bar, you get a blue screen with STATUS_FLOPPY_WRONG_CYLINDER (0XC0000166). This usually happens right after you've swapped a floppy drive, changed the BIOS battery, or replaced the motherboard on a machine that still relies on a 3.5" floppy for boot. I've also seen it on industrial PCs from the late 90s where the floppy controller is used for recovery, and the CMOS settings get reset.

The trigger is almost always a mismatch between what the BIOS thinks the floppy drive's geometry is (heads, sectors, cylinders) and what the drive actually reports. Microsoft's boot loader reads the floppy as part of the boot sequence, and if the geometry doesn't line up, it throws this exact code.

Root cause in plain English

Floppy drives aren't like modern SSDs. They have a physical layout—cylinders, heads, and sectors per track. Older BIOSes let you specify these manually, but modern ones usually default to "auto" or "1.44MB, 3.5"." When you replace a drive, the new one might be a 720K drive, or the BIOS might think it's a 2.88MB drive because of a corrupted CMOS. The boot sector from Windows NT stores its expected geometry, and when the BIOS feeds different numbers, the check fails with 0XC0000166. It's not a virus, not a RAM issue—just a classic hardware/software handshake gone wrong.

Fix it in 4 steps

  1. Enter BIOS — Reboot and press Del, F2, or F10 (depends on your motherboard). If you see a floppy drive type setting, write down what it says.
  2. Set the correct drive type — Change it to 1.44MB, 3.5" for standard drives, or 720KB, 3.5" if that's what you actually have. If there's a "auto" option, use it, but only if the drive is a standard high-density type.
  3. Disable the floppy controller if you don't need it — If you're booting from a hard drive and only get this error during memory dump or recovery, just set Drive A to None and disable the floppy controller in the peripheral settings. This is the fastest fix and works for 90% of cases.
  4. Clear CMOS — If BIOS settings are corrupted, power off, unplug, and move the CMOS jumper (or remove the battery for 30 seconds). This resets everything to defaults, which usually corrects the geometry.

If it still fails after steps 1-4

Then you're dealing with a non-standard drive or a failing one. Try these:

  • Swap in a known-good 1.44MB drive. I've seen cheap replacements with mislabeled capacities cause this exact headache.
  • Use a bootable CD or USB instead. If your system supports it, change the boot order to CD-ROM first and forget the floppy entirely. Windows NT can install from CD without a floppy if you have the right drivers.
  • Check the floppy cable—make sure pin 1 is aligned. It's easy to flip it upside down, which causes all sorts of weird geometry errors.

If you're still stuck, you can also try running winnt /ox from a DOS boot disk to recreate the boot floppies, but honestly, that's a last resort. In my experience, the geometry fix in BIOS solves 95% of these cases. The other 5% are dead drives, and no amount of CMOS fiddling brings those back.

Tip: If you're working on a vintage system, write the BIOS floppy settings on a sticky note inside the case. Future you will thank you when the battery dies again.
Related Errors in Hardware – Hard Drives
0XC00D0017 NS_E_DISK_READ (0XC00D0017) – What Actually Breaks Disk Reads 0X00000876 Fix driver install error 0X00000876 - device driver does not exist 0X00000462 Fix ERROR_FLOPPY_ID_MARK_NOT_FOUND 0X00000462 in 3 Steps External Drive Used Space Wrong – File Sizes Don't Add Up

Was this solution helpful?

EP
Erropedia Team
Tech Support Editors
The Erropedia editorial team researches and documents real-world tech errors from across Windows, Linux, macOS, networking, databases, cloud platforms, and more. Every solution is reviewed for accuracy and updated as software and systems evolve.