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

[jugeen]

I have installed bios 1001, confirmed and working by me

again can someone please post what changes have been made ?

[ 1001 ]
----------------------
1 Support AHCI mode SATAII hot plug function
2 Fix after downgrade CPU ratio, the Conroe L frequency not correct under ASUSCPU
3 Add new CPU uCode to support new processors

[Chosen.]

After further testing, I found out the reason I was rock-stable at 400MHz fsb but couldn't complete POST at 405MHz, was because of an FSB hole around 400-420.
So I lowered the multiplier, and jumped the fsb to 440MHz, and presto! Fully stable, gaming, 3D and 1+ hour of 4ple Prime:



Next step was around 460MHz, which also proved stable. Things started getting "blue" ( ) at around 480MHz, so I backed down to 440Mhz for the time being, where I am planning to leave it for a week or so, before I start stress testing at 460MHz.
Voltages are the same as the ones I had for 400MHz, which is 1.4V Vfsb and 1.55V Vnb (stock heatpipe cooling + low rpm 80mm fan over NB)

[D_o_S]

Are there any problems in running 4GB memory with this board (4x 1GB sticks)? Will it still be dual-channel?

Also, anyone have a QX6800 on this board? How does it clock?

Thx.

[krompirusa]

Cellshock c5@2.95v + Asus Commando
1290 c4 @ 2.95v
http://valid.x86-secret.com/show_oc?id=189806

I give them up to 3.1v ( mesured with multimeter) but oc was the same
1070 c3 @ 3.1v( forgot to validate )
http://shrani.si/?535c3y1vb.png

Max spi1m on air C2D E6600@4067MHz, 1.7v | Cellshock c5 2x1gb DDR2-1000@1016 4-4-3-5 | Asus Commando
http://shrani.si/files/zajebanuxaqk.png

And a suicide sreenshot at 4.1ghz@1.7v on air

[HoriWanderFuLL]

After further testing, I found out the reason I was rock-stable at 400MHz fsb but couldn't complete POST at 405MHz, was because of an FSB hole around 400-420.
So I lowered the multiplier, and jumped the fsb to 440MHz, and presto! Fully stable, gaming, 3D and 1+ hour of 4ple Prime:


Next step was around 460MHz, which also proved stable. Things started getting "blue" ( ) at around 480MHz, so I backed down to 440Mhz for the time being, where I am planning to leave it for a week or so, before I start stress testing at 460MHz.
Voltages are the same as the ones I had for 400MHz, which is 1.4V Vfsb and 1.55V Vnb (stock heatpipe cooling + low rpm 80mm fan over NB)

Hi i have a commando with a Q6600 and mines runs bit differant to yours...
Mine wont boot from 375 fsb up to 400 fsb.

But when i Set to 401 fsb it boots right up to 460 fsb....weired ay ??
any reasons why yours boots at diff fsb to mine ????
Thanks Hori

[sreedx2]

I am having an issue, ever since I have got a new conroe and try to update the bios to either 902 or 1001 after a few reboots the bios will post and right before loading windows it will just lock, this has happend with both bios's listed now back to 0803

I was running blend for 14 hours then my rig just rebooted, from there I ram some memtest and got errors so I upped the voltage one and no errors but could the reboot be from the ram or the cpu because before I was getting a lot of bluescreens, now just a reboot ?

here are my settings

CPU vcore : 1.4625 bios 1.43 under load
FSB term : 1.2
NB : 1.325
Memory voltage : just over 2.2v
SB : 1.5
SB chipset : 1.050

390x9 3.5ghz ram at 4:5 487.5mhz 4-4-4-10

I was thinking of bumping the FSB down to 389 to see if that makes any difference ? or now that I have no memory errors try orthos blend again, I just find it weird no bluescreen just a reboot so can that be ram related ?

[Chosen.]

Hi i have a commando with a Q6600 and mines runs bit differant to yours...
Mine wont boot from 375 fsb up to 400 fsb.

But when i Set to 401 fsb it boots right up to 460 fsb....weired ay ??
any reasons why yours boots at diff fsb to mine ????
Thanks Hori

I bet it's your ram. Not that it's bad or anything, but I am pretty much convinced now, that it's all down to the ram sub-timings that we don't have access to, through BIOS. In any case, the 400MHz mark seems to be the point where a lot of things change, when it comes to ram+fsb cooperation.

Also, the above tests were not possible with my previous ram (Gskill 2GBPK) which although was stable to up to 950MHz with a divider different to 1/1, when I set 1/1, it would crap out around 840 (either the ram or the chipset/fsb).
With the new ram (Cellshock 800MHz D9) all the options work...

[Chosen.]

bump

(still reading this thread, so I can't let it die )

[Marco André]

Hi!

I've this motherboard and with a C2D E6600, how can i decrease the multi?

[Drager2]

diplomatan1 RTFM! Advanced > CPU Configuration > Modify ratio Support > Enabled.

My questions: Is it true that this mobo doesnt have 1600strap? I cant load 500fsb after stock. I have to load 450fsb first and only after that 500. So everybody has such bug?

[oqvist]

trying to install the matrix storage controller on my commando on vista but it says it doesn´t meet the minimum requirements??? Core 2 duo E6600, 8800 GTX 5 sata drives...

[HoriWanderFuLL]

I bet it's your ram. Not that it's bad or anything, but I am pretty much convinced now, that it's all down to the ram sub-timings that we don't have access to, through BIOS. In any case, the 400MHz mark seems to be the point where a lot of things change, when it comes to ram+fsb cooperation.

Also, the above tests were not possible with my previous ram (Gskill 2GBPK) which although was stable to up to 950MHz with a divider different to 1/1, when I set 1/1, it would crap out around 840 (either the ram or the chipset/fsb).
With the new ram (Cellshock 800MHz D9) all the options work...

Thanks for that info mate

[Chosen.]

No probs mate. I moved to the P5K Deluxe now, as the Commando killed my QX6700 and I thought it was the board that died.

Did the Vdroop mod, booted with the 1.4V from BIOS, monitor showed 1.544V. Reset to defaults and now monitor shows correct voltages under load:
1.35 in BIOS shows 1.35
1.4 -> 1.4
1.45 -> 1.44
1.5 -> 1.49
1.55 -> 1.53

Ran a 3dMark06 at 3900 with 1.55, got a D3D driver error, rebooted, got "Bad BIOS checksum" message. Attempted BIOS recovery with the Asus CD and a USB key with the latest BIOS renamed to "COMMANDO.ROM", on reboot got the same message (that happened several times).
Tried 3 cards (8800GTS + 8800GTX + X600 Pro), 3 sets of ram (Gskill 2GBPK, Cellshock D9s, El-cheapo 256Mb 533MHz), 2 PSUs (Hiper 580W, Seasonic S12 600W), but unfortunately I did not try a 2nd proc...
So I RMA'd the Commando, got the P5K-Dlx, first boot gave me the exact same message Commando gave me :/
So after using 3 sets of ram, 2 PSUs, 3 gfx cards and 2 boards, my fear of a dead QX6700 came to life. The proc is now sent to hipro for an attempt to revive (proc boots the board(s) but doesn't complete POST)

So happy that the P5K board doesn't need a Vdroop mod...

[blade148]

hi ya I'm running a Q6600 on a commando. So far very good results and quite stable too. I'm wondering what the max voltages are for the NB ( is it 1.6Volts ? ) etc etc,

I understand there is a FSB hole with these mother boards around 345-400hz is that right .?

and has any got any BIOS settings ? for over clocked cpu's ? ( I mean a quick and dirty guide. ) as there are many settings that I don't know the meaning . ( I come from AMD over clocking ) So far I just leave the other settings on AUTO for now.

[MacClipper]

I dunno about the other stuff right now but I had the same problem with my Crucial PC2-5300 C3 tenth anniversary ram. No matter what I set the tRAS would always stay at 18 with this board. In the end I used SPDTool to change the SPD on the memory sticks so it had a tRAS of 12 at 333mhz. Now I can set it to whatever I want with the commando bios
This is probably a bug though and contacting Asus about it would likely get it fixed.

Just got the Commando and ran str8 into this problem of the Tras setting stuck at 18 despite BIOS settings (version 1001) on my Crucial PC5300 Tracers - any alternative fix other than flashing the RAM sticks?

Thx.

PS: If not, is there a good guide on using SPDTool to adjust the Tras somewhere?

[Khapz]

i'm using e4300 on my commando, but i'm set multi on 8x or 7x in everest and system about windows mark as 9x. example: running e43 in 266x8x = 1866 ok? but in windows and coretemp .95 and everest last version mark as 2400 = 9x266
it's normal?

and other problem, when i open coretemp .95 in windows i'm get a bluescreen crash how to fix this?

using bios 1001, winxp 32 with lasted drivers installeds

[bullit]

trying to install the matrix storage controller on my commando on vista but it says it doesn´t meet the minimum requirements??? Core 2 duo E6600, 8800 GTX 5 sata drives...

I think you have to install the Operating System on AHCI mode (on the BIOS) to intel matrix storage controller recognize your hard drives.

[MacClipper]

btw, since no one has mentioned it yet - S3 sleep/resume works beautifully on this mobo (on 1001).

[MadSurfer]

Has anyone tried to place Commando upside down in an inverted ATX style case such as Stacker 830 or Lian Li? Will the heatpipes operate normally or is it unsafe?

[Khapz]

i'm using e4300 on my commando, but i'm set multi on 8x or 7x in everest and system about windows mark as 9x. example: running e43 in 266x8x = 1866 ok? but in windows and coretemp .95 and everest last version mark as 2400 = 9x266
it's normal? and its running in 8x, only marks 9x

and other problem, when i open coretemp .95 in windows i'm get a bluescreen crash how to fix this?

using bios 1001, winxp 32 with lasted drivers installeds

somebody can help me?

i'm flashed bios via windows (asus updt) its good?

[BenchZowner]

New BIOS for Commando, BIOS v1302
Gonna check it out soon

[Drager2]

Khapz 1.Maybe yes. Check cpu freq in CPU-z. 2. Use old core temp.
BenchZowner We`re waiting

[MacClipper]

It'll be great if this new BIOS fixes the stuck at 18 tRAS for D9GMH DDR667 Crucial sticks, waiting too.

[MacClipper]

Are there any problems in running 4GB memory with this board (4x 1GB sticks)? Will it still be dual-channel?Thx.

E6300@475FSB 1:1 with 4GB Crucials (2 x Tracers, 2 x 10th Annivs), note the tRAS stuck is at 18 bug (grrrrrrr!). Hope new BIOS can solve the tRAS bug, really dampens mood to push the o'c.



NB: Vcore set 1.45v, Vdimm 2.10v, NB 1.3v, FSB 1.3v, SB 1.1v, all others Auto.

[MacClipper]

I dunno about the other stuff right now but I had the same problem with my Crucial PC2-5300 C3 tenth anniversary ram. No matter what I set the tRAS would always stay at 18 with this board. In the end I used SPDTool to change the SPD on the memory sticks so it had a tRAS of 12 at 333mhz. Now I can set it to whatever I want with the commando bios
This is probably a bug though and contacting Asus about it would likely get it fixed.

Can confirm that this works for my rig too, thanks for the tip. Crucial still hasn't gotten back to me so I just went ahead and got it done.

PS: change tRAS to 36ns for those still wondering about the value.