Originally posted by: Big Lar
The errant ram error can point to the NB GTL. Could just be the chipset being flakey due to being hot too.
With my board if I run prime blend at say 490fsb for a coupla hours, then reboot and run prime again, I'll error out fairly quick. I have excellent cooling, so I doubt thats the problem, I think its just the nature of the beast. I'd run Blend tho.
Larry
I'm pretty much about to give up on fighting with this much more.
I've spent all week & last night all evening & early this morning rebooting trying things, & whenever i find a combination that works, it'll go for 2, 3, or 4+ hours but then it goddamn fails.
And it's sometimes on a larger FFT, sometimes a medium one like 160k, & even on 20k, & i know it's not CPU or RAM holding things back. So heat it may well be...
I've tried a zillion combinations of VTT + GTLs & vNB + GTL, & i basically always have to come back to settings around this area, as they at least get me a couple hours before errors.
CPU Voltage: 1.3
CPU GTL Voltage Reference(0/2): 0.680x
CPU GTL Voltage Reference(1/3): 0.680x
CPU PLL Voltage: 1.58
FSB Termination Voltage: 1.36
DRAM Voltage: 1.96
NB Voltage: 1.38
NB GTL Reference: 0.670x
SB Voltage: Auto
PCIE SATA Voltage: Auto
Load-Line Calibration: Enabled
CPU Spread Spectrum: Disabled
PCIE Spread Spectrum: Disabled
CPU Clock Skew: -100
NB Clock Skew: -200
CPU Margin Enhancement: Optimized
I've tried 1.32-1.36 range VTT along with GTLs from 0.63 to 0.71, & basically i have to stick w/ 1.36VTT + 0.68 & 0.68.
Any lower VTT is no good, & @ 1.36VTT, if i try lower GTLs or higher, or mix them up like 0.675 & 0.680, not good...has to be the same value, & seems to like being right around 0.925 (1.36 x 0.68).
For NB, increasing from 1.38 to 1.4 hasn't helped, & i need to recheck my notes to see if going from 1.36 to 1.38 was needed or not to get from ~465 to~475.
I do seem to need the higher NB GTL; lower doesn't work.
My guess would be due to my 8 GB.
It's been 1.38vNB + 0.67 GTL that get me a couple hours or more before errors, which is right around 0.925 too...both VTT & NB GTLs like that area, & whenever i try to lower that or increase that, doesn't work, so that much i've figured out.
I've tried upping vCore & vDIMM, but doesn't help, as those aren't issues.
I've loosened RAM clock twister from Moderate to Light, but not helping.
Loosened tRD from 10 to 11 or 12; not helping.
400 strap vs. 333 strap; not helping.
I forgot to try lowering PLL, but increasing to 1.6 didn't help. I really doubt lowering it will do anything, but i'll try that next i suppose.
Latest thing i decided to mess with was CPU & NB clock skews.
I've actually been using them @ CPU Skew -100 & NB Skew -200 for so long now i can't even remember why i started...it might have been your suggestion back with my Q9550,
Big Lar
But i tried a whole bunch of combinations of them from AUTO up to -400.
Turns out the only way to actually get into the OS & then get more than seconds into P95 is at my usual CPU -100/NB -200, or edit: nope, system locked up 20 mins in.
So only CPU Clock Skew: -100 & NB Clock Skew: -200 are stable for at least over an hour.
Auto doesn't work!
Neither does higher combinations.
I'm guessing this is because i've always had them at -100/-200, & my VTT/NB + GTL settings have been set around them to work that way?
Anyway, thanx again for all the suggestions.
After wasting hours & hours trying to get over 465 truely stable, it appears i may very well be stuck at the same FSB i was back with my Q9550, which well, isn't too surprising really.
Just was hoping i'd have gotten a bit smarter by now & figured out how to outsmart my mobo...
Originally posted by: theprodigalrebel
I salute your jpeg naming convention.
Hah, glad you like it.
I keep track of settings that way in notes & the screenshots i take.
If i didn't note the exact settings i use i'd never get anywhere when OCing