Was that issue only reported by Nvidia-users? I daresay thats a bug in Nvidia-driver which is caused in OpenGL ( i think VS uses this, right? ). I saw similar loops years ago. But unimportant - i solved the problem for me. :-) Thank you!
I've not had any issues with VS on the 2 laptops I've used it on. One was a shitty shared intel family something other chipset (was pretty bad) & my current laptop has a dedicated (dual) amd card with about 2gb+ of vram & hasn't had any problems so far other than the occasional crash due to horrible WxWidgets form thing that VS uses.
