• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

BSOD with any kind of OC (i5 2500k)

F

fishingcat

Member
I had a post a couple of days ago about not being able to get my 2500k to OC past 4ghz. Now the situation has changed, with any attempt to OC resulting in a BSOD (this is with the latest BIOS, everything on auto or with the CPU VCore set to 1.3V). The strange thing is that the latest BSOD was a BCCode 24 which indicates an issue with the NTFS filesystem, which was rectified by setting everything back to stock. Does this mean that their are issues with my motherboard? In case anyone was wondering my temps at stock idle in mid/low 30s and run up to about 50 degrees at maximum load under Prime95 (cooling is a Hyper 212+ in a HAF 932) so they really shouldn't be an issue. Sorry if this post is inappropriate because of my previous post earlier in the week, and thanks in advance for any advice you can give.
 
Did you disabled the C3/C6/cpu spread spectrum, up your Load Line Calibration and manually set your VRM fixed state + phase control?
 
I can't trigger any problems with the processor at stock, even after 3 hours of folding@home or prime95. Temps don't break the low 50s after hours at full load. I haven't tried disabling the C3/C6/CPU spread spectrum though so I may try that later.
 
amdhunter said:
Do you know which setting may have helped you the most?
Click to expand...

There is no magic settings that work for all.

But on another note the best tip in the guide is:

Go to onboard devices and shut off anything you arent using (USB3/Firewire controllers, extra LAN controllers, Extra SATA controllers)
Click to expand...

If you have no use for them then it's best to disable them. I tend to do this before I even instal windows. Helps alot on cold bootup times dependant on what you disable also. Downside is if you forget you disabled something like firewire, etc later and you try to use it 🙂
 
I think that disabling EIST (and possibly C1 states) probably made the difference. I'm now successfully running at 4.4ghz stable, 4.5ghz won't boot so I guess it would need PLL Overvoltage which I would rather avoid.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top