@WWSmith, I noticed that after reboot I need to activate my underclocked profile again in Afterburner. Also, the underclocking is reset after drivers update. BTW, even after it, sometimes in game I can notice sort of a black screen appeared for a split second with a micro-freeze, but game just doesn't crash. Anyway, in my opinion this is a dirty hack. I mean, let say, all your other games dont crash, and system stability tests pass fine, so no reason to think that the problem is with your hardware. This "device removed" problem shows that your GPU was physically removed or your driver stopped working. But believe me - there is a bunch of ways to drop the driver from the application. I had this issue writing a simple program in CUDA. You can drop a driver or receive a BSOD by writing to non-allocated memory of your GPU (in my case it was so-called unified memory), and such problem may appear on one GPU and be completely hidden on another. So, to summarize - developers should debug it and find a problem in a source code. First of all - they should eliminate the messages that we see in log file that some model wasn't found or some texture is missing. I guess this is not normal in a campaign which was released already some time ago and should work smoothly.
