Windows 10 keeps getting corrupted

[aidenrelkoff]

Windows 10 is being an absolute turd, I have legit reinstalled from scratch 4 times now. Windows keeps getting corrupted. I have ran Disk checkers and Ram error checkers. Both displayed no errors. Also the ram is about 4 months old and the HDD is 2 weeks old. All drivers are up to date. 

I'm getting standard issues that everyone seems to get, Start menu wont open, calculator icon gone, random blue screens with the code (critical-process-died). Which after some googling critical process died means that windows basically stopped working...

I ran "sfc /scannow" in windows powershell. It said it could not repair the corrupted files. Here is the part of the output file that shows it.

Spoiler

output log

2016-02-02 09:20:01, Info                  CSI    00004e9c [SR] Verify complete
2016-02-02 09:20:01, Info                  CSI    00004e9d [SR] Repairing 1 components
2016-02-02 09:20:01, Info                  CSI    00004e9e [SR] Beginning Verify and Repair transaction
2016-02-02 09:20:01, Info                  CSI    00004e9f Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
  Found: {l:32 Ui1iPYLRlrK/KdPVb2btwB5JqasIeak0eCk42vnG8bQ=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2016-02-02 09:20:01, Info                  CSI    00004ea0 [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-02-02 09:20:01, Info                  CSI    00004ea1@2016/2/2:17:20:01.829 Primitive installers committed for repair
2016-02-02 09:20:01, Info                  CSI    00004ea2 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
  Found: {l:32 Ui1iPYLRlrK/KdPVb2btwB5JqasIeak0eCk42vnG8bQ=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2016-02-02 09:20:01, Info                  CSI    00004ea3 [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-02-02 09:20:01, Info                  CSI    00004ea4 [SR] This component was referenced by [l:125]"Microsoft-Windows-RemoteFX-VM-Setup-Package~31bf3856ad364e35~amd64~~10.0.10586.0.RemoteFX clientVM and UMTS files and regkeys"
2016-02-02 09:20:01, Info                  CSI    00004ea5 Hashes for file member \??\C:\Windows\SysWOW64\opencl.dll do not match actual file [l:10]"opencl.dll" :
  Found: {l:32 Ui1iPYLRlrK/KdPVb2btwB5JqasIeak0eCk42vnG8bQ=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2016-02-02 09:20:01, Info                  CSI    00004ea6 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
  Found: {l:32 Ui1iPYLRlrK/KdPVb2btwB5JqasIeak0eCk42vnG8bQ=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2016-02-02 09:20:01, Info                  CSI    00004ea7 [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\Windows\SysWOW64"\[l:10]"opencl.dll"; source file in store is also corrupted
2016-02-02 09:20:01, Info                  CSI    00004ea8@2016/2/2:17:20:01.865 Primitive installers committed for repair
2016-02-02 09:20:01, Info                  CSI    00004ea9 [SR] Repair complete
2016-02-02 09:20:01, Info                  CSI    00004eaa [SR] Committing transaction

[Pepi28]

When you say you ran disk and ram checkers, which ones specifically and for how long? 

[S7117]

Windows 10 just does that.... I have been through this about 10 times with my laptop....

Only thing I can just suggest is do a complete format of the disk and then reinstall it fresh via usb dongle if you haven't tried that.

[aidenrelkoff]

2 minutes ago, S7117 said:

Windows 10 just does that.... I have been through this about 10 times with my laptop....

Only thing I can just suggest is do a complete format of the disk and then reinstall it fresh via usb dongle if you haven't tried that.

yeah... i have done that like 4 times. Screw it, windows 8 runs better anyways, ill just reinstall that. This is why i haven't updated my primary pc yet.

2 minutes ago, Pepi28 said:

When you say you ran disk and ram checkers, which ones specifically and for how long? 

both software, and windows memory diagnostic. windows one ran for about 20 min, software one ran for a few hours. I used seagate's drive checker software to check for errors. Since both of these are new i don't expect them to be bad anyways.

[Pepi28]

1 minute ago, aidenrelkoff said:

yeah... i have done that like 4 times. Screw it, windows 8 runs better anyways, ill just reinstall that. This is why i haven't updated my primary pc yet.

both software, and windows memory diagnostic. windows one ran for about 20 min, software one ran for a few hours. I used seagate's drive checker software to check for errors. Since both of these are new i don't expect them to be bad anyways.

A good memory test is MemTest86, works outside of an OS and should be ran for at least 24 hours. 20min really isn't enough to find an error. 

[Macronus]

3 minutes ago, aidenrelkoff said:

yeah... i have done that like 4 times. Screw it, windows 8 runs better anyways, ill just reinstall that. This is why i haven't updated my primary pc yet.

both software, and windows memory diagnostic. windows one ran for about 20 min, software one ran for a few hours. I used seagate's drive checker software to check for errors. Since both of these are new i don't expect them to be bad anyways.

Are you more then certain you did obtain the installation from the Microsoft and what media did you use to install it, as it might have caused some files to become corrupt leading to failed installations or even failed second time boot ups. Be sure that .img file or whatever other way you are installing is valid.

I've had this happen with Windows 7 before problem was in the USB stick I used. Try using a different one or a different CD?

[aidenrelkoff]

8 minutes ago, Macronus said:

Are you more then certain you did obtain the installation from the Microsoft and what media did you use to install it, as it might have caused some files to become corrupt leading to failed installations or even failed second time boot ups. Be sure that .img file or whatever other way you are installing is valid.

I've had this happen with Windows 7 before problem was in the USB stick I used. Try using a different one or a different CD?

I am going to university and i used their windows 10 education edition ISO. I have used two different DVDs and one USB, all with the same issues.

[Macronus]

Just now, aidenrelkoff said:

I am going to university and i used their windows 10 education edition ISO. I have used two different DVDs and one USB, all with the same issues.

I'm sorry other then that I would not know. I'm not familiar with education edition All I can suggest is downloading it straight from Microsoft and buying a license for it if it works

[aidenrelkoff]

10 minutes ago, Macronus said:

I'm sorry other then that I would not know. I'm not familiar with education edition All I can suggest is downloading it straight from Microsoft and buying a license for it if it works

education edition is basically windows 7 version called "enterprise". It have every single feature that microsoft has developed for windows 10. It actually has more features then Pro.

Also i installed windows 10 pro one of those times. same issue.