You're definitely on the very latest Version and Build.
Did this crop up immediately after those particular updates were applied? A "how long has this been going on" assessment is necessary and pinpointing (or something close) when the issue began may be key to the solution. I've definitely got devices running under Windows 10 using drivers that were not built for it, many are Windows 8 or Windows 7 drivers.
Windows 10 is, however, exquisitely sensitive to drivers like no other version of Windows I've ever worked with.
In checking the Update history on my own machine the update that brought us Build 540 appears to be:
2017-08 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4034674)
If you were not having the issue on Build 438, then either use system restore or the uninstall update feature to roll back and see if the issue goes away. Then follow the advice here:
Edited by britechguy, 09 August 2017 - 01:43 PM.
Brian AKA Bri the Tech Guy (website in my user profile) - Windows 10 Home, 64-Bit, Version 1803, Build 17134
. . . the presumption of innocence, while essential in the legal realm, does not mean the elimination of common sense outside it. The willing suspension of disbelief has its limits, or should.
~ Ruth Marcus, November 10, 2017, in Washington Post article, Bannon is right: It’s no coincidence The Post broke the Moore story