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

I have a Commando on its way to me. I see many tests in this thread but IMHO these tests have been anything indicative of stability. A minimum of an 8hr Orthos blend should be mandatory and 12hrs is even better (I've had Orthos error out 9hr 29min 9sec). I've also found that Orthos should be at a priority of 3 instead of the default of 1 and at the same time the tester should use his PC for normal apps.

I guess if you're testing for benchie numbers only then a 1hr run is fine. But those who claim stability with such tests do others a disfavor.

Even Orthos is not the be-all end-all of bench testing. My brother's ICFX3200 can run a 24hr Orthos blend yet it locks when running one of his intensive Oracle scripts after 15min. My advice: find your max stable overclock with Orthos then bump down 100MHz to be safe. That's what he did and he hasn't had any problems at all.

I have done testing with an eVGA 680i, Gigabyte DS3, Infinity 975, and DFI ICFX3200. So far my max oc was with the ICFX3200 at 3651MHz. I hope to achieve more with the Commando.

One question: Has anyone experienced lockups with a USB mouse with 0803? I've heard it can be an issue.

Quote:

---

Originally Posted by NLight95

A minimum of an 8hr Orthos blend should be mandatory and 12hrs is even better (I've had Orthos error out 9hr 29min 9sec). I've also found that Orthos should be at a priority of 3 instead of the default of 1 and at the same time the tester should use his PC for normal apps.

I guess if you're testing for benchie numbers only then a 1hr run is fine. But those who claim stability with such tests do others a disfavor.

---

Good luck on that. I don't mean to be harsh but as has been said time and time again on this forum, this is Xtreme Systems not Xtremely Stable Systems.

Running Orthos for x-amount of hours is good for two things, using a lot of electricity and making sure that orthos will run. Stability is what you make of it, if all people want to do is run Superpi or run a game then as long as you can finish a run or play without issues then thats plenty stable enough.

Have any of you tried DQW chips with commando? Any problems?

Mine don´t get further than 450 or so with 4-4-3-5 when I can do around 520 with team xtreme d9 GMH..... Any info about it?

Thanks

Quote:

---

Originally Posted by HermS

Good luck on that. I don't mean to be harsh but as has been said time and time again on this forum, this is Xtreme Systems not Xtremely Stable Systems.

Running Orthos for x-amount of hours is good for two things, using a lot of electricity and making sure that orthos will run. Stability is what you make of it, if all people want to do is run Superpi or run a game then as long as you can finish a run or play without issues then thats plenty stable enough.

---

Not harsh at all. I just don't like when I see statements like "completely stable" when in fact it's totally contrary to the truth. Completely stable means just that--100% stable. I see a degradation in stability testing even with high profile sites like Anandtech (which I've discovered considers 30min Orthos stable with various testing). My point: Don't toss around the word "stable" until it has no meaning--leave the word out and let the result speak for itself.

Enthusiasts who play games--perhaps the primary reason why they oc--and then find their PCs locked up will sometimes blame it on the game or Windows or some other software when in fact it's hardware related. This puts an unnecessary burden on tech support staff (I know--I've worked in several for years). To mis-educate people about what stability really is only leads to more confusion and frustration. Everyone is entitled to their opinion but their opinion may not be reality. :D

Now back to the Commando... ;)

I would like to know what BIOS most favor, for stability and not necessarily overclocking. I hesitate on upgrading to 0803 because of some of the issues being reported (I won't repeat them here).

I've seen from a post of Tony that there is eventually going to be a Rev B Infinity 975 board. If you read this Tony perhaps you can comment on the board's availability.

What is best clock gen program for oc.
Thanks in advance

i think SETFSB

http://www13.plala.or.jp/setfsb/

Got my mobo from RMA, for now it's working perfect :D

regards

Quote:

---

Originally Posted by NLight95

Not harsh at all. I just don't like when I see statements like "completely stable" when in fact it's totally contrary to the truth. Completely stable means just that--100% stable. I see a degradation in stability testing even with high profile sites like Anandtech (which I've discovered considers 30min Orthos stable with various testing). My point: Don't toss around the word "stable" until it has no meaning--leave the word out and let the result speak for itself.

---

I totally get what your saying, some people run orthos priority 1 for a half hour and say its stable then wonder why they have random reboots. But you also have to understand that stability is subjective.

Just because you have certain standards for what you consider stable doesnt mean thats across the board. For example i run orthos at no less than priority 9. I've had an oc that was unstable after 19hours on priority 9 run for days at priority 1. So like i said its all subjective.

On the flipside though if you can run orthos for 30min to an hour blend with a high priority then thats a good start and it shouldnt take much tweaking to find more stability.

About the bios, i never updated past 0702. I saw alot of posts with people trying to revert so i just took it as a bad sign and havent had any issues with the board.

Has anyone tried the 0803 BIOS yet? I see there weere issues with a bios of the same name when used in the Striker.

Quote:

---

Originally Posted by MrDeeds

I totally get what your saying, some people run orthos priority 1 for a half hour and say its stable then wonder why they have random reboots. But you also have to understand that stability is subjective.

Just because you have certain standards for what you consider stable doesnt mean thats across the board. For example i run orthos at no less than priority 9. I've had an oc that was unstable after 19hours on priority 9 run for days at priority 1. So like i said its all subjective.

On the flipside though if you can run orthos for 30min to an hour blend with a high priority then thats a good start and it shouldnt take much tweaking to find more stability.

About the bios, i never updated past 0702. I saw alot of posts with people trying to revert so i just took it as a bad sign and havent had any issues with the board.

---

Thanks for your insightful reply. My "standard" for testing is in a continuous state of flux, so I try to weigh any suggestions and incorporate those I feel would be benficial. As I mentioned previously, Orthos is not the be-all end-all test; my brother discovered that rather quickly. I wish I had a "run-time executable" of his Oracle script because he's found it to be a superb indication of stability, other than video. I may try your suggestion as I really tire of long Orthos tests and I do agree with HermS that it's a waste of electricity. I'm always on the hunt for a test that yields quicker results but haven't found any yet. Instead of Orthos I've been giving strong consideration to BOINC instead. At least that way the computing cycles are not going to waste. And per your method, I'd run at at high priority.

I finally found all the Commando BIOSes here. Think I'll stay with 0702 as well.

ftp://ftp.asus.com/pub/ASUS/mb/socket775/Commando

edit(Forgot to mention have tried 0702 and I'm presently on 0803) Hardware as per sig.

This is driving me nuts. For the life of me I can't get x-fi to install/detect. Have tried various pci slots, and even my old audigy 2, but no joy.

I have setup raid-0(A first for me) with this setup, would that have anything to do with it. Is it SB voltage related?

Basically has any one else come across this problem? If so your help would be appreciated.

Cheers

RLM

@RLM - Have u tried it with Bios PCI Pnp - [Plug & play OS} Enabled the default is disabled.

I've had some problems with the commando soundcard. Progs claim that EAX is not enabled. I've tried two different sound drivers but the problem remains. Ay tricks? Can you check with the latest Everest if it shows the same info as in my case? Many thanks.
http://img99.imageshack.us/img99/826/commando2ow1.jpg

Quote:

---

@RLM - Have u tried it with Bios PCI Pnp - [Plug & play OS} Enabled the default is disabled.

---

Thanks Supershanks, I hadn't considered that. That bit of info, may well help in the future.

I have it up and running now. Not positive, but it seems to be a problem either with my new case or the PCI slots. The card, when pushed in doesn't sit flush with the screw hole on the back bracket, if that's the right word. It's a couple of mm's out. You have to use a bit of force to align it and screw it in. This may well of been the problem in that, when screwed in it's pulling the card out a bit.

Now I don't have it screwed in, and it's working.

It's either that or the fact I reset the the cmos, with the card installed.

RLM

nice avatar supershanks..:banana: ...thats all i have to say

keep the good information comming guys :cool: , this might be my next board

peace

Just picked this up to replace a dead P5B after Windows BIOS flash. :( The software package consists not only of GRAW, but Kaspersky AV, and 3D Mark 06 advanced. :D What sort of sinks are you guys using for this board? I've got a Jing Ting for the chipset, but need something for the SB that won't interfere w/ the 8800. Also, cooling the PWM's w/ some Microcool's worth it?

Having a bit of a mess with this board.

Have tried 400x9 vcore 1.45v with a 4:5 divider. Memory 1000 4-4-4-12-42 2.3v. All sorts of voltage settings, but cannot get any stability at all. It doesn't like it.

405x9, 410x9 no problems. I'm new to this strap malarky, but I'm guessing that at <=400 it's on a 1066 strap and 400+ is 1333. Is that right?

Is there any secret to getting stability at 400x9. I've switched off everything on the cpu apart from vanderpool, and in the bios I've switched off cpu spectrum.

I've got to say on the quad GT this was a pretty easy setting.

Any help would be appreciated:)

RLM

@TheReds -

Quote:

---

nice avatar supershanks.. ...

---

Cheers m8 Hehe:D not caught yours b4 either, guess yu don't manage many home matches:)

@RLM I think the strap switches @401 , it's probably memory timings/voltage tweaks to get 4:5, assume 1:1 is stsble ??

Hej guys. What about the soundcard issue? Can anyone please check it for me? It seems f*cked up to buy a $200 mobo and not to have 3D hardware sound. Lack of EAX support is really weird.

Well that was a big old :banana::banana::banana::banana:up. Booted 400x9 fine with looser timings on the memory 5-5-5-15. Then used memset to tighten up to 4-4-4-12. System crashed and one of raid disks failed. Ended up losing a couple of days work. Lesson learnt :slapass:

Didn't realise raid was so fragile.

Quote:

---

Hej guys. What about the soundcard issue? Can anyone please check it for me? It seems f*cked up to buy a $200 mobo and not to have 3D hardware sound. Lack of EAX support is really weird.

---

With my sound card problems, it just wasn't being detected. It wasn't just the way the card was mounted, but I had to reset cmos once installed to sort it out.

Just wonder though is your soundcard okay? I know we don't all have a spare machine lying around, but are you able to test it in another machine.

I know my audigy II progressively failed overtime. It went for about a year without being able to install and run eax presets. eventually I lost volume, before I replaced it with the X-fi.

RLM

Quote:

---

Originally Posted by RLM

405x9, 410x9 no problems. I'm new to this strap malarky, but I'm guessing that at <=400 it's on a 1066 strap and 400+ is 1333. Is that right?

Is there any secret to getting stability at 400x9.

RLM

---

You are right, from 401 Mhz you have 1333 strap.

To get stability at 400x9 with a 6600 I have to push vcore at 1.585 (measured by bios 1.5 idle and 1.47 full load); I have nbridge at 1.55 and fsb vcore at 1.45.

With these settings I am rock stable but I am on water and after some hours of Orthos I reach 80 C&#176; on cores.

This is my cpu......I was not lucky but not completely unlucky....

@RLM,

hv u tried disabling HD audio controller in bios....might help

Loving my recently purchased Commando here is what I have so far

http://valid.x86-secret.com/show_oc?id=172585
Vcore 1.6 in bios 1.54 -1.53 load
NB Vcore @ 1.3

all other voltages at lowest setting

I do notice some odd glitches or bugs if I may call them that

when I first had vista installed I was getting all 5.9 except cpu and ram 5.3 and 5.6 being ram, after I corrupted my OS so after all said and done it now reads all 5.9 except the cpu at 4.8 with an OC of 3.6 ghz anyone else get this ?

also after changing settings in the bios, the rig shuts down and starts back up sometimes twice :confused:

Quote:

---

Originally Posted by RLM

Well that was a big old :banana::banana::banana::banana:up. Booted 400x9 fine with looser timings on the memory 5-5-5-15. Then used memset to tighten up to 4-4-4-12. System crashed and one of raid disks failed. Ended up losing a couple of days work. Lesson learnt :slapass:

---

Try running with cas 5 and other timings as u like/mem can handle. With 1066 strap and 4/5, cas 4 is a no go, regardless volts and mem. It's a chipset limitation, same applies to P5B.

BTW the worst enemy of a raid 0 array, is mem testing... ;)

ATTN ALL COMMANDO OWNERS!!!!!!!!!!!!!!!!!!

please check with me where did your Commando PCB was made.

mine was made in China

yet, somehow pictures in this EK block thread shows PCB made in Taiwan ( http://www.xtremesystems.org/forums/...95#post2039795 )

i've also notice another picture from a PC mag in UK showing PCB made in Taiwan too.

could this mean why some of us Commando owners are having great OC and others not?

maybe someone can post their results with info from where their PCB is made?

My first commando (dead)
Made in taiwan
http://florianflf.free.fr/bench_comm...CF0053%20b.JPG
not very good in o/c and especially for the ram

My second commando (dead)
Made in taiwan
http://florianflf.free.fr/bench_comm...o/RIMG0021.JPG
Better than the first (boot at 580 fsb, 588 fsb max)

My third commando
Well i hope simply that it will be more solid than the two first :p:

Quote:

---

Originally Posted by florian76

My first commando (dead)
Made in taiwan
http://florianflf.free.fr/bench_comm...CF0053%20b.JPG
not very good in o/c and especially for the ram

My second commando (dead)
Made in taiwan
http://florianflf.free.fr/bench_comm...o/RIMG0021.JPG
Better than the first (boot at 580 fsb, 588 fsb max)

My third commando
Well i hope simply that it will be more solid than the two first :p:

---

2 dead mobos and you want another one ? Asus fanatic :confused: :lol: j/k

hmmmmmmmmmmm..........

need more info......

if someone post up results of crap OC from a china PCB, then im going to stab someone with them heatpips......

Quote:

---

Try running with cas 5 and other timings as u like/mem can handle. With 1066 strap and 4/5, cas 4 is a no go, regardless volts and mem. It's a chipset limitation, same applies to P5B.

BTW the worst enemy of a raid 0 array, is mem testing...

---

I can't find the thread now, but I was inspired by Herms's results. If I'm right he was running 400x9 4:5 and with Gskill GBHZ. I'm guessing he was pretty lucky with his board though.

I'm currently on 405x9 4-4-4-12 4:5 Vcore set to 1.45v reading 1.41v. The Vdimm is set to 2.3v and is jumping around between 2.28 and 2.35???

My QX6700 should be here on monday, along with the swiftech kit, so the boards got to come out. Seriously considering now, whether to put the Quad Gt back in (Potentially a raid nightmare though). The 1066 strap really doesn't seem to be such an issue on the Quad GT. Never plain sailing, but will see.

Thanks for the info on raid, that what I wanted to know. Got to say it's taking a bit of the fun out of oc'ing. I do have a third drive connected. I'm thinking I might be better to disconnect the raid drives, and run the OS of that, while I'm tweaking:confused:

Cheers for your feedback. Appreciated.

RLM

My board says made in china currently running 400x9 see my post on the page before this


what is the difference between the boards ?

Quote:

---

Originally Posted by RLM

I can't find the thread now, but I was inspired by Herms's results. If I'm right he was running 400x9 4:5 and with Gskill GBHZ. I'm guessing he was pretty lucky with his board though.

I'm currently on 405x9 4-4-4-12 4:5 Vcore set to 1.45v reading 1.41v. The Vdimm is set to 2.3v and is jumping around between 2.28 and 2.35???

---

I think for running at 400 4:5 (1066 Strap) NBVCore is of utmost importance; I used 1.65v set in Bios which gives 1.68v when measured by a multi-meter. Once you move onto the 1333 strap the board doesn't need nearly so much voltage, for example 450 4:5 needs only 1.6v NBVcore on the 1333 strap.

All my results are summarised here and you should be able to at least get an idea of the voltages needed... obviously not all boards or chips react the same though.

Best of luck getting your rig setup just the way you like it, if there is any way I can help let me know. :toast:

Maff

Safe NBVcore for 24/7 with the stock heatsink??:confused:

Is that at me?

If so, I couldn't say. I only use the board for benching and not in a closed case so all I can tell you is that it was memtest and bench stable for a couple of hours at a time, this was with stock heatsink. For further testing in a 24/7 closed case environment you'd need to check for yourself. Sorry I can't be more help than that. :)

Cheers HermS, your help is appreciated.

I haven't given this board much of a test yet, but early indications aren't great.

Reluctant to try out the 1066 strap 4:5 again, after buggering up my raid setup last time.

This is just a quick test 410x9 4:5 4-4-4-12. Would of been nice to have results in the 13 seconds rather than 14. 3D Mark results seem to be pretty poor as well. Might be missing something, but not sure what. My board is also a screecher. I asked for the buzz edition, but they were unfortunately out of stock.

Edit: Looking at your results that 1066 strap really makes the difference. I'll get some work out the way and have another blast at it over the weekend I think)

http://img120.imageshack.us/img120/9...iresultgy0.jpg

Cheers

RLM

A comparison with my Quad Gt. Posted these result before. Vcore is at 1.47 on the Asus as opposed to 1.42 on the Abit. DDR voltage 2.05 1:1 as opposed to 2.325 4:5 on the Asus. Basically I'm having to stick a lot more juice into my components on the Asus to achieve lesser results.

I realise the strap is the issue here, but the fact that this board is struggling with the 1066 strap is a limitation for me.

http://img168.imageshack.us/img168/5...rpitesteq3.jpg

Cheers

RLM

Been following this post for awhile all the info here is very useful. Just took off the heatsinks and installed Thermaltake Spirit on nb and sb. Will post pics later. Here's my latest results:banana:

I don't know if I'd call it a coil noise, but the ram chirps on this board and something's definitely making a faint, whine that goes in and out. Very faint, but annoying...

Quote:

---

Originally Posted by ReaperX

Safe NBVcore for 24/7 with the stock heatsink??:confused:

---

just see how low you can have it stable, some people can have it down really low mine is at 1.3

specs are in sig

Quote:

---

Originally Posted by RLM

A comparison with my Quad Gt. Posted these result before. Vcore is at 1.47 on the Asus as opposed to 1.42 on the Abit. DDR voltage 2.05 1:1 as opposed to 2.325 4:5 on the Asus. Basically I'm having to stick a lot more juice into my components on the Asus to achieve lesser results.

I realise the strap is the issue here, but the fact that this board is struggling with the 1066 strap is a limitation for me.

Cheers

RLM

---

First, why run the commando at 410fsb if you want to use the 1066 strap then run it at 400fsb. Simple enough and like the man told you earlier memory ocing is tough on raid. 1.47v on the asus isnt really that, its been mentioned time and time again that with vdroop the board will go down .05 to .07 volts.

So your really running somewhere around 1.4v give or take. If you want to be sure pull out a multimeter. You cant blame the board for the voltage on the ram considering you are running 4:5 and high fsb cas4. I understand you feel your trying to compensate for the 1333 strap but unless you've somehow found a way to get paid to run superpi. I'd be hard pressed to believe that the commando is giving you so much less performance wise in comparison to the quadgt.

I just think that some of you guys fixate too hard on the whole strap thing. Yes its slower in pi but the 1333 strap should allow you to oc higher which compensates for the slower strap. I cant imagine your cpu is stuck at 3.6ghz. Now if you arent concerned about max oc and really only want to run 400x9 then i dont think the commando is for you because you arent reaping the benefits of what its really good at. High fsb.

Removed: Longwinded and not worth discussing. Lifes too short.

Spirits on the NB and SB

http://www.xtremesystems.org/forums/...9&d=1172750215

http://www.xtremesystems.org/forums/...0&d=1172750763

http://www.xtremesystems.org/forums/...1&d=1172750763

A friend of mine has a spare Jing Ting that I thought about using on the SB, but I was concerned about it impeding air flow to the GTX. Do you notice anything unusual there w/ your spirits?

[QUOTE=grsz06]Spirits on the NB and SB

Curious is that the dominator ram cooler ? ... how loud is it

Quote:

---

Originally Posted by Jodiuh

A friend of mine has a spare Jing Ting that I thought about using on the SB, but I was concerned about it impeding air flow to the GTX. Do you notice anything unusual there w/ your spirits?

---

In the TJ09 there is an intake fan that blows on the 8800 and the SB so I have not had a problem with that.

Quote:

---

Originally Posted by Jodiuh

A friend of mine has a spare Jing Ting that I thought about using on the SB, but I was concerned about it impeding air flow to the GTX. Do you notice anything unusual there w/ your spirits?

---

In the TJ09 there is an intake fan that blows on the 8800 and the SB so I have not had a problem with that.

Sreedx2

I don't think the Dominator fan is that loud, but I do have 5 case fans running, so it's hard to tell. Still in the TJ09 with Scythe S-Flex 120's the noise isn't overbearing

Hi All

If this has been answered before I appologise, I tried reading the whole thread and didnt see any answers to my questions so here goes:

ClockGen, what PLL should be used?

Anyone have any issues with using MemSet? I am using 3.2 but will try 3.1 or 3.0 as I have seen screenshots of others using the older versions. When I try to set any timings in MemSet, if I go to CPU-Z it cannot seem to read the timings back, and if I reopen MemSet it cannot display the timings either. I have to reboot to get CPU-Z to show the timings again.

Also, I dont know where this fault lies but I am running Crucial Ballistix PC2-5300 RAM and on default SPD its running 4-3-3-12 @ 400mhz. If I change the Bios to manually configure the timings it doesnt seem to matter what I set the last digit to, it is always 18. so setting 4-4-4-12 in the bios results cpu-z showing 4-4-4-18. Anyone else with this problem? I was thinking of taking the ram out, resetting the bios and turning the pc on with no ram in it to try sort of hard reset the settings and see if it makes any difference.

Hope someone can be of help. Thanks!

Yeah, the latest CPU-Z(1.39 I believe) doesn't show vcore and probably some mem timings correctly. Such is life w/ a new board. :D

Quote:

---

Originally Posted by grsz06

Spirits on the NB and SB

http://www.xtremesystems.org/forums/...9&d=1172750215

http://www.xtremesystems.org/forums/...0&d=1172750763

http://www.xtremesystems.org/forums/...1&d=1172750763

---

How did you get the Spirits to sit flat on the NB/SB?
I tried to use a Spirit on the NB of my DS3 but gave up after many tries to get it flat against the chip and went back to the stock sink with a 60mm fan on top...

self adhesive rubber spacers i would guess that give cooler a level platform

Quote:

---

Originally Posted by Jodiuh

Yeah, the latest CPU-Z(1.39 I believe) doesn't show vcore and probably some mem timings correctly. Such is life w/ a new board. :D

---

The question really relates more to MemSet I think, as it reads the timings correctly, just if I try to set anything in MemSet then it seems to bork out. If you were relating to me setting the mem timings in the bios and CPU-Z only reporting 18 where I have set 12 then I dont think its the programs fault, other people here set theirs and it reports properly?

Quote:

---

Originally Posted by MrDeeds

I just think that some of you guys fixate too hard on the whole strap thing. Yes its slower in pi but the 1333 strap should allow you to oc higher which compensates for the slower strap. I cant imagine your cpu is stuck at 3.6ghz. Now if you arent concerned about max oc and really only want to run 400x9 then i dont think the commando is for you because you arent reaping the benefits of what its really good at. High fsb.

---

I think a lot of people look at that 3.6ghz as a wall on air cooling and thats what they're shooting for. A lot of attention is then placed on achieving 400x9 oc's.

I have a question though regarding ram to go along with the 1333 strap. Is running 1:1 or 4:5 more beneficial? Would someone benefit from purchasing PC8000 stix to make 1:1 easier on the 1333 strap?

Haven't been having a great time with this board so far, but something of interest cropped up for me.

I currently have a galaxy II water cooling setup(pants I know). Only reason I mention this, is that it has a fan mounted to the waterblock, which keeps surrounding areas cool. It does tend to do a pretty good job at keeping areas like the pwms?? cool.

For the fun of it I've stuck on the optional fan on the pwm heatsink as well. Overkill I thought, but checking in asus probe, speedfan and coretemp, it seems that my cpu temps have dropped by about 6 degrees.

Does that seem right or make sense? If the pvm area gets hot does that increase cpu temps as well?

RLM

Quote:

---

Originally Posted by ubern00b

Hi All

If this has been answered before I appologise, I tried reading the whole thread and didnt see any answers to my questions so here goes:

ClockGen, what PLL should be used?

Anyone have any issues with using MemSet? I am using 3.2 but will try 3.1 or 3.0 as I have seen screenshots of others using the older versions. When I try to set any timings in MemSet, if I go to CPU-Z it cannot seem to read the timings back, and if I reopen MemSet it cannot display the timings either. I have to reboot to get CPU-Z to show the timings again.

Also, I dont know where this fault lies but I am running Crucial Ballistix PC2-5300 RAM and on default SPD its running 4-3-3-12 @ 400mhz. If I change the Bios to manually configure the timings it doesnt seem to matter what I set the last digit to, it is always 18. so setting 4-4-4-12 in the bios results cpu-z showing 4-4-4-18. Anyone else with this problem? I was thinking of taking the ram out, resetting the bios and turning the pc on with no ram in it to try sort of hard reset the settings and see if it makes any difference.

Hope someone can be of help. Thanks!

---

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.

forgive me if im asking at wrong place

ive a commando board & when i tried to downgrade(0803) the BIOS(0702), error message pop-up telling that the BIOS(0702) is corrupted/ didnt match with my board.

have u guys facing the same?

thanks

I'm considering Commando, but please comment on memory compatibility.
My 2x1GB Patriot 800LLK is rated 2.1 or 2.2v and it only contains one setting in SPD which is 400MH.
My Gigabyte DS3 Rev1 c1 hardly boots with that memory even if I boot with cheap ram and set DDR volt to +0.7v.
How is Commando doing with that kind of memory?

Quote:

---

Originally Posted by gengstapo

forgive me if im asking at wrong place

ive a commando board & when i tried to downgrade(0803) the BIOS(0702), error message pop-up telling that the BIOS(0702) is corrupted/ didnt match with my board.

have u guys facing the same?

thanks

---

addition:

ive done several times & download from each of their mirror
pr0b still consist, any solution?

.....]

To downgrade bios, you'll have to use an old version of AFUDOS.
Here's one that will work.
Oh, and for those interested, my Commando is made in china.
On a sad note, I seem to have ruined a pair of Gskill PC6400-HZ's. I only ran them as high as 2.3v at times. Usually 2.1-2.2
Doesn't seem like that would kill these from what I've read of others with this ram.

At last，I break 14.000S on commando at 3.6G with windows XP sp2
4:5 1000 4-4-3-4 no way

http://bbs.expreview.com/attachments...crBOwXjGCW.jpg

4:5 1000 4-4-4-4 ok la

http://bbs.expreview.com/attachments...LGmCPYy0rO.jpg

Quote:

---

Originally Posted by Gitsum

To downgrade bios, you'll have to use an old version of AFUDOS.
Here's one that will work.
Oh, and for those interested, my Commando is made in china.
On a sad note, I seem to have ruined a pair of Gskill PC6400-HZ's. I only ran them as high as 2.3v at times. Usually 2.1-2.2
Doesn't seem like that would kill these from what I've read of others with this ram.

---

thanks br0
but b4 i may proceed, does this version afudos same with the current downloadable afudos in asus official site?

Quote:

---

Originally Posted by grsz06

Been following this post for awhile all the info here is very useful. Just took off the heatsinks and installed Thermaltake Spirit on nb and sb. Will post pics later. Here's my latest results:banana:

---

What heatsink/cooler did you use on the mosfets?

[QUOTE=sreedx2]

Quote:

---

Originally Posted by grsz06

Spirits on the NB and SB

Curious is that the dominator ram cooler ? ... how loud is it

---

That is the Dominator cooler. It's actually rather silent. Both my Tuniq Tower & psu drown it out.

Quote:

---

Originally Posted by NLight95

What heatsink/cooler did you use on the mosfets?

---

I used this one...8 of them


http://www.performance-pcs.com/catal...oducts_id=4291

Quote:

---

thanks br0
but b4 i may proceed, does this version afudos same with the current downloadable afudos in asus official site?

---

No, it's older version that doesn't check dates of ROM file.

Quote:

---

Originally Posted by Gitsum

No, it's older version that doesn't check dates of ROM file.

---

thanks br0
already flash to 0702 again

i can see some feat. removed in latest commando's bios

:woot:

Quote:

---

Originally Posted by NLight95

What heatsink/cooler did you use on the mosfets?

---

I went commando on my mosfets. :p:

Butt Naked :banana: :banana:

My commando runs fine with no undies. As long as you have decent air flow in your case i think it'll be fine.

has any1 Entered the matrix yet with their commando, nice finishing touch.:D

Quote:

---

I went commando on my mosfets.

---

I made me own Cool Commando Mod
:D

Quote:

---

Originally Posted by MrDeeds

I went commando on my mosfets. :p:

Butt Naked :banana: :banana:

My commando runs fine with no undies. As long as you have decent air flow in your case i think it'll be fine.

---

What are your VRM temps as a result, and do you have a fan blowing on them?

I've got my QX6700 in my quad gt right now. I'm experiencing problems in that 2 of the cores are stuck at a 6 multiplier. I have all cpu features apart from Ex bit disabled. Seems this is possibly a bios issue.

Just interested to know if there are similar problems or any problems for that matter with the qx6700 and the commando boards?

I've got to install my swiftech so the commando may well be the board going back in my case.

Cheers

RLM

Quote:

---

Originally Posted by NLight95

What are your VRM temps as a result, and do you have a fan blowing on them?

---

I'll check them tommorow and no i dont have a fan blowing over them. Just the exhaust fan on my v2000 close to them.

Quote:

---

Originally Posted by MrDeeds

I'll check them tommorow and no i dont have a fan blowing over them. Just the exhaust fan on my v2000 close to them.

---

this is on phase right?
have you tried a higher vcore?

the reason is ask is, i hope i can finally build my rig (sig) this weekend and start testing the goodies (getting neophrene here is a pain in the *$$),
i was planning on feeding the chip 1.55'ish vcore (1.70v bios) and run somewhere between 4.0 and 4.5ghz 24/7. but im still not sure if i wanna use the jingting i have laying around or the standard heatpipe construction. i have done some theoretical testing with sinking the vrm area, but with that much vcore im still kinda worried it will overheat.

sorry for hogging you with all this, but i'm looking for a 24/7 game stable rig and thus dont really feel like building the rig with heatpipe testing stuff, then rebuilding everything with jinting/heatsinks and testing again with the chance i might have to change everything again if that dont work out well. so im looking for some user experiences with phase/commando/high vcore/naked or custom cooled vrm , and there dont seem to many of those around :rolleyes:

@NLight95
I checked the bios and pc probe and nowhere does it give me temps on the vrms, if anyone happens to know where i can see those temps i'd appreciate a clue. As far as mobo temps they are lower at idle and load in comparsion to the stock heat pipe.

@dinges
Sadly the vdroop on the board hasnt allowed me to realiably use voltages higher than where i am at the moment. I do intend on doing the pencil vdroop mod this weekend and hopefully that'll allow me to go further. Im my case i havent been able to find stability at 4.3ghz and higher. I can boot all the way to 4.6ghz for suicides and can sustain 4.5ghz for 32mb pi but not much more.

It could be my cpu but i really think its the fact that i havent really had the patience to find the settings to go further. I was stuck at 3.8ghz for months on my previous board so when i could hit 4.2ghz 24/7 orthos stable i pretty much just took it.

The heatpipe is a waste and you definately need something better for orthos testing over 4ghz. The one thing you do have to remember though is you'll need something for the sb once you pull the heatpipe. To each his own on the vrm area, I havent experienced anything adverse by running without sinks so i'm just going to continue that way.

On another note i wasnt able to get 525x8 stable while i have no issues doing 9x467. It isnt the ram or the cpu. I can run small ffts for hours but blend is a no go. It dies after about an hour. I think it may be because i dont really know what to do with cpu vtt. I dont think its nb voltage becaue i actually have worse results when i raise my nb volts. Also has anyone found it helpful to raise ddr2 termination volts.

My latest that's rock solid.

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 ?

Quote:

---

Originally Posted by MrDeeds

@dinges
Sadly the vdroop on the board hasnt allowed me to realiably use voltages higher than where i am at the moment. I do intend on doing the pencil vdroop mod this weekend and hopefully that'll allow me to go further. Im my case i havent been able to find stability at 4.3ghz and higher. I can boot all the way to 4.6ghz for suicides and can sustain 4.5ghz for 32mb pi but not much more.

It could be my cpu but i really think its the fact that i havent really had the patience to find the settings to go further. I was stuck at 3.8ghz for months on my previous board so when i could hit 4.2ghz 24/7 orthos stable i pretty much just took it.

The heatpipe is a waste and you definately need something better for orthos testing over 4ghz. The one thing you do have to remember though is you'll need something for the sb once you pull the heatpipe. To each his own on the vrm area, I havent experienced anything adverse by running without sinks so i'm just going to continue that way.

On another note i wasnt able to get 525x8 stable while i have no issues doing 9x467. It isnt the ram or the cpu. I can run small ffts for hours but blend is a no go. It dies after about an hour. I think it may be because i dont really know what to do with cpu vtt. I dont think its nb voltage becaue i actually have worse results when i raise my nb volts. Also has anyone found it helpful to raise ddr2 termination volts.

---

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).

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.

Quote:

---

Originally Posted by dinges

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

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.

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.......

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.:D

Quote:

---

Originally Posted by 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.:D

---

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?

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

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.

Quote:

---

Originally Posted by sreedx2

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.

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.:D


http://ziberia.1g.fi/kuvat/10.156.jpg/full

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!

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.

Quote:

---

Originally Posted by 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.

---

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!

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)

Quote:

---

Originally Posted by iviustang50h

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!

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.

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 ?

Quote:

---

Originally Posted by 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.

---

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! :mad:

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.

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.

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.
http://img.photobucket.com/albums/v6...maxvr4651M.jpg

Short orthos 1.35 vcore.
http://img.photobucket.com/albums/v6...0comOrthos.jpg

Quote:

---

Originally Posted by loc.o

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.
http://img.photobucket.com/albums/v6...maxvr4651M.jpg

Short orthos 1.35 vcore.
http://img.photobucket.com/albums/v6...0comOrthos.jpg

---

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

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

http://img.photobucket.com/albums/v6...rap465boot.jpg

Quote:

---

Originally Posted by 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.

---

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.

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?

Quote:

---

Originally Posted by Severance

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.

Quote:

---

Originally Posted by DoomSayer

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.:mad: