Quote:
Originally Posted by Kunaak
I was grinnin like a felon :D. EAR to EAR. Post 450fsb np now, just need to get it into windows, then work on 3d stability. I also see what you said now about the issues around 400fsb. I think the Fsb holes are making some things a bit trickier to do, but clockgen maybe can get me to where I want to go. Just hope it play nice like this on LN2...we'll see
What bios you on btw?
I use bios 1002.
was thinking of trying beta 1100, but I am not much a fan of changing bioses on this board, since it seems each bios brings up new problems.
1 bios I can't get the Vcore above 1.5 volts. they fix that, then the next bios I cant get the NB above 1.6 volts.
with this bios, I am good on all voltages, most of the time.
when the next official bios comes out, I will give that one a shot.
You could go even higher if you remove/unsolder 8 resistors Vince... ;) :p:
Right now I'm trying to find out the Northbridge GTLREF to mod it too..... :( This Striker by DEFAULT with only 1.86VCore and uninsulated, took my X6800 at ~5340MHz+ benchable in 3D....So I think that it'll do well as soon as I mod it and insulated....we'll see... :)
Vince at 1T and Cas 3-3-3-x, what your Striker can do?.....How high?... Coz this one I got now and unmoded, did only 431MHz.... :(
On ABIT IN9 I could do ~ 445 - 455MHz (chipset depentent) and on the EVGA I could do ~442MHz...
Nice! Which resistors and how much higher bro?Quote:
Originally Posted by hipro5
what happened to the IN9 benching?? Board is no good?
As for the mem clocks at 1T 3-3-3-x, I think those limits will vary from mobo to mobo. I could get about same on evga/striker maybe slight difference.
With the IN9 I could do ~455MHz max at Cas 3 - 3 - 3 - 3 - 1T - 8 - 17 - 1 - 6 - 2 - 7.8us.....with this one NO GO..... :(Quote:
Originally Posted by k|ngp|n
My first IN9 was ROCK STABLE (except the QUADs) till it didn't power up one day.....Code 90 no matter what..... I think that that flucken uGuru chip get's "blocked" somehow and that's it..... :(
My second IN9 did almost the same (power off/power on next day and nothing - no power up)....My third IN9 did almost the same but Digital PWR went down like my Quad GT's...... :(
My EVGA could do ~444MHz at the above (well except 17 - it was 19)......with this Striker I can do 432MHz MAX at the above timmings (21 for 17) and no more.....Now that I have mod it, I'll test it and I'll report back....;)
I decided to go with the Striker for ONE reason.....DIGITAL PWR....IN9 has it and no go with the QUADS......TOO difficult to bench....EVGA has TINY Mos-fets (like the 8800GTXs VGAs).....No go for me PLUS its overclockability sucks big time .....DFI Digital PWR = NO GO ... :D
So I gave Striker another shot and we will see.... :)
About the mods.......You could gain another 20 - 30MHz more (CPU depented)...... :)
UPDATE ..........
DONE...... :D
MAX (without "well" tuning) I'm at 471MHz with Cas 3-3-3-4 and 1T.....I'll upload screenshots a bit later..... ;)
EDIT: Here you go.....This in on my untweaked HD..... :)
http://www.thelab.gr/images/Hipro5/A..._471MHz_1T.png
http://www.thelab.gr/images/Hipro5/A...71MHz_1T_1.png
http://www.thelab.gr/images/Hipro5/A...71MHz_1T_2.png
.....and here's where I want to finally bench with the x12 multi......
Untweaked HD....
http://www.thelab.gr/images/Hipro5/A...51MHz_1T_1.png
....a bit tweaking (LOD, etc.)....
http://www.thelab.gr/images/Hipro5/A...51MHz_1T_2.png
.....and finally on my 3D Benching HD....:)
http://www.thelab.gr/images/Hipro5/A...51MHz_1T_3.png
http://www.thelab.gr/images/Hipro5/A...51MHz_1T_4.png
Bottom line is I think that I'm OK for the time been....Let's move on now.... :D
P.S. If you could follow Kunaak's guide and mod your mobo, you'll be satisfied for sure... ;)
Hipro.
amazing how much one little mod, can completly change these boards huh?
any plans on Quad Core?
seeing Kingpin go from 370 to 430+ stable, was cool.
I am wondering how others would do now too.
Quote:
Originally Posted by Kunaak
A little mod?.... :rofl: I've done 7 of them till now....and believe me, ALL of the GTLREF mods aren't easy to be done..... :D
I've done ALL GTLREF pins/mods 4 of them, Vdroop, VCore, Stabilize and filtered the VNorth and now I'm trying to find out where the heck is that dumn North GTLREF.... :(
Yes that was the reason I've done all those GTLREF mods....coz of the QUAD..... :)
for anyone curious FCG has a great article on the GLT Ref Voltages, and why the voltages arent universal, and do need to be tuned according to the FSB.
his knowledge on the subject is a thousand times more then my own.
I got a monkey see, monkey do, kinda mentality. I see the mod... I do it.
but if you really really want to know why the mod acts as strange as it does... this article will give a great understanding to it.
this quote stood out to me the most, as it was 100% in line, with everything I had experienced with this mod so far.
no one voltage, is universal... just like I said in my first posts..
just nice to finally see I was right, and not imagining it.
when you dont know what your doing, and your learning on the fly as you do it... its kinda scary to stand up and say anything, cause you can easily make yourself into a fool.
glad for once, my experience was right on with how the mod really does go.
http://www.thetechrepository.com/showthread.php?t=87Quote:
Once you begin adjusting GTLREF voltages (for each core data and address bus) you will find that different bus frequencies respond differently to variations in the voltage. This has to do with harmonics and reflected signals as the FSB changes. The best way to make adjustments is by using a "Clockgen" program from inside the OS to set a previously unstable FSB frequency while simultaneous moving the GTLREF voltage points. Memory or data intensive applications (such as Super PI) will stress the system the most. This inherent variation in system response and stability while passing through different ranges of FSB is most likely the reason that some users experience what they describes as "FSB holes." Just because the FSB signal timings are tuned for 350MHz and 450Mhz doesn't necessarily mean that they are adequate for 400Mhz FSB. Figure 5 illustrates this concept graphically.
anyways, give the article a read, if your interested. its quite interesting to finally see whats really happening when you use this mod.
but after reading it... it only makes me even more curious to tweak the board even farther now, since it kinda clues me in on somethings.
Did the mod exactly as it has to be done and the result now is that system won't initialize the CPU. All the voltages are OK - vCore reading 1,26V, vRef = 0,87 (originally 0,77; tried up to 0,96 and down to 0,66) - still no go. Unsoldered the variable resistor and put new one in the place of the originally installed on the board (214ohms) I had to unsolder to do the mod - the Striker still refuses to initialize the CPU. Any ideas what could have happened, or all I can do is get a new board?...
One more question - with the removed 200ohms resistor and soldered 500ohm, I couldn't up the GTL Ref voltage more than 0,96V, however I read in this thread people are using 1,1V... how is it possible?
EDIT: RMA'd the board, next week getting a new one, hopefully. Getting 3220 pretty soon too, so I will definitely need the mod for 400+ FSB and I need some opinions what would have gone wrong last time; is it mandatory to remove the resistor, as Shamino gives instructions, isn't there a possibility for the mod to work without doing so?... And is 500ohm VR fine - as I said, I couldn't get more than 0,96 vRef, (I saw Kunaak uses 1K, maybe this is the way to go).
hi,
for those who have successfully completed this mod, what thickness tip did u use on the soldering iron? is it worth getting a 0.12mm tip for my 25watt iron, or is this overkill? and where did u find was the easiest place to earth it?
The RMAed board returned to me, moded it and it works fine now, only when I measure the vCore with DMM I get 1,6V when 1,9V are set in BIOS. Strange, didin't have this issue with my previous Striker... Next week, probably, will try with a quad and see how the mod helps, until then I will play with a crappy 6700, that won't do even 3,75GHz stable...
About the grounding - I prefer to use screw hole, there is one where the heatpipe is curverd, just a few cm above the resistors, participating in the mod.
=( I'm stuck at 350FSB...
When I FIRST got my G0 Q6600, I was able to do 3.33GHZ, without even trying. Then I did some undervolting, just to see how low of voltage I could go on stock speeds. Now I'm trying to overclock, it won't let me get past 350FSB.????
And if I'm reading this right, I have to take a soldering iron to my motherboard?! =| =|
My settings
3.15GHZ Q6600 G0, 1.3875v (probably over volted)
P5N32-E SLI 1103 BIOS, NB 1.5, SB 1.55, CPU VTT 1.55, 1.2VHT 1.4
OCZ DDR27200 2GB, 888MHZ, 4-4-3-15 2.2v
edit: my idle temps are 30C/26C/27C/27C, load temps 43C/43C/40C/40C
Any suggestions besides soldering the MB?
Try booting at 1600 - 1680 within bios, Linked and at 1:1....Quote:
Originally Posted by treatmentx
Do these mods apply to the P5N32-E SLI Plus??
I ask becuase I am certainly experiencing similar FSB issues with G0 6600 Quad.
Currently using latest ASUS 0805 BIOS.