Real quick... anyone able to get into Windows on Maximus with quad at 488x8 or any setting in the realm of 3.75-4ghz... if so what settings are you using, or could someone try. I simply cant with 0505, could on 0401.
Printable View
Real quick... anyone able to get into Windows on Maximus with quad at 488x8 or any setting in the realm of 3.75-4ghz... if so what settings are you using, or could someone try. I simply cant with 0505, could on 0401.
anyone else get cold boots, even with a stable OC???? also sometimes i get a hang after it detects my usb devices.
Dude, are you really passing this known core temp bug as an overclock? No one shows a core temp shot as a legit overclock. That is what CPU-Z is for. I'm pissed, because you're insulting my intelligence. That shot you posted can be reproduced in many instances of high overclocks; and I bet you were using a higher multiplier.
@ChaosMinionX
I got it too...
0505 is good couse loadline working, but in other hand it really sux!!
Cant OC at all...
Max fsb is about 510 !!! when on 0401 it was 550 easily.
0505 was cool with 500x6 or 7 with stock Vcore, but with x8 it wont boot...or even 520x7... didnt check lower fsb than 500 cose i wasent buying mobo for over 300$ to run it lover than fsb500.
Maybe they will combine the two bios files and then hey we are all happy , i am sure Asus must scan some of the threads around the world :scope:
Does this Maximus have any real advantage with its X38 over the Blitz P35 board if your not going for SLI? I read some reviews that said that Intels P35 chipset is good enough for it not being worth upgrading to a X38, but does anyone here who's used both have any opinion on this matter?
we'll I just spend the better part of the night reading the ENTIRE 27 pages, lol. Looks like a winner to me, I'm going to be building a new rig in January. The only other chipset I've heard about that is yet to come out between then and now is nvidia 780i, which I heard is just a modified 680i. Can anyone confirm that?
With my P5E so far:
http://img115.imageshack.us/img115/8...0fsbkf7.th.png
My RAM wont boot pass 1200Mhz, it´s not the board. I will try later another mem divider for max FSB.
Every time i install the drivers that comes with the cd, after a frech install. and i try to type something with my keyboard. it will just freeze. like if i go to start and try to type in search it will freeze the start windows. also if i open notepad and try to write it will freeze... what can i do to fix this. tried a new install and as soon i put the maximus drivers it will happen. also tried to change the usb port.. same thing.. what should/can i do?
no :banana::banana::banana::banana: supermiguel!!!! that happened to me with xp64!!!!!!!!!!!!!!!!!!!!!!!!!!! couldn't figure out for the life of me what it was. it only happened in IE, firefoc, steam... seems to be things that are connected to the net. odd!!! i ended up installing xp32 and no problems now.
i flashed back to 0401 hoping to get a higher stable clock the 3.825... well, no luck. back to 0505 i go.
i also think that 0401 can oc better it supported a higher fsb
Officially to my knowing there isn't any SLI support, if you want or need SLI Nvidiot chipset is the only path to walk ( though it's a treacherous one), there are minor differences between X38 and P35 (surely for Crossfire users) , but nothing for me talk about, though I think it will unleash it's fury with the new upcoming CPU's and GFX cards...
I hope to have my Maximus Formula tomorrow and will do some comparisons...
E6700 L631A
Crucial 8500 Tracer
Lunasio LiquidCooling
Hiper 670
http://www.pctunerup.com/up/results/..._screen006.jpg
http://www.pctunerup.com/up/results/..._screen013.jpg
How is vdroop on these boards ?
Especially with quad core > 3,6 Ghz.
don't test with Q but with last bios 0505 it's 0.01 :D think same with Q
Yes, droop is almost non-existant on B3 Q6600 @ 3.6ghz, 450x8, w/0505. My idle is 1.456, load is 1.454.
Well, I am investigating this further...it seems not to be voltage related, but TEMP related. It will "trigger" when my cpu hits 69c(1.424v, q6600/B3).:rofl: More investigation needed..I feel it might be EPU driver causing this trying to control temps.:rolleyes: However, when I use BIOS 0401 or whatever, I'd have to set a voltage higher than 1.5v to get this votlage, due to droop, so it might be partially related to voltage...but seems more likely to be TEMP or current draw that triggers this problem.
What exactly is EPU and how does it work?
Your guess is as good as mine. The box says:
"The ASUS EPU utilizes digitally monitor and tune the CPU power supply with improved VR responses in heavy or light loadings."
The chip on the mobo labelled EPU is the controller that we usually work off of for VDROOP and VCPU mods, and this board has a driver that installs for this "EPU" chip from the driver DVD. Based on what it is and what it is supposed to do, the driver may shown up as "SYSTEM" in taskmanager if it is actively working as described above.
The issue that GAR and I have is also not temps, or voltages...it seems either current- or FSB/cpu speed-related only. I'm working at eliminating speed as a factor..running 3400mhz @ 400FSB or 425 FSB does not "trigger" the problem, but 400X9 or 450x8 does, although, of course, voltage is higher for the 3.6ghz to be prime stable than it is for 3400mhz.
Setting 1.424v(reported by PC Probe) @ 3.6ghz and the behavior does not start immediately, but once temps hit 69c it starts. Unfortunately my cpu is not stable @ this voltage, so I was unable to see whether it's an intermittent thing, but this also makes me think it's current-induced, as obviously it's not the speed directly that causes the issue.
ON some other boards when the droop is real high due to the current load, the multi "bounces", which I myself blame on TM1 or TM2, and it's possible that this less than 100% prime load is a feature to overcome THAT behavior..i dunno..I'll have to extract another quad from yet another box to confirm that, as I have another quad that would do this "bounce" with more than 1.3v, or faster than 3.1ghz(again the bounce points to being current-induced by my testing).