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 :banana::banana::banana::banana: load of other stupid issues.
Printable View
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 :banana::banana::banana::banana: load of other stupid issues.
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.
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
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...
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.
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.
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.
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.
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
Code: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
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???
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
Silly question maybe, but, you're setting your RAID while overclocking? If yes, than try at stock. If not, ignore my comment
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
Windows check disk, and tick: check bad sectors. Long test, but tests read/write operations of all clusters
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?
already found bad sectors on the second drive... should i try to repair or just rma? man i have the sh*tiest luck!!!!!!!!!
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.
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.
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
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
This is one I use http://www.hdtune.com/
It's good and best of all it's free.:up:
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
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?
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.
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
Here are some more Anomalies detected Via OCCT Beta
http://i31.photobucket.com/albums/c3...00-Chipset.png
http://i31.photobucket.com/albums/c3...h00-Memory.png
http://i31.photobucket.com/albums/c3...outhBrigde.png
I just noticed, I spelled Southbridge wrong :shakes: :ROTF: :shrug: :shakes:
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.
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!
Thanks for the repsonse on the version number clarification. I have the Se water cooled version. Nice to know I have the latest version.
Thats not the point of that test, I'm pointing out for no reason at all the CPU Vcore drops to around 1.2volts! These drops could be the source of the instability problems everyone is having.
I've already fully tested these setup. OCCT was just to detected anomalies, like a few pages back, i did one with everest.
that's what i was worried about... a failure later on down the road and not being able to return it. i have installed xp64 on the other one with a slow format just to double check it. everything turned out fine.
thanks, i'll take a look!
WB
do you have load line calibration enabled?
it might be your power supply. I'm not seeing any drops on any of the psus I've used in this board.
Warboy you are insain. "My cup of water is almost ice cause I have to bench test. Sorry honey you have to wear a jacket when you come over." My wife would just throw my computer gear outside if I ever did that. Although I used to get my room to around 50*F when I was single so my puter was nice and cool.
My point is I don't think the ramp down would be as fast as the ramp up. Real world I believe you would see a sawtooth type waveform, that is a quick rampup from heat, but slow rampdown. Something is fishy there.
I don't think its the power supply, But OCCT did detect something strange on the 5V rail for no reason.
http://i31.photobucket.com/albums/c3...8h00-Volt3.png
http://i31.photobucket.com/albums/c3...8h00-Volt5.png
http://i31.photobucket.com/albums/c3...h00-Volt12.png
PS I know I'm insane, Insanely Xtreme Air Overclocker :rofl: :ROTF: :yepp: :P
My temps on the CPU after these test was only 28C on core 3-4, and 31C on 1-2.
For Some reason cores 1 and 2 are alot hotter, I know their on different dies but damn.
how do i go about getting these pretty little graphs?
Just thought I'd mention something.
I managed to solve the iaStor timeouts and freezes by simply doing this:
Making sure there are no external hard disks connected.
Making sure to load the ICH9R driver on the drive select screen during Vista install from Floppy.
Once fully Vista is setup, install the latest 8.4.0.1016 Production Version of Intel INF, restart, boot and then restart again.
Lastly, install the latest 7.8.0.1013 version of Intel Matrix Storage drivers.
I then checked the iaStor registry and Parameters had already disabled LPM for me, very interesting, because that did not occur the last 3 times I had installed.
Anyways, hope this helps a few people that have experienced any problems in-regards to RAID instabilities.
how do you go about installing the newest drivers once the system is setup? i made a floppy with the new ones already but i was just wondering. also, i chose the ichr8/ichr9 RAID (desk/work/server) one. obviously i haven't been able to figure out if it's the right one (though it seemed to work) because my drive was bad.
i was just wondering because most people are choosing a ichr7 driver. what exactly is the difference?
Sorry to ask again, but anyone with a QX9650, able to set the multiplier?, Second anyone on 0702 able to set the multiplier of any processor at all?
Thanks,
ERIC
My little Maxipad has been Folding her gutz out now all week 24/7 at 3600.
The settings are all "green" voltages in BIOS and the temps are good enough I guess...About to drag the bollocks onto the porch to take advantage of this 3C weather :D
Just got an I-RAM device and flex PCI cable so I'll be benching the crap out of the Maxipad again and looking for some souped up Super Pi times.
And if GOD would stop punishing me for my inequities I might even get a damn YORKfield in the lil beeyotch. That might be too much to hope for :shrug:
On the ASUS website I can't download anyhting under Maximus Formula SE, but there are downloads in the Maximus Formula page. Are the BIOS and drivers the same for both these boards?
Hi Guys,
Max FSB so far here is 500x6 valid with my QX6850 on water for both chipset (30~34°) and CPU (22~24°) this cpu can do 515x6 valid on P35 in same conditions. Since Three days trying to got a 490x6/490x8 rockstable but it's really hard this board really drive me crazy :mad: I think 480~485 will be more doable... I will post my results here later...
P.S: Wich bios is the best for you guys ? I use 0505 here
Bye
p€p|n0r@ng
So far people prefer the ASUS board. Abit seems to be okay but a lot less "fun extras". Check the Abit IX38 Quad thread for more info.
The DFI isn't out yet ... as far as I know.
As for X38 vs X48, ask yourself if you can afford the DDR3 RAM?!
So far as I've read, only DDR3 boards have been mentioned.
That should help with your decision.
Maxipad is what you call her? :rolleyes: :D
Creative name though :clap:
I'm thinking of naming mine Bubba :D I had a better suited name but I forgot to write it down and now it's just lost in the ether...
What you guys call your comps?
Yes, the only difference is the cooling setup that is used on each board.
You have the Water Cooled version and it is 1.03g?
I don't mean to insult but care to post a pic that includes both revision number and the water block in sight?
Just wondering but does running more than one test stress the comp more or do some tests just negate each other?
Say for example running OCCT on RAM and small FFTs in Prime95 or some other mix of tests.
Cool. Been reading this thread a lot and unfortunately I don't know enough to help with the really tough stuff but good to know I was able to help this time.
After you recover, let us know how it goes! Good luck.
Cool, thanks! I always thought the 1.03g on my board meant the change in heatsink since the non-SE (mine) came after the SE.
I've seen before where a change in heatsink usually would warrant a change in revision number as well. But once you post your pic, then that means the revision number is tied to the board only and has nothing to do with the cooling setup.
Thx for the input TheSamurai and Majoram, That is all I need to hear from you TheSamurai. I will order right after I read some reviews on the board. Thx again TheSamurai.
cyberdruid how you likin this board compared to your dfi?
as stable?
got anyone with this board went for phase change cooling?
NP :D i'm sure you'll love the board once you figure out it's quirks. after reading around on all the other x38 boards i realized that i made the right choice. they all seem to have issues in one area or another. i've also read that the x48 wasn't a big deal as well as the new yorkies (i know i'm going to get flamed for that one haha).
what are you going to be running on the board? i'd update your signature so that it shows. ;)
Not a bad board. I think in some ways I am more at home in the DFI BIOS..I probably need more time with "Princess" to make a call.
The DFI is loads cooler on the CPU but the Chipset is way hot. The Maximus seems hot on the CPU to me in comparison...but the chipset stays cool even under hefty volts.
Best I could do so far is 4050 with the Maximus and was getting a tad over 4100 with the DFI on the same CPU. There are too many variables though to say why.
Folding performance on the Maximus is better than the DFI by several seconds at the same CPU speed. Could be the X38 is some advantage there.
Without a doubt the dual 16X lanes are superior to the DFI set up. With all things equal that extra bandwidth yields better 3D performance.
Not very happy with the RAID controller on either board TBH. Pretty lame to see bandwidth in RAID0 that is not even equal to single drive speeds. And this with Raptors...I am clueless.
I actually gave up on RAID with these boards..the first time in a long time I have done that.
I think for overall Clocking Finesse the DFI rules...but for actual 3D performance the Maximus takes the prize. They both run dead stable at 3600 and will bench at 3950.
thanks for reply
i'm more of a 500fsb+ junky
when i tried the x38-dq6 performance was great well 5% over my p35 got my cpu to 4.3
but for 3 weeks a reinstalled os 10+ times
for 500fsb+ which one you think is better i'm thinkin of waitin on the dfi-x38
as the x38 needs a good bois imho
my only concern is the pwm
:wave: Hello! I have a Maximus Formula, with the Bios 0602.
I change, the LCD poster option, to "User string" (default setting is "Current time"), ok, but ... how to define the "User String"? :D
Hi, my replacement motherboard has arrives, 1.02g of course, found out I'd ordered the wrong sized tubing for my wc so I'll have to wait until the correct ones get here now. Just trying to get the NB/SB off, seems to be tight, do I need to heat it up?
Thanks...
ChrisC
I have a temp issue and I don't know why ?
All at stock Q6600 I have on speed fan 51-47-43-39 at idle ... I cannot lauch 3d06 because I think It raise the temp and boot me out ???
On everest :
Températures:
Carte mère 45 °C (113 °F)
Processeur 74 °C (165 °F)
CPU #1 / Coeur #1 71 °C (160 °F)
CPU #1 / Coeur #2 68 °C (154 °F)
CPU #1 / Coeur #3 62 °C (144 °F)
CPU #1 / Coeur #4 58 °C (136 °F)
North Bridge 47 °C (117 °F)
South Bridge 46 °C (115 °F)
Ventilateurs:
Processeur 2394 RPM
Châssis #3 2174 RPM
Alimentation 2173 RPM
Ventilateur nº1 1140 RPM
Ventilateur nº3 2812 RPM
Valeurs de voltage:
Noyau CPU 1.22 V
+3.3 V 3.22 V
+5 V 4.97 V
+12 V [ TRIAL VERSION ]
Mise en veille +5 V 4.90 V
FSB VTT 1.25 V
Noyau North Bridge 1.44 V
Noyau South Bridge 1.09 V
South Bridge PLL 1.55 V
DIMM 2.02 V
DIMM VTT 1.01 V
Debug Info F FF 8D FF FF FF
Debug Info T 45 74 20
Debug Info V 98 D6 CA C9 AB CF AD (03
A Tip!!
Use nail varnish remover to get rid of the goop that sticks the NB/SB heatsinks inplace, works really well and saves all that scraping...
Chris
seriously..do u guys feel that blitz formula is better then maximus se? or isit this board still have immature bios?i would love to hear u guys opinion....it seems that with this board maximus, my 8500 balistik tracer is so damn hard to past 1200mhz...also the ram overvolt alot too...
i need some help here
i run my Q6600 G0 @ 3.4 ghz now, stable @ orthos
but, when i try 3.6, i get error after only 2 seconds
i have tried to raise my PLL volt to 1.6 and vcore to 1.41
but it dont help..
tried both 0602 and 0505 bios.. using 0505 at the moment
i need a recipe :p:
We have almost exactly the same setup. These are the settings that I am using to obtain 3.6
Quote:
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 : Auto
PCI-E Frequency: 100
DRAM Frequency: DDR2-1066
DRAM Command Rate : 2T
DRAM Timing Control: Manual
CAS# Latency : 5
RAS# to CAS# Delay : 5
RAS# Precharge : 5
RAS# ActivateTime : 15
RAS# to RAS# Delay : 3
Row Refresh Cycle Time : 25
Write Recovery Time : 6
Read to Precharge Time : 3
Read to Write Delay (S/D) : 8
Write to Read Delay (S) : 3
Write to Read Delay (D) : 5
Read to Read Delay (S) : 4
Read to Read Delay (D) : 6
Write to Write Delay (S) : 4
Write to Write Delay (D) : 6
DRAM Static Read Control: Auto
Ai Clock Twister : Auto
Transaction Booster : Auto
CPU Voltage : 1.41875 = 1.4 <--- Bios setting = Actual
CPU PLL Voltage : 1.52 = 1.648
North Bridge Voltage : 1.49 = 1.520
DRAM Voltage : 2.12 = 2.224
FSB Termination Voltage : 1.40 = 1.472
South Bridge Voltage : 1.05 = 1.088
Loadline Calibration : Enabled
CPU GTL Reference : Auto
North Bridge GTL Reference : Auto
DDR2 Channel A REF Voltage : Auto
DDR2 Channel B REF Voltage : Auto
DDR2 Controller REF Voltage : Auto
SB 1.5V Voltage : 1.5 = 1.552
NB LED Selection : NB Volt
SB LED Selection : SB Volt
CPU LED Selection : CPU VOlt
Voltiminder LED :
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
What's the reason for disable TM2-Function?Quote:
CPU TM Function : Disabled
The 5v looks really bad. The other spikes could be artifacts, but I remember GAR noted important fluctuations on voltages on this board too. There was another guy noting DDR2 fluctuations on load. Maybe there's some thing buggy on the PWM of the Maximus.
The only thing is that your 5v makes me feel there's maybe something wired with your PSU. You should really try another one to be sure
Yep, you only compromise each test stoling some CPU clocks on both
Hi,
okay, C1E and EIST should be disabled anytime, right. But TM2 are only throttle Core frequence and Vcore if the CPU heats up to the critical temperature. Some oc'ed systems are not working in this critical area, so we can leave TM2 enabled, i think. Q6600/G0 throttle first time when the Coretemperature arrives 85°C/185°F. Before this Value are not arrived, TM2 are not active. Ricgth?
cya,
Cb
Sorry for my bad english
TM2 should be kept active, as you explained
C1E is for vcore, but it is automatically disabled when you overclock, even if you enable it, sadely...
EIST, opposed to what was once said, won't impact your OC at all. Personally, I disable when looking for best clock (precaution). Once stable rock, I enable and test again. If oll is ok, I keep it (never had to disable it). That way I spare energy, money and my components life. No need to run at 3.5Ghz when I write a post in XS :)
I'm gonna receive this board (non-SE) this week I hope it will be a great board :)
Other way around.
EIST is automatically disabled when overclocking.
C1E can be left on if you wish for your multi to drop when idle. most leave it disabled to avoid possible issues with low voltage when resuming load.
As for TM some leave it on, some leave it off. It really is a matter of choice.
Sorry, you're wrong
EIST: adjusts multiplier, lowering it to 6x on idle, it is active when you overclock if your multiplier is left to Auto/default
C1E: once you increase your vcore manually, it will no longer kick in to lower your vcore on idle
As for TM: some leave it off, but silly decision. If your CPU cooler fails, your CPU won't go in protection mode and will fry
Attached is an image with ESIT kicking in at my 3.51GHz overclock, multiplier is 6x at idle
http://www.izipik.com/images/2007111...6-Untitled.jpg
Ok. What is the difference between C1E and EIST?
Ok, thanks for the answer jonny ;)
Hi guys, I have my CPU up to 3.9GHz and ran through 3dMark2k6 with no prob. However, when I run Bioshock (game) for about 15mins, sometimes it will lock up, but Vista is still running fine and can recover. My question is where should I be focusing my efforts? CPU volts, or NB volts, ram volts, or ram timing? I think I can make this system stable and I will be very happy with 3.9GHz! TIA
ElEctric_EyE => What is your Northbridge Voltage?
You should use some dedicated software to adjust your OC rather than a game. A game is ok for benching, but not for finding your stable OC
Use Prime95 small FFT to check your vcore is ok or no, and OCCT RAM to see if your NB and RAM are way too stressed. Small FFT or OCCT CPU mode first, once your vcore found, set it a notch or two above the limit found, get OCCT RAM stable, than maybe begin lowering your vcore vPLL to find the real lowest stable value
Good luck, you'll be the first to get a stable 3.9GHz Q6600 :confused:
Ok.
But I don't understand one thing:
I disable the EIST in my Bios (multiplier: 8, FSB 410MHz), I keep enable the C1E.
When my cpu is idle, the multiplier is 6 and the VCore 1.248Volt, when the system is busy (with Boinc), the multiplier is 8 and the Vcore 1.216Volt ...
Normal? :D
I kept the NB Volts on auto because I think on OC (crazy) it is regulating at 2.21V. And for SOME reason this version (0701)of BIOS will only let you go up to 1.85V on manual adjust
Sorry, NB Volts n OC(crazy) is at 1.62V... Gonna retry tests on manual 1.85V.
I don't believe so, but before this thread provides anymore false information:
C1E - Enhanced Halt State
"Whenever the OS executes the halt instruction, the CPU enters what is known as the halt state. Architecturally, what's going on in a halt state is the clock signal is shut off to the CPU for some period of time. With no clock signal, none of the logic in the chip will do anything and thus power consumption is reduced. Performance is also significantly reduced; however, the halt instruction isn't usually called during application usage, so the performance aspects of the halt state aren't very important.
The problem with the halt state is that it does nothing to reduce voltage, only current draw by stopping clocks from going to the CPU. Since Power varies linearly with both current and voltage (P = I * V), you're effectively only addressing half of the problem. The Enhanced Halt State, as Intel calls it, does two things: it reduces the clock speed of the CPU by decreasing the clock multiplier down to its minimum value (on the EE 965 series, that's 14x, or 2.8GHz), then reducing the voltage. The clock speed is reduced and then the voltage is dropped, to maintain stability.
Intel insists that the enhanced halt state is a significantly lower power state than the conventional halt state, thanks to the reduction in voltage in addition to the reduction in clock speed. While the standard halt state causes a linear reduction in power, Intel's enhanced halt state causes an exponential decrease in power, potentially offering better power savings than the standard halt state. The real world impact obviously depends on how idle your system happens to be."
EIST:
"What EIST does is very similar to AMD's Cool'n'Quiet. It is demand based reduction in CPU clock speed and voltage. Using the same mechanism of adjusting clock speed and voltage, based on the application demand, the processor will dynamically increase/decrease its clock speed between its minimum clock and its normal operating frequency, as well as voltage, in order to optimize for power consumption.
Because of the way EIST (and AMD's Cool'n'Quiet) works, there's inherently a drop in performance. The idea is this: if you're performing a task that's not using 100% of the CPU, the CPU will operate at a slightly reduced frequency in order to conserve power. So, while some tasks will require that the system run at full speed, others will run at lower speeds. "
Automatic thermal monitoring mechanism #1 (TM1)
* Operation: on overheating (when temperature reaches the sensor threshold, specified at the CPU production stage)
* Performance control: CPU clock modulation
* Voltage control: not available
* Behaviour: priority of the CPU temperature over its performance
* Additional characteristics: duty cycle reduction of the processor up to 46% (3.4 GHz Prescott, 3.4 GHz Nocona).
TM1 is an interesting and useful technology that prevents CPU overheating in emergency cases (for example, when a fan on the CPU cooler fails). Of course, nothing stops this technology to work in standard situations – for example, with a low-quality cooling system. To our mind, this technology has one serious drawback in this connection: TM1 effect is absolutely transparent for the operating system as well as to inexperienced users and typical sysinfo software. Why? Because an operating system as well as popular utilities like CPU-Z or WCPUID will tell users that the CPU clock in their systems is still 3.4 GHz (it's an example) and the CPU load is 100% (at full load). But in fact the CPU may be actively "throttling", that is operating at its minimum 46% and shock a user with its performance.
Automatic thermal monitoring mechanism #2 (TM2)
* Operation: on CPU overheating
* Performance control: CPU clock modulation
* Voltage control: available
* Behaviour: priority of CPU temperature over performance (nevertheless, performance is less reduced compared to TM1 due to the simultaneous voltage reduction)
* Additional characteristics: reduction of the CPU duly cycle to the level corresponding to the minimum to standard multiplier ratio (14/17 = 82% for the 3.4 GHz Xeon Nocona).
TM2 is a very similar (because it is actually based on the same principle – clock modulation), but still improved version of the TM1 technology. The key improvement consists in reducing voltage when TM2 snaps into action (that is when a CPU is overheated). It's useful both from the point of view of extending the CPU service life as well as its performance (which drops to a lesser extent in TM2 than in TM1). An heir to TM1, TM2 is not without the same drawback – its complete transparency to users.
So it seems to me that EIST/C1E have pretty much the same function, While TM1/2 offers protection in the case of overheating.
Anyway. my recommendations as to disabling these items came from none other than: http://www.xtremesystems.org/forums/...d.php?t=114824
A Beginners Guide to Intel Overclocking. Features and Problems Explained.
Quote:
EIST. that stands for Enhanced Intel SpeedStep Technology.
EIST is a feature, that adjusts your Multiplier, depending on the level of activity of the CPU.
if all your CPU is doing is browsing the internet or typing, then it will default to the lowest available multiplier, since its basically doing nothing.
this is to do many things, save on CPU power, save on actual power used, and to save on heat put out by the CPU.
theres no reason to have a CPU at full speed... if your only doing little mundane things like listening to a MP3, or browsing the net...
theres also... C1E.
C1E is a feature, then when it first came out, drove me absolutly nuts, cause no where was it explained what the feature was or even what CPU had it, for awhile after it started being used in processors.
so I'd be overclocking, run super PI, and get some great run... then C1E would kick in, and my voltage would drop from 1.5 volts, to 1.2 and my OC would stay the same... and this would always lead to instant CPU freezes.
this one single feature drove me so nuts trying to figure out what was going on, when about a year ago it started being used, and my Abit AS8 had no option to disable it, and I had no idea what it was...
I got to the point where I almost took the board outside, and smashed it from being screaming mad.
had I done that, I would have killed a perfectly fine board... cause this is a CPU feature.
a realllyyyyyyyyyy annoying CPU feature.
what C1E does, is lower the Voltage of the Processor, when at Idle, to save on heat output.
remember, a CPU is meant to only be run at stock.
Intel designs these CPU's to be stable at thier stock speed, with C1E active.
however, C1E for a overclocker, can leave you going nuts if you dot know what it is.
especially if you have a older LGA processor, that doesnt have EIST on it, but does have C1E.
C1E. if used with EIST, is actually a handy feature to have, if you want to keep your CPU temps low while at idle.
but if you choose to disable EIST, I strongly suggest you disable C1E at the same time, otherwise, this feature may drive you bonkers too, just like it did with me.
and then theres TM1/TM2.
I know what these are, Thermal Monitors.
however, I am still confused as to how these are different from C1E and EIST.
but, in my Gigabyte board here, in the bios, the description it gives is... TM1 lowers the CPU Voltage and MHz, when the CPU is at Idle.
to me, that just sounds like EIST and C1E... so I dont know how thats any different. but either of these 3 features, can and will alter your voltage readings in windows.
which is why, when you set say 1.5 volts in bios, you only see 1.2 volts, when you actually get into windows, cause EIST or C1E are active... or TM1/2.
disabling these, in bios, should obviously force the CPU to run at whatever voltage you select... assuming you keep in mind, you still have a voltage droop to deal with
Johnny must be getting some info from there as well. It is a little outdated as evidenced by the info i posted earlier and the exact functions of these items. Anyway, I will continue to disable C1E/EIST, as for TM, I may have to rethink that. So for now, that is my last word on this.
I stand by my previous statement. Take it or leave it, LOL
Very nice research. Thanks for that crazyea!
Most stable I have found for general use is with Vcore @1.5V and ram @ 2.19V in windows everything else set to default using bios 602
450 * 8 = 3.6GHZ 1800 FSB ram @ 600Mhz 5,5,5,15
Anything else temps go to high and I'm watercooled, I can go higher but OCCT doesnt like it and im happy 24/7. BFG GTX card OC with Riva to 650Mhz Core and 1050 Memory (effective 2100)
3D Mark06 14500 I would like to know though whats 2 ATI cards in crossfire getting with this board?
anyone try this yet? http://www.xtremesystems.org/forums/...d.php?t=162537
http://img442.imageshack.us/img442/3293/coldms8.png
These is with the 0701 bios ;)
WB please list your bios settings.
Good job Crazyea on the basics of the thermal monitoring.
I just wanna add a few notes.
C1/C1E does do as described but only if used with TM/TM1/TM2 It is like EIST but works in a different manner. EIST is the Intel "branded" halt state that is working between CPU and mobo NB chipset and is controlled by chipset in supported BIOS. This method of switching between modes is thus slower and actually uses system bus resorces so user will feel the drag i overclocked systems, even cuasing instability at medium overclocks. This may be 1 reason ASUS and most, fix it so it is not even available under higher FSB OC's.
C1E+TM2 s the on die (CPU) based P state that does its swiching right on the CPU so it is of corse much faster and you usually dont even notice it happening. It gets its "halt" commands from the OS though but s needs to see and use the CPU clock and vcore table ratios (for each CPU supporting) so it can relate to and adjust multi and vocore together. Now this how it is supposed to happen if at normal speeds, but a lot of mobo maker loose full use when you take vcore out of ato cause many CPU's cannot respond to such a vcore drop in idle and would just crash. I saw this a lot w/ my early E6600. So, for example, like w/ ASUS or Gigabyte, even if vcore is in auto but you move FSB too high, TM2 mode is lost, reverting to TM1 only but working w/ C1E still allows us to get reduced multi at low halt state of a % of usually 3 - 10% usage of combined 2 cores. Before, in C1 (non E) both cores would need to reach a 1 - 3% usage in order to reduce Multi.
Interestingly enough, My Abit's as IP-35 Pro and even budget IP-35-E, and AW9D MAX all supported full C+P state in a mild OC to 400FSB with Abit utilizing full ACPI control for S1/3/4/5. And when it works like it should, the vcore and ratio/multi are called for as any interupt in halt state so you get the full high multi and upper vcore as used by the C/P ratio tables of TM mode on CPU. The newer E6x50's are better at scaling this upwards as opposed to the older E6x00's
So, since C1E & EIST are alike, you should avoid ever having them on together. One or the other. For OC, TM2+C1E is fine, but just know it's normal for some reason for ASUS to revert to TM/TM1+C1E when taking ratio, FSB and vcore out of "Auto". So you will only get reduced multi but will cut down on heat anyways.
There's way more to it but this is just an addition to the earlier post
Has anyone been successful in lowering their CPU fan speed using the Afan settings in the BIOS or ASUS AI Suite? I can't seem to get them to change the speed.....my fan is freaking loud. I have two 120mms set up for push/pull so I've met a point of diminishing returns on CFM....