Found out What the Issue Was
Select messages from # through # Forum FAQ
[/[Print]\]

Bad Karma -> General Technology
#1: Found out What the Issue Was Author: Franklin, Location: Los Angeles PostPosted: Wed May 15, 2013 7:32 pm
    —
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.
#2: Re: Found out What the Issue Was Author: GroundTrooper, Location: Union, Missouri PostPosted: Thu May 16, 2013 12:56 am
    —
Dude, if you want that expensive game box to last. Don't OC it.
#3: Re: Found out What the Issue Was Author: Abram, Location: Fort McMurray, AB PostPosted: Thu May 16, 2013 1:03 am
    —
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.
Bad Karma -> General Technology


output generated using printer-friendly topic mod. All times are GMT

Page 1 of 1