Windows 10 BSOD and updates failed installation

Falloutsquad1 · 26 Mar 2017

Attachment 126842 I need help on how to fix these two problems. I don't really know what's causing the blue screen of death, it could be a software I had previously installed but since I did a system restore that should not be a problem. My computer installed most of the new windows 10 updates except for the acumulative one which seems to always keep failing so I'm not sure if that could be one of the main factors that's causing all these BSOD.

philc43 · 29 Mar 2017

Hello :)

There is not a lot of information in the files that I could see which helps identify your problem. Make sure you have verified that all your system files are correct by using the system file checker.

Also check your hard disks to make sure that there are no bad sectors or lost files.

BSODHunter · 03 Apr 2017

1. Please uninstall Daemon Tools. Its known for causing bluescreens.

2. There are "bad block" errors and "file system" errors in eventlog:

Code:

2017-02-26T08 15:35.509  Error: The device, \Device\Harddisk0\DR0, has a bad block.  
2017-02-26T08 15:39.603  Error: The device, \Device\Harddisk0\DR0, has a bad block.  
2017-02-26T08 15:42.665  Error: The device, \Device\Harddisk0\DR0, has a bad block.  
2017-02-26T08 15:45.900  Error: The device, \Device\Harddisk0\DR0, has a bad block.  
2017-02-26T08 15:48.931  Error: The device, \Device\Harddisk0\DR0, has a bad block.  
2017-02-26T08 15:52.337  Error: The device, \Device\Harddisk0\DR0, has a bad block.  
2017-03-19T15 19:52.477  Error: The file system structure on volume C: cannot be corrected.Please run the chkdsk utility on the volume C:.  
2017-03-19T15 20:00.041  Error: A corruption was discovered in the file system structure on volume C:.  
2017-03-19T15 21:36.582  Error: A corruption was discovered in the file system structure on volume C:.  
2017-03-20T19 48:01.004  Error: The file system structure on volume C: cannot be corrected.Please run the chkdsk utility on the volume C:.  
2017-03-20T19 48:14.930  Error: A corruption was discovered in the file system structure on volume C:.  
2017-03-20T19 48:36.090  Error: Volume C: (\Device\HarddiskVolume1) needs to be taken offline for a short time to perform a Spot Fix.  Please run "CHKDSK /SPOTFIX" locally via the command line, or run "REPAIR-VOLUME <drive:>" locally or remotely via PowerShell.  
2017-03-20T19 48:36.090  Error: The file system structure on volume C: cannot be corrected.Please run the chkdsk utility on the volume C:.  
2017-03-20T19 48:36.259  Error: Volume C: (\Device\HarddiskVolume1) needs to be taken offline to perform a Full Chkdsk.  Please run "CHKDSK /F" locally via the command line, or run "REPAIR-VOLUME <drive:>" locally or remotely via PowerShell.  
2017-03-20T19 48:36.259  Error: A corruption was discovered in the file system structure on volume C:.  
2017-03-20T19 56:27.952  Error: A corruption was discovered in the file system structure on volume C:.  
2017-03-25T16 36:13.640  Error: The device, \Device\Harddisk0\DR0, has a bad block.  
2017-03-25T16 36:16.972  Error: The device, \Device\Harddisk0\DR0, has a bad block.  
2017-03-25T16 36:19.909  Error: The device, \Device\Harddisk0\DR0, has a bad block.  
2017-03-25T16 36:22.942  Error: The device, \Device\Harddisk0\DR0, has a bad block.  
2017-03-25T16 36:25.955  Error: The device, \Device\Harddisk0\DR0, has a bad block.  
2017-03-25T16 36:28.994  Error: The device, \Device\Harddisk0\DR0, has a bad block.  
2017-03-25T16 36:32.086  Error: The device, \Device\Harddisk0\DR0, has a bad block.  
2017-03-25T16 36:35.133  Error: The device, \Device\Harddisk0\DR0, has a bad block.  
2017-03-25T16 36:38.056  Error: The device, \Device\Harddisk0\DR0, has a bad block.  
2017-03-25T16 36:40.981  Error: The device, \Device\Harddisk0\DR0, has a bad block.  
2017-03-25T16 36:43.990  Error: The device, \Device\Harddisk0\DR0, has a bad block.  
2017-03-25T16 36:47.014  Error: The device, \Device\Harddisk0\DR0, has a bad block.  
2017-03-25T16 36:50.010  Error: The device, \Device\Harddisk0\DR0, has a bad block.  
2017-03-25T16 36:52.995  Error: The device, \Device\Harddisk0\DR0, has a bad block.  
2017-03-25T16 36:55.949  Error: The device, \Device\Harddisk0\DR0, has a bad block.  
2017-03-25T16 36:58.975  Error: The device, \Device\Harddisk0\DR0, has a bad block.  
2017-03-25T16 37:01.892  Error: The device, \Device\Harddisk0\DR0, has a bad block.  
2017-03-25T16 37:04.889  Error: The device, \Device\Harddisk0\DR0, has a bad block.  
2017-03-25T16 37:07.908  Error: The device, \Device\Harddisk0\DR0, has a bad block.  
2017-03-25T16 37:10.946  Error: The device, \Device\Harddisk0\DR0, has a bad block.  
2017-03-25T16 37:13.906  Error: The device, \Device\Harddisk0\DR0, has a bad block.  
2017-03-25T16 37:18.998  Error: The device, \Device\Harddisk0\DR0, has a bad block.  
2017-03-25T16 37:21.970  Error: The device, \Device\Harddisk0\DR0, has a bad block.  
2017-03-25T16 37:24.916  Error: The device, \Device\Harddisk0\DR0, has a bad block.  
2017-03-25T16 37:27.931  Error: The device, \Device\Harddisk0\DR0, has a bad block.  
2017-03-25T16 37:31.036  Error: The device, \Device\Harddisk0\DR0, has a bad block.  
2017-03-25T16 37:33.909  Error: The device, \Device\Harddisk0\DR0, has a bad block.  
2017-03-25T16 37:36.832  Error: The device, \Device\Harddisk0\DR0, has a bad block.  
2017-03-25T16 37:39.845  Error: The device, \Device\Harddisk0\DR0, has a bad block.  
2017-03-25T16 37:42.743  Error: The device, \Device\Harddisk0\DR0, has a bad block.  
2017-03-25T16 37:45.803  Error: The device, \Device\Harddisk0\DR0, has a bad block.  
2017-03-25T16 37:49.504  Error: The device, \Device\Harddisk0\DR0, has a bad block.  
2017-03-25T16 37:52.454  Error: The device, \Device\Harddisk0\DR0, has a bad block.

Please check your hard drive:

Diagnostic Test

HDD TEST

Run HDTune to check health and scan for errors.

Note

It may take some time, but look for signs of any errors or failure.

You can also run a disk check using chkdsk. Refer to the tutorial for details of how to do this.

Repair Windows Filesystem:

1. Open an elevated command prompt.
2. In the elevated command prompt, type these commands below, and press Enter:

dism /Online /NoRestart /Cleanup-Image /CheckHealth
dism /Online /NoRestart /Cleanup-Image /ScanHealth
dism /Online /NoRestart /Cleanup-Image /RestoreHealth

sfc /scannow

chkdsk %systemdrive% /F /R /X
fsutil dirty set %systemdrive%

SFC:
The SFC command scans the integrity of all protected system files and replaces incorrect versions with correct Microsoft versions.
DISM:
If a Windows image becomes unserviceable, you can use the Deployment Imaging and Servicing Management (DISM) tool to update the files and correct the problem.
For example, you would use DISM to fix Windows component store corruption when a sfc /scannow command is unable to repair corrupted or modified system files because the component store (source) is corrupted. SFC should be able to repair the files afterwards.
CHKDSK:
Checking your drives for errors every once in a while can help fix some performance issues. Drive errors can usually be caused by bad sectors, improper shutdowns, bad software, corruption, physical damage, etc...