What do various crashes mean when overclocking?

Soldato
Joined
22 Dec 2008
Posts
10,369
Location
England
It's a difficult question obviously, as the same crash can mean many different things. Despite this it's probably the most important thing to know when working out why your overclock isn't stable, so please contribute any patterns you've noticed while overclocking. I'll make a start and maintain this post with whatever is added.

On P45,
Blue screens tend to mean memory problems, increase vdimm or northbridge.
Failing several hours into prime, more vcore.

On X58,
System freezing suggests memory failing, more qpi or possibly more vdimm.
Rebooting, more vcore needed.
Erratic behaviour over 200bsck, increase pci frequency a couple of Hz

I really did think I'd come up with more points than that, but apparently I can't. Please contribute :)
 
Unfortunately I don't think you can generalize like that really as my UD3R acts totally different when unstable than my P5Q...and both are P45 based.
 
Damn, I was hoping common chipsets would be sufficient for common traits to be found. I wonder if my P5Q behaved the same as yours does.

In that case I'll also welcome any theories/observed patterns which move away from trial and error as the established pattern to overclocking. There must be a slightly more logical approach than increase/decrease settings at random until it's a bit more stable, then iterate.
 
Does it really matter?when u o/C you should only make one adjustment at a time so u,ll no what caused the system crash!
 
Back
Top Bottom