Yes, a full run, I've let it go overnight, many times. I've let the windows memory diagnostic go, overnight, many times. Never get BSODs or any other issues from XP, it just doesn't happen, there is nothing wrong with the memory, which I think is verified when I actually try to underclock the RAM, and the situation isn't helped at all.
I've done those steps in Nvidia's answer now 7 times. I've been over this, apparently it's just not being read. And it isn't as if I'm the only person having this issue.
My video card is -not- factory OCed.
It runs at 60-65 degrees in Vista
I have tried every voltage for every setting
I bought a new hard drive and installed Vista on it, and that hard drive is specifically for trying to figure this out.
I've tried RCs of service pack 1, but as far as I know the official sp is not out, but of course I will be giving it a shot then as well.
There's nothing else I can think to try to prove to you guys this isn't a hardware fault.
I think it may also be important to note that Aero will even crash it, its not just an intensive game. I mean, if I remove whatever amount of RAM, my GPU usage on the desktop (aero enabled) is 0-1% at all times. You mean to tell me that World in Conflict on XP can use 100% of my GPU, and nothing happens, but if Vista uses nothing at all, it crashes? How is that believable?
I have, over and over, acknowledged that a lot of the problems surfacing are just bad hardware. And yes, Vista may exacerbate a problem that already existed in XP, but was managable in XP. The point is, I have no problems at all in XP, and all my hardware passes any test I can throw at it. It even passes the same tests in Vista, provided I lower the RAM amount.
You say that this is a hardware fault, and yet there is a update to attempt to fix it. Now, it possibly fixed the issue for some people, but is it so unbelievable that it didn't fix it for everyone?