View Full Version : Veteran OC'er needs some advice!
$n][pErMan
12-15-07, 02:43 PM
Attached is a picture of the settings that work for my current OC in my Sig. Respectable but I am looking for more :) I am not sure what issue I am running into, but I can't get above 3.2Ghz (no system post) no matter how much voltage I pump into that CPU (had set as high as 1.45V in the BIOS). For the memory I am running slower to get a 1:1 ratio, but even if I run it at higher speeds I still can't post the system. I have tried setting the NB voltage to 1.45V and that did nothing, set the FSB Termination voltage to 1.3V at one point, that did nothing. I manually set the PCI-E frequency to 100Mhz and the PCI sync to 33.33Mhz and that also did nothing. Worth noting is I tried these things by themselves to see if any one was the issue. I also took back the CPU ratio to 8 and the system would still not post so I am thinking a FSB limitation of some sort.
What I am asking is if any of you know a combination in which to try? I am also curious what is a safe value for FSB termination and NB Vcore for voltages. I have always had them set on Auto and don't want to put those to high as to damage my mainboard. What can I say... im stumped here, any help will be good :)
XDanger
12-16-07, 07:47 PM
Since when was the massively overclocked northbridge issue in that fsb range fixed?
edit: "The bad part is that between 360 and 399fsb" nm
But still, Have you tried 400?
$n][pErMan
12-16-07, 09:45 PM
Since when was the massively overclocked northbridge issue in that fsb range fixed?
edit: "The bad part is that between 360 and 399fsb" nm
But still, Have you tried 400?
Hmmm... no I have not. I was not aware fully of the FSB issue in the range 360-399. Is it possible for you to explain more why 400Mhz would be more stable than 360-399? I assume it has something to do with stepping in the NB chip but am curious. I guess to humor the idea I can take the multiplier of the CPU down so I can raise the FSB to 400 and see if its stable that way. Worth a shot I guess! Before I had the multiplier down but never went up near 400Mhz on the FSB thinking I had hit its limit much lower. From what you are saying I might have been close or in the unstable range.
$n][pErMan, you will have to get above the 400 fsb range to keep the NB from over working to hard, once you go to 401 to 450 or higher the timings on the NB are more relaxed where it will be more stable on that motherboard BUT I think your memory is what will hold you back. If you had 8500 memory this would not be an issue you could easily his hit 425x8@3.4 or 475x7@3.3.
Below you can see the difference between the 400 & 401 fsb and how the timings on the NB become more relaxed. Then you can see the performance gain as you move up on the FSB. All of these benchmarks were made with my P5B Deluxe.
400 x 8 1:1 @ 1600 FSB / Mem was @ 800Mhz Vcore 1.375 @ 3.2 - Idle-34c Load-54 (orthos)
SiSoftware - MEM = 7259/7285
SiSoftware - CPU = 29380/20477
PCmark05 - 7421
401 x 8 1:1 @ 1604 FSB / Mem was @ 802Mhz Vcore 1.375 @ 3.2 - Idle-34c Load-54 (orthos)
SiSoftware - MEM = 6761/6769
SiSoftware - CPU = 29463/20523
PCmark05 - 7380
425 x 8 1:1 @ 1700 FSB / Mem was @ 850Mhz Vcore 1.425 @ 3.4 - Idle-36c Load-58 (orthos)
SiSoftware - MEM = 7172/7196
SiSoftware - CPU = 31203/21777
PCmark05 - 7595
450 x 8 1:1 @ 1800 FSB / Mem was @ 900Mhz Vcore 1.55 @ 3.6 - Idle-40c Load-71 (orthos)
SiSoftware - MEM = 7365/7385
SiSoftware - CPU = 33188/22560
PCmark05 - 7893
475 x 7 1:1 @ 1900 FSB / Mem was @ 950Mhz Vcore 1.425 @ 3.3 - Idle-36c Load-58 (orthos)
SiSoftware - MEM = 7814/7828
SiSoftware - CPU = 30532/21296
PCmark05 - 8528
XDanger
12-17-07, 03:17 PM
my crummy 6400 promos works fine @ 427 with tighter than stock timings.
http://www.thetechrepository.com/showthread.php?t=41
$n][pErMan
12-18-07, 07:58 PM
$n][pErMan, you will have to get above the 400 fsb range to keep the NB from over working to hard, once you go to 401 to 450 or higher the timings on the NB are more relaxed where it will be more stable on that motherboard BUT I think your memory is what will hold you back. If you had 8500 memory this would not be an issue you could easily his hit 425x8@3.4 or 475x7@3.3.
Below you can see the difference between the 400 & 401 fsb and how the timings on the NB become more relaxed. Then you can see the performance gain as you move up on the FSB. All of these benchmarks were made with my P5B Deluxe.
400 x 8 1:1 @ 1600 FSB / Mem was @ 800Mhz Vcore 1.375 @ 3.2 - Idle-34c Load-54 (orthos)
SiSoftware - MEM = 7259/7285
SiSoftware - CPU = 29380/20477
PCmark05 - 7421
401 x 8 1:1 @ 1604 FSB / Mem was @ 802Mhz Vcore 1.375 @ 3.2 - Idle-34c Load-54 (orthos)
SiSoftware - MEM = 6761/6769
SiSoftware - CPU = 29463/20523
PCmark05 - 7380
425 x 8 1:1 @ 1700 FSB / Mem was @ 850Mhz Vcore 1.425 @ 3.4 - Idle-36c Load-58 (orthos)
SiSoftware - MEM = 7172/7196
SiSoftware - CPU = 31203/21777
PCmark05 - 7595
450 x 8 1:1 @ 1800 FSB / Mem was @ 900Mhz Vcore 1.55 @ 3.6 - Idle-40c Load-71 (orthos)
SiSoftware - MEM = 7365/7385
SiSoftware - CPU = 33188/22560
PCmark05 - 7893
475 x 7 1:1 @ 1900 FSB / Mem was @ 950Mhz Vcore 1.425 @ 3.3 - Idle-36c Load-58 (orthos)
SiSoftware - MEM = 7814/7828
SiSoftware - CPU = 30532/21296
PCmark05 - 8528
Hmmm... well I tried both 401Mhz and 410Mhz, both at 8x Multiplier and 7x Multiplier and my system would not post by jumping up past the bad zone either :( How much voltage should I give my North Bridge and FSB Termination voltage??... right now both are at Auto and I have no idea what they read... I dont want to go frying my chipset or anything by manually setting them to high. :p Just trying to rule things out.... perhaps I just hit my max :(
[pErMan']Hmmm... well I tried both 401Mhz and 410Mhz, both at 8x Multiplier and 7x Multiplier and my system would not post by jumping up past the bad zone either :( How much voltage should I give my North Bridge and FSB Termination voltage??... right now both are at Auto and I have no idea what they read... I dont want to go frying my chipset or anything by manually setting them to high. :p Just trying to rule things out.... perhaps I just hit my max :(
On this board you have to set all of them manually, try these for starters. Did you do the Vdroop pencil mod? Have you removed that retarded foil wrapper of the NB to add a 40mm fan, I like blue leds can you tell LOL. You really need it if your FSBv is over 1.6v.
http://img59.imageshack.us/img59/4067/11my5.th.jpg (http://img59.imageshack.us/my.php?image=11my5.jpg)
After doing these setting with no avail then try 2T on your ram instead of 1T.
PCI-E F = 100
PCI SYNC = 33.33
SPEED SPECTRUM = Disabled
FSB-TERM = 1.3
NB VCORE = 1.45
SB VCORE = 1.50
ICH = AUTO
------------------------------------
CPU CONFIG
only 3 I have ENABLED , the rest are disabled.
Modify Ratio support = ENABLED (7-8-9)
CPU TM Function = ENABLED
Execute Disable Bit = ENABLED
$n][pErMan
12-21-07, 07:06 PM
THanks! :) I am going to give that a try over the long weekend :)
[pErMan']THanks! :) I am going to give that a try over the long weekend :)
OK dude, I will keep an eye on this thread. Good luck!:)
Here are some pics of my BIOS settings,
http://i129.photobucket.com/albums/p234/Spoudazo/BIOS_15119.jpg
And for RAM, my 4gb of G.Skill DDR2-800 I just got in the mail does 3.4ghz fine, and my former RAM (http://www.nvnews.net/vbulletin/showthread.php?t=104777) did it fine as well. :)
$n][pErMan
12-22-07, 02:15 PM
Here are some pics of my BIOS settings,
http://i129.photobucket.com/albums/p234/Spoudazo/BIOS_15119.jpg
And for RAM, my 4gb of G.Skill DDR2-800 I just got in the mail does 3.4ghz fine, and my former RAM (http://www.nvnews.net/vbulletin/showthread.php?t=104777) did it fine as well. :)
Cool... looks like I have a few examples to try and work from. Curious, did you do any special cooling additions to your NB and SB like Mullet did for that voltage of 1.45 on the NB? I will probably end up doing it anyway, but if for testing purposes I don't need to it would save me some time :)
methimpikehoses
12-22-07, 03:41 PM
Do different mobos have different straps? Does my P35 have one?
All I did was change the NB to 1.45, nothing else. All I did in the BIOS, you see there (except for setting boot-drive priority :p ). :)
$n][pErMan
12-22-07, 05:47 PM
Ok, what the hell... I must have hit my max or something.. so sad. I have tried both Spoudazo settings and Mullets settings or a combination of the settings.. tried it on 402 FSB, 385 FSB and only 356FSB (which did not post either). It seems no matter what I set, if I even go 2Mhz over my current OC it goes unstable fast and I think the max FSB I can get and have the system post is 354Mhz no matter what I set things at in the BIOS. Am I missing something simple here, there is no way this can possibly be my max! I tried setting the CPU voltage as high as 1.45V while testing just to rule that out as the issue. I also loosened the timings on my memory and went to a 4:5 strap and still... nothing! :( :mad: Even tried it on Auto.... nothing! Any other ideas guys, so should I just throw in the towel?
What BIOS are you using? I updated my BIOS to a new Beta BIOS about a month or two ago (when I got my Q6600). However, even on the old BIOS from late 2006 it still OCd the e6400 to 3.4ghz just fine. I just updated the BIOS because it woudln't recognize the quad-core until the BIOS update. :)
Also, perhaps it's just your RAM having issues with your motherboard or something else. Hopefully you get it worked out. :D
$n][pErMan
12-23-07, 03:57 AM
I am using BIOS version 1216 (8/14/07). I have no idea whats causing the issues... perhaps because I am using 4 1gig sticks instead of 2 2gig sticks? I suppose I could take 2 of them out and see what happens to rule some things out... I am running out of ideas!
I heard alot of people like the 1219 bios for quads.
$n][pErMan
12-23-07, 02:15 PM
I heard alot of people like the 1219 bios for quads.
Spending most the day switching to Vista 64-bit from 32-bit. After that I will try 1219 BIOS and see if that does anything. I find it odd that a BIOS might be responsible, but at this point I am willing to try anything :)
vBulletin® v3.7.1, Copyright ©2000-2012, Jelsoft Enterprises Ltd.