Windows 10磁盘间复制文件时频繁蓝屏崩溃求助

Hey Jason, sorry to hear you're stuck with this frustrating BSOD issue when copying that massive 8TB dataset—this kind of problem is such a time sink, especially after you already went through a Windows reinstall to fix it once. Let’s walk through targeted troubleshooting steps based on what you’ve shared:

WD REDs are solid, but large-scale writes can expose hidden connection or power issues:

• Swap cables/ports: If you’re using an external drive, grab a high-quality USB 3.0/3.1 cable (cheap ones often fail under heavy load). For internal drives, switch to a different SATA port on your motherboard—loose connections or faulty ports are a common culprit for BSODs during high-throughput tasks.
• Run WD’s official diagnostics: Fire up WD Drive Utilities to do a full scan of both source and target drives. System-level tools like Disk Manager might miss low-level sector or cache issues, especially since RED drives are optimized for NAS/JBOD setups.
• Check power supply: 8TB drives draw more power during sustained writes. If you’re using an external drive without a dedicated power adapter, try plugging it into a powered USB hub. For internal drives, make sure your PSU has enough headroom—old or underpowered units can cause voltage dips that trigger system crashes.

Default Windows settings can overload system resources when handling huge files:

• Disable write cache flushing temporarily: Go to Device Manager → Disk Drives → Right-click your target drive → Properties → Policy → Uncheck "Enable write caching on the device" (note: this reduces data safety if you lose power, so revert it after copying).
• Use Robocopy with low-overhead parameters: The standard Robocopy command might be using too much cache. Try this instead:

  robocopy "C:\SourceFolder" "D:\TargetFolder" /E /Z /W:5 /R:3 /J
  

  The /J flag uses unbuffered I/O (perfect for large files), /Z enables restartable mode so you don’t lose progress if a crash happens, and /W:/R: sets retry delays.
• Pause background tasks: Disable Windows Update, scheduled disk defragmentation (for mechanical drives), and any backup tools during the copy—these can compete for disk bandwidth and cause conflicts.

BSODs leave clues, so let’s track them down:

• Enable minidumps: Right-click This PC → Properties → Advanced System Settings → Startup and Recovery → Settings → Make sure "Write debugging information" is set to "Small memory dump (256KB)". After the next crash, head to C:\Windows\Minidump and use WinDbg (free from the Microsoft Store) to analyze the dump file. Look for driver names (often disk/storage controller drivers) that are flagged as the cause.
• Update storage controller drivers: Go to Device Manager → Storage controllers → Right-click your controller (e.g., Intel SATA AHCI Controller) → Update driver. Use the manufacturer’s official driver from your motherboard’s website instead of Windows’ generic driver—these often fix compatibility issues with large storage setups.
• Install pending Windows updates: Even after a fresh reinstall, there might be critical cumulative updates that patch storage subsystem bugs. Run Windows Update and install everything available, especially updates labeled for storage or file systems.

Since you’ve used JBOD before, let’s check that angle:

• Recreate the JBOD array: If you’re using Windows’ software JBOD, delete the array and set it up again. Sometimes metadata corruption from initial setup can cause intermittent write failures under heavy load.
• Test the drive outside JBOD: Pull the target drive from the JBOD array and connect it directly to your PC (as a standalone drive). If the copy completes without crashing, the issue is with the JBOD configuration or controller—you might need to switch to a hardware JBOD controller or adjust your array settings.

内容的提问来源于stack exchange，提问作者Jason