KB3213986 could cause problems while running 3D apps, here is the solution
Microsoft had recently announced the Windows 10 Build 14393.693 for PC and Mobile users including non-insiders, Production and also Release Preview. In a case of PC users KB3213986 the cumulative patch installed has been posing some problems. The patch was expected to fix the usual bugs and also bring about some improvements to the operating system but it seems that many other things have been affected.
Issues like the reliability of the Groove Music Playback app, fingerprint authentication, issues with input device not working and many other connectivity problems were fixed promptly in KB3213986. However soon after the update was applied users with multi-monitor setups were experiencing screen stuttering/clipped screens whilst running 3D apps.
This problem was mostly observed in multi-monitor setups running in full-screen mode. After digging into the issue we found out that Microsoft has already noted this issue and has also included it in the “known issue” section.
This is what Microsoft had to say about the problem,
Users may experience delayed or clipped screens while running 3D rendering apps (such as games) on systems with more than one monitor. The solution, however, seems to be more of a workaround to this movement and we are pretty sure that Microsoft will address this issue in the upcoming builds.
In order to prevent the display from stuttering Microsoft advises users not to run the application in the full-screen mode and instead opt for the Windows mode. Additionally, users are also advised to use the application with only one connected monitor. Apart from the 3D apps stuttering Microsoft also notes that “The Cluster Service may not start automatically on the first reboot after applying the update.”
The workaround is to start the Cluster service with the Start-ClusterNode PowerShell cmdlet else reboot the node. In case you are yet to install this update, we would advise you to wait for some time till Microsoft issues an official fix for the aforementioned problems in the KB3213986.