I agree with you 100% that generalizing is one of the biggest problems with this bug.
Just check out
http://www.nvlddmkm.com/
There are 14 methods of fixing this problem and all claim to have the definite answer, because something worked for them. The reason is simple: The error has different causes and different effects. The only thing that remains the same is the reset and the error message.
Now, if you state that this is the ultimate fix, that is not really true. The TDR does produce the hardware-reset and the error message, but it does not eliminate the cause why the TDR is triggered: A more than 1-second freeze of your graphics card!
You should also not fall for Microsofts explanation. If you dig a bit deeper, you'll find that Microsoft released about 20 similar fixes for various bugs in Vista that are not as critical for everydays use, but still give error messages or show up in the event manager. The fixes, however do all follow the same principle: Disable the error-message, ignore and hope it works.
In other words: In case of fire disable the firealarm and all goes well. I don't see why this is sold as a professional "fix" by MS.
And I don't want to disappoint you on Win7, but the only differences between Vista and Win7 are the optics, the installation-routine and the much improved marketing campaign. There are several professional magazines which proofed that the structures running Vista and Win7 are not only similar but to 99% identical.
Keeping this in mind, it's also pretty sure the bug will be in Win7-final, too. I followed this problem for over a year now and MS strategy did not change: It's the fault of nVidia and ATI not that of MS. Nothing has changed concerning that attitude.
Am I just refering to 2nd hand information? No.
I had the problem myself when I got my ATI4870 last year. I thought it was the card and literally tested all possible fixes (including yours). Some made the crashes appear less often, some didn't help a thing. Then I found that in any combination with one of my memory stick not plugged in, it worked perfect, plugging it back in I got a crash after 30 seconds into IL2.
On my other PC I tested it for fun and found the same error appearing in Win7. Again testing all components I found it only worked flawlessly without my old IDE-DVD-ROM drive and disabled IDE-support in the BIOS.
So again, I'm glad your PC works with this trick, but it is not a general fix and people have to know that it is not fixing a bug, but silencing the alarm.