Forum Discussion
Corrupted System Files That Cause Random Crashes But SFC /SCANNOW Finds No Issues
when I run the command sfc /scannow, it reports no issues found, and I am unsure how to identify or fix the underlying problem causing these crashes. Despite the system appearing stable after running the scan, the crashes continue to occur unpredictably, affecting my workflow and system reliability. I am looking for guidance on how to properly diagnose and resolve these underlying file corruption issues that are not detected by the standard system file checker.
1 Reply
Hi Estorehf! You should first try using event viewer to see if its a hardware issue or an issue with Windows. Also, you should try using DISM (dism /online /cleanup-image /restorehealth in cmd) before running sfc to make sure the component store is healthy.
