As some of you are aware from my numerous (sorry!) posts in the main driver threads, myself and others have been experiencing some very annoying Windows issues since installing driver v368.22, the first of a new branch which was released around the launch of the new GTX 1080 Pascal card. These issues have persisted through all the 368.xx drivers so far, including the v368.51 Hotfix released today (or yesterday). The issues are all non-gaming which is what makes them so frustrating. Ironically, the driver is great for games, it's just other things that aren't! It is also the reason why some of us did not even think that the driver might be causing the issue in the first place. Some people have even done a clean install of Windows only to find the issues return as soon as they install a v368.xx driver (which also suggests that it may not be a software conflict...). The issues I've experienced are as follows: 1. Intermittent "Stub has received bad data" errors that pop up ONLY while opening non-games applications and programs such as the Event log, PerfectDisk, PureSync or DXDiag.exe, etc, etc. This even came out while running the setup.exe file for the v365.19 driver when I using v368.39!!! When it happens, the affected program can always be ran a second time. This issue occurs fairly infrequently and does not seem to affect the running of Windows apart from having to open the program twice to use it. I have never seen this error before though and it does not happen with v365.19 installed. To reiterate this issue does not seem to happen with games, only other applications and programs. 2. When checking for updates manually from the Windows Store it never completes and gets stuck in a neverending loop until I shutdown or restart my PC. This also prevents Windows Store apps and games from updating automatically. When I reinstalled the v365.19 driver and checked for updates, the Windows Store found a dozen updates and all of them downloaded successfully (some of these were over a week old, which is as long as I was using the v368.xx driver hinting that it was preventing Windows from updating these normally). 3. Task Scheduler will throw up a "cannot connect to remote server" error after an unspecified amount of time despite being set to Automatic. This error can be fixed by restarting the service but it's irritating to have to do this. Something in this driver causes the service to halt for some reason (this is almost certainly connected to the issue in 4. below). It can also cause problems when shutting down or restarting as I will see the screen informing me that it shutting down or restarting then it will return to the desktop with a Task Scheduler error. 4. The Event log shows a lot of services terminating unexpectedly and restarting. These services include Task Scheduler, Computer Browser, Xbox Live services, etc. These appear in blocks of 12-15 and are all different services, none of which seem connected to the graphics driver. These blocks of errors appear periodically and do NOT occur when using the v365.19 or earlier drivers. All of these issues can be resolved by installing the v365.19 driver. In fact, you don't even need to do a clean install; I just installed them over the top of the v368.xx driver, rebooted and all the issues were fixed. Forum user, gwit, identified what appears to be the cause of the issues, a DLL file, named nvwgf2umx. By deleting this file (or overwriting it with the one from the v365.19) the issues can be fixed, suggesting that it is the cause of the issues. However, doing so appears to revert DirectX from 12 to 11.3 according to DXDiag so, alas, it is not a fix just a workaround. The few games I tested however (none of which used DX12) all ran fine but I suspect that DX12 only games will not run properly, if at all, if the nvwgf2umx.dll file is missing or is a mismatched version from an older driver. I'd be interested to hear from anyone else who is having this problem, particularly as ManuelG from NVIDIA and the GeForce.com forum has said that they've been unable to replicate the issue so far (but keep trying to reproduce it). I am hoping that he reads this and that gwit's finding regarding the nvwgf2umx.dll file might throw some light on the issue. Obviously, the more information people can add to this the thread the more chance we have of getting the issues fixed, especially if anyone has found a way of fixing or working around these issues that does not involve downgrading the driver or losing full DX12 compatibility. Please ONLY post in this thread if you are experiencing one or more of the above issues. It might be a good idea for people to share hardware and software configurations too (which I will do in another post so this one isn't too long) to see if there are any commonalities that we all share that might help NVIDIA further. Thank you.