Just chiming in again that this also happens to some people that run 60hz screens, as it has prior to the 5.0 patch.

Might be a completely unrelated issue, but would still like to get that out there.

Main difference there is that it runs fine for a few hours, or few minutes and then crashes with a similar error.

There was a topic about that as well, but it'll probably get buried between the issues related to the refresh rate problem at this rate.