Lets assume we have passed many weeks of use with no issues, is everything stable?  Well, environmental factors can and do CHANGE during the course of time. Dust in the system, increases in ambient temperatures during the year, hardware can be stressed and weakened whereby a module or a chip could start to display signs of stability issues after being clocked for many months.

THERE IS NO SUCH THING AS 100% STABILITY WHEN WE CLOCK A SYSTEM. PLEASE REMEMBER THAT. I hope I have made this point very clear.

That being said, with a new system and a new clock setup it is critical to adhere to the warnings about stability and system use. You may very well find that even after every temp/load test has PASSED that the addition of PCIe 3D render loads MAY display minor stability issues... case in point: http://www.simforums.com/forums/bsod-when-flyinghow-bad-is-that_topic47467.html

REAL WORLD USE SYSTEM CLOCK RELATED CRASHES:

With a new system and new clock setup established if you find during render or other real world use that stability issues exist, (BSOD, CTD, lockups that you have confirmed are clock related) then small increases to Vcore (CPU VOLTAGE) or System Agent (VCCSA) may need to be applied. This is the final step to establishing a stable clock setup. Add a minor increase to Vcore and/or System Agent offset and then fly it again.

So please do remember that until your system has been tested in combat over a reasonable period of time you should avoid performing very large installations and major maintenance while clocked. This is why I outlined that all software be installed and that all maintenance is performed prior to beginning a clocking session and system use. During the initial test period if maintenance needs to be performed use your 'save BIOS' profile system to switch back and forth. Once you get past the initial testing period then you may work with the system as you normally would but in the clocked state.