Hmmm... I haven't had time to test it on anything but the netbook I'm building it on. And the integrated video in this thing is total underclocked garbage too... I'll try it on my old quad core with an nvidia card in it when I get a chance. Chances are that it's the fantastic video driver, and since it's a netbook I won't be bending over backwards to make it work on here.
If the problem persists between my other pcs, I'll post my cap.
On that note, I've noticed whenever I ran fullscreen on my other pcs in my earlier builds (directly from Construct, not a compiled exe) it takes forever for construct to actually open up again. It will hang with the (not responding) garbage in the window bar for like a minute and then load up the textures again. I'm assuming that this is because Construct actually uses DirectX to run itself?
Is the game running smoothly for you? I disabled motion blur and had to redo all the timings in the game... that was an odd glitch.