Originally Posted by xorbe
What I encountered was that if I let my Titan cool down to idle temps, and then fired up Valley, the max boost was then realized and crashed (while attempting too aggressive overclocks). After the card heats up to 80C (mine seems to sit at 79-81C no matter what I twiddle with in evga precision x 4.0) then it doesn't seem to reach that max initial boost. I've only tried one game so far (FC3) with no issues, but that keeps the card pegged at 99% of course. I'll try TF2 / Portal tonight at low settings / vsync -- that'll probably get the card to trigger those middle grounds.
I'm just running +100 core/+250 memory for now (still not 100% sure on it, I thought I saw some artifacts last night while raiding). This is a superclocked card, and with these settings this is 1176MHz max boost. However, hardly anything uses that or even close. Valley/Heaven rarely take it above 1136 even with keeping the temps below 70C.
It makes me wonder what these people running valley at 1176+ are getting for their "max boost", soon as they start up a game that actually uses it, I can only assume it's going to cause issues. The only way I found to actually find my "max boost" is enabling K-boost in Precision and restarting. It will then run the card at 100% on the desktop, so you can easily see it. My first overclock was actually 1228 core for the "max boost", and it was STILL stable in valley/heaven because it only ran it at 1100-1176, but soon as I got into a game that sometimes uses max boost, it had major issues.
Why did they make this card so difficult. I thought my 680 was difficult, but Boost 2.0 takes it to another level.Edited by Murlocke - 3/1/13 at 11:18am