So needless to say this is frustrating so I will try to brief. It is obviously clear that there is a large systemic problem that Microsoft has let go for a long time.
At over 120 pages this thread is losing its utility quickly. I think there is clearly no solution and I would prefer to read about updates, clean installs, or returns anymore. A more practical and in my opinion more helpful post would be a summary of any
"best practices" to deal with the problem. Is there a way we can deal with the problem or prevent it - even if that practice is inconvenient.
I am in no way trying to let Microsoft off the hook on this. This in an atrocious problem and maybe someday there will be a remedy, but until then, we all have to work with what we got.
Any helpful tips much appreciated.
Yeah, I agree.
I do have to say that following the Reddit thread about fixing issues from "sfc /scannow" with opencl.dll corruption," I had the most interesting result. Using the beta drivers from Intel did nothing, but the cleaning up the "sfc /scannow" corruption issues
did produce some change in behavior. (I think most of the people have given up on the ctl-shift-win-B, win-P, ctl-alt-del, etc. - none of those worked for me)
https://www.reddit.com/r/Surface/comments/49g46p/i\_am\_going\_to\_make\_one\_post\_to\_convey\_a\_fix\_for/
Prior to fixing the opencl.dll problem, I had my computer set up to reproduce the computer freeze after sleeping problem very reliably - my screen off and sleep timer was set to 1 minute. I set up a egg timer for 5 minutes, and every single time the computer
would not come out of the black screen after sleep when the egg timer went off.
After fixing opencl.dll, I noticed that the computer always woke up with the same identical method of getting the computer to sleep 1-minute sleep, wait 4 more minutes. That night, I was convinced that the sleep problem was fixed.
Next day I noticed that the computer would not wake up from the black screen after an extended period of sleep. And now I realize that the freezing problem is still there, it's just been changed in that it requires more time.
So something changed when I fixed the opencl.dll corruption, just not 100%.
Does anyone know if there is a program that logs what happens every 20 seconds or so to see if we can catch the computer in the act of freezing? I still don't know whether the computer crashed in sleep, or it's alive but can't communicate when I see the
black screen.