Joined: Jun 20, 2012
Posts: 302
Location: Los Angeles
I was talking about my system crashing to a "Blue Screen" everyday. Well I found out why it was doing that. I had my "Memory" clocked way too high. So intel told me what the settings should be at. And it has yet to "Crash" since I changed the voltage and values of my memory. But next month I'm going to RMA my CPU because it damaged it. But I want to thank you ALL for your Help, and insight to the situation I was having....
Thank You.
The Two Most Important Days In Are Life Are The Day We Were Born And The Day You Find Out Why.
Joined: Feb 09, 2013
Posts: 212
Location: Union, Missouri
Dude, if you want that expensive game box to last. Don't OC it.
]
Joined: May 31, 2011
Posts: 2631
Location: Fort McMurray, AB
I've overclocked every system I've had. I've had my former gaming CPU clocked from 2.8 to 3.4ghz for years, and now it's still chugging away happily in my HTPC. So long as you have good cooling a decent mobo, and take baby-steps during your OC, you're fine. OC a tiny bit, wait, repeat, then start running stress test software as you go higher, and lots of research. But ya, RAM can be pretty fussy abot goign above specs; generally, to get any signifigant speed increase, you have to raise the latency so much that it almost defeats the purpose. This was a little lame for older socket types, as CPU speed was a little more restrained by RAM/FSB speeds.
Glad you got it worked out, Franklin.
-- Of all the soles I've ever tasted, his had the most ....cumin. --