new commando thread that hopefully is not cursed but the old one

[No.72]

oh nice, I wish I had a e6600

[Clunk]

Nice one mate, I havent done any dual superpi runs on this....should be fun making that work

[Supershanks]

I was actually taken by suprise how quick my pi32m runs were, was browsing forums the other night & clocked the tables then thought hang on.... what were mine Another poser is born

I'm sure you guys will come up with something better

[Clunk]

Those runs are quick, I cant get anything near when running 2 of them at the same time.

16.32 on one core and 16.42 on the other was what it finished at, and that was with the cpu at 3680mhz and ram at 1150mhz with 5-5-5-18.

Cas4 isnt happening on this board at all, only a couple of stable runs so far, but it needs much more voltage than the P5B did for the same clocks.

And, I'm not sure if there is a large amount of duff commandos, but theres a hell of a lot of recent posts on xs with similar problems to me. Which is nice

[Supershanks]

I'm not sure if there's a bios issue, my superPi timings are all based on the 801bta & this last week on the 803 4,4,4,12 has been rock steady on everything i've thrown at it.

[Clunk]

I would just like to point out that this thread is cursed as well.

After another set of dead ram (commandoed to death), and another dead commando (went commando), enough is enough, 3 whistling, chirping, buzzing, ram killing, E4300 hating motherboards in a row just isnt funny.

So, the commando becomes my most troublesome board ever (close to the SLI-D), but it's not quite the worst, the DS3 still holds the crown for that.

What have I learned from all this? Well, Asus quality control is piss poor, so much so, that I certainly wont be buying another one for a while, but not out of malice or anything, I just really beleive that for the prices they charge for their products, they should be solid and reliable, and if they choose to tout them as "silent" or for "superior overclocking", then they should do exactly that, without any problems. No doubt that people will say that I've just been unlucky, but 3 in a row, is ridiculous, and it becomes very aparent that something is really wrong with Asus boards when you look around at other forums and see lots of similar complaints.

In its favour, It overclocks well, but no better than a P5B deluxe (at least not for me anyway), will do cas3 at high fsb, where normally cas4 would only be possible, excellent range of voltage adjustments, on board switches (if they work), highly tweakable bios.

I feel that the Commando has Power issues, build quality issues, it doesnt recover well from a bad overclock, Mine had problems with cas4, although in fairness, that was because it was in the process of murdering another set of ram. The heatpipe cooler is attrocious, it simply doesnt fit properly and it is next to useless., 2 of the 3 boards had wobbly ram sockets (cause of ram death?), the jmicron controller is terrible (no worse than others, just that it is another reason to avoid this board), the onboard cmos switch is hit and miss, sometimes it worked, sometimes it wouldnt.


Get your finger out of your Asus, Asus.

[Supershanks]

Well taking your point around asus qc i think your right out of 4 of us:-

No72 - 1 RMA
Me - 1 RMA
Clunk - 3 RMA
EtheAv8r - 0

Total 5 RMAs 4 Users ain't good.
Apologies to any1 not mentioned please post your experience if u have any

it doesnt recover well from a bad overcloc

It can be quircky, i'm not too familiar with Ami bios but the rebuild/update of DMI Data pool seems pretty crap, not sure if it's a general or mobo feature. I had my 4 x80gb drives out the other day numskull had forgotten to use hitachi tool to eneble sata2. Being in raid drives & cables are labelled so were put back exactly as they were. I booted up & it hung, only thing to do - clear cmos.

Have had no issues with jmicron but am only running a single dvd on it so wouldn't expect any issue. Otherwise apart jmicron & the whistling can't argue with your points.

May your next mobo be blessed whatever it is

[excalibur2]

erm Commando goes off my short list.

[No.72]

Clunk it must have issues with the combinations of other hardware you have. There is no way you are unlucky enoth to have 3 crap ones. imo

[Clunk]

Clunk it must have issues with the combinations of other hardware you have. There is no way you are unlucky enoth to have 3 crap ones. imo

Nope.

E4300/E6400
P5B/Commando
Enermax Galaxy x 3/Silverstone Zeus/Seasonic S12 380w
OCZ flex 9200 / Generic PC2-4300 ram
X1900xt/ Nvidia 6200
Built in the case and out of the case

Various combinations of the above hardware were used for testing.

Thing is, if it was one of the existing components, then they could cause problems in the P5B....transfer all the stuff to the P5B, no probs. It was definately the commando, have a look round, loads of people with the same problems

[No.72]

Nope.

E4300/E6400
P5B/Commando
Enermax Galaxy x 3/Silverstone Zeus/Seasonic S12 380w
OCZ flex 9200 / Generic PC2-4300 ram
X1900xt/ Nvidia 6200
Built in the case and out of the case

Various combinations of the above hardware were used for testing.

Thing is, if it was one of the existing components, then they could cause problems in the P5B....transfer all the stuff to the P5B, no probs. It was definately the commando, have a look round, loads of people with the same problems

mehzz your cursed

[Clunk]

mehzz your cursed

And the Commando is a Chirpy Burpy Cheap Sheep.

[No.72]

imo the commando is the commander of 965

[Clunk]

Reminds me of that Jay and Silent Bob film

[shaftyboyire]

Supershanks, Clunk and all, No.72

I have been reviewing this thread and many others online since i purchased my Commando. I have also raved about how great the Commando is and really promoted it . In or around the same time frame you guys all started reporting issues with the CPUINIT errors and system failures I started to get concerned . But needless to say my System kept going although I did stop over clocking it and kept it at stock levels.

Which brings me to last night. I get home from a coont of a day in work and want to play some CSS . I power on check some mails and all seems fine. I then kicked off a game, and bam the entire system powers off and all I could hear was a high pitched squeel in my headphones. Strange I said, as the system didn't actually reboot it just lost its display - all the lights were on but no one was home.

Being the hardware wizard that I am I immediately started trouble shooting the issue. Of course it was the dreaded CPUINIT error on the LCD poster. Ooooh no I cried as flash backs of this thread and others rushed passed my eyes .

Long trouble shooting story short my Commando is now dead. All of my components work fine in another system and the only thing left is the mobo. Believe me I've made every attempt to get rid of the CPUINIT error, clearing the cmos no joy, jumper settings no joy, removing battery for 10 mins no joy, removing battery and leaving over night still no joy. So it now seems we have a 100% failure rate of all Commandos. My mobo is now being RMA'd which leads me to my next question!

Q: Those who have RMA'd their Commando, what was the replacement one like?

I've read some repeat RMA's and complete disasters. Should I get a different board or hold true to the Commando. Initially I fell in love with the board but if its like an ex girlfriend that just won't work out I need to know now before I get back with her

Any advice is welcome

Shafty

[Clunk]

The commando should have an extra button next to the cmos/reset/power that plays a short but annoying segment of "Another one bites the dust".

It depends how patient and tolerant you are mate. after the third, I decided that enough was enough. Since then, Ive seen lots of people with the same/similar issues, but the most alarming for me is the fact that the commando seems to like to kill expensive ram.