Macbook Pro and ATI Graphics crashes in Windows Vista and 7

Question

Hey all, I was wondering if anyone else had been having problems with Windows 7 and Vista having graphics driver crashes. I have been having this problem since the Boot Camp beta, and it has yet to be addressed as far as I can tell.
Basically the problem is that after a few minutes in either Vista or 7(after installing all the boot camp drivers from the Leopard or Snow Leopard disc) the screen graphics will start getting all corrupted. Eventually I will get a message in the taskbar telling me that the ATI driver has crashed and recovered from an error.
I have looked everywhere online I can think of for an answer, but have come up pretty empty thus far. The only thing I remember finding that was a possibility a long time ago was something to do with trying it with 1 stick of ram installed rather than 2, or that my ram could be problematic.
I tried running with just 1 stick, and that didn't help at all. I also tried each stick individually also with no change. I even went as far as running a diagnostic using some kind of memory testing software to see if the ram was bad, but it came back as good.
Also, I have run in XP without any issues whatsoever, so I am assuming it is something Vista and 7 specific. I was thinking it might have something to do with the Aero features as when I disable the ATI driver and run in Windows Basic without Aero enabled, I don't get the graphics glitches. Another clue might be that when the graphics glitch up, if I bring up the ctrlaltdel screen which gives you the option of Task Manager, Log Off, etc. the graphics are NOT glitched on that screen. As soon as you exit that screen however, the glitched screen is immediately back.
Bah, I am at pretty much the end of my sanity trying to figure this out, and was just wondering if anyone else has had this problem with the older MacBook Pro or is mine just inherently bad? Any help would be greatly appreciated.
Here is my system info just for extra help possibly?
Hardware Overview:
Model Name: MacBook Pro
Model Identifier: MacBookPro1,2
Processor Name: Intel Core Duo
Processor Speed: 2.16 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 2 MB
Memory: 2 GB
Bus Speed: 667 MHz
Boot ROM Version: MBP12.0061.B03
SMC Version (system): 1.5f10
ATI Radeon X1600:
Chipset Model: ATY,RadeonX1600
Type: GPU
Bus: PCIe
PCIe Lane Width: x16
VRAM (Total): 256 MB
Vendor: ATI (0x1002)
Device ID: 0x71c5
Revision ID: 0x0000
ROM Revision: 113-xxxxxx-086
EFI Driver Version: 01.00.086

Answer 1

Just an added update for anyone interested. I believe I have finally figured out what the issue is.
Apparently, at least on this model of MacBook, Apple has the ATI card underclocked to 310MHz / 278MHz (GPU and RAM respectively) when running normally. However, when running in Windows the ATI driver automatically uses the full clock speed of 470MHz / 470MHz (or something to that effect). The reason that it ends up getting artifacts and driver crashes is because of overheating. Apple has it underclocked because of the way heat is distributed in the system.
Anyway, I found a tool that KIND of works for fixing the issue I believe. It is called ATITool, and allows you to change the clock speed to the 310MHz / 278MHz that works so well in OS X.
It is located at: http://www.techpowerup.com/atitool/
One thing though, the newest version 0.27 beta 3 (on mine at least) causes the backlight of the screen to go off when you load it in Windows. If you put the machine into hibernate, then bring it back up it will come back on... but that is annoying. I have found that the version 0.25 beta 13 doesn't have this issue. It is possible some of the other versions prior to 0.27 beta 3 also don't have this issue, but I haven't tested them yet. I will give some of them a try later.
The previous versions can be found here: http://www.techpowerup.com/downloads/Tweaking/ATITool/
Anyway, if anyone else has luck with other clock speeds or knows of any other solutions please let me know. This way works, but I would like to find a better solution if possible.