Confused - Tobits is an Extra Spicy right? And his uncore seems to be at 16x?
You are right, yet on dmolter's thread, we decided these chips are locked at 18x...hmm
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Confused - Tobits is an Extra Spicy right? And his uncore seems to be at 16x?
LMAO... uh oh, we could be looking at "The Folder formerly known as Tobit".
I'd worry about timings last. Get the fastest, lowest density, modules you can as the lower density modules seem to put less stress on the memory controllers (low density also confirmed by an EVGA tech). In my case, I went with two Kingston HyperX 3GB DDR3-2000 kits and couldn't be happier. I am now running them just a tad over DDR3-2100 at this BCLK.Shopping for SR-2 RAM...For better TPF, should I look @ lower CAS, or simply higher RAM speeds?
I'm just starting to read all the thread to get an idea on how to clock an SR-2.
MoBo and CPU's, X5650's, arrived yesterday.
Case should arrive today if it doesn't snow to badly.
I've already got Ram, PSU & Vid card from the old farm.
So I need to tweak the old fard, remove vid cards to drop power draw.
Then build my new boxen.
Luck .............
[H]
Finally another x5650 I can actually help with!
4.0 overclock here http://hardforum.com/showpost.php?p=1036089513&postcount=7
4.2 overclock here http://hardforum.com/showpost.php?p=1036223866&postcount=142
Both of these are a bit out of date, since refined. 4.2 was a bit frustrating - it needs a bit more vcore than what is posted back then to be 100% stable through bastard units like 6701 - and those predated unlocked uncore BIOS - so the 16x did not actually do anything - it was actually at 20x.
I am working on updated screenies with latest battle tested settings that have survived a few months... be up soon.
Hey! I exist too I wouldn't mind seeing some newer settings/results as well.
I'm just starting to read all the thread to get an idea on how to clock an SR-2.
MoBo and CPU's, X5650's, arrived yesterday.
Case should arrive today if it doesn't snow to badly.
I've already got Ram, PSU & Vid card from the old farm.
So I need to tweak the old fard, remove vid cards to drop power draw.
Then build my new boxen.
Luck .............
[H]
Ok tried Tobits settings from a few pages back and I can boot at 200BLCK with everything else on Auto.
But when i put a full load on it, my NV display driver fails and the recovery times out = BSOD because of GPU driver.
Not sure what i should do to fix this? Any ideas?
What PCIe slot do you guys run your GPU in?
Mine are both in slot #1. Have you touched your PCI-e clock speed at all? Maybe downclock PCI-e a bit? I have never had a video card driver crash on either of mine.
I do have so interesting notes from my latest session. While running stable at 206bclk I've got the [email protected]. [email protected]. Unlike some of the others, I can't even get booted into windows at 211, it hard locks at the windows logo and requires a reboot.
Those voltages are quite a bit lower than I had before. I was using 1.45 and 1.4. I don't know why, but I'm seeing over 15sec faster TPF. I'm down to 16:44 TPF on my 6900wu. That's 90k PPD from old quad cores. (New personal record btw)
I still can't get my ram stable at the rated settings. I have the corsair dominator 1gb sticks, 8-8-8-20 DDR3 1600. But I'm only stable at 8-9-9-24 1630. Is is because of the higher bclk's? I'm capped at 2:8 it seems so that limits my testing.
Confident that 211 BCLK is stable having returned one bigadv and a few normal SMP units, Tobit has decided to push on [H]arder. He first tried a 214 BCLK but the onboard NIC died soon after loading up all cores to 100%. Tobit is now at 213 BCLK and all appears well and he's currently folding a bigadv.
moar later... 213 however may be his limit.
Edit: onboard NIC problems have returned at 213 BCLK as well. Time to install the dedicated Intel NIC I believe.
It seems that random reboots are turning out to be the norm for me. To put it in perspective, the longest I've ran the computer nonstop is 19days. It doesn't happen that often, I'm just going to put it off on the high overclock.Fascinating. I woinder if you are seeing what I am - phantom occassional boots that result in faster times. My fastest rig SR2#3 had one magic day where it would bench 10:48. But I cannot get that back. I photograph my BIOS screens, I know I am on the same settings, but I consistenly bench 10:58. If I cannot work out why I will have to reduce my figures in Jebos benchmark spreadsheet.
But I am thinking they are more to do with wacky inconsistent RAM polling at boot than voltages.
I have pm'ed vcdz382 - as he suffered this - different benches after rebooting - reboot and run 3 frames, reboot and run 3 - each consistent times within a reboot, just very different across reboots.
I'm just starting to read all the thread to get an idea on how to clock an SR-2.
MoBo and CPU's, X5650's, arrived yesterday.
Case should arrive today if it doesn't snow to badly.
I've already got Ram, PSU & Vid card from the old farm.
So I need to tweak the old fard, remove vid cards to drop power draw.
Then build my new boxen.
Luck .............
[H]
I knew it was just a matter of time...
Welcome to the club Tiger!
I'm starting to stress test mine at only 3.2 Ghz.
Setting off 12x copies of Orthos, set to blend, uses just over 17 gig of memory ........
I'll let it run for an hour or so then up the clock.
Max core temps at the moment are only in the mid 50C, so I've still a bit of headroom there.
Luck ..........
[H]
I need to try to get to 4.00 Ghz by 18x 200 with turbo.[H]
MIBW can confirm, but I do not believe this is possible. Your chip has a 2x turbo with a 20x multiplier. The problem is that you end up with a 3x turbo with a 19x multiplier or a 4x turbo with an 18x multiplier. In other words with turbo on, it will try to run at 22x under load regardless of what you set the multiplier to. This is probably a bug in the SR-2 bios, but as far as I know, it is still there.
Good luck with numa zero.
From what I've heard, its probably a ram issue. If you figure it out please tell me how!
Posted via [H] Mobile Device