This has been happening since my new display port monitor(Asus VK278). I thought it was the driver, but when I connect my HDMI monitor (Samsung T260HD) it still happens. However, with the latest drivers it seems to happen less frequently. It's only happened twice.
Yes, I've been running at stock speeds, but I did enable my 4.5GHz overclock the other day and it is an Intel per-set auto setting in the new 2040 BIOS. It runs fine and cool. Barely hits 60C with Intel Burn Test on my water cooler. In fact, it hasn't been giving me the error as much since the overclock. Now I'm afraid to turn it back down. lol
Hopefully it is just the drivers.
Thanks for the help