2025年11月19日 星期三

windows using up C drive

 

The most common reasons why ntoskrnl.exe (the Windows kernel) causes constant disk access and fills up your C: drive are system-level logging, memory dumps, or runaway services like Windows Search or Superfetch.

Here’s a breakdown of what might be happening and how to investigate:


🧠 Possible Causes of Disk Usage by ntoskrnl.exe

  1. Memory Dump Files (e.g., MEMORY.DMP)

    • After a crash or BSOD, Windows may write a full memory dump to C:\Windows\MEMORY.DMP, which can be several GB in size.
    • Check: Open C:\Windows and sort by size to see if MEMORY.DMP or similar files are growing.
  2. Windows Error Reporting Logs

    • Located in C:\ProgramData\Microsoft\Windows\WER, these can accumulate if error reporting is frequent and not cleaned up.
  3. Windows Search Indexing

    • The SearchIndexer.exe service can cause heavy disk I/O, especially after updates or if many files are added.
    • Try disabling Windows Search temporarily:
      net stop "Windows Search"
      
  4. Superfetch / SysMain Service

    • This service preloads frequently used apps into memory but can cause high disk usage.
    • Disable it via:
      sc stop "SysMain"
      sc config "SysMain" start=disabled
      
  5. System Restore Points

    • Windows may be creating frequent restore points, consuming disk space.
    • Check via: Control Panel > System > System Protection > Configure
  6. Windows Update Cache

    • Updates are stored in C:\Windows\SoftwareDistribution\Download. These can grow large and are safe to clean up.
  7. Third-party Drivers or Antivirus

    • Some drivers (especially GPU or storage-related) or antivirus software may cause ntoskrnl.exe to behave abnormally.
    • Try a clean boot to isolate the issue:
      • Disable all non-Microsoft services via msconfig
      • Disable startup items in Task Manager

🛠️ What You Can Do

  • Run Disk Cleanup: Use cleanmgr and select system files to remove old updates, dumps, and logs.
  • Check with Resource Monitor: Open resmon.exe, go to the Disk tab, and see which files are being accessed most.
  • Use Process Explorer: Download from Microsoft Sysinternals to inspect what ntoskrnl.exe is doing.
  • Run DISM and SFC:
    DISM /Online /Cleanup-Image /RestoreHealth
    sfc /scannow
    

If you'd like, I can walk you through using Process Monitor to trace exactly which files are being written by the system process. That would give us a precise answer. Would you like to try that?

沒有留言:

張貼留言