Wednesday, September 4, 2013

[Article] BSODs can corrupt your Windows installation and run System File Check to fix them

Most people who h e been using Windows operating system in their PCs have experienced at least one blue screen. Once that happened, you can do none other than press the reset button. Because of that, people started calling it Blue Screen of Death (a.k.a BSOD). In the early days, a blue screen could come up even by running software that acted erroneously. But nowadays, you hardly see them and almost always it is the 3rd party drivers that can give you a BSOD.
 
That, is only if you are not an overclocker.  BSOD is the most common way of identifying instability when you are overclocking your CPU. You might get a BSOD while booting Windows up, or idling on the desktop, light loads or when stress testing heavily. If you are getting BSODs while stress testing heavily, at least you can be happy that you are almost there. If you are getting BSODs while loading Windows, then you are a long way away from your stable settings.
 
BSODs can be a minor hassle. But it can corrupt Windows which might make is completely unbootable. Or, the BSODs that you get afterwards can be actually caused by the corruption. Fortunately, there is a way to check if the Windows system files are corrupted or not. Up to Windows 7, there was this small utility called System File Checker, which is launched from the command prompt (in admin mode.) But in Windows 8, there is another "better" way to do it. The System File Checker is still there, but people say that there are times that you might not be able to fix all issues with it.
 
I'll list them both for you.
 
System File Checker method.
 
Run the following command from command prompt that was launched as Admin.
sfc /SCANNOW
It will show you the following screen and run for few minutes. If it finds errors, it will try to auto repait them and it will tell you where the log is saved so that you can check what was wrong and if it was successfully fixed or not.
 
2013-09-03_23-24-14
2013-09-03_23-23-48
 
The new method.
 
Again, run the following command in a command prompt launched as Admin.
DISM /Online /Cleanup-image /Scanhealth
You will see the following screen and just like SFC, it will run for few minutes checking if there are any issues. It will automatically correct the files.
 
2013-09-03_23-29-42
 
I suggest that you run these system file checks if you ever get any BSODs. I’d actually run both of them.
 
Related Posts Plugin for WordPress, Blogger...