Thanks you for feedback. Unfortunately I'm also not sure why compatibility mode solved the problem. And I can only say --disable-gpu is temporary.
This is the first report in Windows, but there were similar problem on Linux. It's a little hassle to add --disable-gpu every time if the problem is happening. We are planning to improve settings page in v3.6, so adding something for this might make sense.