This Microsoft Answers article recommends running an SFC (system file check). This did not solve the problem for me, but it is something you should try first.
Here’s how I cleared it up: A summary of what this does: By temporarily turning off virtual memory, you allow yourself to delete the (now-corrupt) paging file.
My SQL Enterprise Backup adds CRC32 checksum support in 3.8.1, with some limitations.
Refer to the My SQL Enterprise Backup 3.8.1 Change History for more information.
You can also use raw disk partitions as data files. Using a battery-backed disk cache in the SCSI disk controller or in the disk itself speeds up file flushes, and makes the operation safer.