Commando Results by Tony and Andre (and others...)

[MrDeeds]

Sorry to hear the bad news. Even though the heatpipes arent that hot to the touch its evident that they really cant handle much more than 1.5v to the nb.

[grsz06]

thnx for the info, did some testing over the weekend but not for long .
at first i discovered one of my ram sticks was doa, so i started playing with only one stick, just set alot of high volts (all purple-red, nb@1.4v) and booted at 4ghz (450x9), installed windows at that speed and did some 5min of orthos blend, then 475x9, same story.
485x9 was not stable though, so to find stable bus and mem speeds i set 8x500 1:1, turned orthos blend back on and went out for some groceries, when i came back (10-15mins later) the rig was off and would not post anymore. so seems like another quick commando kill

btw all this was on the standard heatpipe cooling, which i cleaned and put as5 underneath. at 4 and 4.25ghz i did feel some of the heatsinks but none of them where exceptionally hot, even upto 1.685v vcore (bios).

After hours of different combos I found that 510x7 with ddr at 1000 1:1 ratio is the most stable. Orthos blend will run for hours and heat is not an issue, but I do have the Spirits on SB and NB

[dmross]

Argh... after establishing a stable baseline, I am starting to have a ton of problems with this board.

I'm running 360 x 10, 1080mhz @ 4-4-4-12 on 8888 Dominators. It will run Orthos blend for 12+ hours with no problems. Everything seems rock solid and then every few days when I turn on my screen everything is dead. Attempts to boot the system will freeze every time with CHIPINIT or DET DRAM. I swap memory to a cheap stick, and it starts booting, but nothing will bring it back online. Unplugging it, clearing the CMOS, etc. all have no effect. It just hangs at CHIPINIT and wont post.

If I let it sit disconnected for 30 minutes I can get it started again. Then it will work flawlessly. Orthos will run for hours and everything is solid... then a few days later, it happens again. I am very frustrated at this point. CPU temps don't go over 56-57C running Orthos, idle they are at 42C or so. I don't know if I should RMA or not. Powersupply is the Corsair 620W (Seasonic).

It's very frustrating, especially after all the BS I went through with the EVGA 680i POS killing my memory.

[unit365]

dmross

For your information, i have same problem. But i had same problem with some p5b also which killed my RAM 3 times. (GSKILL 6400, OCZ 8800, and OCZ 9200 !!!), now with commando ram don't die but have many pb like you. Work some days correctly and the next day, blue screens, freeze and more...

Boring.......

[ziberia]

Thought my experience might be helpful to some:

My Commando crashed badly at 3dmark benching and I thought it was gone. Voltages screwed, cpu init etc. I let it reset for 24h, didn't help much. I managed to re-flash the 0803 bios with afudos, still the same problems. Tried about any other trick in the trade.

I already got a new board but before sending the old one to rma, I tried the following:

I used Ez Flash to flash to bios 0801 and after reboot flashed back to 0803.

That worked, and now the board is running better than ever.

[dinges]

Thought my experience might be helpful to some:

My Commando crashed badly at 3dmark benching and I thought it was gone. Voltages screwed, cpu init etc. I let it reset for 24h, didn't help much. I managed to re-flash the 0803 bios with afudos, still the same problems. Tried about any other trick in the trade.

I already got a new board but before sending the old one to rma, I tried the following:

I used Ez Flash to flash to bios 0801 and after reboot flashed back to 0803.

That worked, and now the board is running better than ever.

was your board still posting after it crashed?
cos mine isnt and im not sure how to flash the bios when it doesnt even post?

[ziberia]

It was posting after the 24h reset- battery out etc.

[Supershanks]

I thought i was similarly screwed last month following crash. cleared cmos, pulled battery etc., & applied power nowt.

But whilst frigging around noticed when power applied the cmos button didn't light up, pressed again lightsa on action.. Seems i had a sticky cmos button needs to be pressed x2 to work.

[syne_24]

Maybe someone can help me out, some guys think I have way to much Vcore for the settings I am running here they are

400x9
Vcore @ 1.5875 This is the lowest I can get the cpu stable
FSB termination voltage lowest
NB Vcore 1.3
SB sata lowest
SB chipset voltage lowest

I have tried a lot of different setting's, higher FSB T voltage, higher NB vcore with a lower CPU vcore all makes no difference

Is it that my CPU just needs that amount of Vcore ?

If that is your first time running the cpu at those speed then you dont really have anything else to reference it by. So it could either be the cpu or the board. But I think with the x9 multi on this board it needs more voltage to get stable. Try 515 x 7 with 1.55v and NB vcore at 1.4v to see how it's.

[ziberia]

I was testing and matching some single Crucial D9GMH sticks. Decided to push one set a little bit further:

Vcore 1.65v.
Vmem 2.6.v
Vmch 2.0v.

[iviustang50h]

I have read this entire thread (took forever), so I thought I would be all set to go when I received my Commando, E6600, Tuniq Tower and G.Skill PC8000...boy was I wrong! Orthos stops and erros after ONE minute running at a 3.2

I am running 1:1 memory and using 2.3V per spec. I copied the bios settings from this post to try to fix the issue, but it didn't help:
http://www.xtremesystems.org/forums/...d.php?t=115217

Any advice would be much appreciated. I can't believe it's not even stable at a 3.2!

[MrDeeds]

Even though the commando is based on the P5B-Deluxe i wouldnt just use the same bios settings recommended for that board. Also that thread by fcg was a general guideline for you to get up and running and he never intended for people to use those settings 24/7.

Give us some more info and hopefully we can help. What are you individual settings. Voltages, bios version, etc etc.

[iviustang50h]

Even though the commando is based on the P5B-Deluxe i wouldnt just use the same bios settings recommended for that board. Also that thread by fcg was a general guideline for you to get up and running and he never intended for people to use those settings 24/7.

Give us some more info and hopefully we can help. What are you individual settings. Voltages, bios version, etc etc.

Sorry, I should have clarified. I turned off the same thing he did if my bios had them; that's what i meant when I said I "copied" his settings. I didn't use his voltages.

When overclocking my settings were:

Using Bios 803
Spread spectrum - off
PCI clock sync - 33.33
PCI express frequency - 100
DRam - 1:1 (533)

CPU Vcore - 1.45
FSB Voltage - 1.4
NB Vcore - auto
Memory voltage - 2.3 (per G.Skill specs. I have the DDR1000 stuff rated at 4-4-4-5)
DDRII Channel A, B and Ref voltage - all 3 at auto
SB Vcore - 1.5
SB Chipset Voltage - auto
ASUS C.G.I. - auto
Static read control - auto
Cas Latency - 4
Ras to Cas - 4
Ras Precharge - 4
Active to Precharge - 5
Write recovery time - 6
DRAM TRFC - 42
DRAM TRRD - 10
Write to Read - 10
Read to Precharge delay - 10
Write to Precharge delay - 11

CPU ratio CMOS setting - 9
C1E - disabled
Max CPUID Value - disabled
Vanderpool Tech. - disabled
PECI - disabled

Sorry for the long list, but I want to get this issue fixed.

Is it possible the Tuniq tower is incorrectly installed? I followed directions perfectly and hand tightened the screws until I almost couldn't turn them any more. Is that too tight? Oh, and the fan is inside the tuniq tower is facing the rear of the case so it blows the air out the back. Is that correctly installed?

Thanks!

[Jodiuh]

NB Vcore - auto (auto on the P5B caused me to lose some parts, it jacks up the #'s to unsafe levels)
DDRII Channel A, B and Ref voltage - all 3 at auto (not sure here, someone will chime in)
SB Chipset Voltage - auto (same as NB Vcore)
ASUS C.G.I. - auto (turn off if not using xfire)
Static read control - auto (off)
Cas Latency - 4 Ras to Cas - 4 Ras Precharge - 4 Active to Precharge - 5 Write recovery time - 6 (You can increase these to eliminate any RAM related ocing bottlenecks)

Is it possible the Tuniq tower is incorrectly installed? I followed directions perfectly and hand tightened the screws until I almost couldn't turn them any more. Is that too tight? Oh, and the fan is inside the tuniq tower is facing the rear of the case so it blows the air out the back. Is that correctly installed?Thanks!

I tighten mine until the sink can just barely be rotated, don't wanna over tighten! Blowing out the back's fine and as long as you didn't splooge on the thermal paste (TIM)/grease, you should be fine. What does Core Temp say for temps? For reference:

P5B
Tuniq @ 1200RPM (roughly halfway)
Vcore @ 1.475
room temp: 26C
Core 0/1: 49 idle, 67 load

If your Tuniq's on good and you're full rev, I'm thinking around 37-45 idle and load using orthos large would be around 57-65 depending on ambient of 23-26. Good luck!

[MrDeeds]

Using Bios 803
Spread spectrum - off
PCI clock sync - 33.33
PCI express frequency - 100
DRam - 1:1 (533)

CPU Vcore - 1.45 you may need some more juice here depending on your cpu
FSB Voltage - 1.2 your fsb is still low and you dont need to crank this yet
NB Vcore - 1.35-1.5 since your running 1:1 you shouldnt need much voltage at all
Memory voltage - 2.2 4-4-4-12 you can try loosening up the timings till you find a comfortable oc for your cpu
DDRII Channel A, B and Ref voltage - all at the lowest level -30mv or something
SB Vcore - 1.5
SB Chipset Voltage - 1.05
ASUS C.G.I. - disable
Static read control - disable
Cas Latency - 4
Ras to Cas - 4
Ras Precharge - 4
Active to Precharge - 5
Write recovery time - 6
DRAM TRFC - 42
DRAM TRRD - 10
Write to Read - 10
Read to Precharge delay - 10
Write to Precharge delay - 11

CPU ratio CMOS setting - 9
C1E - disabled
Max CPUID Value - disabled
Vanderpool Tech. - disabled
PECI - disabled

Auto settings on the asus boards are more trouble than they are worth.
Set all your oc settings manually.

[sreedx2]

MrDeeds... can you elaborate what the DDRII channel a b and ref do and how to adjust them or do you always leave then at the settings you mentioned in an earlier post ?

[iviustang50h]

Using Bios 803
Spread spectrum - off
PCI clock sync - 33.33
PCI express frequency - 100
DRam - 1:1 (533)

CPU Vcore - 1.45 you may need some more juice here depending on your cpu
FSB Voltage - 1.2 your fsb is still low and you dont need to crank this yet
NB Vcore - 1.35-1.5 since your running 1:1 you shouldnt need much voltage at all
Memory voltage - 2.2 4-4-4-12 you can try loosening up the timings till you find a comfortable oc for your cpu
DDRII Channel A, B and Ref voltage - all at the lowest level -30mv or something
SB Vcore - 1.5
SB Chipset Voltage - 1.05
ASUS C.G.I. - disable
Static read control - disable
Cas Latency - 4
Ras to Cas - 4
Ras Precharge - 4
Active to Precharge - 5
Write recovery time - 6
DRAM TRFC - 42
DRAM TRRD - 10
Write to Read - 10
Read to Precharge delay - 10
Write to Precharge delay - 11

CPU ratio CMOS setting - 9
C1E - disabled
Max CPUID Value - disabled
Vanderpool Tech. - disabled
PECI - disabled

Auto settings on the asus boards are more trouble than they are worth.
Set all your oc settings manually.

Thanks a lot Mr Deeds, you rock buddy! I set the settings exactly as you requested (after remounting my Tuniq in case it was too tight). However, orthos still erros in under 2 minutes. This is ridiculous!!! What can I do to fix this?

My temps are 32 at idle and never rise above 50 under load (according to Core Temp). Something has to be wrong!

Edit: Okay, I changed the vcore to 1.5 and tras from 5 to 12. So far orthos has been running for 12 minutes - never got this far with this setup at a 3.2 yet. I hope it lasts 24 hours. Anyway, what do you think was holding me back; the voltage or the tras setting? I don't know why an e6600 would need 1.5 volts to hit 3.2 but it's possible I guess. What is a safe vcore setting for 24/7 usage using the Tuniq Tower to cool the proc?

Obviously I want to overclock higher. 3.6 is preferred and if stable, it will be my 24/7 speed. I don't need to set any world records here; I just want a nice stable system at 3.6GHz.

[DoomSayer]

50° really aint that bad under load.
everything under 65° is safe in my book.
i idle around 25° with my big typhoon @ 3.4GHz.
Id keep tras at 12 or something.
It looks like youre voltages are fine anyway.

[Viss]

Initial results but not that much time right now so only quick testing. Aircooled tuniq tower.

Max on 1066 strap 8x465 (vfsb 1.5/vmch 1.55/ sb sata 1.65/ sb 1.2) which is a lot more then with me unmodded P5B at max voltages.


Short orthos 1.35 vcore.

[puttekula]

Initial results but not that much time right so only quick testing. Aircooled tuniq tower.

Max on 1066 strap 8x465 (vfsb 1.5/vmch 1.55/ sb sata 1.65/ sb 1.2) which is a lot more then with me unmodded P5B at max voltages.


Short orthos 1.35 vcore.

where did that PI 1m time come from...?

[Viss]

? 8x465 1M 4-4-4-12. This is 8x465 boot.

[Severance]

Argh... after establishing a stable baseline, I am starting to have a ton of problems with this board.

I'm running 360 x 10, 1080mhz @ 4-4-4-12 on 8888 Dominators. It will run Orthos blend for 12+ hours with no problems. Everything seems rock solid and then every few days when I turn on my screen everything is dead. Attempts to boot the system will freeze every time with CHIPINIT or DET DRAM. I swap memory to a cheap stick, and it starts booting, but nothing will bring it back online. Unplugging it, clearing the CMOS, etc. all have no effect. It just hangs at CHIPINIT and wont post.

If I let it sit disconnected for 30 minutes I can get it started again. Then it will work flawlessly. Orthos will run for hours and everything is solid... then a few days later, it happens again. I am very frustrated at this point. CPU temps don't go over 56-57C running Orthos, idle they are at 42C or so. I don't know if I should RMA or not. Powersupply is the Corsair 620W (Seasonic).

It's very frustrating, especially after all the BS I went through with the EVGA 680i POS killing my memory.

Just got this board last night. And nothing but problems from the get go. Same thing is happening to me also. Using a quad core liquid chilled ocz pc8000 and ati 1950 crossfire. Only way to get crossfire working is to use new drivers with old catalyst control center....unbelievable. By far the worst board i have ever had. FSB max is 360 on this board.this cpu was 445fsb stable on My bx2. Also...Does turning power supply off suppose to reset the bios on this thing or what? cus it doesent, or is there another way you are suppose to do it? Pulling out one of my video cards sometimes brings this pig back to life but not to often.

[iviustang50h]

I just received a blue sreen of death followed by a reboot after 11 hours of orthos. I had just woken up and opened asus probe to check the MB temps and bam, BSOD and the computer rebooted! This is very frustrating!!!

Anyone know what might have caused this? My vcore is 1.5 now. How high can I take the vcore using a tuniq tower for cooling?

[DoomSayer]

Just got this board last night. And nothing but problems from the get go. Same thing is happening to me also. Using a quad core liquid chilled ocz pc8000 and ati 1950 crossfire. Only way to get crossfire working is to use new drivers with old catalyst control center....unbelievable. By far the worst board i have ever had. FSB max is 360 on this board.this cpu was 445fsb stable on My bx2. Also...Does turning power supply off suppose to reset the bios on this thing or what? cus it doesent, or is there another way you are suppose to do it? Pulling out one of my video cards sometimes brings this pig back to life but not to often.

youre doing something very wrong if youre max fsb is 360.
I boot at 487 fsb

if youre talking about clearing CMOS its totally gay on this board.
you need to disconnect youre psu and then push the cmos button.

[Severance]

youre doing something very wrong if youre max fsb is 360.
I boot at 487 fsb

if youre talking about clearing CMOS its totally gay on this board.
you need to disconnect youre psu and then push the cmos button.

Thanx for clearing up the reset question. I just got another commando from local comp shop and its same results for me. I have three setts of d9 ram here and none will boot on this board anymore. only ram thats working at this point is elpida sticks. If i set all to auto in bios then it works fine. but any overclock what so ever and it goes bonkers.