The other day I kept getting bluescreen errors any time I started a Direct3D game, it didn't happen if I started the first Call of Duty, which is OpenGL. I got five bluescreens that night, some in NFS Hotpursuit 2010 and one when I tried to start 3DMark06. So far they haven't came back but I wonder if anyone has any idea what it might have been? The bluescreens were right after the game or 3dmark06 started, no delay at all. I think I started NFS Carbon or NFS Most Wanted for one of them but can't remember for sure.
My system specs are below. But the most important spec is probably PNY GTX460 1G.
Here's the highlights from the bluescreen errors. (Oh, this is Windows XP Pro SP3)
12/18/2010 1:24:58 AM THREAD_STUCK_IN_DEVICE_DRIVER nv4_mini.sys
12/18/2010 1:23:19 AM THREAD_STUCK_IN_DEVICE_DRIVER nv4_disp.dll
12/18/2010 12:58:21 AM THREAD_STUCK_IN_DEVICE_DRIVER nv4_disp.dll
12/18/2010 12:06:29 AM THREAD_STUCK_IN_DEVICE_DRIVER nv4_disp.dll
12/17/2010 11:59:46 PM THREAD_STUCK_IN_DEVICE_DRIVER nv4_disp.dll
I see a lot of views so I thought I'd add what I did after my initial post. I ran both FurMark and rthdribl for about 15 minitues without any errors. In FurMark the max temp was 74c and in rthdribl the max temp was 65c. I think those numbers are about right but I'm not sure since I didn't run either of those tests when I first put the system together. I haven't had any more blue screen errors but it's sure strange they were so bad that one night. If you notice the time in the log above you'll see I got all the errors one right after the other after I rebooted. Oh well. I DID go back to an older set of drivers but I got one of those blue screen errors after I installed the older drivers (260.89), but it did take just a little bit longer to error then, but not that much. But I ran the lastest drivers for a long time without any problem, so I guess I'll install the 260.99s again.
I reinstalled the 260.99 drivers and everything is still okay. I don't know what happened but everything is working normally again. Everyone probably knows about this program I found but it's called BlueScreenView and it works great to view the mini dump a blue screen error always creates.