I have beta tested several years so for me i'm used to trouble shooting and methodical. I have an Asus Rog which is on fast ring win 10 pro, always ran fine. I upgraded my Clevo to Rtm Win 10 pro from Win 8.1 , upgrade went smooth, however after a few days my clevo errored bsod video error, on reboot, no nvidia gpu showing. I need add it was prema modded, wondered if maybe an issue so reverted to stock bios, no fix, reverted back to win 8.1 still no fix. I believe Bios is altered with win 10 and permanent until reflash bios, it appears the main problems regarding gpu are higher end gaming ones with more than 1 card, intel nvidia if search online, site after site, page after page. The temporary solution was i modded INF files in bios, taking care to mod correctly the subsystem ID . Anyway i was not happy at needing to mod my files when ought not have to, i flashed bios again to Prema, then to a different stock bios, clean installed win 10 pro and loaded and updated, adaptors on, all fine. Nvidia updated to latest version 368.81 , all fine, after an hour or so bsod, same as before, nvidia gpu now not seen as before. This time i had been staring for hours all day so noticed the problem. My nvidia hardware id had somehow just changed from 11E1 to 11E2 , that is why error 31 not same as POSTed and nvidia refusing to install. As before, modding the files and disabling driver signature enforcement on recovery, also making sure repeat it in internet advanced options resolves this. I did contact Microsoft support twice, both remote sessions when pointed it out to them and even showed my fix but requesting to know why win 10 is changing id, they both on reboot, somehow vanished, had my mobile number etc yet i guess too complex, the answer is your hardware id for the gpu has changed more than likely, a check in device manager to see if error 31 will no doubt be there. Not sure why Microsoft refuse address or discuss it, tried previously, seems they have not a clue and therefore we are stuck with it. I suggest flashing bios again and maybe stick to win 7/8/8.1 as a solution until this is resolved maybe...if it ever is that is lol