New
#1
Computer freezes and bsod's happening randomly.
My friend got a new computer almost 1 year ago and hes getting bsod's I need help to pin point what the problem can be.
Computer info:
Cpu: intel i5 2500k
Motherboard: Asrock z68 Extreme 4 gen3
ram: Kingston 2x4gb
gfx: Radeon HD4890 ( he has plans on buying new gfx soon)
ssd: Corsair Force GT 120gb
PSU: CORSAIR TX950WATT
I attached zip file with logs.
I tried updating drivers, bios, memtest, uninstall virus program and install MSE. I just couldnt figure out the reasons for bsods and freezes. I also have one windows update that cant succeed, Kernel-Mode Driver Framework version 1.11.
I then did a chkdsk and sfc scan. Chkdsk was fine, but sfc scan found errors:
SFC /scannow report:
Summary:
Seconds executed: 343
Found 30 errors
CSI Manifest All Zeros Total count: 12
CBS MUM Corrupt Total count: 9
CBS Catalog Corrupt Total count: 9
Unavailable repair files:
winsxs\manifests\amd64_microsoft-windows-wdf-kernellibrary_31bf3856ad364e35_6.1.7601.22004_none_d50d68344da151bb.manifest
winsxs\manifests\amd64_microsoft-windows-wdf-kernellibrary_31bf3856ad364e35_6.1.7601.17803_none_d482f2fd34846558.manifest
winsxs\manifests\amd64_microsoft-windows-w..ellibrary.resources_31bf3856ad364e35_6.1.7601.22004_en-us_7c40c56a2af7ab50.manifest
winsxs\manifests\amd64_microsoft-windows-w..ellibrary.resources_31bf3856ad364e35_6.1.7601.17803_en-us_7bb6503311dabeed.manifest
winsxs\manifests\amd64_microsoft-windows-wdf-kernellibrary_31bf3856ad364e35_6.1.7600.17013_none_d2919c4737664b78.manifest
winsxs\manifests\amd64_microsoft-windows-w..ellibrary.resources_31bf3856ad364e35_6.1.7601.17803_da-dk_d599e4fe21265e8e.manifest
winsxs\manifests\amd64_microsoft-windows-w..ellibrary.resources_31bf3856ad364e35_6.1.7600.17013_da-dk_d3a88e48240844ae.manifest
winsxs\manifests\amd64_microsoft-windows-w..ellibrary.resources_31bf3856ad364e35_6.1.7600.21203_en-us_7a59681a2dd2260d.manifest
winsxs\manifests\amd64_microsoft-windows-w..ellibrary.resources_31bf3856ad364e35_6.1.7601.22004_da-dk_d6245a353a434af1.manifest
winsxs\manifests\amd64_microsoft-windows-w..ellibrary.resources_31bf3856ad364e35_6.1.7600.21203_da-dk_d43cfce53d1dc5ae.manifest
winsxs\manifests\amd64_microsoft-windows-w..ellibrary.resources_31bf3856ad364e35_6.1.7600.17013_en-us_79c4f97d14bca50d.manifest
winsxs\manifests\amd64_microsoft-windows-wdf-kernellibrary_31bf3856ad364e35_6.1.7600.21203_none_d3260ae4507bcc78.manifest
servicing\packages\Package_1_for_KB2685811~31bf3856ad364e35~amd64~~6.1.1.11.mum
servicing\packages\Package_1_for_KB2685811~31bf3856ad364e35~amd64~~6.1.1.11.mum
servicing\packages\Package_3_for_KB2685811~31bf3856ad364e35~amd64~~6.1.1.11.mum
servicing\packages\Package_3_for_KB2685811~31bf3856ad364e35~amd64~~6.1.1.11.mum
servicing\packages\Package_5_for_KB2685811~31bf3856ad364e35~amd64~~6.1.1.11.mum
servicing\packages\Package_5_for_KB2685811~31bf3856ad364e35~amd64~~6.1.1.11.mum
servicing\packages\Package_76_for_KB2685811~31bf3856ad364e35~amd64~~6.1.1.11.mum
servicing\packages\Package_76_for_KB2685811~31bf3856ad364e35~amd64~~6.1.1.11.mum
servicing\packages\Package_78_for_KB2685811~31bf3856ad364e35~amd64~~6.1.1.11.mum
servicing\packages\Package_78_for_KB2685811~31bf3856ad364e35~amd64~~6.1.1.11.mum
servicing\packages\Package_80_for_KB2685811~31bf3856ad364e35~amd64~~6.1.1.11.mum
servicing\packages\Package_80_for_KB2685811~31bf3856ad364e35~amd64~~6.1.1.11.mum
servicing\packages\Package_for_KB2685811_RTM~31bf3856ad364e35~amd64~~6.1.1.11.mum
servicing\packages\Package_for_KB2685811_RTM~31bf3856ad364e35~amd64~~6.1.1.11.mum
servicing\packages\Package_for_KB2685811_SP1~31bf3856ad364e35~amd64~~6.1.1.11.mum
servicing\packages\Package_for_KB2685811_SP1~31bf3856ad364e35~amd64~~6.1.1.11.mum
servicing\packages\Package_for_KB2685811~31bf3856ad364e35~amd64~~6.1.1.11.mum
servicing\packages\Package_for_KB2685811~31bf3856ad364e35~amd64~~6.1.1.11.mum
servicing\packages\Package_1_for_KB2685811~31bf3856ad364e35~amd64~~6.1.1.11.cat
servicing\packages\Package_1_for_KB2685811~31bf3856ad364e35~amd64~~6.1.1.11.cat
servicing\packages\Package_3_for_KB2685811~31bf3856ad364e35~amd64~~6.1.1.11.cat
servicing\packages\Package_3_for_KB2685811~31bf3856ad364e35~amd64~~6.1.1.11.cat
servicing\packages\Package_5_for_KB2685811~31bf3856ad364e35~amd64~~6.1.1.11.cat
servicing\packages\Package_5_for_KB2685811~31bf3856ad364e35~amd64~~6.1.1.11.cat
servicing\packages\Package_76_for_KB2685811~31bf3856ad364e35~amd64~~6.1.1.11.cat
servicing\packages\Package_76_for_KB2685811~31bf3856ad364e35~amd64~~6.1.1.11.cat
servicing\packages\Package_78_for_KB2685811~31bf3856ad364e35~amd64~~6.1.1.11.cat
servicing\packages\Package_78_for_KB2685811~31bf3856ad364e35~amd64~~6.1.1.11.cat
servicing\packages\Package_80_for_KB2685811~31bf3856ad364e35~amd64~~6.1.1.11.cat
servicing\packages\Package_80_for_KB2685811~31bf3856ad364e35~amd64~~6.1.1.11.cat
servicing\packages\Package_for_KB2685811_RTM~31bf3856ad364e35~amd64~~6.1.1.11.cat
servicing\packages\Package_for_KB2685811_RTM~31bf3856ad364e35~amd64~~6.1.1.11.cat
servicing\packages\Package_for_KB2685811_SP1~31bf3856ad364e35~amd64~~6.1.1.11.cat
servicing\packages\Package_for_KB2685811_SP1~31bf3856ad364e35~amd64~~6.1.1.11.cat
servicing\packages\Package_for_KB2685811~31bf3856ad364e35~amd64~~6.1.1.11.cat
servicing\packages\Package_for_KB2685811~31bf3856ad364e35~amd64~~6.1.1.11.cat
I think it has repaired 12 out of 42 errors, so 30 errors not repaired. Is this fixeable ?