Overclock.net › Forums › Intel › Intel CPUs › Commando OC Problem 350FSB Wall. Help!
New Posts  All Forums:Forum Nav:

Commando OC Problem 350FSB Wall. Help!

post #1 of 20
Thread Starter 
Hi all Im having real problems overclocking my rig past 350FSB, Heres my spec:

520w Coolermaster PSU
Asus Commando Mobo
C2D E6420 Conroe 2.13Ghz
Geforce 880GTS
SpecTek PC26400 800Mhz DDR2 (set at a 1:1 ratio)
Maxtor 200gb HDD

Current Voltages:

vCore: 1.35
SBvCore: 1.09v
SB Sata: 1.58v
FSB Termination: 1.21v
DDR2: 1.92v
DDR2 Termination: 0.96v
NB vCore: 1.28v
Memory Timings with everything at Auto and stock speeds: 5/4/4/12/ and SPD: 5,6,6,18

I seem to hit a wall at 350FSB with a multiplier of 8x. 340 is ok and can just about get it to 2.6ghz but never past the 2.8ghz mark (345x8).
At 350 FSB with all voltages at Auto I get no boot/post and just hear the fans going. Thankfully my mobo automatically resets to last working conditions so i can fiddle with it easily, but even raising the mem voltage to 2.0 or 2.1, and the vcore up to 1.41/1.42 does not do a thing. Same goes for FSB termination which ive taken to 1.35v with no help.
Ive also tried lowering the multiplier to 7x. But even at 350x7 it will not boot.
I am completely stumped and have found no other similar problems/solutions on forums.
I have rang up a few PC tech guys from the yellow pages to see what their response is and they both said its probably sub-standard ram but Im pretty sure it should be able to take 350fsb at 1:1.
Please help me! Any advice would be greatly appreciated otherwise it looks like ill have to replace memory/mobo and I really dont want to do that!

Thanks all!
Chrispin
post #2 of 20
i remember somethign like that. just jumped to 380 and i could continue.
if that doesnt work, set your chipset volts a bit higher.

EDIT:
try this (if FSB 380 doesnt work):
DDR2: auto, NB vCore: 1.40, FSB termination:1,30
post #3 of 20
Thread Starter 
Thanks for the response!
I tried 350/380/401 with auto voltages and with the voltages you suggested on both 7x and 8x multiplier with no boot. Still the same DET DRAM post on the back of the mobo.
Im beginning to think there is a serious problem with some component, most likely the ram, however memtest x86 contradicts this by giving me 0 errors at stock settings, although Ive only run it for about an hour.
Considering we have very similar mobo/cpu and power (except im on stock CPU cooling) this doesnt look good
post #4 of 20
in a 1:1 ration with less than 400FSB, RAM cant be your problem. try more Vcore. i need 1.45 to be stable at 3.36Ghz, so you could try going to 1.40 to begin with. i know you did this already, but now try with the new Chipset voltages.
post #5 of 20
Thread Starter 
ive tried .125 increments of the voltages up to these:

vCore: 1.45
FSB Term: 1.45
NBvCore: 1.425

Im pretty sure these voltages should be enough for a moderate tweak (this is at 380/401 FSB at 7x and 8x. Still no boot.
post #6 of 20
damn man, i dont know what your problem is then. unless...
is it that when you try to boot, the PC immediately shuts down with a beep?
post #7 of 20
Thread Starter 
After changing settings in bios, Push power on, (does that double reset thing that often happens with these mobos), then cd drives flash, fans start, but no post. Im worried Im just overlooking something very minor but Im sure its all set up right. I cant even take it to someone to do cos I know noone who has any idea about overclocking, and any PC techs arent gonna do it in case they fry the rig. Damn.
thanks for the advice though bud.
post #8 of 20
the thing i tried was first to check all the rails on my PSU. put the GFX on one rail, mobo on one rail, the rest on the last rail.
i also ran stock for a day or 2, after which it miraculously started working and OC'd to where i am now.
post #9 of 20
I'm guessing it's your RAM/Memory controller (it's just a guess).
The Commando should need very few if any voltage tweaks up to 401, maybe 390 - 400 FSB, but I found 401 would run fine with all mobo voltages at their lowest, and thats with a quad core.

Your RAM should be good for those speeds and voltage, but you are getting the DRAM post error, maybe its the memory controller in the NB(?)
The voltages ChielScape suggested look, so I'm kinda at a loss here...
Just keep playing around, and good luck.
24/7 BOINC!!
(13 items)
 
  
CPUMotherboardGraphicsRAM
Q6600 @ 3.20 GHz, 1.400v ASUS Commando BFG 8600GTS OC 2GB Team Xtreem PC2-6400 
Hard DriveOSMonitorKeyboard
250 GB Maxtor Ubuntu and XP for games and CAD Acer AL2216W 22" Logitec 
PowerCaseMouseMouse Pad
SilverStone Zeus 750W Antec P180 Logitech G7 Everglide Richochet 
  hide details  
Reply
24/7 BOINC!!
(13 items)
 
  
CPUMotherboardGraphicsRAM
Q6600 @ 3.20 GHz, 1.400v ASUS Commando BFG 8600GTS OC 2GB Team Xtreem PC2-6400 
Hard DriveOSMonitorKeyboard
250 GB Maxtor Ubuntu and XP for games and CAD Acer AL2216W 22" Logitec 
PowerCaseMouseMouse Pad
SilverStone Zeus 750W Antec P180 Logitech G7 Everglide Richochet 
  hide details  
Reply
post #10 of 20
Hi Chrispin,

I've noticed that sort of thing can happen on this mobo, after changing some OC settings. Even if I know I'm stable, since settings are sooo much lower than I top out my OC at. Just seems to happen on mine, through multiple bios too and different rams. I don't know if it's maybe the same for you, but mine only does it the first time, after restarting from bios after turning up some things past certain point. Then all I do is press and hold the power button to shut down, wait 5-10 seconds and turn it back on.

Then it will always work after that, I can even shut down for a long time, restart whatever and it always works, as long as I'm not changing bios again too much. Like I said though, I know I'm stable too cause I can go way higher and be stable as hell, just seems to be a quirk with this board. It doesn't always happen, seems to depend on how much I change something, or how high, haven't figured that part out.

But it doesn't really bother me, only happens the one time then everything's fine and I know how to get past it. I also noticed it can do it sometimes if I've had the rig unplugged (again only if it's manually OC'd past certain point it seems), like when manually OC'ing, it won't post first time until I manually shut down and restart. But everything works like a champ, and stability tested hard. My board just seems to do it, almost like it's supposed to or something or it's a bug they haven't worked out.
    
CPUMotherboardGraphicsRAM
I7 920 D0 @4GHz Asus P6X58D-E evga gtx260 896mb core216 superclocked 6GB Kingston HyperX 
Hard DriveOptical DriveOSMonitor
4x WDRaptor 74G Raid0 BenQ DW1655 Win7 Home Premium 64bit Samsung 226BW 
KeyboardPowerCaseMouse
Logitech G15 Seasonic S12 600W Antec Nine Hundred Logitech G7 
Mouse Pad
S&S Steel 
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
I7 920 D0 @4GHz Asus P6X58D-E evga gtx260 896mb core216 superclocked 6GB Kingston HyperX 
Hard DriveOptical DriveOSMonitor
4x WDRaptor 74G Raid0 BenQ DW1655 Win7 Home Premium 64bit Samsung 226BW 
KeyboardPowerCaseMouse
Logitech G15 Seasonic S12 600W Antec Nine Hundred Logitech G7 
Mouse Pad
S&S Steel 
  hide details  
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Intel CPUs
Overclock.net › Forums › Intel › Intel CPUs › Commando OC Problem 350FSB Wall. Help!