ASUS Maximus Formula SE

[TheSamurai]

oh, btw, still no luck with the RAID intsall... something is just not right. i can't understand why it's not working. i keep getting hangups with the dvd drive for some reason and just a load of other stupid issues.

[Maglin]

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!

Raising the FSB also increases the RAM speed. But you have a RAM divider that plays the biggest part in OCing ram. It's your FSB Strap and DRAM Frequency that make up your RAM divider. CPUz will show you your ram divider and so will MemSet along with the actual speed which doubled will be the DDR speed.

[Cumulonimbus]

Hi,

my first Post in this Forum :-)

FAN-Connector Formula Maximus for Speedfan 4.34b34:

FAN-NAME on BOARD - Controller/Channel in Speedfan

CHA-FAN1 + CHA-FAN2 ->> Winbond 83627DHG-Pwm1
CPU-FAN_ ->>>>>> Winbond 83627DHG-Pwm2 (only adjustable if ypu use a 4-Pin PWM-Fan)
CHA-FAN3 ->>>>>> AD7475-Pwm1
OPT-FAN1 ->>>>>> Winbond 83971D-Pwm1
OPT-FAN2 ->>>>>> Winbond 83971D-Pwm2
OPT-FAN3 ->>>>>> Winbond 83971D-Pwm3

You see, you can controll 6 Channels on Maximus Formula, but 1 Channel controlls two Connectors

Greets,
Cb

[icon57]

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.

thx maglin....
i actually did read this entire thread...lol....l0ng a$$ thread...
i seem to remember some one talking about prying off the fuzion block with a screwdriver, and using a pci slot for leverage...didnt want to do it that way...

and once i get the fuzion off the attached northbrige heat sink, i will use the as epoxy to rebond it, as well as as5 in the middle...as per raju recommendations...

[ssideratos]

Thanks to ZilverPhish, Jonny_ftm, Marjoram and all others for the replies and advice.

NOTE!!: I abbreviated the quotes so that this reply isn't too long.

@.....>

This board consistently undervolts the ram at reboot. I´ve too been through ALOT of powercycling it demands a dram volt adjustment to
boot properly...

Even changing the dram voltage and then rebooting via power cycle allows a POST with your new bios settings, so yes this board and its current bios versions has this flaw.

Had this issue with the commando as well, even with later ´bios versions.

My previous board was the P5W DH Deluxe. It was on the rare occasion of an aggressive overclock bios setting test that I might have to power cycle. Power cycling this board between BIOS settings is a real annoyance. However, most bios combinations that will POST, at least for me, will then require a power cycle after Windows Shutdown for cold boot. In those cases, the LCD poster never goes through the CPU INIT, DET RAM cycle -- The fans just spin up to max speed and the LCD poster just stays at time display. I can't live with the need to reach for the power switch every time I want to boot.

Looks like many fails OCCT RAM at stock too. But, it is a good idea, try keep your OC then wait and see. If it never fails, you're safe, if you have wired errors from time to time, than this damn board is broken or unstable, or maybe the whole X38 thing. Everywhere, it sounds that the X38 is very tricky on RAM settings and brands. Maybe this board is really unstable even at stock when you ask too much of it.....

So, if you really don't care, ignore OCCT in RAM, but just keep it in mind if by case you have wired errors (often induced by RAM)

Under Vista 32, it should be rock solid, or it's hardware issue/bios issue... For me, under bios 1223 (last final and previous 12xx except 1221, my system will reboot under OCCT in RAM mode)

I went X38 over P35 thinking as replacement for 975X and several months after P35, Intel would have worked real hard to make this chipset shine. Also X38 with PCIe2 support might buy me more time before MB upgrade fever set in the future.

Sounds like what was happening to me. OCCT kept failing just between 25 and 35 minutes (though I didn't have any POSTing issues...).

In my case though I only passed after downloading the Beta latest version from a link someone posted here.

I then realized by accident that I was using an older version of OCCT and that may have been the issue.

Sure enough when I run the Beta, I'm 4+ hours stable in OCCT. And when I run the other version, I fail.

So, if you haven't checked, what version are you running?

http://www.ocbase.com/download.php?fileext=beta

Majoram and jonny_ftm. Thanks for the link to the new OCCT 1.2 beta.

Like I said in last night's post, I'm really tired of the emotional roller coaster I've been on and the amount of time I've invested in nothing but testing this system/motherboard with no useful work getting done. So, as of last night I resigned to the fact that I would no longer bother with OCCT and went onto to a fresh Vista and apps install at 3Ghz, 4GB Ballistix at DDR2-800 4-4-4-10. Everything has been smooth as silk (of course the system hasn't been pushed at all.)

But Majoram, you're right, I was using 1.1.1. In researching my issues on this thread I noticed mentions to 1.2beta, but couldn't find it. I must have missed previous links if they are in here.

I promise I'll test out the new OCCT and report back soon. Forgive me however if I need some time to recover first from the stress of the last few weeks and just get on with my life and use my computer in a useful way for a couple of days before I have the energy to give OCCT another shot and risk getting caught up in another cycle of settings changes and testing.

Majoram, if you had the same problems with 1.1.1 and they went away with 1.2 then I'm hopeful they will for me too. If that's the case then much of the ill will I had for this motherboard would have been unfairly imposed.

All in all, I'm very happy with my experience outside of OCCT 1.1.1 with current settings. If OCCT 1.2 pans out, then I think that this board has the potential to be fantastic if the BIOS can be improved. The stress I've encountered is the price we pay for being early adopters.

[Maglin]

OCCT 1.2.0b has been vital for me in getting voltages under control and in so doing has brought the stability "DRAGON" that I've been so hard at chasing. I've pretty much found my lowest voltages with the exception of maybe some more vNB, but I already have it nice and low. Here is what I'm running right now. I'm going to run this OCCT for 12 hours and see how it does.

400x9 DDR 800 4-4-4-12

	BIOS 701
Extreme Tweaker	
Ai Overclock Tuner :	Manual
OC From CPU Level Up :	Auto
CPU Ratio Control :	Manual
-Ratio CMOS Setting :	9
FSB Frequency :	400
FSB Strap to North Bridge :	400
PCI-E Frequency:	100
	
DRAM Frequency:	800
DRAM Command Rate :	2T
DRAM Timing Control:	Manual
CAS# Latency :	4
RAS# to CAS# Delay :	4
RAS# Precharge :	4
RAS# ActivateTime :	4
RAS# to RAS# Delay :	12
Row Refresh Cycle Time :	Auto
Write Recovery Time :	Auto
Read to Precharge Time :	Auto
	
Read to Write Delay (S/D) :	Auto
Write to Read Delay (S) :	Auto
Write to Read Delay (D) :	Auto
Read to Read Delay (S) :	Auto
Read to Read Delay (D) :	Auto
Write to Write Delay (S) :	Auto
Write to Write Delay (D) :	Auto
DRAM Static Read Control:	Enabled
Ai Clock Twister :	Light
Transaction Booster :	Disabled
-Relax Level	0
	
CPU Voltage :	1.38750
CPU PLL Voltage :	1.54
North Bridge Voltage :	1.49
DRAM Voltage :	2.00
FSB Termination Voltage :	1.26
South Bridge Voltage :	1.050
Loadline Calibration :	Enabled
CPU GTL Reference :	0.63x
North Bridge GTL Reference :	0.67x
DDR2 Channel A REF Voltage :	Auto
DDR2 Channel B REF Voltage :	Auto
DDR2 Controller REF Voltage :	DDR2-REFF
SB 1.5V Voltage :	1.50
	
NB LED Selection :	NB Volt
SB LED Selection :	SB Volt
CPU LED Selection :	CPU Volt
Voltiminder LED :	Disabled
	
CPU Spread Spectrum :	Disabled
PCIE Spread Spectrum :	Disabled
	
Advanced CPU Configuration	
CPU Ratio Control :	Manual
- Ratio CMOS Setting :	9
C1E Suppport :	Disabled
CPU TM Function :	Disabled
Vanderpool Technology :	Disabled
Execute Disable Bit :	Disabled
Max CPUID Value Limit :	Disabled
	
	
USB Configuration	
USB Functions:	Enabled
Legacy USB Support :	Enabled

[TouGe]

thx maglin....
i actually did read this entire thread...lol....l0ng a$$ thread...
i seem to remember some one talking about prying off the fuzion block with a screwdriver, and using a pci slot for leverage...didnt want to do it that way...

and once i get the fuzion off the attached northbrige heat sink, i will use the as epoxy to rebond it, as well as as5 in the middle...as per raju recommendations...

That was me LOL. I didn't really pry it off persay but it just poped off. I put the screw driver under each corner and just turned it 90 degrees. It came off with little effort.

[TheSamurai]

just an update, it seems that i keep getting and error on one of the drives in the posting raid screen... i ended up using the ichr8/ichr9 for desk/work/server driver instead of the ichr7 one that most have said they're using... could this be a problem? oh, and to even start to come close to completing the install, i had to purchase one of those things... you know... the things we used about 20 years ago. yup, you guessed it, a floppydiskette drive! my usb one wouldn't work. ugh. next i'll be testing the harddrives through windows.

anybody know of any good HDD testing programs???

[jonny_ftm]

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)

The only thing is that on 1.47 FSBT you ran OCCT on Large setting, while in the second you ran on small. On small, it will stress the CPU, and quiet not the NB-RAM. The calculation data is so small it fits the CPU cache, so no need to go in RAM --> NB and RAM not tested much. Maybe that's why you got no cripple in second test.
The RAM mode is the mode that will stress the much RAM and NB. remember, that the main difference between modes is the data size. Small data remains in CPU cache, big data is transferred to RAM through the NB
Would be interesting for you to vheck also your NB temperature when you crash, also the VDIMM voltage noted to fall by others. The RAM on this boards has two PWM that can also get too hot --> ram voltage drop

Just some ideas to explore...
Also
Speedfan logs can be of a huge help too. Whatever kind of crash, even OS reboot, the log file is written to HD in real time and saved. So, on reboot or recovering of a blue screen, you open the previous log (as speedfan creates a new log file on each start) and you can see the values of your logged settings at the crash second. It helped me identifying a vcore delayed drop after 2h of stress testing: my PWM were getting hot and delivered a lower voltage to CPU

oh, btw, still no luck with the RAID intsall... something is just not right. i can't understand why it's not working. i keep getting hangups with the dvd drive for some reason and just a load of other stupid issues.

Silly question maybe, but, you're setting your RAID while overclocking? If yes, than try at stock. If not, ignore my comment

I'm going to run this OCCT for 12 hours and see how it does.
400x9 DDR 800 4-4-4-12

It's a very good idea to make a first full check and tests at that 3.6GHz point. So, if it is rock stable, unbreakable, you can go ahead basing your settings on the 3.6GHz reference point. But, hope you can get higher later. It'll be disappointing to see the Maximus topping at 3.6GHz as a rock solid setup, and to see that anything above that is not stable on all benching programs

just an update, it seems that i keep getting and error on one of the drives in the posting raid screen... i ended up using the ichr8/ichr9 for desk/work/server driver instead of the ichr7 one that most have said they're using... could this be a problem? oh, and to even start to come close to completing the install, i had to purchase one of those things... you know... the things we used about 20 years ago. yup, you guessed it, a floppydiskette drive! my usb one wouldn't work. ugh. next i'll be testing the harddrives through windows.

anybody know of any good HDD testing programs???

Windows check disk, and tick: check bad sectors. Long test, but tests read/write operations of all clusters

[TheSamurai]

thanks for the input jonny. it's at stock settings and i'm running the WD diag software. if this shows up fine i'll run the windows one of the "bad" disk.

am i choosing the wrong driver?

[TheSamurai]

already found bad sectors on the second drive... should i try to repair or just rma? man i have the sh*tiest luck!!!!!!!!!

[Maglin]

Repair it and see how much space you loose. Worst part of it is you loose that much space now all all drives in the array.

Did you do a full (LONG) format when you remade your partition? If you just use quick format bad sectors get missed. Now I always do a full format (which takes like an hour for just 500GB) and I always see a shrinkage in size from the removal of the bad sectors.

If I was in your shoes I would redo ther raid low level format each drive and then rebuild the array and do a long format. I don't think you will have much luck getting a RMA unless you loose over 10% of your drive space as it would probably be within manufacture's specs which are probably listed somewhere in very tiny print.

[TheSamurai]

it was fubah'ed... i RMA'ed. ordered a new one and added rush to it only to realize that it won't get out any sooner... man i'm an idiot sometimes. oh well. i'll let you guys know how it goes when i can finally set it up.

i bought it through the egg and had no problem with the rma. one of the many reasons i buy through them.

[Maglin]

Just a repost for those wondering what OCCT codes mean. You need to check your OCCT forlder for Threadx.txt and review all 2-4 in their.

Code 1 : thread stopped because another thread stopped
Code 2 : stop by user
Code 3 : memory error
Code 4 : calculation error

[jonny_ftm]

it was fubah'ed... i RMA'ed. ordered a new one and added rush to it only to realize that it won't get out any sooner... man i'm an idiot sometimes. oh well. i'll let you guys know how it goes when i can finally set it up.

i bought it through the egg and had no problem with the rma. one of the many reasons i buy through them.

I would have RMA ed the drive too. What ever the reason, a good drive shouldn't have bad sectors. If you have bad sectors, the drive got a serious issue and needs to be changed as a bigger failure could occur. New drives are that way. Few years ago, there was no security and the heads could litterally fall on the disks on a bad shutdown. Now, if it happens, means your disk got broken

[kimandsally]

just an update, it seems that i keep getting and error on one of the drives in the posting raid screen... i ended up using the ichr8/ichr9 for desk/work/server driver instead of the ichr7 one that most have said they're using... could this be a problem? oh, and to even start to come close to completing the install, i had to purchase one of those things... you know... the things we used about 20 years ago. yup, you guessed it, a floppydiskette drive! my usb one wouldn't work. ugh. next i'll be testing the harddrives through windows.

anybody know of any good HDD testing programs???

This is one I use http://www.hdtune.com/

It's good and best of all it's free.

[vegettoxp]

Hey Guys, I didn't wanted to start another thread on this MB, so here is my question. After reading the quick review on X48 at AnandTech, I wasn't really suprised that there isn't whole alot of BIG difference between X38 and X48. My plan right now is to buy the ASUS Maximus Formula SE Motherboard. Is it safe for me to buy this board. I know its already at the EOL, but as long as I get Bios/driver support from Asus and As long as Asus gives me some Tech suport for this board, I am willing to buy it. So can you guys comment on my question. Is it safe for me to get the ASUS Maximus Formula SE (X38). I really don't need X48 in my opinion. The Asus already supports 1600FSB. So guys please comment on my question. Thank you for your help!

Just for FYI, Which other X38 Motherboard would you guys recommend from Asus or from Others?

P.S. Fusion

[Sgt. Slaughter]

I just bought and received the ASUS Maximus Formula SE Motherboard. I received version 1.02. What is the difference between 1.02 and 1.03?

[crazyea]

i love my board. 100% problem free so far. I'd recommend it.

as for rev, i've heard of talk that the diff is SE vs non SE. other than that no other differences. could be wrong though.

[safan80]

For what do you need a PCIe-eSATA-Controller?
Just use another connector/ bracket.

I am using this thing:
http://www.newegg.com/Product/Produc...82E16812226003

nice catch... I wanted something that didn't depend on the onboard controller. it's not like I'm using any of the pci-e 1x slots anyways.

and for those looking for the occt beta that works on this board. the original link is on page 90.
http://www.ocbase.com/download.php?fileext=beta

[Cumulonimbus]

I just bought and received the ASUS Maximus Formula SE Motherboard. I received version 1.02. What is the difference between 1.02 and 1.03?

Rev. 1.02 = Special Edition with Watercooler on Northbridge
Rev. 1.03 = Normal Version without Watercooler on Northbridge

[Warboy]

Here are some more Anomalies detected Via OCCT Beta





I just noticed, I spelled Southbridge wrong

[Maglin]

Warboy. Don't use small data size (CPU) I was almost 1hr stable at extremely low voltages. Then when I went to blend test it BSODed. Ended up have to up the vCPU back to where it was before and up the CPUPLL a few notches to get it stable on RAM (Large data size). I wouldn't really suggest anyone test with small data size. Use Medium or Large. I also get some random drops in voltages. I actually think it might be running PC Probe along side Everest.

[ElEctric_EyE]

Maybe it's a software or interrupt issue, the SB temp spikes obviously aren't realworld measurements. Looking at the negative voltage spikes alone, I'd be worried, but looking at those temps tells me that something is interacting with the software somehow. I'd believe temps "could" rise that fast, but def not come down that fast!

[Sgt. Slaughter]

Thanks for the repsonse on the version number clarification. I have the Se water cooled version. Nice to know I have the latest version.