Neither your approach or mine seem to have helped anything... Funny is that we just got a new dev laptop, and it has the same issue. Afterall, nvidia is a small company and has only one driver for all its products, must be normal...
I know it might not be helpfull to state how much they don't care. But Ashley way to address this concern is just as not as helpfull. They only answer we got is: "I tried on my computer, it's not happening", end of the discussion. We al lknow that every single dev reacts like that, we all do, because we created the software on our own machines, we didn't notice anything and all the sudden someone comes out of the wild and tells you it's broken, where you exactly know it isn't. Then, you have to make the effort to go deeper, and not just say: "No, not my problem, we, small company are not in fault, but the big fishes (nvidia, and it seems like intel too) are in fault".
It is not the work of nvidia/intel to adapt to Construct 2, but Construct 2 's work to adapt to what they lay on top of, the graph drivers. For as long as they aren't in a leading position of producing graphic drivers/components. But afterall, they are way too busy porting Construct 2 on Chrome to fix these issues maybe.....
I have another bug, but I'm not even considering posting it here, because the only answer I gonna get is to change my computer where this one is about 4 month old with almost top notch hardware. Instead of that, we just move away from C2.