How about windowed mode?

Does it happen both with default and Legacy shortcuts?
I'll try to look into it, but I have only one Win10 machine at home and that might not be enough to replicate the problem ;)

It's a Source game and there is a lot of cool stuff that can be applied through /cfg/autoexec.cfg ;)
If you're not scared of it you can try fiddling with it in the meantime
(for example disabling audio completely to test if problem might be there)

but always make a backup >.>

Also to add to that - do you have one screen or more?

Only if you force a clean install and most people just update the drivers.
For future reference:

when facing such problem an easiest way is to change .exe name to anything else (just adding an '_' wil do) and then try to run it. Any compatibilities / profiles won't be applied to the different filename and it might help to hunt down the culprit ;)