Ok, and just to make sure I'm completely understanding things here, this does NOT occur when Driver Verifier is off, correct? You can check if DV is on or not by either going into command prompt and typing
verifier /query or opening DV up as normal and clicking "Display existing settings" then Next. If it shows a list of drivers and it shows checks are enabled, then it's obviously on.
The freezing thing when DV is on kinda puts a big damper on our endeavor to find cause for this, as it's rather crucial in making sure the system BSODs when the culprit is causing the problem and not afterwards. Without those crashdumps we're kind of at a loss.
The only other option I have for gettin more info on this besides DV is to have it crash one more time and then send us the
MEMORY.DMP file located in your Windows directory. It'll compress heavily in a zip, rar or other archive variant, but it'll still be too big here. Upload to a 3rd-party filesharing site and I'll have a look at it to see what I can come up with, but I can't guarantee I'll find something conclusive (better than nothing, though). Make sure to explain when the crash occurred and what the PC was doing at the time.
While we're working on figuring it out through this route, you can run some more hardware tests. Have
Prime95 going on Torture Test on Blend settings overnight. Then follow that up with another overnighter but on Large FFT settings instead. If your system crashes during any of the runs, send us the crashdumps (minidumps might just be fine here, no kernel dump from
MEMORY.DMP). If a test fails in Blend but not Large FFTs, you have most likely a motherboard/RAM issue. If test fails on Large FFTs but not Blend, most likely an internal CPU failure. If it fails on both, it can be anything but most likely bad CPU.
As for it being a GPU problem here, can you try a beta version of the driver, or perhaps a rollback? Also, if you have onboard graphics controller on your mobo, you can try switching to that to see if things stabilize. If they do, it's a driver bug or a graphics card problem. Or if you have a different video card you can swap that in and try that a bit to see how things go.
It may very well be the graphics card, which isn't a rare issue as it's always possible to get a dud piece of hardware for a new system. Nevertheless, unless you're willing to go the caveman route and start swapping hardware, it's cheaper to try and get more info on this and analyze it further than to go off buying more stuff.
