I have observed a file filled NULs that was caused by a power loss in the middle of a write -- my UPS alerted me that utility power is gone, I tried to shutdown cleanly, but the battery died before a clean shutdown completed. This was NTFS on a HDD and not a SSD.

I am not saying it happens often, but it does happen once in a while.

NTFS guarantees file-system metadata integrity, not file data integrity. Subtle but important difference.

The file was corrupted, but the file-system remained consistent.

Had the same on journaled ext4 on Linux. Lots of NULL bytes in the middle of the syslog because of unclean shutdown.

Yes, corruption does appear to be correlated with power cycles.

However I'm using it it certainly isn't. It's certainly quite likely the problem is me, not Windows.

Most of the files that are getting corrupted are being written to in an append-only fashion, which is generally one of the mechanisms for writing to files to avoid corruption, at least on POSIX.