BSOD 66 (ATDISK_DRIVER_INTERNAL): causes and diagnosis

Status / error code:		Category:

Constant name:
Source:		Operating System:
Description: ATDISK_DRIVER_INTERNAL

Could be also:
Constant	Type	OS
ERROR_BAD_DEV_TYPE	Win32 error	Windows
EREMOTE	errno	Linux
ENOTEMPTY	errno	Mac
EREMOTE	errno	Solaris

Previous	Next
MUST_SUCCEED_POOL_EMPTY	NO_SUCH_PARTITION

ATDISK_DRIVER_INTERNAL

ATDISK_DRIVER_INTERNAL is bug check 0x42. Microsoft classifies it as very infrequent and does not publish meanings for the four bug-check parameters. The symbolic name identifies an internal stop-code category; it is not, by itself, proof that a physical disk failed or that a particular ATA command was rejected.

Do not diagnose from the historical name alone

The useful evidence is the dump from the exact failing Windows build. Keep all four raw arguments, load matching symbols, and inspect the stack and modules active at the stop. A storage filter, controller path, or unrelated corruption may be visible in the dump, but those are findings to establish from evidence rather than meanings assigned to 0x42.

What to preserve

Record the Windows build and all four arguments exactly as displayed.
Run !analyze -show 0x42 to see debugger-known information for that build, then use !analyze -v on the dump.
Compare repeated crashes by stack and module version before replacing storage hardware.

References

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