QuadGT Arrived (56k warning)

[bingo13]

I have followed your instructions (dos flash to original , then flashed with flashmenu with all options enabled as well as disabled to b06) , but I still cannot manipulate the multi through the bios . The strange thing is that i cannot change the multi even with the original bios.
The jmicron still does not show up during boot, and my hd led is always lit.

I do not know what to say at this time. I replicated your issue but solved it on both boards, just tried the same process again and it worked. Any other BIOS settings you might have changed?

[Revv23]

pic two

you mch and DDR volts are pretty insane for those speeds.

[fhpchris]

My little results so far...





Yes, the 32m time is slow... I clearly only did it to show stability.

[momomo6789]

is that that real volt b/c my mobo Vdroops like .5v also can you hear your mobo b/c mine @ 3.9 1.7v 1.65 in uguru makes A Noise Really loud also every few secs the voltage drops for 1.65 - 1.51 maybe a bug but every few secs prime fails @ the same time =/ also how is your pwm average current so high mine is like 5A .... maybe 16 max

[momomo6789]

wow i think i like this mobo with my brand new cpu i had to lap

[Ace-a-Rue]

you mch and DDR volts are pretty insane for those speeds.

BURN BABY, BURN!...LOL

kidding aside, this is a Q6600...it needs a little more help when you have four cores wanting a piece of the action...smile

[Ace-a-Rue]

Try upping VTT and ICHIO, lowering your DDR2 and VCore.

i'll give it a try but i have tried a LOT of combinations already....i do have another pair of memory that is in use on this rig...i'll swap out to see if that makes any difference....i have dominators in now, ddr1142 kind.

[hadji_a]

I do not know what to say at this time. I replicated your issue but solved it on both boards, just tried the same process again and it worked. Any other BIOS settings you might have changed?

This is what i have done:
1.dos flash to original using /py /sn /cd /cp /cc
2.enter bios set all options in cpu menu to disable, set jmicron to raid.
3.a.boot to windows , flash to b06 using flashmenu with all options selected
b.boot to windows , flash to b06 all options not selected
c.use awdflash , flash to b06 without any parameters.
4.enter bios set multi to 8x , check all options in cpu menu were disabled (they were), set jmicron to ide.
5.boot to windows, check multi using cpuz, and in all cases showed that it was 9x.
I repeated steps 1-5 3 times, each time changing step 3.
I also checked with the original bios (set multi to 8x) , and it still showed up as 9x in windows.
The jmicron controller never reappeared, and my hd led always stayed lit.
I guess i will have to wait for a new beta or final bios.
Bingo13 thank you very much for your time and effort

[Ace-a-Rue]

Try upping VTT and ICHIO, lowering your DDR2 and VCore.

Orthos won't even go 30 seconds with lower vcore and vmem (couple of notches lower) than what is posted on the previous page...but...sandra will accomplish the burn-in at the lower vcore and vmem when i run the arithmetic or multi-media tests or both...sandra uses all four cores while orthos only uses the 1st two cores...i have the latest orhtos beta but i haven't figured out how to make orthos stress all four cores at the same time.

also...the board will boot into windows at 340 FSB using default vcore and vmem of 1.8..it will run sandra burn-in (just did 10 times) but orthos blend stops after 2 plus minutes...so...the voltage is needed for the last 60-70 Mhz increase in the FSB.

i've tried lowering the multi to 8x at 400 FSB...i am able to squeeze 10 more Mhz out for the FSB...anything above that starts developing a no post issue when i want to restart the puter...it just sits there in a black hole until i shut it down and then start up again...i think i have reached the maximum for my Q6600...all in all, i am VERY pleased with the boards performance in addition to the performance of the Q6600!

[bingo13]

Orthos won't even go 30 seconds with lower vcore and vmem (couple of notches lower) than what is posted on the previous page...but...sandra will accomplish the burn-in at the lower vcore and vmem when i run the arithmetic or multi-media tests or both...sandra uses all four cores while orthos only uses the 1st two cores...i have the latest orhtos beta but i haven't figured out how to make orthos stress all four cores at the same time.

also...the board will boot into windows at 340 FSB using default vcore and vmem of 1.8..it will run sandra burn-in (just did 10 times) but orthos blend stops after 2 plus minutes...so...the voltage is needed for the last 60-70 Mhz increase in the FSB.

i've tried lowering the multi to 8x at 400 FSB...i am able to squeeze 10 more Mhz out for the FSB...anything above that starts developing a no post issue when i want to restart the puter...it just sits there in a black hole until i shut it down and then start up again...i think i have reached the maximum for my Q6600...all in all, i am VERY pleased with the boards performance in addition to the performance of the Q6600!

Try this for Quad Core Testing- ftp://mersenne.org/gimps/p95v251.zip
My system did 10 hours and 51 minutes at the 8x450 setting before CPU 3 gave up the fight.

Every CPU and board is just a little different. I have found that less is more on the Quad cores but you are getting excellent results from the Q6600. My Q6600 actually clocks better than the QX6700 but it is an ES sample so I will not be showing those results. I would run your Dominator modules around 2.350V with 2% DDR2 ref voltage, you should be able to do 4-4-3-10 at 1000 easily.

[bingo13]

This is what i have done:
1.dos flash to original using /py /sn /cd /cp /cc
2.enter bios set all options in cpu menu to disable, set jmicron to raid.
3.a.boot to windows , flash to b06 using flashmenu with all options selected
b.boot to windows , flash to b06 all options not selected
c.use awdflash , flash to b06 without any parameters.
4.enter bios set multi to 8x , check all options in cpu menu were disabled (they were), set jmicron to ide.
5.boot to windows, check multi using cpuz, and in all cases showed that it was 9x.
I repeated steps 1-5 3 times, each time changing step 3.
I also checked with the original bios (set multi to 8x) , and it still showed up as 9x in windows.
The jmicron controller never reappeared, and my hd led always stayed lit.
I guess i will have to wait for a new beta or final bios.
Bingo13 thank you very much for your time and effort

Honestly, I would RMA the board, as the JMicron controller issue (not appearing at all when enabled) is not a BIOS issue and the reflash procedure should have solved the multiplier issue. In the meantime, you can try this fix for the multiplier issue - http://forum.abit-usa.com/showpost.p...6&postcount=26

p.s. You did disable Thermal Control, C1E, and EIST in the BIOS, correct?

[Ace-a-Rue]

all-righty-then!

[bingo13]

bios didnt fix the problems.

Try this - http://forum.abit-usa.com/showpost.p...6&postcount=26 -last ditch fix I guess for the time being.

[fhpchris]

Yes, the board droops alot, 1.57v idle drops to 1.55v during 1m and drops to 1.53v during orthos.

Clearly running orthis high on this board is hard

The bios didnt fix the RAID problems, but I will try again.

[Ace-a-Rue]

Try this for Quad Core Testing- ftp://mersenne.org/gimps/p95v251.zip
My system did 10 hours and 51 minutes at the 8x450 setting before CPU 3 gave up the fight.

Every CPU and board is just a little different. I have found that less is more on the Quad cores but you are getting excellent results from the Q6600. My Q6600 actually clocks better than the QX6700 but it is an ES sample so I will not be showing those results. I would run your Dominator modules around 2.350V with 2% DDR2 ref voltage, you should be able to do 4-4-3-10 at 1000 easily.

discovered one of my dominator ddr1142 sticks will fault around 1020 mhz...will just try the one stick with less voltage on the core and vmem...i still think the Q6600 is the controlling factor in my equation

[bingo13]

Yes, the board droops alot, 1.57v idle drops to 1.55v during 1m and drops to 1.53v during orthos.

Clearly running orthis high on this board is hard

The bios didnt fix the RAID problems, but I will try again.

No issues here at all with RAID except you cannot use a SATA Optical drive on the ICH8R with RAID enabled, all other issues we had have been fixed. I have run every RAID combination with 3 WD74GB Raptors to 5 Seagate 7200.10 320GB drives on this board without a hiccup.

[momomo6789]

bam i love this mobo cept high clocking ram is not to be found yet =/

[momomo6789]

also are there any programs that record correct temps today i seen my temps drop to 0c witch just never happened =/ not even close

[fhpchris]

posted in the xeon thread too, but it applies here...



1.34v prime @ 3600

[Ace-a-Rue]

bingo:

do you have any re-start problems from windows when you overclocking over 380 fsb?...i get a no-post screen on restart when overclocking above 380 fsb....if i command shutdown and then power up, everything is ok.

[momomo6789]

i get like it cold boots then reboots its self and starts up

[bingo13]

bingo:

do you have any re-start problems from windows when you overclocking over 380 fsb?...i get a no-post screen on restart when overclocking above 380 fsb....if i command shutdown and then power up, everything is ok.

No issues here from a restart and overclocking. I sweet talk my equipment so maybe it just likes the extra TLC and treats me well.

[fhpchris]

Look Bingo, I dont know what board you are using, but the raid issues are NOT fixed with the beta bioses, no matter how many times I flash in DOS or Flashmenu, or how many times I do anything else.

Please try posting a bios that does not take 5+ minutes to just detect my drives.

[Revv23]

My little results so far...


Yes, the 32m time is slow... I clearly only did it to show stability.

I have the same issue with the 32m... i get way faster benchmarks then my P5B in and benchmark you name it but then in 32m i cant beat my old score??

And i also agree we need to find some way to vdroop this mobo, its not like asus bad but it isnt to good either, i havent been able to check DMM yet but i can tell by the way it scales with voltage on this cpu.

Can you tell me what you used as your vcore read point? i have a guess, but i dont just want to guess per risk of shorting the board... digital VRM confuses me.

[fhpchris]

I have the same issue with the 32m... i get way faster benchmarks then my P5B in and benchmark you name it but then in 32m i cant beat my old score??

And i also agree we need to find some way to vdroop this mobo, its not like asus bad but it isnt to good either, i havent been able to check DMM yet but i can tell by the way it scales with voltage on this cpu.

Can you tell me what you used as your vcore read point? i have a guess, but i dont just want to guess per risk of shorting the board... digital VRM confuses me.

the small resistors above the cpu, on the cpu side I dont think you will be able to short anything