Help with Asus Commando Issues

[iviustang50h]

I just received my Asus Commando, E6600, tuniq tower and G.Skill DDR1000 (rated at 4-4-4-5 @2.3V) memory. I installed everything and widows installed without a hitch, but I can't even maintain stability for more than a minute using prime95/orthos when overclocked. I overclocked to 3.2GHz and prime95 errors in less than a minute. I have read through this forum and xtremesystems.org's forum and know that most people can hit mid 400's FSB with some tweaking and remain stable on air cooling.

I installed the tuniq tower following the directions perfectly and hand tightened the four screws until I almost couldn't turn them anymore. Is that too tight? The fan inside the Tuniq faces the rear and blows air out the back of the case. Is that correct?

Here were my settings when overclocked:

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. Temps never got higher than 50 degrees Celsius using core temp (case temp was around 40). I used artic silver 5 as the thermal compound.

Does anyone have any suggestions?

Thanks!

 

[Supershanks]

Hi iviustang50h, welcome to the forum.
Re CPU settings:-
unless u change the multiplier from default leave Modify Ratio support as disabled.

See if that helps
Most of my overclocks have started from:-

evrything apart from memory volts & timings to auto.
Dial in desired fsb & go.

load up asus probe assiuming u can get in xp. Make a note of vcore.

run OCCT which only takes 30m & if it passes u know you have a moderately stable oc. I'll ussually follow with an overnight orthos if i'm finished ocing.

As i'm on air & to keep the temps down i usually try putting the pcprobe vcore into bios & re-testing. The auto vcore usually overstates the vcore needed & i've found using the vdroop adjusted vcore from probe will give the same stability at 2~3C less.

hope that helps, let us know how u get on.

Luck

 

[Gary Key]

You need to increase your NB Voltage, anything over 320FSB at stock voltages is not going to provide 24/7 stability.

 

[Warpirate]

Gary have you guys done a review on this board and if so did you have any issues?

 

[Supershanks]

You need to increase your NB Voltage, anything over 320FSB at stock voltages is not going to provide 24/7 stability.

If u laeve NB volts on auto it scales. i'm running @385x9 with nb on auto see link

385x9@4:5 note Auto NB Volts in Asus Probe
1.60v is ample have seen may pull it back to around 1.54

 

[iviustang50h]

oops, double post. SOrry

 

[iviustang50h]

Thanks, Gary. I did up the voltage to NB 1.5 and ran orthos overnight. It had passed 11 hours when I came down this morning. So I opened Asus Probe to check temps for the MB and I got a brief blue screen of death followed by my PC rebooting. Anyone know what would have caused this? My MB temp was around 44 and my CPU was 58 undle load of orthos. Were temps too hight? Why would I get a BSOD right after opening Asus probe?

Gary, if you don't mind me asking, how did you mount the Tuniq Tower when you tested it for review? IOW, which way was it facing/the fan blowing. I mounted it with the fan blowing towards the rear of the case so it would exhaust the heat. Is this correct?

By the way, this site is phenomenal! I check it every day and love the effort you guys put into everything! Thanks!

 

[tcsenter]

Set your DRAM voltage to AUTO. Humor me.

 

[iviustang50h]

I tried loosened timing but cannot get anything better. I am going to return the mobo and probably get a different E6600 in case I got a dud. The mobo came with a broken memory clip anyway, so I should certainly get that fixed.

What are your thought, though? Did I get a crappy E6600 or is it the mobo?

 

[SilverPhish]

Im having simular problems with qx6700 Dominators 8500 and Commando with Tuniq 120 [BIOS]FSB325x11 Vcore @ 1.5125 V FSB term @ 1.450 V RAM 5 5 5 15 @ 2.3 V NB @ 1.5 V and sbvcore @1.65 sbchipset @1.2

Been trying alot of different tunings and FSB settings and alot of them yield the same stability issues with both occt and Orthos getting computational errors.

BUT I was experimenting with vista 64 ulti so alot of beta drivers and whatnot to get lost in.

btw My tuniq is blowing towards the RAMs