|
Post by ShrimpBrime on May 21, 2018 21:27:03 GMT -5
Run the two orange slots with 512MB sticks single sided
|
|
|
Post by ShrimpBrime on Jun 1, 2018 23:31:17 GMT -5
So AleSlammer sends me a couple of processors, one of which I've posted in the GD70 board. So Mr. Scott was right, cpu was dead. Board lives...But not without it's quirks. I was able to reach 4ghz Cinebench stable on 3 cores and pretty close to it unlocked to 4 cores. First post was a little sketchy. It hung in bios and on the splash screen at least once each and then started working normally. OK great, it unlocked a fourth core and that was good. Clocked that up to 3877 and Ran cinebench R15 which a couple of you may have seen at HWBot. I pressed on to try and get a validate at 4ghz, and I used the dial on the board. Which I must say is a fairly neat feature, however I don't understand how it works. The cpu is a B73 Phenom II.
So now I'm posting 246 bus clocks and 14 multi. However in windows it reports 276 bus clocks. I've restarted twice to check bios, and it's posting 246bus clocks, but windows shows 30 extra. But the overclock is true as benchmark scores confirm the clock speed.
Now I figure the dial is where the 30 extra bus clocks are, but it's off. You have to manually turn it on via the touch pad on the PCB it's self. When I turn it on, it increases clocks from where it reads in windows. I have been turning it back down to 276 bus clocks before I restart or shut down. Is it supposed to do that?
|
|
|
Post by Vinster on Jun 1, 2018 23:58:28 GMT -5
that sounds weird. I'm not familiar with the board, but happy the board is OK.
Vin
|
|
|
Post by Bones on Jun 2, 2018 7:57:24 GMT -5
Shrimpy, if you've used the dial before it's keeping the amount of FSB increase you ran it up to previously.
You'll see in the BIOS concerning the dial to either "Keep" or "Reset". Go in and select "Reset", then the FSB setting and result should match again. If I'm not mistaken you'd need to do that every time you tinker with the dial BUT the dial works and definitely lets you squeeze that chip for all it's worth. At worst it's a very minor annoyance.
If I"m not mistaken there is also an option to auto oc the system after bootup that works too. Just be sure the timer allows for everything in the OS to do it's BS before it kicks in, usually 7 seconds does it well enough.
The dial itself is one of the few things I've ever seen on a board for our purpose that actually works.
|
|
|
Post by ShrimpBrime on Jun 2, 2018 17:20:39 GMT -5
Thanks Bones, I'm still getting familiar with the bios. I'll have a look for Keep and Reset. But it's odd that bios doesn't report the increase where the dial was left at. Probably will not auto OC. In the past I've had terrible luck with such a feature. The dial is pretty neat though. Very useful and seems to work rather well. Just reach over and give it a couple of clicks and go. Good stuff!
Should have a chance to play with it more soon. I need to set it up on the Tap to Drain and give it some decent cooling. I can bench 4ghz with the current cooling which is an Opteron cooler. Nice heavy plate of copper and one heck of a loud fan. I need to eliminate the noise lol.
|
|
|
Post by Bones on Jun 2, 2018 17:54:14 GMT -5
It won't show in then FSB settings proper but should be displayed with the dial settings ("Keep"/"Reset" part) as like 30+ or something, based on what the last setting was with the dial over stock. The auto OC thing is for getting it into the OS then applying the desired OC you really want. Worked great with my now dead G54 board and with that combined with the dial I was able to crank it up to some nice clocks. I first set the board's FSB and adjusted the auto OC setting to a speed I knew the system itself could boot with, got it ready to go in the BIOS with all my other tweaks and let it boot the OS itself. Once it was there and the auto OC had kicked in THEN I'd run it up even further with the the dial for that last bit of OC I could get. You'll have to mess around with it, once you figure it all out you'll probrably like it..... I did and my results did too.
|
|
|
Post by ShrimpBrime on Jun 2, 2018 18:36:15 GMT -5
Haha, love the pirate smiley! Arrrr.
I'll look into that auto OC feature and see how it works out then.
If you want my honesty of it.... I'm actually still shocked the board posted with a different CPU. The last board I had that gave me the FF error didn't revive.
At least the memory is decent. Have had no issues on any divider that's chosen. 1100mhz is no issue and running super tight timings seems flawless also. Right where I have it now the timings are 8-9-8-27-36 1T @ 738mhz ratio 3:8. It'll clock up to where ever I want from here. These are the same timings I've always used with Corsair in the past, while these particular sticks call for 8-9-8-24-51 2T.
The bios doesn't have a listing for tRC at 51 clocks. I need to look into bios revisions yet also. Right now running V1.15. Which bios do you recommend Bones?
|
|
|
Post by Bones on Jun 2, 2018 21:10:44 GMT -5
If it's working good as is, leave it as is. As they say "If it ain't broke, don't fix it".
It's been years since mine ran so I can't recall what BIOS version was in it. Bear in mind the BIOS chip isn't removeable so unless you have a util that will let you go back to an earlier BIOS version if you want I'd let it ride as is.
|
|
|
Post by ozz on Jun 2, 2018 21:23:20 GMT -5
this^^^^^ i wouldnt be touching it either, its going well so leave it be, or you could be facing another differential issue lol
|
|
|
Post by ShrimpBrime on Jun 2, 2018 21:48:40 GMT -5
OK fellas, I will leave bios as is. It's working, so no need for differential errors lol.
|
|
|
Post by ShrimpBrime on Jun 3, 2018 1:04:09 GMT -5
This is just about 4ghz. Unlocked to a quad on air cooling. Did that on the dial. Tried the auto OC genie. It gave an FF error and restarted itself booting to windows at 3.48ghz.
|
|
|
Post by Bones on Jun 3, 2018 2:55:51 GMT -5
I'd just stick with the dial. If it doesn't work then it's of no use. Takes a longer time without it just to get there since spinning the dial like a madman will cause a crash, esp if close to the limit. However it does look good from here.
|
|