G3D.dll based CTD and BSOD

Hello,I do not currently have a problem with either CTDs or the BSOD, but I am making a note here in this forum because for a very long time, with successive FS systems, I had been plagued with both of these conditions from time to time.There can be many contributing causes at play in one or both of these gamestoppers, so I don't want to reinvent the wheel and recite all the lists of possible reasons and remedies. I think I have tried them all. Some helped, many didn't.One possible cause I kept hearing about but was reluctant to believe (because of the cost of a PSU swap-out) is that both of these conditions can, and will, be triggered if there is an inadequate or irregular power supply.Recently I was inflicted with the same conditions once again, which at first occurred only occassionaly, then at an ever increasing pace. I won't bore you with the details, but I went end to end to diagnose and correct the problem.The answer showed up after taking the following measurements for power provision calculations: CALCULATE POWER REQUIREMENTS - Long story short, it was my one year old power supply causing both my CTDs and BSODs. During that year my video card had been upgraded from a 275 GTX to a 470 GTX and then to an OCed 480 GTX, along with ever increasing GPU and RAM overclocks. The PSU, even though still adequate on paper, was overloaded and had faulted under stress.Here is the point of this post. If you are plagued with CTDs or BSOD, or both, check your power supply first to make sure it is both rated high enough and is functioning properly. It might save you a lot of time, grief and money. By the way, since I bought a larger more powerful (pun intended) PSU, I have been unable to induce either condition no matter how hard I try to provoke it, at least for now. I hope this helps.Kind regards,