New
#161
Is this opencl.dll issue with NVIDIA and Microsoft already fixed? Are Microsoft and NVIDIA even aware?
Is this opencl.dll issue with NVIDIA and Microsoft already fixed? Are Microsoft and NVIDIA even aware?
Just as I thought. But using the opencl.dll from NVIDIA doesn't really do any harm, does it?
That does make sense because I think its mainly a Microsoft problem. Not AMD, Nvidia, or in your case Intel. How long it is going to take Microsoft to admit this and fix their problem thou, could be a while. Hopefully the Graphic card companies will contact Microsoft and report these problems.
Just to add another idea on this issue, I have turned OFF, Device Driver Updates, so this is suppose to stop MS from updating any of our drivers. Don't know how well this will really work, but I thought its worth a shot.
Device Driver Updates have nothing common with this bug. MS install (and not update yet) x86 part of their Remote FX driver (without x64 part). MS do it in any case, independently of Device Driver Updates on/off.
I am not sure why folks are having problems with this. I have not seen it so far and am running the 353.82 version of the Nvidia drivers. My install is an updated 10240 version which hasn't been used much.
Since the opencl.dll file seems to be part of the WDDM driver which update apart from the Nvidia drivers, has anyone seen one of those drivers being installed? Nvidia is using an nvopencl.dll file on my system although I cannot be sure it doesn't interact with the other one.
We have seen SFC errors like this before. When Microsoft was changing the servers around we have several files which showed the problem, but one update cleared that up. I am still seeing Metadata errors and DeviceSetup warning messages in Event Viewer.
Has anyone with a problematic system checked the DISM log after trying that fix. Maybe it would yield more info about the situation. I know there are some listings in this thread so I will go back and check if any of them come from the dism.log file.