Performing a random disk check at startup ensures system integrity and detects any issues early.
Performing a random disk check at startup ensures system integrity and detects any issues early.
Thank you for your message. It seems the "Unsafe Shutdowns" counter isn't visible in the current view. The raw values you're seeing might be from a different context or screen. Could you clarify where you're looking and what you're trying to check?
You've noticed a couple of potential issues, but only two seem to be flagged. It's understandable to feel concerned—especially if you're unsure about the shutdown behavior. Let's see if we can resolve this together. Are there any other symptoms or changes you've observed recently?
Perform a DISM/SFC check just to verify the installation's health. Execute these commands from an administrator CMD prompt (always research a command first for safety). If needed, run DISM /Online /Cleanup-Image /ScanHealth SFC /SCANNOW. If not, you're likely dealing with faulty hardware—still, back up your important files.
You've identified three corrupted system files. Besides ensuring backups, consider monitoring any unusual activity around unscheduled shutdowns—tracking this could help spot patterns. Other recommended steps include checking for additional signs of compromise and following your organization's incident response procedures. Let me know if you need more guidance!
Have you experienced power interruptions or lightning events? The system has remained "online" for 200 days. If you were away from the machine during most of those 14 shutdowns, do you often leave it running while you're not there? Have you ever attempted to boost performance by overclocking your hardware? Be sure to save crucial files! Very important! Beyond that, based on how often this happens—just 14 shutdowns in two months—you might try booting from a live Linux USB drive to determine if crashes persist. However, that would require waiting a long time for the test. Additionally, you could completely reset the drive by reformatting it and wiping all data before reinstalling Windows. Check its stability afterward. Unfortunately, many programs and drivers end up installed depending on your usage, so a faulty driver or software might be the root cause. A fresh installation is acceptable, but if you install every app and device driver immediately after a clean setup and it starts failing again, it becomes harder to tell whether the problem lies with the drive or the drivers/software. Edit: (the files you shared are linked to your PC's Bluetooth adapter, so keep that in mind if you use any wireless devices; otherwise, just turn off Bluetooth temporarily as the first troubleshooting step after backing up your data.)
Thanks to @NinJake, the issue is that I've never had any problems with the PC. There were two power outages a half year ago which caused two shutdowns, but since then it's been very stable. Unfortunately, it will be tough for me to test this PC because I rely on it daily. I'll follow all your advice: keep it closed at night, disable Bluetooth, do backups, and monitor if the unsafe shutdowns increase. Thanks again!