You can download it as part of Microsoft’s free Windows Developer Kit if you really want to dig into the gory details. There’s a complete BSOD handling infrastructure available from Microsoft, built around a tool called the Windows Debugger (aka WinDBG). (Image credit: Tom's Hardware) Try NirSoft’s BlueScreenView Tool Keep running SFC until it’s cleaned up all integrity violations. Here’s what you want to see after your final SFC run: Note further that running either or both of these commands can take some time to complete, especially if one or both find items in need of fixing. Note that if SFC finds and fixes anything, you should run the command until it comes back with a clean bill of health (in some cases, I’ve had to run it two or three times before it came back clean). The second of these commands runs the System File Checker (SFC) and will repair any damaged files it finds. The first of these two commands finds and replaces any damaged operating system components in the side-by-side filestore (aka WinSxS). DISM /Online /Cleanup-image /Restorehealth.From the command line, enter these commands, one at a time: At this point you want to reboot into safe mode once again, and open an administrative command prompt or PowerShell session. If the BSOD recurs despite the items taken out of the picture by removing, disabling or uninstalling them, whatever’s still left in the picture remains problematic. If not, you’ve probably isolated the cause and can start researching some kind of fix.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |