SpykeAlpha

@hjf288 - If you're running your RAM at 1066 or higher (even if they aren't overclocked), try dropping it down to 800 and see what happens. It looks like a lot of the issues could be related to fast(er) RAM. In some cases it turns out to be bad RAM, but in my case by severely under-clocking my RAM I haven't had any issues yet (in the little testing I've done... I'll know more tonight/this weekend). Basically, it looks like there's some sort of issue between how the TDR (read:

Found some information for people that might be having the same issues. Here's some information from Nvidia from their forums on the subject: Link: NVIDIA Statement on Vista TDR Errors Seems like it is all based on an interaction between the drivers and the application. Also, here's some information from Microsoft on the specifics of the driver resetting: Link: <a href="http://www.micros

Roger that. I'll be emailing you my dxdiag in a couple of minutes. To list everything I've tried so far in Vista Ultimate 32-bit: Nvidia Driver 158.24 (current release), 162.22 (Beta), 163.11 (Beta) No compatibility mode selected, XP SP2 Compatibility Mode Aero enabled, Aero disabled 1650x1080, 1280x1024, Windowed Mode No AA, 4x AA (selected from within game) No external apps running except for Multiplicity, Windows Defender, Anti-Virus, G15 Keyboard LCD m

Tried it in windowed mode with Aero disabled and Aero enabled. No dice either way. At least I'm able to get some auto-saves in so my game is SLOWLY progressing. I'm running out of ideas on things to try.

Last thing to try today. I tried running the game in XP compatibility mode just to see if that'd make a difference. No dice. Will try it in various resolutions later. Taking a break for now.

Btw, if anyone from Ironclad or Stardock are reading this, I'll be more then happy to run some sort of debug client that has extra logging to try and help you with this. I'm sure it's not directly "just an issue with Sins" but some combination of Sins and the Nvidia driver, and I'd love to do anything I can to help.

I don't often feel stupid. Or silly. Meh. It was an honest mistake.

Actually I never mentioned which games I had tried, that was someone else. But you do bring up a valid point about Sins could be calling something "different" then the others. For me Company of Heroes (especially in DX10 mode) and Supreme Commander are the two benchmarks I use for taxing a system. SupComm has a great built in benchmark tool that will cause almost any machine to come to

For S&G's I just tried it after unloading Multiplicity. The game barely had time to load up my save game (fairly late in this game so a lot of stuff to load) before it tripped the Vista video driver reset. This is frustrating.

You sure you dont got any programs running in the background that could interfere with the game? Again, why would Sins be the only game having issues when I've run other games/programs that are much more graphically complex/intensive on both my CPU and GPU hardware? If there is a program running in the background, it's only interfering with this game. But with that said, due to this issue with Sins I do

Well if it is a setting that I flipped, it's only being impacted by Sins, and no other game that I've played since getting this box (which is why I think it's something with Sins specifically, but I don't know what). But I haven't tweaked any settings in the Nvidia drivers. They are all still set at default settings based on whatever was installed originally. So basically it's set to "let all the programs figure everything out". I wonder if it's the difference between Vista 3