I think the problem here is the bios we're all trying to flash from? We need The Stilt to come in and confirm a few things before anyone tries it.Quote:
Originally Posted by Mic
Has anyone tried a Rampage bios using 'Crash Free' yet?
I think the problem here is the bios we're all trying to flash from? We need The Stilt to come in and confirm a few things before anyone tries it.Quote:
Originally Posted by Mic
Has anyone tried a Rampage bios using 'Crash Free' yet?
It was my understanding that the needed bios was included with the cripple / mod files.
Or did I read the instructions wrong?
RAMPAGE-ASUS-Formula-0207.ROM thats the only bios asus has on there site, has ne 1 tried that yet?
ftp://ftp.asus.com.tw/pub/ASUS/mb/so...mpage_Formula/
I don't see where to monitor the frequency in the BIOS, but in the settings I have mine placed at 105mhz.Quote:
Originally Posted by Grnfinger
Then that is the speed. It doesn't vary from what you set it to.
In the Cripple.zip we get the batch files, the rampage file and the loader file. We're supposed to flash the loader and then the rampage, but we can't flash the loader file to start with.
ahh ic
I wonder what bios he was on b4 the Rampage conversion, maybe it needs to be the same?
can someone share Bios 1004??? the link in 1st post doesnt work for me :(
Still working here? http://rapidshare.com/files/97357451/MF1004.zipQuote:
Originally Posted by andre X_X
Hmm then my BSODs are from something else. Works fine at stock speeds... I wonder if I just have a crappy board because the CPU and RAM work fine on other boards at those speeds.Quote:
Originally Posted by Renegade5399
I'm running out of ideas here :/
EDIT: It seems to fail after about 1 hour no matter the setting if I am OCed. I also cannot boot at 350-399 FSB. I'm wondering if my memory just doesn't get along with this mobo as most BSODs tend to be memory related. Then again when at stock speeds the memory still runs at 800mhz : / I'm stumped.
Anything faulty with my settings for the speed I'm trying to regain?
Extreme Tweaker
Ai Overclock Tuner : Manual
OC From CPU Level Up : AUTO
CPU Ratio Control : Manual
- Ratio CMOS Setting : 8
FSB Frequency : 400
FSB Strap to North Bridge : 400
PCI-E Frequency: 105
DRAM Frequency: DDR2- 800
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 : Auto
Row Refresh Cycle Time : Auto
Write Recovery Time : Auto
Read to Precharge Time : Auto
DRAM Static Read Control: Auto
Ai Clock Twister : Strong
Transaction Booster : Auto (Enable makes the system not boot)
CPU Voltage : 1.2625v
CPU PLL Voltage : 1.5v
North Bridge Voltage : 1.33v
DRAM Voltage : 1.92v
FSB Termination Voltage : 1.44v
South Bridge Voltage : Auto
Loadline Calibration : Enabled
CPU GTL Reference : .63x
North Bridge GTL Reference : .67x
DDR2 Channel A REF Voltage : Auto
DDR2 Channel B REF Voltage : Auto
DDR2 Controller REF Voltage : DDR2_REF
SB 1.5V Voltage :
CPU Spread Spectrum : Disabled
PCIE Spread Spectrum : Disabled
Sorta, for a Full CMOS Reset:Quote:
Originally Posted by doctorwizz
1. Pull 12v ATX Power cables from Mobo. 24 pin and 4/8 pin.
2. Clear CMOS Button: Hold for 10 secs
3. Remove Battery for 3 Hours. Has to be 3 hours on this board.
4. Put CMOS Battery Back.
5. Put Only 1 GPU in First PEG Slot closest to CPU. Leave 2nd Card out.
6. Plug all 12v ATX Power cables back to Mobo.
Quote:
Originally Posted by .OCX
Thanks for the info
What program are you guys using for clocking in windows? And does memset work on this board ??
This is a wives tale. There is no way the board holds a charge for that long with everything disconnected. I have personally tested this with a meter on several caps on the board. Once you pull the battery, power cables, tap the power button, and hit the CMOS reset button, the charge is gone. There is no more voltage left on the board. There was a heated discussion about this over at BPC and to shut everyone up, I whipped out the meter. I even intentionally used settings that caused the board to not be able to recover and need a CMOS reset. Did everything but let it sit for 3 hours :rolleyes: and what do ya know...booted right back up fine.Quote:
Originally Posted by .OCX
On another note, 1004 while being better than 1003, is still trash. With 0907, I can use the 7x, 8x, and 9x multis. With 1003/1004, I can only use 7x and 9x. 8x is broke no matter what I do. The same dividers are still broken and the memory timings seem to be more finicky. Also settings from 0907 with the 9x multi are not stable under 1003/1004. I can't for the life of me find what it is they have changed, but 0907 is still the way to go for 65nm CPUs.
They basically changed trfc, but I find its very 45nm friendly. Sold my quad awhile ago and my ES Xeon just got shipped the day b4 this bios came out so I cannot say for 65nm. But if you have a wolfdale its a keeper imoQuote:
Originally Posted by Renegade5399
This is my setting now, the problem is I can't use the divider to run memory speed higher, if memory speed higher than 1092 MHz gaming will crash with "Nvidia driver stopped responding message" , I don't know why ?? I don't know if this vcore is ok for 24/7 ??
Extreme Tweaker
Ai Overclock Tuner : Manual
OC From CPU Level Up : AUTO
CPU Ratio Control : Manual
- Ratio CMOS Setting : 9
FSB Frequency : 470
FSB Strap to North Bridge : 333
PCI-E Frequency: 105
DRAM Frequency: DDR2-940
DRAM Command Rate : 2T
DRAM Timing Control: Manual
CAS# Latency : 4
RAS# to CAS# Delay : 4
RAS# Precharge : 4
RAS# ActivateTime : 10
RAS# to RAS# Delay : AUTO
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: Disable
Ai Clock Twister : Auto
Transaction Booster : disabled
Relax level: 1
CPU Voltage : 1.4375
CPU PLL Voltage : AUTO
North Bridge Voltage : 1.51
DRAM Voltage : 2.20
FSB Termination Voltage : 1.52
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.5
Try the above settings plz... NB voltage is way too low for quad for sureQuote:
Originally Posted by Deus Excalibur
Do you still get the error if you set timing to 5-5-5-15 and run above 1092MHz?Quote:
Originally Posted by icecpu
Intel states that the ACTUAL voltage for E8400 should not exceed 1.45, so I would think its safe for 24/7 use.
He might want to increase his NB higher than that. 4GB taxes the NB more than 2GB so 1.45 might still be to low, I would recommend 1.49 and adjust from there.Quote:
Originally Posted by Leeghoofd
Loosen the timings on ram instead of 4-4-4-12 use 5-5-5-15 to get above 1066Mhz and set Strap to 400FSB, don't get it, you guys try to force something which isn't logic at all... be happy it already ran at your current settings....Quote:
Originally Posted by icecpu
Quote:
Originally Posted by Leeghoofd
OCCT is another benchmark that found error like memtest. Infact today I tested with OCCT ram, and after about 1 hour stopped. ( set 6 hours)
Quote:
Originally Posted by Renegade5399
Actually, this was the only way for me to get around DETDRAM with my HK's when that was the only ram I had on hand at the time to POST. I had to wait 3 hours between each CMOS Drain with Battery pulled. Even tried it at 2.5 hours and couldn't POST. Waited for full 3 hours and was able to POST.
Even seeing more and more manufacturers saying that the CMOS Reset buttons + Default values is not a proper reset when using new Memory. They [Geil, GSkill] are even suggesting pulling the CMOS battery for hours to reset the Bios completely.
Yes, everything stable except when gaming
I did use 5-5-5-15 for 1092Mhz, no go
I use 4-4-4-10 at 940Mhz
That's funny. I've swapped back and forth between 2 different types of memory today three times and it hasn't batted an eye.Quote:
Originally Posted by .OCX
for some damn reason my G.Skill HZ's won't work. I have ti use a crappy DDR667 Kingston stick to boot the computer to the bios. From there i tried to play with some ram setting and upped' the voltage for Dram and the computer worked for a week. As soon as I powered it down for the first time...
The damn DET Ram came up again... what gives ??
First off, what is really the big issues with the ASUS final BIOS for the Penryns, the duals in particular? I realize everybody's hiped on RAM sub timings but is it really making a big difference over stability in real world apps or just for benching?
So what really didnt work for this CPU in say v602 802? Also I was likely gonna' get a Q9450. I know too many people saying they cant get a lot of OC out of these QX9650 extremes. Is this judged on simply the highest clock on highest multi? Is anybody actually utilizing the low multi of these to see how much higher they can go with mobo FSB?Quote:
Originally Posted by bro20000
See my previous post on haw to flash from other media sorces. It doesnt have to be flash stick or USB.Quote:
Originally Posted by Mic
Single partitioned, FAT32, bootable medai sorce. If MAXIMUS can see it in POST, you can flash from it in EZ-Flash.
When the board goes back to defaults after an OC failed, the DIMM voltage goes back to 1.8-1.9v. This will cause the DET DRAM hang on RAM that needs 2.0v or more to run. There are a few ways around this.Quote:
Originally Posted by .OCX
1. Use only one stick in the slot farthest from the CPU and try to boot.
2. Take all sticks out and power the unit on. You should get the no memory beeps. Power down via PSU switch and put one stick in. Try to boot then. It should come up.
3. Get a stick of cheap DDR2 667 or 800 Value RAM that only needs 1.8v. Put the stick in and power on. I can almost 100% guarantee it will boot. Then just go into the BIOS and tweak your settings, Save and Exit. Once the rig boots, re-enter the BIOS and kill the power via the PSU switch. Put your good RAM and and power back up. Voila! It will boot.
Now as far as the tech on the phone telling you that an "extended CMOS clear" is needed: They are doing this to get you off the phone and guarantee you won't call back for 3 hours. Think about it. "New Memory" is just like "Old Memory". It's a set of chips on a PCB. It has NOTHING to do with how long you need to clear your CMOS for.