To bad its not 215, altho the board is supposed to be shipped with it.
I'll see if he will make a copy from the mobo itself.
To bad its not 215, altho the board is supposed to be shipped with it.
I'll see if he will make a copy from the mobo itself.
try trans booster disabled level1Quote:
Originally Posted by cajer
A small update from me again. I swapped the E6600 with an E8400 - this board actually rocks now! My ram has never been faster, and has never been clocked so high (544MHz), perfoamnce level 8 with all pullins enabled. CPU clocked at 4.1GHz (1.311v), FSB VTT 1.23V, NB 1.47V, SB 1,1V
Everest bench with my 24/7 settings: 9461MB/s read, 9479MB/s write and 9016MB/s copy. Latency is 52.9ns.
But I have an issue with 1:1 dividers, they just don't boot with FSB above 398MHz :/
8400's play very nice with this bios
I gained an extra 100MHz with little voltage increase
Bandwidth is very very good
What ram are you running?
hey Grn?
what everest voltage are you putting through your ram for 1175 ?
are you version 2.1 or 2.2 ?
2.2 volts and my ram is ver 1.2
I can post my bios setup if you like
Hi
Anyone else here has strange sound coming from maximus formula at load (occt, super pi)? it sound like old 56k modem connecting, only quieter, but gets louder when oc memory to 1080MHz 2.1V (from 900MHz 1.9V). i think that sound is coming from somewhere near NB. Otherwise mb is stable (few hours of occt and prime95).
Thanks in advance for any info or help.
Then most peepz don't know they can drop the multi and take full advantage of the higher FSB.Quote:
Originally Posted by Nuckin_Futs
does it go away for a second when you scroll your mouse wheel?Quote:
Originally Posted by jurc_podgurc
Yeah, I used to get that ever once in a while when I am running Prime95 Small FFTs. I believe the sound is comming from the Mosfets. After I dropped my CPU GTL to 0.63x/NB GTL to 0.65V and CPU PLL to 1.50V (1.616V) I haven't heard anything.Quote:
Originally Posted by jurc_podgurc
On a side note, that sound you speak of plagued many people who owned Nvidia 680i reference boards but it was much louder from what I understand.
Here it is: Formula.ROMQuote:
Originally Posted by ericab
the version you posted is : 207Quote:
Originally Posted by Edro Davis
Is it possible to extract BIOS ROM instructions from the MB as someone else suggested?Quote:
Originally Posted by ericab
It seems very odd to me that ASUS would be shipping the boards with 0215, shipping the DVDs with 0207, and putting 0217 on their website.
I wonder why? What is their "official" word on 0215? :shrug:
Thanks for checking the version for me. :up:
i believe Grnfinger is working on 215, with a friend.Quote:
Originally Posted by Edro Davis
as for shipping different bios versions on cd/mb/web etc... someone here stated it pretty well... the cds are burned with the latest version available at the time; and as the r&d / manufacturing of the boards finalizes, the most recent version is flashed to them. it sucks, but never install drivers with included cd/dvds; their always outdated. google is your friend :yepp:
To make clear. Are you saying you could not cold boot in full auto dufaults or sujt your RAM when set to 1066 period? 1.55v is rather for 1066 and especially if on mild FSB of under 475. I can Run Ballistics at 1200MHz on a NB of only 1.504v in 5:6 divider at 500x8. However, S3 (Stand By/Sleep) is not 100% stable unless I up NB to 1.54v and FSBT to 1.504v.Quote:
Originally Posted by Eastcoasthandle
So are you MAXIMUS owners now not able to boot w/ defaults after a BIOS flash or just because sinne BETA BIOS v0903? Isa this gonna be the norm from now on?
no, it doesn'tQuote:
does it go away for a second when you scroll your mouse wheel?
already have the same voltages set in biosQuote:
Yeah, I used to get that ever once in a while when I am running Prime95 Small FFTs. I believe the sound is comming from the Mosfets. After I dropped my CPU GTL to 0.63x/NB GTL to 0.65V and CPU PLL to 1.50V (1.616V) I haven't heard anything.
i left pc running orthos overnight (~5 hours) without problems, temps are fine. the sound doesn't disturb me (fans are louder and seagates when reading too), board is stable, without det ram problems if nb 1.45V or more, should i keep or rma the board? does this sound mean it will die on me soon? motherboard is only few days old and this strange sound is present from day one.
thanks
Will have the bios Friday
mc2k is busy with school and has not installed the board yet.
Personally I would have been all over that board like a fat chick on chocolate but....
Has anybody else removed their X38 chipset IHS for added cooling efforts on NB? I did it for now to see how I like it just like we used to do with our A64's. It's already added a 2c drop and it hasnt even set in yet (using AS#5) I used OEM cooing for now till I get the correct mounting for my HR-05-SLI. It screws down just fine without the slab of plated copper inbetween. If needing it for leveling, one can lap the inside and reseal but w/ AS cement.
Oh ya, I finally got my mobo back and it's up and running back to normal. They returned it back to me w/ BETA BIOS v0903, figured it'd be a final like v0802. I'd just go back to v0602 since uit was the most reliable for my set.
Your post isn't to clear for me but I'll try to answer (both 907 and 1004 yield the same results):Quote:
Originally Posted by Nuckin_Futs
-When I first got my MF it would not boot with my PC8500 ram. I just so happen to put in my PC6400 ram and it worked. I later installed my PC8500 ram and it worked but that was only after I installed the PC600 ram. My northbridge voltage was left at auto. I had my PC8500 at 2.02Volts in the bios (Everest reads 2.128V). At this point everything was working fine. I had no problems whatsoever but, I realized that my norhtbridge voltage was reading higher then I liked at 1.64V. So I decided to manually set it to 1.43V.
-All was well for a few days. I never counted the number of days. Then one morning it would no longer cold boot (plugging in the power cord to a wall socket for example) with det-dram hangs. I switched back to PC6400 and had no problem. PC8500 ram would only work only after I re-installed PC6400 ram 1st. To make a long story short, as long as I didn't unplug the power cord from the wall socket I could warm boot with PC8500 ram just fine. If I removed all power from the PC and left it alone for at least 5-8 hours I would get a det-dram hang with PC8500 ram. The only fix was to up the voltage on the NB to 1.55V which has worked for 3 consecutive days in a row with no power, cold boot-up. This cold boot was after a complete power shut off from the wall socket for more then 5+ hours (IE the power strip was turned off).
OCZ FlexXLC 6400 CAS3. There is still some room left in them, at 2.38V they can run 575MHz CAS 5-5-5-18, but itunes will crash :/Quote:
Originally Posted by Grnfinger
24/7 setting is as stated above.
LMAO:p:Quote:
Originally Posted by Grnfinger
Just got my Asus Rampage Formula yesterday (no maximus -> rampage conversion.)
It had BIOS version 0219 ready. Voltages seem to be bit strange (Dram voltage set 2.1 in bios, reads 2.192 in bios; cpu voltage set 1.38125, reads 1.360 in bios ?).
Can anyone comment those voltage readings?
Ok now even with a new psu i get the same problem and i was confused as my cheap 300w psu powered it up fine. So on a close look i found that the cheap psu only had the 4 pin cpu cable and not the 8 pin ? well after pulling the 8 pin out and swapping it with the 4 all seems to be well but is this ok for my quad :shrug: It sure is strange that my maximus formula has cold boot problems then my rampage had the same problem then with two new psu`s still the same problem but now with only the 4 pin in its fine..
If (and only if) you have a fan connected to the power fan connector (upper left corner of the board page 2-33 of MB manual) remove it and see if it will boot up.Quote:
Originally Posted by wilson
Quote:
Originally Posted by Eastcoasthandle
Now with these new settings I can post and boot but it freezes in the windows load screen. Also idleing my NB is at 48 degrees C. Voltage wise it is at 1.65 in the Hardware Monitor. Also how would I mount a fan on my NB if I am running my system in a case?
My P5E converted to Rampage does the same.Quote:
Originally Posted by GoldiClocks
Actually, to have 2.1 V BIOS sensor reading, I have to set 2.02 V.
Cpu voltage is normal because if you don't enable LLC, the BIOS apply a minus offset to the preset voltage, following Intel best practice in designing a VRM for core2 processors.
Yup, just what I thought, your NB is to hot for idle temps IMO. OK, now I'm willing to guess that if you figure out a way to cool your north and south bridge chipsets you should be in the clear for stability. Right now your problem appears to be heat related regarding the northbridge chip. Get yourself 2, 40mm fans and 4 1 1/2" wood screws and you should be good to go. For now, I would lower your dram frequency to 800 then lower your NB voltage between 1.45V to 1.50V and you should be ok in the meantime.Quote:
Originally Posted by cajer
Side note:
Did you ever remove that thermal cement before you installed the MB to your PC? If you look at my post here you will see that the HS doesn't always make full contact with the chipset.
Loadline Calibration was turned on when I looked at the voltages though :(Quote:
Originally Posted by Brama
Not stable till now, 533FSB is hard to reach but I am close:
533x6:
http://www.abload.de/thumb/cachemembios1004533x5vc.png
525x7:
http://www.abload.de/thumb/cachemembios1004525x8mh.png
Has anyone had problems installing soundcards on this board?
I've tried with both the Supreme FX II in the top black slot, and with a Creative X-Fi Platinum in the lower white PCI slot.
None of the drivers work, and I get a "No Audio output device is installed" message.
This is under Vista Ultimate 64-bit SP1 RTM.
Could this have anything to do with SB voltages or PCIe Frequency? (Currently running 1.5v SB and 110 MHz PCIe Frequency)
I want to run multiple displays on two Nvidia graphics cards. Just to be clear, I'm NOT talking about SLI.
Does anyone see a problem with that? Does anyone have specific experience with multiple display adapters for multiple displays? I want to run an 9800GX2 (which only runs one display) and a 320MB 8800GTS for my secondary display.
I run an X-Fi Platinum on the top slot (to make room for my HR-03+, sigged pics) with no problems whatsoever. I run Vista Ultimate x64. The only time I did have a problem was when I tried the drivers from the included disc. There is only one appropriate storage contained for the drivers disc: the rubbish bin. Your vSB is very high. I run a little over 1.1 with no problems... unless you're talking about vSB 1.5v, which I also have at 1.5 (and I also run PCI-E at 110). I don't think these things should have an effect, though.Quote:
Originally Posted by Durkadurka
***UNRELATED EDIT: New Maximuses at NewEgg! Maybe we're not going to be left out with the laundry!
The vDRAM is a normal overvolt. A lot of ASUS boards do that, and the Maximusi were no exception, so it surprises me not in the least that Rampages would do the same. Just be aware of it and undervolt where necessary.Quote:
Originally Posted by GoldiClocks
Your CPU undervolt seems odd. I have no comment regarding it besides that.
We should compare the X48 Rampage results vs. the X38 Rampage results to really see the benefit of the X48 NB.
I get the exact same over voltss on the ram and same under volt on the cpu.Quote:
Originally Posted by GoldiClocks
I have load line enabled but it still does it
Just make the adjustment in bios
Quote:
Originally Posted by GoldiClocks
Loadline calibration helps with vdroop (the drop while under load) and not the vdrop which is the undervolt I've seen on every board I've owned. I have mine set 1.30v in bios and get 1.28v real. I also have the vdroop pencil mod and the voltage doesn't budge under load.
Loadline calibration never seemed to do anything for me so I left it off. Pencil mod works much better.
btw this is with P5E -> Rampage
I do think you need to run different cards ie 1 nvidia and 1 ati or else there will be a driver conflict and only 1 nvidia card will be enabled. I could be wrong but I think it wont work with 2 nvidia cards installed.Quote:
Originally Posted by Dostoyevsky77
I run a X-FI ExtremeGamer in the top slot., Vista 32 and SP1 and have had no issues. I installed the drivers from the cd and then do updates from creative site.Quote:
Originally Posted by Durkadurka
my PCIE is set 110, google the issue and see if others have had the same problem and see how it was resolved
I can not put any fans on my nb or sb because my 9800GX2 commpletly covers my SB and my TRUE's fans compelety cover my NB. :( Any other ways to cool my NB and SB?Quote:
Originally Posted by Eastcoasthandle
ok, thanks for all the replies guys, guess I won't be RMA'ing my board yet.. :p:
I'll give it more work tomorrow, completely new to c2d overclocking so it will take some time to get results.
I think you are on your own on that one based on your setup, case, etc.Quote:
Originally Posted by cajer
you could try one of these fans from antec to cool your nb.Quote:
Originally Posted by cajer
http://www.antec.com/us/productDetai...?ProdID=75018#
Hey, that's a good idea.Quote:
Originally Posted by brewer265
Look here
Look at the bottom of my sig for the model of SB sink that I use. There are two types of Enzo coolers for the SB, the one I have listed comes with a fan and the GX2 clears it just fine.Quote:
Originally Posted by cajer
For my Vista x64 Ultimate acpi 2.0:Quote:
Originally Posted by avrionis
off = no sleep
on = sleep
What about some of those legacy options for USB?
So you guys experiencing this DET_RAM issue on cold boot, are you also getting this upon loading of system defaults? And also, are we talking since new on an ASUS final BIOS of v0802 and below?
I got mine on BETA v0903 and I can boot form reset of CMOS on cold boot out of the box w/ my Crucial Ballistix Tracers PC28500 2x1g on al BIOS to v0903. Never was an issue till I dabbled with BETA v0907 and then on. I RMD'd and the new one is fine again.
I'm just asking cause this is not normal and 2 of mine never did that w/ same RAM or even my OCZ. These RAMS just load as DDR800 and vdimm is already 2.0 since the mobo overcolts. My NB was only 1.35v on out of the bos cold boot for the first time. I did so in 2nd slots so cannot confirm 1st slots today on this mobo but my 1st one was fine either way.
Are you willing to remove the stock NB + SB assy.? This is the best method but then you need to find air or water cooling to fit in there where ned it.Quote:
Originally Posted by cajer
2nd is to just remove the "ROG" badge off the SB and fix 10x30 fan to take the load off the NB since it is fed upwards. Another idea, would be to shroud the whole length of the aluminum himps with NB inside and fan from front to back. Just make sure air is drwan from front lower cool area and exhaulsted to somewhere away from GPU. If anything shield the heat from that GPU as it isnt helping the already limited NB block.
Just some ideas!
I'm hoping that can be resolved in device manager by "updating" the driver on the other device.Quote:
Originally Posted by Grnfinger
Anyway, I think I'm going to do this thing (pending wife's approval). I'm nervous but excited: I can't wait to see the improvement.
I'll let you all know how it goes, but it probably won't be until next weekend.
Here is my sweetie:
http://www.newegg.com/Product/Produc...82E16814130344
Quote:
Originally Posted by Nuckin_Futs
So... are you saying that if I revert to an older bios or do the maxiumus rampage mod everything will clear up? Also I don't think that I can go water or buy some better cooling for my whole mobo because I am short on money. :( So I will just get hte Antec spot cool and point that thing towards my NB.
Is the older bios compatible with your CPU (X3350). I would be very careful with older Bioses.
I will go check.Quote:
Originally Posted by Eastcoasthandle
NO, reverting did not help me once I did go v0907, and from what I understand on RAMPAGE BIOS, this will void your warrenty (correct me if it has changed). But nevertheless, you're only opening the door for more problems if using a BIOS written for another mobo. So if doing so, do so at your own RISK.Quote:
Originally Posted by cajer
I had to RMA mine to get back to normal after the bad v0907. I know others have used it and claim no issues, so again, as with any beta BIOS, nothing is guarentied. Either mine was an isolated case or nobody wants to report it.
As for the cooling, totally understood, thats why I gave the idea of modding with things around the house, some plastic and cut and shape a duct for the NB and put small 40x25mm fan either to case rear exhaulst or on front end. Abit used this method on their early OATES system to cool mosfets and it did fine on air. I still have the 1st IC7-MAX 3 and changed the mosfets blocks to copper.
Do you have your ram at 2.224V from the bios or from Everest when going to 4-4-4-10? If not from the bios what voltage do you have set in the bios for Dram and northbridge?Quote:
Originally Posted by Nuckin_Futs
I always refference the reported , effective voltages as reported by CMOS Power Management I wish many would follow this as it does get comfusing.Quote:
Originally Posted by Eastcoasthandle
So YES, reported 2.24v by just about by PC Probe II and Everest. It may require a CMOS setting of 2.12v.
Should I try and flash back to 903 bios and see if I still get det dram error, or does it not allow me to do so using ez flash.
EZ-Flash (CMOS method) will not work, or didnt for me to revert back. The simplest way is Windows based ASUS Live Update. For XP x64 and server use v6.10x or compatable. under main options, check old BIOS to let it know you are recovering an olde BIOS ignoring the ROM date.
I never thought to try the DOS based EZ-Flash but I imagine it is the same as CMOS version, but worth a shot or plain old trusty AfuDOS with switches may work, I cant confirm that yet.
The 3rd is scarier then it sounds but I can say it works. attempting to reflach same BIOS rom you have now but cut PSU power off as it bigins to write new data. After a reboot, this promptes for the ASUS Crash Free BIOS Recovery Option. If you use this method, make sure you have only the ROM file you intend to flash on a CD or USB deivce by itself (no other BIOS ROM) or it will flash the first one it finds. It is fine to just use the CD too as it has origional BIOS v0402 as long you know your CPU will boot w/ it. As far as I know, this mobo was Penryn from day one anywayz.
If you do and you loose the DET_RAM, do let me know cause it didnt help for mine and any BIOS I was on form then on had quirks in it.
use afudos
make a dos bootable usb key, and use this file as it is the engineering software version of aufos.
http://www.xtremesystems.org/forums/...9&d=1205468995
copy the file mentioned above, and the rom image you want to flash to the usb key.
boot from usb key
in dos use
afudos /iROMNAMEHERE /n /pbnc
viola. :up:
1000000000x easier plus opens doors for more mods
Possible solution for some to eliminate "DET RAM" hang
Over the past few weeks of testing different OC configuations, I've being trying to completely eliminate the odd "DET RAM" hang. It only happends occasionally or some would say it appears when they start their system from a cold boot.
You can skip directly to PART 2 if your system is stable enough to pass hours of OCCT Mix and Prime Blend but still experiencing occasionl odd DET RAM hang during reboot or cold boot
Part I
What most people and I found about DET RAM hang issue is that the occasion for it to appear is related to the value of your FSB set accordingly. Usually people will starting to experience the first sign of DET RAM at around 440 ~ 450 FSB. And becouse everyone's system configurations are not identicle, there is not really a solution for all.
First thing to suggest is to check your CPU Vcore, make sure it's sufficient enough to pass 1hr CPU Prime/OCCT stress test.
Next we look at your NB and FSB voltages. FSB 1.40v bios set should be well enough to pass hours of Blend or Mix stress tests using Prime or OCCT even for the 65nm Q6600 G0 I've been testing with.
1.51v on the NB is a good starting point to troubleshoot the first sign of DET RAM hang, blue screen upon logging to windows, or blue screen/error detected/failure from Prime Blend or OCCT Mix.
As for CPU PLL, leave it at AUTO setting as the motherboard again overvolts in this area as well and AUTO setting will automatically scale with the given Vcore. Yes, auto setting is even enough to stable my 65nm Q6600 G0 at high 465+ FSB setting. If auto setting is good enough for 65nm quad, I believe it should be good enough for all 45nm cpu as they're even much easier to OC with given Vcore/CPU PLL.
Check your current Strap (266, 333, 400) and the ram divider set accordingly. This mobo works fairly poor using FSB 266 as opposed to its P35 chipset mobos. I'd recommend using 333 Strap for best overall system bandwidth. 400 Strap for further stability at high FSB setting but at the cost of overall system bandwidth.
Ram frequency/timings/relative given Vdimm: Make sure your desired given Vdimm is stable enough for its frequency and timings set. 2.12v bios set is a good starting point for OC DDR2-1066 modules as the mobo overvolts by ~0.8v which results in ~2.208v. Again each ram modules behaves differently, usually 5-5-5-15 for primary timings and rest subtimings set to AUTO or manually set to mobo's auto predetermined values are tight enough for daily use.
Part II
By adjusting my PCI-E Frequency from 110 to 112 finally solves the oddity of DET RAM hang or called the "black screen". This explains why no matter how high I've tried to raise the FSB voltage, CPU PLL voltage, SB voltage, loosen timings, higher CPU Vcore and higher Vdimm wouldn't completely eliminate DET RAM hang. If you are currently in the same situation where I was, I highly suggestion you try raising your PCI-E Frequency to a certain frequency that may aid you from getting DET RAM hang. Please note that this area isn't the priority when OC and it should only be overlooked when you're experiencing occasional odd DET RAM hang during reboot or cold boot but yet the system is stable under hours of stress tests.
RAMPAGE FORMULA 0219 BIOS.
Extreme Tweaker
Ai Overclock Tuner : Manual
OC From CPU Level Up : AUTO
CPU Ratio Control : Manual
- Ratio CMOS Setting : 8
FSB Frequency : 465
FSB Strap to North Bridge : 333
PCI-E Frequency: 112 No more DET RAM hang ("Black screen")
DRAM Frequency: DDR2-1116
DRAM Command Rate : 2T
DRAM CLK Skew on Channel A : Normal
DRAM CLK Skew on Channel B : Normal
DRAM Timing Control: Manual
CAS# Latency : 5
RAS# to CAS# Delay : 4 (TRCD)
RAS# Precharge : 4 (TRP)
RAS# ActivateTime : 10 (TRAS) TRAS = TRCD + TRP + 2 (4 + 4 + 2 = 10) For stability, this setting should not be set lower than this given formula.
RAS# to RAS# Delay : 3
Row Refresh Cycle Time : 35 (AUTO = 42)
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
Write to PRE Delay : 14
Read to PRE Delay : 5
PRE to PRE Delay : 1
ALL PRE to ACT Delay : 5
ALL PRE to REF Delay : 5
DRAM Static Read Control: Disabled
Ai Clock Twister : Stronger
Transaction Booster : Manual
C/P: A1 A2 A3 A4 A5 | B1 B2 B3 B4 B5
LVL: 07 07 07 07 07 | 07 07 07 07 07
Common Performance Level [7]
Pull-In of CHA PH1 Disabled
Pull-In of CHA PH2 Disabled
Pull-In of CHA PH3 Disabled
Pull-In of CHA PH4 Disabled
Pull-In of CHA PH5 Disabled
Pull-In of CHB PH1 Disabled
Pull-In of CHB PH2 Disabled
Pull-In of CHB PH3 Disabled
Pull-In of CHB PH4 Disabled
Pull-In of CHB PH5 Disabled
CPU Voltage : 1.46750 (1.452)
CPU PLL Voltage : AUTO (1.664-1.680)
North Bridge Voltage : 1.65 (1.680) *Note: high 1.65v NB is absolutely needed for hours of stability under Prime mix and OCCT blend stress tests. Using *8 multi Q6600 G0 at high FSB is indeed putting a lot more stress on the NB but also allows the system to gain greater amount of system bandwidth from using *9 multi of the same CPU frequency with relatively lower FSB.
DRAM Voltage : 2.12 (2.208)
FSB Termination Voltage : 1.40 (1.456)
South Bridge Voltage : 1.10 (1.12)
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-REF (1.104)
SB 1.5V Voltage : 1.5 (1.54v)
CPU Spread Spectrum : Disabled
PCIE Spread Spectrum : Disabled
Possible solution for some to eliminate "DET RAM" hang
Over the past few weeks of testing different OC configuations, I've being trying to completely eliminate the odd "DET RAM" hang. It only happends occasionally or some would say it appears when they start their system from a cold boot.
You can skip directly to PART 2 if your system is stable enough to pass hours of OCCT Mix and Prime Blend but still experiencing occasional odd DET RAM hang issue during reboot or cold boot.
Part I
What most people and I found about DET RAM hang issue is that the occasion for it to appear is related to the value of your FSB set accordingly. Usually people will starting to experience the first sign of DET RAM at around 440 ~ 450 FSB. And becouse everyone's system configurations are not identicle, there is not really a solution for all.
First thing to suggest is to check your CPU Vcore, make sure it's sufficient enough to pass 1hr CPU Prime/OCCT stress test.
Next we look at your NB and FSB voltages. FSB 1.40v bios set should be well enough to pass hours of Blend or Mix stress tests using Prime or OCCT even for the 65nm Q6600 G0 I've been testing with.
1.51v on the NB is a good starting point to troubleshoot the first sign of DET RAM hang, blue screen upon logging to windows, or blue screen/error detected/failure from Prime Blend or OCCT Mix.
As for CPU PLL, leave it at AUTO setting as the motherboard again overvolts in this area as well and AUTO setting will automatically scale with the given Vcore. Yes, auto setting is even enough to stable my 65nm Q6600 G0 at high 465+ FSB setting. If auto setting is good enough for 65nm quad, I believe it should be good enough for all 45nm cpu as they're even much easier to OC with given Vcore/CPU PLL.
Check your current Strap (266, 333, 400) and the ram divider set accordingly. This mobo works fairly poor using FSB 266 as opposed to its P35 chipset mobos. I'd recommend using 333 Strap for best overall system bandwidth. 400 Strap for further stability at high FSB setting but at the cost of overall system bandwidth.
Ram frequency/timings/relative given Vdimm: Make sure your desired given Vdimm is stable enough for its frequency and timings set. 2.12v bios set is a good starting point for OC DDR2-1066 modules as the mobo overvolts by ~0.8v which results in ~2.208v. Again each ram modules behaves differently, usually 5-5-5-15 for primary timings and rest subtimings set to AUTO or manually set to mobo's auto predetermined values are tight enough for daily use.
Part II
By adjusting my PCI-E Frequency from 110 to 112 finally solves the oddity of DET RAM hang or called the "black screen". This explains why no matter how high I've tried to raise the FSB voltage, CPU PLL voltage, SB voltage, loosen timings, higher CPU Vcore and higher Vdimm wouldn't completely eliminate DET RAM hang. If you are currently in the same situation where I was, I highly suggestion you try raising your PCI-E Frequency to a certain frequency that may aid you from getting DET RAM hang. Please note that this area isn't the priority when OC and it should only be overlooked when you're experiencing occasional odd DET RAM hang during reboot or cold boot but yet the system is stable under hours of stress tests.
RAMPAGE FORMULA 0219 BIOS.
Extreme Tweaker
Ai Overclock Tuner : Manual
OC From CPU Level Up : AUTO
CPU Ratio Control : Manual
- Ratio CMOS Setting : 8
FSB Frequency : 465
FSB Strap to North Bridge : 333
PCI-E Frequency: 112 No more DET RAM hang ("Black screen")
DRAM Frequency: DDR2-1116
DRAM Command Rate : 2T
DRAM CLK Skew on Channel A : Normal
DRAM CLK Skew on Channel B : Normal
DRAM Timing Control: Manual
CAS# Latency : 5
RAS# to CAS# Delay : 4 (TRCD)
RAS# Precharge : 4 (TRP)
RAS# ActivateTime : 10 (TRAS) TRAS = TRCD + TRP + 2 (4 + 4 + 2 = 10) For stability, this setting should not be set lower than this given formula.
RAS# to RAS# Delay : 3
Row Refresh Cycle Time : 35 (AUTO = 42)
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
Write to PRE Delay : 14
Read to PRE Delay : 5
PRE to PRE Delay : 1
ALL PRE to ACT Delay : 5
ALL PRE to REF Delay : 5
DRAM Static Read Control: Disabled
Ai Clock Twister : Stronger
Transaction Booster : Manual
C/P: A1 A2 A3 A4 A5 | B1 B2 B3 B4 B5
LVL: 07 07 07 07 07 | 07 07 07 07 07
Common Performance Level [7]
Pull-In of CHA PH1 Disabled
Pull-In of CHA PH2 Disabled
Pull-In of CHA PH3 Disabled
Pull-In of CHA PH4 Disabled
Pull-In of CHA PH5 Disabled
Pull-In of CHB PH1 Disabled
Pull-In of CHB PH2 Disabled
Pull-In of CHB PH3 Disabled
Pull-In of CHB PH4 Disabled
Pull-In of CHB PH5 Disabled
CPU Voltage : 1.46750 (1.452)
CPU PLL Voltage : AUTO (1.664-1.680)
North Bridge Voltage : 1.65 (1.680) *Note: high 1.65v NB is absolutely needed for hours of stability under Prime mix and OCCT blend stress tests. Using *8 multi Q6600 G0 at high FSB is indeed putting a lot more stress on the NB but also allows the system to gain greater amount of system bandwidth from using *9 multi of the same CPU frequency with relatively lower FSB.
DRAM Voltage : 2.12 (2.208)
FSB Termination Voltage : 1.40 (1.456)
South Bridge Voltage : 1.10 (1.12)
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-REF (1.104)
SB 1.5V Voltage : 1.5 (1.54v)
CPU Spread Spectrum : Disabled
PCIE Spread Spectrum : Disabled
@ kup
do you think performing the vdroop mod helped with o/c or o/c stability? i know you said you had a problem that was fixed by re-applying the mod, just curious about your thoughts on this matter. im trying to squeeze every last drop out of my rig.
I'm sill not getting a clear answer from the peepz experiencing this DET_RAM issue.Quote:
Originally Posted by XtremeTiramisu
I am talking about fresh after BIOS flash and clearing of CMOS. For the ones experiencing this, are you guys on hacked RAMPAGE BIOS or BETA v0907 and above?
has anybody on and only on final BIOS experiencing this at all? Is anybody on and ONLY on BERA BIOS v0901 - v0903 experiencing this as well. (excluding those who even flashed once to v0907 and back to something else)
I'm trying to clear up or compile some statistis on this when and aftering flashing of BETA BIOS v0907.
Mine did this ONLY on and since v0907. It never did that on v0903 and below for over 4months of many OC tests ewach stock and OC and vatious RAMs.
ThanX!
Right now I am on bios 1004. I will flash to bios 903 tomorrow and see if it helps. If it does not I will do the Rampage mod. If it still does not work I will try to RMA it to Asus.
Well after messing round with my new , 2nd SE mobo, I found out it is very picky on its beta v0903. Yet, if and if once setteled out, it is fine for the day. Even works in S3 mode on my 5:6 divider. My old one never did that on any BIOS version except v0903 but it was hit or miss. most days it would just fail to resume.
I still cant use FSB strap manual to 400 and is pick if I set RAM freq. to something equal of 1:1, but 5:6 is cool even to 500FSB for my DDR1200. It is also very picky if I try to enable Performance Booster, even to just (0) when at 480+ FSB in 5:6 CPU/RAM. Ai Clock Twister @ "Strong" is iffy, too unstable to Prime for long, but that's to be expected with an already high OC.
Removing the X38 IHS proved good. Idle temps went down by -1c (AR5 is not completely set in yet), but loading is lower by almost -4c. It is helping SB by 1c too, but this is mainly due to 80mm fan off ThermalRight RAM sinks. A draft blows right down into it and under the ROG badge.
For the hardest hang up, I had to clear CMOS and tap atx pwr periodically for almost 1min. this was enough to discharge caps of stored energy. It would then fire right up and let me load my profile save. When it did hang, it was sometimes during IDE_DET or mostly during Intel Matrix RAID detection. swopping a single SATA disc as IDE mode didnt matter here.
EDIT: Here's the weird thing, now after I got it back in order, it takes a longer time to detect my RAID array on Intel. Is this possable to hard crashing on RAID disc.
Otherwise, it's doing OK so far on day 2 of testing.
I think it did. It definitely made it more stable. With LLC and the vDroop mod I the vCore would go a tiny bit over bios set values on Load. :up:Quote:
Originally Posted by ZenEffect
well perhaps uou dont need to install fans on the NB or SB if you remove the cooling pipe option that comes with the mobo. just get rid of them and install a couple of HR05SLI/IFX thermalright sinks there and you should see a good temperature drop. and yes they are a tight fit but i have managed a way around it by rotating things around and i believe that you can do it too. consider that i have a 120 U-Extreme, 2 HR05 and a HR03plus on my 8800GTS. so it definitely can be done and with good effect too.Quote:
Originally Posted by cajer
i think most of us have around here. i for one did it as soon as i took the mobo out of the box. took my wife's hair dryer and got to work on it one morning while she was asleep. :rofl: got caught anyway. but i have seen my temps are quite good. i am still tinkering though right now.Quote:
Originally Posted by Nuckin_Futs
on a separate question that you had about the 0907 Bios, i had just recently flashed to that version and have no problems at all with my system. its running pretty rock solid overclocked and all.
Correct me if I am wrong, but this thread seems to be support for the x38 and not the P35 version. Can anyone point me to a thread dedicated to the P35 support here or somewhere else? I have one coming in to replace my Gigabyte P35-DS3R. I went with the Blitz Formula due to price that I got it at, voltage adjustments and the plethora of features compared to my Gigabyte. Any suggestions concerning the setup would be helpful. I have read various posts and have some ideas, but I have some specific questions that I would like to get answered.
1 - Since I already have my OS installed with raid and I am using a ICH9R chipset already do I need to do anything special to get the new MB to recognize the raid?
2 - Any gotcha's I need to be aware of when first setting this board up?
Thank you in advance for any help on this,
Utnorris
Tbh, 99% of the info in here applies to the Blitz as well. I owned both side by side and any tweaks I could apply to the Maximus also worked on the Blitz.
Just don't performa the Maximus mods on the Blitz!!!!!
Thanks for the quick response. Any idea about the raid question?
Utnorris
What is your Northbridge chipset voltage set to in the bios?Quote:
Originally Posted by Nuckin_Futs
Not really sure of RAID, if I'm honest. A few of the other chaps here are far more versed on the ins and outs of RAID and should be able to help you?Quote:
Originally Posted by Utnorris
Guys I just bought a maximus my e3110 does 9x450 np but the chip in my P5K-E would do 8x512fsb any suggestions on voltage etc in the bios to get my maximus up to 500 fsb. The P5k-E only needed 1.36v to get it there on the core. I'm sure the maximus can match it any suggestion on settings?
You need to enable RAID in the bios, get into the RAID ROM, setup your array to your liking, head back to the boards BIOS if you have additional drives to set it as the boot drive (if intended).Quote:
Originally Posted by Utnorris
For OS install use the traditional F6 pressing step.
Install the Intel RAID manager and set your RAID volume to enable "write back cache".
If you want you can also cut the array into pieces, which'll also increase performance...
For more info, check this thread:
http://www.xtremesystems.org/forums/...d.php?t=166867
Hey guys, I've spent hours reading this post, tons of great info but can't seem to find what I need. Does anyone have an e8400 running at 4.0 with 0907 bios? If so, please post your settings.
Thanks!
Why do you all suggest to people to use 333 strap?
266 is working just fine....only with the 4:5 it has a few issues but usually some other function is a reason like dram static or Tbooster..
Using moderate needs lower nb voltage.
Try using moderate and the problems may dissapear with det ram
even with your previous setting of pciexpress frequency and other
I have extreme problem:
Only ALL 3 DRAM led are ON, and nothing else (fans are working fine). There is no beep, no picture (I've try to change ram, moved ram to different slots,... even without ram) ANY IDEAS WELCOME:confused: :confused:
Do a search in this thread for Zucker2k and Grnfinger in this thread. They've both posted their E8400 BIOS settings a number of times, IIRC. If you're still having problems, it might be easier for you to post your settings... and especially your system specs!!!Quote:
Originally Posted by wreckwriter
This board pwns the E8400!
If you're going to the same chipset the RAID might migrate to the new board, but I don't think it'll work on a different chipset. I've done Nvidia 570 to 680i RAID migration and it worked, but never tried the ICH9R. I did however move a RAID from one Maximus to the other and it was fine. I would suggest you back everything up and cross your fingers. It just might work but I'm not sure.Quote:
Originally Posted by Utnorris
Also, like Wolf2000me said. Set everything in your and bios properly, but you shouldn't need to setup the RAID utility. You could go in ther to see if ti recognizes your array, but obviously you do not want to change the stripe size, format or anything in there or it will overwrite and your RAID will not work. (I'm pretty sure about this but I do not know what "write back cache" does)
4.0GHz is walk in the park.Quote:
Originally Posted by wreckwriter
Post your bios settings and we can see what needs to be adjusted
Quote:
Originally Posted by Spyrus
Thanks for the tips. I will try that and see if that helps to bring my Q6600 config up to 475*8 with 5/6 divider using the same current NB Volt or lower.
Reverting to older bios didn't work and cooling my NB with the Antec spot cool didn't work. (Although it dropped my temps by 6 degrees C.) I can't flash my bios to the Rampage bios because my USB stick refuses to become bootable. I also tried the settings that you guys said would get rid of the det dram. error but it still did not work. Any other ways to get rid of the det dram. error above 440 fsb?
Hello! I've been following this thread (and a few others) since this past weekend. I've just been waiting (for 4 days!) for the ability to post... :)
My issues are incredibly odd with the board. It sounds like Nuckin_Futs and Eastcoasthandle are in similar situations...
Basically I have all kinds of rididculous boot issues if i touch anything in manual mode in the BIOS. I've even (after clearing the cmos) gone into the bios, changed nothing, save/exit'd and it just powers off. Turning the PSU off until the board LEDs clear, and then back on again will often get it to boot.
I've tried a variety of BIOS versions to no avail.Quote:
Originally Posted by Eastcoasthandle
I recently tried a full cmos clear after re-flashing 1004 (removed memory, cmos battery, left overnight, etc). After putting the pieces back together my system seemed to have no issues until after a few hours and it was right back to the odd boot issues.
I too discovered that jamming the on-board power button a number of times after a failed post would sometimes get it to boot-up.
Sometimes if I remove or unplug some components/fans from the motherboard I can also get it to boot up. Once I've successfully booted and successfully gotten some OC settings applied. I can plug everything back in with no boot issues (so long as I leave the PSU switch on the whole time).
I've gotten my QX9650 up to 4 ghz with (10*400 and 12*333) and stable. I'd still love to tweak some things but having to deal with clearing my cmos and redoing the settings again and again is driving me insane (I can't just save my settings to a profile as I often have to incrementally adjust the settings or it seems to freak out and not boot).
However, the problems all come back again the moment I turn off the power switch on the PSU. Once it loses that it's the same issues aaall over again.
I'm trying eastcoast's suggestion of pumping the NB voltage up to see if that gets me anywhere, but it's not looking good.
Any help or suggestions would be greatly appreciated. I've been banging away on this thing since last Friday.
All I can say is that I'm using a E8400 so I don't have to go as high on the NB voltage. Plus, I am using fans on both north and south bridge heatsinks. If you are using a quad and over clocking higher then 400 (were I am comfortable with) one suggsstion is that you may need to go higher then 1.55V (for example 1.59Vor 1.60V depending on your FSB) on the northbridge with proper cooling. It's really all trial and error if the MB is actually working properly. Can both of your guy post your current Extreme Tweaker settings (IE: What setting you tried that didnt' seem to work)?
Volume write-back cache greatly increases performance, certainly in benching. Run a HD tach bench enabled and disabled, you'll be pleasantly surprised.Quote:
Originally Posted by iadstudio
It's not a bios option of course, you'll find it in the Matrix Storage Console.
I'd never recommend installing an OS on one chipset and later replace it on a different chipset. I've seen it work a few times but never without any hiccups. It's not a good idea at all, imho. I wouldn't give a eurocent for the OS' stability and it also adds a new stability variable when overclocking.
For just swapping out data it's a piece of cake when using the same RAID controller. Don't rebuild it, just plug it in and see if it gets detected correctly.
Then it's generally good practice to go back to the system bios and check out the boot order, among other things.
Utnorris...
If you do want to go down the OS swapping road, see if it boots. If it does then the first thing I'd do is install the chipset drivers for X38 after the swap.
Uninstall most of your drivers when you're still on the P35 board but make sure the storage driver is still live.
I can set absolutely nothing in the BIOS after a fresh CMOS clear, and it will exhibit this behavior. Which is - Enter bios after cmos clear, save/exit - Computer turns off (LCD still reads EN SETUP). Computer will not power back on except when I turn off the PSU - wait for MB LEDs to clear - turn PSU back on. Computer will turn on and I can even save out a few setting adjustments in the BIOS.Quote:
Originally Posted by Eastcoasthandle
That aside... I finally got to my breaking point and took apart my file server so I can try its PSU out, which is a:
Thermaltake W0131RU ATX12V / EPS12V 850W Power Supply
So far it seems like the issues of turning the PSU off and not being able to boot up with OC settings afterwards are gone. It will try to power on, turn back off again, then a second later power back up. The POST screen shows the correct settings I had enabled for OCing, but I'll get an error message after it goes through the entire POST (hard drive/raid read-outs and all).
"ERROR! The CPU core to bus ratio or VID configuration has failed!
Please enter BIOS setup to re-config it.
F1 for setup
F2 for defaults"
Interestingly enough, if I just hit the reset switch on my computer it reboots and I load up windows just fine w/o ever having to go back into the BIOS...
YES, moving an Intel RAID will migrate easily from P35 to X38/X48, even an older !975x on ICH8R will go (only needing chipset INF update). Just configure as in other mobo and you're good to go> INF appears to be fine but you can update with driver from this mobo CD.Quote:
Originally Posted by Utnorris
I'd say stick to the final BIOS for now untill you find they dont cut it then take the chance on BETA. Notice the many issues in this tread and other to BETA BIOD mainly 907 and above. Start w/ CPU section in full auto till you get RAID and drivers up to date, before any OC'n. I found v0602 to be the best for mine, but newer CPU's may have other needs. In v0802, For most BIOS vers. keeping FSB strap and RAM frequency to Auto is most stable for 1:1 (some will let you move RAM spd for certain dividers other then 1:1).
NB= 1.504v for up to 500FSB w/ dual in 1:1, in 5:6 (5:6 needs a tad more of each PLL FSBT and GTL_Ref)Quote:
Originally Posted by Eastcoasthandle
I figured it wouldn't , v0907 corrupted mine too so no matter what I did from then on didnt help. Maybe you 'll have better luck.Quote:
Originally Posted by cajer
To make sure card reader is bootable, leave all USB and floppy Emulate options to AUTO, or it wont see a lot of flash drives. NOTE, it doesnt have to be thumb drive, make use of most popular USB mass storages divices you may alread own. iPod, PSP, and most MP3 Media players. Just make sure to follow the file & floder naming rules for FAT_32 DOS, all caps, no spaces. It can even be from full sized HDD as long as it meetsa those rules (FAT_32, single partition).
Also check on ASUS forum to make sure the RAMPAGE hack is not gonna' void your warrenty and you can revert back without them knowing, cause w/ all this hacking, an RMA is not unrealistic nowdays.
I'm curious, cause I got simular, but isor was this after a trial on BETA v0907? Or if you F2, will it boot to OS as defualt? Mine did. But yet if I F1'd to change so much as anything (excluding RAM timings and Freuency), it would always hang at the DET_RAM, requiring hard reset to get teh F1 or F2 option again.Quote:
Originally Posted by jwfitt
So I could get past if I at least set RAN to manual timings and frequency for my RAM. For initial test, I used DDR800 @ 5-5-5-15 for the RAM in sig with 2.0vdimm (as overvolted by CMOS from BIOS 1.8 setting).
So does this work for you too? I knwo it's not normal but just curious.
I know a lot of peepz say they used v0907 and had no "quoted" issues, so maybe it's isolated to a few, or just mine. I also see a lot of peepz claiming the DET_RAM has to do with NB or VDIMM , but not for mine. It happened with stock rated DDR800. And for me, It only happened after V0907 test and moving back to v0802.
What are your bios setting bro I would like to see if my chip can match yours.Quote:
Originally Posted by Grnfinger
i wonder about some setting in the bios.. restore on ac poweer loss.. could this settings effect the boot problems people are having.. i don't have that boot problem but i think i have a tweaky nb problem with 4x1 pc8500 at 1080 and no water yet my temps at 1.51 (1.55 actuall) volts with fan blowing on it get up to 53-54 loaded way less then before i put on the fan but i still have a couple random crashes only when heavy gaming on certain servers with more eye candy than most. i also get a few random hard drive/data loss errors where my raid has to rebuild.
Real quick, so all of us can compare notes! Is there anybody here who never flashed to BETA v907 but has these DET_ hang issues now? and or has also moveed to a BETA BIOS after v0907 and now experienced them?
Please take a moment to share so it can help others.
Thanx!
i can't help.. i went from 401 to 903 and then 907. i never had the boot problem. i must have been lucky. so lucky to get a board with a different problem (hot nb) that hasn't gone away with any of the bios changes i tried. my memory tests out the only thing for me to do is remove the stock nb heat sink and reseat or add water to cool it down. which kind of sucks that i have to take my whole computer apart then dismantle the heat sink and void the warranty so it can run the way it should have right out of the box.
write-back cache enabled bumped me up 25 MB's in most of my HDD bench's. Thanks :up:Quote:
Originally Posted by Wolf2000me
I'm pretty sure we've been chatting over on extremeoverclocking.com too, but let me reiterate for the benefit of everyone else as well.Quote:
Originally Posted by Nuckin_Futs
I did receive the F1/F2 for defaults option after clearing the cmos to try to get the machine running again. Unfortunately, using F2 for defaults did nothing for me as my vista install was on a raid config. Going into the BIOS and save/exit'ing (w//o even changing a thing) would cause the computer to turn off completely. However, if i turned off the PSU until the MB LEDs cleared, and turned it back on I could then start up the machine and the settings I applied would be there.
From that point on the machine would be VERY finnicky. Like if at any time I went into Manual OC mode, and even left everything at defaults, and the power from the PSU was ever lost or manually turned off to the point where the board LEDs cleared, turning it back on wouldn't happen without another CMOS clear.
Sometimes, if i tapped the on-board power button a bunch of times after it tried to start up it would give it a 2nd go and load up fine - even with a lot of OC settings enabled.
I tried pumping my NB all the way up to 1.71ish and still these "cold boot" issues would happen.
I recently (as I mentioned in an earlier post) stuck the PSU from server into this box...same exact PSU basically except this one is 850W vs the newer 1200W PSU I was using.
So far all seems to be functional now.
The strange thing is the machine would run completely fine at stock and OC settings ONCE it got booted. It's like it wasn't getting enough juice at power-on...
Gonna keep testing my rig with the 850W PSU now... I'll keep you updated.
I did not have a chance to try this out, but I'm working well on an older (almost identical but smaller W) 850W PSU.Quote:
Originally Posted by loften
Thermaltake W0131RU ATX12V / EPS12V 850W Power Supply
The one I was using before (1200W) is still in my sig.
Hey, thanks for all the responses everyone. I didn't think it would be an issue since I am going from one P35 with ICH9R to another P35 with ICH9R chipset. I had just read a few posts where people were having problems with raid on the Blitz Formula P35 and I wanted to be ready for it. Now I just need to get the board here and finish my custom case and drain my W/C system so I can set it up on the new board. I am friggin stoked about this board, I am hoping I can run 4Ghz (450x9) with the added voltage settings. My Gigabyte goes from 1.6 to 1.8 with no in between and with vdroop I just can't get it stable at 4Ghz and I am betting it just needs a little more juice. Anyway, I will try some of the settings listed in the forums to see if they work for me.
One other question and I haven't done much research, but is there a SLI driver for P35 boards floating around? Just curious since this board comes set up to run 2 cards (although they are for CF) and I would love to add a 2nd 9600GT card to the system.
Again, thank you everyone for all the replies,
Utnorris
Has anyone tried this yet?Quote:
Originally Posted by XtremeTiramisu
that is kind of interesting about the psu thing.. hmmmm.. i don't know anything about the boot problems. i have never experienced them.. maybe people with multi 12v rail psu's are having problems on this board.. mine is a single rail x3 1k. it works good.. i just have a different problem.
I would guess so and more so for Linux custom users, but would guess it is not gonna be all the great since it will have to be an older exploited hacked firmware just like we did back on the !975X w/ nVidia 6800 Ultras. I did it and was hardly worth anything except to say I did it cause nVidia made it so hard for us not to. But yes, it is in essence truelly compatable, but nVidia will continue to do its best to keep it from us, the SLI support on Intel chipsets, as long as they have ties with AMD and AMD now has interest with ATI so it's a big investment deal. My thoughts of it at least.Quote:
Originally Posted by Utnorris
I did all that last month, and found I only needed at minimum to chamge the Frequency and manual timings so I can reset to get back in CMOS to set RAID. Like I said the min. of corse I set the rest of my profile as desired, but auto voltages had nothing to do w/ my issue.Quote:
Originally Posted by Eastcoasthandle
I used each a SilverStone quad rail and OCZ dual,, same thing, only the quad had less stability issues afterward.Quote:
Originally Posted by loften
Well, I've been putting this thing through the ringer. The smaller 850w PSU seems to be just fine with this board, and the larger 1200W PSU is doing just fine in my server...
What a week... :mad:
Anyhow, onto the fun part with tweaking my OC settings, gonna work on getting a Prime-stable 4 ghz config going. I'll post up my bios specs later tonight or tomorrow I hope!
EDIT:
What are some Max temps I should keep in mind for my cores and my NB (when under full prime loads)?
Sorry about this: but it is the first time I've ever been able to bench at 1GB/s on all R/W/C...
http://i228.photobucket.com/albums/e...Capture-21.jpg
Basically, tRD 7 all pull-ins disabled, and 5-4-4-12-2, tRFC 25 and the rest AUTO.
I have a P5E and I'm looking to flash it to the Rampage's bios. I went through the thread and it looks like a just have to follow the directions on the first page. But before I do will that do it properly and do I have to do anything else?
Just make sure you flash to 0219. You can flash to 0207 and then UPGRADE to 0219, but it's a PITA.Quote:
Originally Posted by xBanzai89
just wondering is your 850 a single 12v rail psu?