Windows & BSOD · high

How to fix0xC0000006

0xC0000006 - In-Page Read Error

What this error means

0xC0000006 shows up as a high-severity Windows operating system fault. An in-page read error occurred, meaning the system tried to load a file from memory but failed due to read/write hardware timeouts. Commonly occurs when launching games/apps from external drives or network shares. Follow the steps below to fix it.

Before you begin

Save open work and back up important files. Use instructions for your exact device and software version. If Windows cannot start, see the startup guide.

Work through these checks

0 of 4 complete
01Run CHKDSK tool to identify bad sectors
  1. Run CHKDSK tool to identify bad sectors
What to expect

Check whether the original symptom still occurs.

If it does not help

Continue only if this check applies to your device. Consult its manufacturer if you are unsure.

Browse related errors
02Inspect and replace SATA or USB connection cables
  1. Inspect and replace SATA or USB connection cables
What to expect

Check whether the original symptom still occurs.

If it does not help

Continue only if this check applies to your device. Consult its manufacturer if you are unsure.

Browse related errors
03Perform clean boot to rule out antivirus locks
  1. Perform clean boot to rule out antivirus locks
What to expect

Check whether the original symptom still occurs.

If it does not help

Continue only if this check applies to your device. Consult its manufacturer if you are unsure.

Browse related errors
04Check drive health status using CrystalDiskInfo
  1. Check drive health status using CrystalDiskInfo
What to expect

Check whether the original symptom still occurs.

If it does not help

Continue only if this check applies to your device. Consult its manufacturer if you are unsure.

Browse related errors

Possible causes

  • Bad sectors or block read errors on drive
  • Loose or damaged external USB/SATA connection cables
  • Network share disconnection or packet drop
  • Antivirus software file locking conflicts