What it says to me is that you need to get an expert involved in this.
I presume that if the store is corrupted, then there's no way to fix it with the system the way it is.
I recall that there is a process for downloading new components to source (obtain) un-corrupted versions to install on your system - but it's a complicated process (and, FYI, it's why I never pursued learning how to do this).
I'd post over in the OS forums mentioning SFC.EXE corruptions in the post title.
If a helper doesn't get to you soon, you could also post over at Sysnative.com in their forums - but again, there are few of them and they are very, very busy.
EDIT: Doing a bit more research on the opencl.dll problem - the usual fix is to remove the nVidia drivers and then install a fresh copy which hasn't worked for you. But I'm a bit confused as Windows File Protection (SFC.EXE) protects Windows files - and this appears to be an nVidia file. I'd check on the nVidia forums to see if others are experiencing this problem.
It seems to me that you've taken all necessary steps to fix any video issues - so it's either fixed, or theirs an incompatibility (highly unlikely, but always a possibility when fussing with a new system)
So that would leave me to assume that there are problems with the motherboard.
Looking at this from a BSOD analyst's viewpoint, there's 3 things that can be happening:
- 3rd party driver problems (non-Windows drivers)
- hardware problems (to include incompatibilities)
- Windows driver problems
Unfortunately, it's not real easy to sort these out - so let me talk about it for a bit.....
The Windows problems are actually sort of easy to fix - simply install Windows and don't install anything else
Unfortunately, that leaves you open to infection, and it sometimes leaves you with devices that aren't working or aren't working properly.
This makes testing the installation difficult as the system isn't operating as optimally as you'd like
But it even gets more difficult if critical components/drivers aren't functioning properly.
NOTE: Ensure that Windows Defender and Windows Firewall are enabled.
So, that leads us to 3rd party drivers. Again unfortunately, the recent release of W10 didn't leave a bunch of time for developers to say "this is the final code, now I can develop a driver for it that will remain stable". And, not surprisingly, the Windows Insider program has already released an updated build (10525) - so I wonder how the developers will keep up with this.
All that aside, you'll need to attempt to get the most recent, W10 compatible drivers for the system from the manufacturer of the device (FYI - I've checked some OEM drivers and have found that their W10 drivers are merely W8 drivers that have been modded to allow installation on W10).
But, as we are not developers or OEM's, we'll have to accept that we'll just have to be satisfied with whatever is available.
In this case, the first thing to do is to check Device Manager (we're proceeding on the assumption that you've done the Windows installation/testing that I described earlier).
Then update the drivers from the device manufacturer's website. We're not looking for performance here, we're looking for stability. So update ONLY the devices that have issues in Device Manager. Then test to see if the system remains stable.
Now somewhere in here there may be a need to test hardware. This is complicated by trying to test for compatibility.
The first step is to check compatibility listings to see if anything sticks out. Then next is to scour the internet to see if there's anything significant there. As this is a new OS, this is sort of like the old "needle in a haystack" problem - you'll sift through lot's of searches just to find few results.
At work we've got a routine going. If we can't fix it quickly we first try to figure if the system has already been activated on Microsoft's servers. If we think it has, we then install W10 clean, update Device Manager devices, and let it go at that. If we're uncertain, we'll give it a try anyway. If it hasn't been activated that way, then we'll clean install the OS required (W7SP1 or Win8.1), activate, and then update to W10. FWIW - if you successfully activate while installing W10, you don't need to worry about it for the same system/OS in the future. When installing W10, you just skip the screen where it asks for the product key two times - and you'll see that the system passes activation as long as you're connected to the internet.
Edited by usasma, 25 August 2015 - 05:57 AM.