ASUS Maximus Formula SE

[intothefantasy]

my max fsb is 475...how abt u guys? anyone over 500? or 500? for q6600 i mean

[TheSamurai]

it's not that hard
http://www.neoseeker.com/Articles/Ha...ation1/11.html

if that doesn't help try this
http://www.google.com/search?q=nlite...en-US:official

i figured it out on my own last night... but for some reason when it reboots for the second part of the install it says that files are missing every time...

also getting an error on one of the drives when it shows the raid boot screen. not sure what's up with that but it's kind of irretating.

[TheSamurai]

Hi, thanks, do you know if there actually is another rev number, or are they still 1.02g?
Cheers...
Chris

yeah, there is... it's the non-se. some monkey thought it would be funny to p*ss off all the SE owners by posting a pic like it actually was the SE. afaik, there isn't another one for the maximus.

[TheSamurai]

Can you give us your bios settings to achieve this OCCT stable OC?

just play around with your board till it ends up around those in windows... everyboard is different so this might not even work with somebody else who has the exact same parts. if there are specific settings you'd like to know, let me know...

[TheSamurai]

Thank you everyone who helped me to get RAID working, I've finally found out what the problem is, the wife played a big part in it.

I don't have a floppy drive in my PC but have a new one in a draw just for things like this, I didn't realise that I actually had 2 in the draw one which was broken (brand new) and another brand new one, I was about to try the other new drive when she said I'm sure that was from Web-systems a local crappy PC store, every single thing I have ever bought from them has either been DOA or died very soon after.

So I took the floppy out of the wifes desktop and it worked straight away no glitches just the way it should have been.

I can't believe how much crap it has given me, if only I had remembered that I bought the floppy from them it would have been the first thing I tried.

Anyway A real big THANK YOU to everyone it is awesome the amount of people on this forum who have taken time to help me, clump has even PM'd me to help, I feel part of a very nice team.

this is a great forum, huh? i love it here, one of the best i've been to. congrats on the raid install... i'm having similiar glitches myself. so i'm going to go get some floppy's in a few minutes and try it with the regular install disk instead of nlite. i'm also a little worried that i have a error'ed raptor, but that's yet to be determined for sure.

[TheSamurai]

my max fsb is 475...how abt u guys? anyone over 500? or 500? for q6600 i mean

i don't think anybody with the q6600 has gone over 500... but i can't remember for sure.

[ShawnTRD]

Was the temp constantly at that level or did it just jump up for only a second or two?

They stayed constant at these temps.

[kimandsally]

this is a great forum, huh? i love it here, one of the best i've been to. congrats on the raid install... i'm having similiar glitches myself. so i'm going to go get some floppy's in a few minutes and try it with the regular install disk instead of nlite. i'm also a little worried that i have a error'ed raptor, but that's yet to be determined for sure.

I hope yours is just a floppy issue, I suppose there's not much else it can be, but as you said yourself you thought it was a floppy issue, crazy really because most people use floppy for BIOS updates I personally hate floppy's as in the past things like this has happened but it was so long ago I tend to forget.

Keep us posted and good luck.

[Maglin]

I never use floppy's cause of that very reason. The disks just go bad with age and the drive fail fairly often at the wrong times. XP is very old now going on what 7 years old I think. I've never installed MCE but I would hope it would allow you to use USB for raid drivers.

@ 1.6v on NB I get 50* ish idle temps. I'm @ 1.47v (1.52v on PC Probe) NB and my NB is at 47* idle and it gets to about 56* after 30 minutes of full load. I think my NB isn't making good contact with the heatsink. Got a few tubes of MX2 coming so when it gets here I'll be reseating the NB and SB sinks and see how my temps are after that.

Every time I fail OCCT it's when vNB gets a small voltage spike. I'm going to pull out my DMM here next week and check my Power from the PSU to see if it's fluxing or if it's the boards voltage regulators. I would still like to know what I can mod to up the output of the boards 3.3v and 5v regulators. If it's the PSU I'll definitely be doing something to fix it but I highly doubt it's the PSU as everyone is showing the same voltages. I've got almost all my setting green now and stable @ 400x9. I'll post up what I've got here very soon for settings.

[KRich]

Depending on your definition of stability, I ran the new OCCT beta referred to here and ran it in RAM mode (slider all the way to the right) and it lasted just under 11 hours before errorring out with a Code 4.

This was with my E6600, 465 FSB (x8 multiplier) and using 1.55V for the CPU. All other voltages were set one notch above green.

[Maglin]

It's going to take a few more days to find the lowest voltage's I can run at 400x9. It is actually getting more stable as I bring voltages down and of course the decrease in case temps. I've been doing this all with the door on and the case where it will always sit. (which is a far from optimal placement for exhaust ventalation)

I'm thinking that once I find my lowest voltages for this clock it will be actually easier to go higher as I would be prone to bad OC's from having to much voltage on certain parts. Gone are the days of just vCore/vDIMM/vNB for OCing. I miss those days as it was a lot faster to get to lowest attainable voltages.

[T2k]

Hey gangsters,

does anyone know if I can use my Swiftech Storm v2 WITHOUT the Intel clip? I can't seem to find it and I am ready to finally put the WC back...

If I can't where the hell can I buy this $0.02 worth of thing?

THX!

PS: currently running 3.6GHz (8x448) on air but it's not fully stable - I have to put water on the chipset as well as on CPU to reach stability and move up to 4GHz... BTW 701 seems to be working fine here.

[culex44]

just play around with your board till it ends up around those in windows... everyboard is different so this might not even work with somebody else who has the exact same parts. if there are specific settings you'd like to know, let me know...

Until now, I've just modify vcore and vdimm and let everything else in auto mode. I'm stable OCCT for 30 min test at 3.8Ghz with 1.48v bios (0505) but no way at 3.9Ghz although I increased vcore until 1.575v (OCCT induced a reboot after 15 min of test with this setting).
I think I'll try to manage with vFSB, vNB and GTL settings

[T2k]

Until now, I've just modify vcore and vdimm and let everything else in auto mode. I'm stable OCCT for 30 min test at 3.8Ghz with 1.48v bios (0505) but no way at 3.9Ghz although I increased vcore until 1.575v (OCCT induced a reboot after 15 min of test with this setting).
I think I'll try to manage with vFSB, vNB and GTL settings

First just raise voltage for NB, that should do the trick I think.

[jonny_ftm]

Every time I fail OCCT it's when vNB gets a small voltage spike. I'm going to pull out my DMM here next week and check my Power from the PSU to see if it's fluxing or if it's the boards voltage regulators. I would still like to know what I can mod to up the output of the boards 3.3v and 5v regulators. If it's the PSU I'll definitely be doing something to fix it but I highly doubt it's the PSU as everyone is showing the same voltages. I've got almost all my setting green now and stable @ 400x9. I'll post up what I've got here very soon for settings.

Yeh, I doubt it is your PSU. Those spikes are either related to the NB heat (as you're on the rather very hot side) or the PWM heating too on the motherboard

Depending on your definition of stability, I ran the new OCCT beta referred to here and ran it in RAM mode (slider all the way to the right) and it lasted just under 11 hours before errorring out with a Code 4.

This was with my E6600, 465 FSB (x8 multiplier) and using 1.55V for the CPU. All other voltages were set one notch above green.

Code 4 is for CPU errors. But it could be yet an error in RAM sometimes. Maybe a small vcore increase could help you... Give Prime95 small FFT or OCCT CPU mode a try as they are heavier on CPU. If unstable, than a notch on the vcore and you're rock solid. If not, than maybe same issue as others on the NB-RAM subsystem of this board

[nvous23]

Noob OC'er here, Well not actually noob, been OC'ing since 486 Days, but I haven't OC'd in a long time. Last OC was a 2.4c. Anyway, I need some assistance anytime I try to start bumping settings in manual mode, It hangs on reboot (The LCD Poster sits at DET DRAM). So this is what I was able to do. I set the Auto OC to Crazy, and I can post just fine and get back into bios, then I bumped the Memory clock to 1167. If you guys could take a look at my screenshot and let me know where I should go from here, because I know it is probably severely overvolted from the crazy setting. Thanks very much in advance.

http://www.teamzfz.com/kev/3.5Ghz.jpg

[Maglin]

When it hangs on DETRAM their is something not right with you RAM settings. It can either be to high/low vNB, to high/low vDIMM, and to tight of ram timings and or to high a RAM speed. I like to test my ram with no OC and see how far it can go and do all the timings tweaking w/o OC so I have a good RAM base line that I can use. Then ensure you don't go over that when in search of your highest OC. I get DETRAM hang ups all the time when I'm tweaking ram. It's almost always to high a setting or tight of timings.

I've just stumbled on something with my vNB voltage ripples. I'm currently working on getting my lowest FSBT and I've dropped it a lot and my vNB ripples are still their way less ripple. I'm really loving the logging of the 1.2.0b OCCT. It's been the biggest help in finding my issues with instability. Here are my vNB at 1.47 FSBT and and 1.27 FSBT.

1.47 FSBT (BIOS)


1.27 FSBT (BIOS)

[icon57]

how are you guys getting the fuzion waterblock off? i have not fired up the mobo yet, but i want to remove the north and south bridge and replace the tim with some as5.
i also want to remove the fuzion block and reapply with as5 in the middle, and as thermal epoxy...
i just dont wanna break anything...hints please...

[StanD]

MY EYES!

My god what a long, yet informative thread. Thanks to everyone who has posted their experiences and settings.

My E6850 will be here in the next few days and I will begin my new build. After reading all the posts here I don't think I have seen one single person post their BIOS Template for the E6850.

I know Raja did an incredible review @ Anandtech but couldn't BIOS settings there either!

So I figured I would finally de-lurk and post asking for those of you with stable E6850 settings on your Maximus if you could possibly share your settings?

Thanks in advance!


- Stan

[Maglin]

The NB/SB is held on with screws and pins so I don't really think that AS Epoxy is necessary. I know this thread is grown pretty large but for the new comers it is a really good idea to read the whole thread. Their is some really go info scattered throughout this whole thread.

If you just read a few posts up using a hair dryer for 20-30 seconds to heat up the NB and then twisting and pulling to remove the HS. If it isn't moving then apply some more heat. It will come loose. Once off apply heat to sink and then use a razor blade to cut off the epoxy/glue/thermal compound that Asus uses.

Also make sure you SB sink is actually touching the SB as someone noted his was not.

[nvous23]

When it hangs on DETRAM their is something not right with you RAM settings. It can either be to high/low vNB, to high/low vDIMM, and to tight of ram timings and or to high a RAM speed. I like to test my ram with no OC and see how far it can go and do all the timings tweaking w/o OC so I have a good RAM base line that I can use. Then ensure you don't go over that when in search of your highest OC. I get DETRAM hang ups all the time when I'm tweaking ram. It's almost always to high a setting or tight of timings.

The funny thing was that I had them all set to Auto, I wasn't even OC'ing the ram at that point. I was just trying to OC the proc. So Start trying to bump the Ram with the default CPU clock? When i goto NBStrap 400 that's 1:1 Ratio correct? So in order to increase the Ram i'll have to start dropping the multiplier so i dont OC the CPU at all correct?

[Maglin]

NBStrap set to 400 and DRAM Frequency set to the middle setting. at 400 FSB it will be 800. So it will be 2x your FSB. That will be 1:1. You are just overclocking the RAM to high leaving it on auto. I really don't like anything set to auto.

Edit: Also avoid the urge to change a lot of settings when finding your OC. That will give you more headaches than you want. Just take the time and adjust one thing at a time. Of course ram timings usually have serveral settings changed when you are adjusting things. Everyone has their own method to finding their OC. I used to use Prime95 for 10 minutes. Now I use OCCT for 10 minutes and then tweak the same setting again (usually going down in voltage) going down in 2 incraments until i either error or it won't post. If I get hang up/no post then I turn puter off and then restart as sometimes the settings don't go into effect properly and a full power down (cold boot) is required and it works just fine. Once I get an error I go up one and run a 20 min test then move onto tweaking another setting. It's time consuming but has helped me with stability greatly on this board.

[KRich]

Yeh, I doubt it is your PSU. Those spikes are either related to the NB heat (as you're on the rather very hot side) or the PWM heating too on the motherboard



Code 4 is for CPU errors. But it could be yet an error in RAM sometimes. Maybe a small vcore increase could help you... Give Prime95 small FFT or OCCT CPU mode a try as they are heavier on CPU. If unstable, than a notch on the vcore and you're rock solid. If not, than maybe same issue as others on the NB-RAM subsystem of this board

That is what I am going to do I've had the board for a week now, so still plenty of testing and tweaking to do.

[thelawns]

When it hangs on DETRAM their is something not right with you RAM settings. It can either be to high/low vNB, to high/low vDIMM, and to tight of ram timings and or to high a RAM speed. I like to test my ram with no OC and see how far it can go and do all the timings tweaking w/o OC so I have a good RAM base line that I can use. Then ensure you don't go over that when in search of your highest OC. I get DETRAM hang ups all the time when I'm tweaking ram. It's almost always to high a setting or tight of timings.

I've just stumbled on something with my vNB voltage ripples. I'm currently working on getting my lowest FSBT and I've dropped it a lot and my vNB ripples are still their way less ripple. I'm really loving the logging of the 1.2.0b OCCT. It's been the biggest help in finding my issues with instability. Here are my vNB at 1.47 FSBT and and 1.27 FSBT.

1.47 FSBT (BIOS)


1.27 FSBT (BIOS)

So sorry for the complete noob question, but how would I go about just overclocking my RAM. I'll probably figure it out when I get home but I thought it was just by raising the FSB!

[TheSamurai]

Until now, I've just modify vcore and vdimm and let everything else in auto mode. I'm stable OCCT for 30 min test at 3.8Ghz with 1.48v bios (0505) but no way at 3.9Ghz although I increased vcore until 1.575v (OCCT induced a reboot after 15 min of test with this setting).
I think I'll try to manage with vFSB, vNB and GTL settings

try raising the NB, FSBT, and maybe the CPU PLL.