That does not sound right, try using core temp, tat, speedfan and everest
probe should be pretty accurate though :confused:
Printable View
That does not sound right, try using core temp, tat, speedfan and everest
probe should be pretty accurate though :confused:
This is my experience so far
I have been running Vista since I first got my C2D and Commando, speedfan,cpu-z and etc did not read two cores but when I open up device manager I see two cores. I noticed this right away but did not think anything of it until I found a thread on OCN about it but this guy was using windows xp at that point I searched and searched until I finally found something on an amd forum which happened in RC 1 which involved changing some files halmacpi.dll to be exact. NOW :woot: I have speedfan,task manager, cpu-z and etc all showing 2 cores, it got me wondering device manager showed two so the whole time was I just stressing one core :confused:, when orthos opens up it would just run one thread.
I was playing with some OC settings and decided to run some orthos blend, nope fail instantly so hmm went back to the bios changed some settings .. nope fail again but I knew when I ran small fft's she was stable before showing 2 cores, so tried that and no go failed instantly.
I just tried to bump the OC down a little but still having no luck so finally I have have her stable at 360x9 3.2ghz my team group running at 4-4-4-4 2.1v
orthos fft's and blend stable, one thing I noticed now when I am close to and above 1.5 my core temps skyrocket using orthos... before around 48C max now would jump up to 53C right away
Started playing some half life last night and it was lagging so bad .. what the heck is going on, so I upped the pci freq from 100 to 105 I noticed some people say lock some boards to 105 but before the changes were made I was running 100 fine ?
AFTER ALL BEING SAID I would have to say I am pretty sure before I changed the files it was just stressing one core :nono:
Calling all Commando and C2D owners or anyone this applies to
If you have not already read my post read it and respond back if programs like speefan, task manager, cpu-z, etc only show one core ????
here are two different examples of the problem :fact:
It's not a regular pci-e x1 it's specific to sound card only.
Thats an honest question to ask where the registration code is for his own software that came with the ASUS Commando. I was wondering the same thing because it didn't come with the CD package oddly enough, and neither did the 3DMARK 06 has its registration that also came with the commando.
So did asus just give us trial software just to make it look like they care? This isn't "heart touching" :fact: ... what a lame slogan. :stick:
What I am experiencing is the error message that will show when I tried to update to V110. It indicates that a previous edition of 3dmark06 is not detected... :slapass:
I am also using the advanced edition v1.02 given by asus..
Anyone met with the same problem??
That's really :banana: :banana: :banana: :banana: :banana: I can't even post my results and I am also getting problems with the free Kapersky software. I am gonna call up the distro here in Singapore.
Btw, would like to check with all commando users if I have only one pcie vga card and would like to slot in on the 4x(which is the secondary pcie lane), would it automatically run it 16x or do I have to change any thing in the bios?
Thanks.
yes you have to download the full 3dmark06. you cant update the commando version . heres the link:
http://service.futuremark.com/suppor...id=14&fid=1309
dumbest thing ive ever heard ;)
I have one question...
Suppose that I have a pcie sound card...
Can I use the second pcie (for vga) for it???:confused:
The Commando has the following:
1 - x1 pcie
2 - x16 pcie
4 - pci slots
unless your soundcard is x1 pcie or pci i don't think you can use your soundcard on the commando. the x1 pcie is supposed to be for the bundled supreme fx sound card but can accomodate any x1 pcie device. as usual the pci slot can accomodate legacy pci-e device.
4 the 2nd time the commando doesn't have an f@**ing a x1 pcie
Asus Commando
Please note:-
The socket looks like it's a x1 pci-e but it ain'tQuote:
Expansion Slots 2 x PCI-E x16 (@ x16 and x4 mode)
4 x PCI 2.2
no, it'll run x4 but a PCI-E x1 card should run in it fine
i have a problem with my commando..
today i update my bios 0803 to 0902. And before the update i test my system with 3dmark06. score is 6,8k. after the update i test my system again and score is 4,8k
i understand why my results are bad. pcie@1x How can i change this ?
http://img169.imageshack.us/img169/2543/cpuzcq0.jpg
my system
E6600@ 3.6ghz
Asus Commando
Crucial Ballistix PC6400
HIS ATI X1900XTX
Thank you for the answer ^^
And for the record, yes, you're right... The slot that looks like a PCI-e 1x is actually... the other way round :P:
If you try to plug a pci-e card on it, it will look inwards. I take that as a "stop being dumb" message from the MB.
Well, first impression with this motherboard is...
What A Bliss!
My previous MB (which I accidentally killed) was the Abit IN9 32X-MAX. It took me nearly two weeks to make it work @ stock settings, and I never managed to stabilize it completely. It was aggro after aggro.
This one booted straight out of the box into XP, and on a "contaminated" (haven't reinstalled yet) installation, with the memory undervolted (should be 2.2v and is running @1.96v) and underclocked (5-5-5-18 800 instead of 5-5-5-15 1066) is yielding the same 3D Mark and Sandra results as the Abit.
That motherboard must have been faulty. Too bad that with 3 VRegs out of 5 crushed I can't RMA it. I should have followed my instinct and RMA-it straight away after the first week of aggro.
Glad your happy, i think it's a good board, but have seen enough issues to know that generally Asus Quality control isn't good & their support even worse. So we're the lucky guys.:toast:Quote:
MrToad
What A Bliss!
I did a RMA on my commando since I grew tired of the whistling sound it made @ reboot I could hit 415 fsb on the qx6700. Lets hope the new one is a gem and not a dud.
this is my second commando install, first install that i recomended and helped to set up on friends system where the mobo was quit and could reach 470 fsb on 6600. Both had !"doubletake" reboot issues though