could it be that its because you are running 45nm processors? mine is 65nm and perhaps that might be the problem. i dont know though coz i tried running and running but it didnt do me no good.Quote:
Originally Posted by safan80
could it be that its because you are running 45nm processors? mine is 65nm and perhaps that might be the problem. i dont know though coz i tried running and running but it didnt do me no good.Quote:
Originally Posted by safan80
Auto CPU PLL gives about 1.60v yu can measure it at anytime in your BIOS, Everest. Auto for CPU PLL is a good starting point as it adjusts acordingly to your overclock, then you can tweak it from there manually.Quote:
Originally Posted by dimsdale
you cant load a saved bios profile after flashing from 907 to 1004.Quote:
Originally Posted by cyrixMII300
clear cmos and redo your settings manually, then resave your profile.
And 1004 has nothing to do with 65nm or 45nm, anybody with 4GB's or higher should go to 1004 for its the only bios with higher trfc
1004 is the best so far and its an official release on the Taiwan ftp. No longer beta, this has been disscussed b4 many pages back. I would look at how you flashed the board and retry it.
Hi Gys,
how are the measure points of Vcore, NB, FSB and VDIMM voltage on the Maximus Formula?
Bios to Actual vDroop listing
http://img128.imageshack.us/img128/6334/001dj0wo6.png
Are the LoadlineCalib on or off on this list ?
THX
Cos
I'm trying to get someone with the same cpu to co-operate, there is little point in running a side by side with dis-similar hardware.Quote:
Originally Posted by zlojack
Everyone with a "real" Rampage seems to have a quad. Perhaps I will open a new thread and get some scores.
MC2K was going to do some tests b4 he sold his Rampage but we didnt get together in time to run them, hard when there is such a time zone difference
So that was the purpose of loading those wr1/wr2.bat files?Quote:
Originally Posted by kup
Maybe this information should be included/posted so ppl are clear what method is best for them. With changing the rom id this will definately be an issue for some later on.
The newer method of flashing should be the prefered way as it makes no seroius changes in voiding the warranty
The .BAT files edited parts of the bios usually locked out, so we could flash the Rampage bios. With the ES version of AFUDOS it doesn't need to be edited.
You can see CPU PLL in Everest? That would be great. I'm running it now. What is it called in Everest? I can't find that in there.Quote:
Originally Posted by Grnfinger
I was on the ASUS Taiwan site last night and managed to find the BIOS downloads and downloaded 1004, but the file size was identical to the "beta" from the global site.Quote:
Originally Posted by Grnfinger
Not sure what to make of that.
I believe under Computer->Sensor it is "South Bridge PLL." I could be completely wrong though :)Quote:
Originally Posted by dimsdale
Hey guys. I've fallen victim to the random BSOD on this board. Previously rock solid settings now randomly and fairly regularly crash. Here's what I'm running.
3.6 cpu
1.66 vcore (I know it's high. but that's what the POS chip needs)
400 mhz fsb
960 mhz memory
2.00 vdimm
1.54 nb vcore
1.17 sb vcore
1.58 fsb vtt
The system doesn't crash under stress since I can play UT3 for hours at a time but randomly it will crash when idle or whenever. Could this be a degradation problem or is this just part of the Maximus owner experience?
Gotcha. Well, I think I'm going to be picking up a Q6600 next week some time, so if you want me to run anything, let me know. I'll contribute.Quote:
Originally Posted by Grnfinger
Hi, ofcourse it will, both are reading from the external diode, you need to read your core temps which are measured internally...Quote:
Originally Posted by rcjian
Chris
I need help... ;)
These were my current best BIOS 907 settings for 3.81GHz with my Q6600 GO. As soon as I deinstalled my 8600 GT, and replaced it with an 9800 GX2, my favorite stable 3.8GHz BIOS settings would not boot withought getting a CPU Check on my Maximus LCD Poster. It booted fine using the BIOS default settings.
I had to then load in my saved OC profile in, and back er down to 3.3GHz.
I need to go back to OCing my system to get my 3.8GHz back. I was thinking it was just a CPU voltage issue, but have given it 2 small bumps with only getting back to 3.4GHz.
After an unsuccessful 3.5GHz attempt, I ran into that Maximus CMOS error message, that only time heals. (The clear CMOS button did not help me out.)
I must have tried 10 times booting unsuccessfully to get around the CMOS ERROR on the LCD Poster. The display would go from 'INIT ROM' to 'CMOS ERR' to System lockes up...
I was real close to removing the battery, but that was under the GX2 and I didn't want to take it back out. I chilled for 20 minutes with the power off to the PC. After some Captain Black, I was ready to try again...
Came back in, hit the system with power, and it acted like it was fine again!! Booted right up.
Loaded the last successful OC profile back in that worked with some light OCCT testing, then backed that down a tad for saftey. 3.4GHz is where she currently sits.
My gut feeling is that I am so new at OCing CPU's, that it just needs a BIOS adjustment that I havent tried yet...
The CMOS error did give me pause though... Scarry stuff for me! ;)
I am trying to decide if I should go to the 1004 BIOS, or try and get 0907 to return my 3.8GHz...
I don't know what BIOS setting that my GX2 put more stress on that caused my system fo fail with a CPU check.
Any help would be appreachiated...
Under Extreme Tweaker
Ai Overclock Tuner : Manual
OC From CPU Level Up : Auto
CPU Ratio Setting : 9
FSB Frequency : 424
FSB Strap to North Bridge : 400
PCI-E Frequency: 110
DRAM Frequency: DDR2-848MHz
DRAM Command Rate : 2T
DRAM Timing Control: Manual
CAS# Latency : 5
RAS# to CAS# Delay : 5
RAS# Precharge : 5
RAS# ActivateTime : 18
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: Enabled
Ai Clock Twister : Strong
Transaction Booster : Auto
CPU Voltage : 1.51250v (BIOS)
CPU PLL Voltage : 1.58v (BIOS)
North Bridge Voltage : 1.55v (BIOS)
DRAM Voltage : 1.80v (BIOS)
FSB Termination Voltage : 1.44v (BIOS)
South Bridge Voltage : 1.075v (BIOS)
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
SB 1.5V Voltage : 1.50v (BIOS)
NB LED Selection : NB Volt
SB LED Selection : SB Volt
CPU LED Selection : CPU Volt
Voltiminder LED : Enabled
CPU Spread Spectrum : Disabled
PCIE Spread Spectrum : Disabled
Under Advanced
And CPU Configuration:
CPU Ratio Setting : 9
C1E Suppport : Disabled
CPU TM Function : Enabled
Vanderpool Technology : Disabled
Execute Disable Bit : Disabled
Max CPUID Value Limit : Disabled
Under Advanced
And USB Configuration :
USB Functions: Enabled
USB 2.0 Controller : Enabled
USB 2.0 Controller Mode: HiSpeed
BIOS EHCI Hand-off : Enabled
Port 64/60 Emulation : Disabled
Legacy USB Support : Enabled
My 4hour error free run using my 3.8GHz settings. Room temp was a brisk 55°F:
http://img216.imageshack.us/img216/8839/run10yv4.jpg
I havent seen any settings for Q6600's on BIOS 1004 that were above 3.8GHz..
I would like to.... If I flash to 1004, I would like a starting point. (Newbie)
I am running with 1 2GB stick of ram rated at 1.8v, and 5-5-5-18 timings.
Is there a benefit either way?Quote:
Originally Posted by kup
hey fellas any reason my usb drive doesn't load the msdos files after format
Hi, I thought I read somewhere that newer CPUs like core 2 duo uses Digital Thermal Sensor to measure their temps internally which make it more accurate than the external diode that was used couple of years ago!Quote:
Originally Posted by cuke2u
Your formatting FAT32? and pointing to the DIR where your dos files are located?Quote:
Originally Posted by trt740
Maybe the 9800GX2 dosent like the PCI-E at 110?Quote:
Originally Posted by Talonman
I dont run a quad ne more so I'm sorry I cannot help you out.
read this thread see what you think i'm doing wrong? Please It would be a great help I thought I used these files usb files from the download?Quote:
Originally Posted by Grnfinger
http://forums.techpowerup.com/showth...t=55422&page=3
Well AFUDOS-ES is a one stop solution, but the method in the first post requires several steps to complete.Quote:
Originally Posted by TouGe
AFUDOS lets you flash back any time you want...
:up:Quote:
Originally Posted by kup
I can't remember which way I flashed mine. No matter though, I am happy w/ where I am at now.
There's really no need to run at 110 talonman, the bus is not even close to the bottleneck on any games that are out right now, only MAYBE in rare situations in advanced CG work with heavy textures.
Thanks for the reply... I will change that to 100. :)
Probably burning your chip out lol... 1.66 dang something's wrong with that chip. I hit 3.6 on my old 6420 at 1.36v, I think it's defective or something.Quote:
Originally Posted by iadstudio
Quote:
Originally Posted by XtremeTiramisu
Quote:
Originally Posted by Grnfinger
Hi guys! I tried raising my NB from 1.47 to 1.49 and left it priming overnight, but worker thread 2 got the hardware failure error at 9 hrs and 18 min while worker thread 1 continued without error. Raised it again to 1.51 and priming stopped at 1hr or so! Dropped the volts to 1.50 and it primed for 3 hrs or so then error again. Now I put it back to 1.49 and set the values below to all 'auto' and its priming again right now.
Read to Write Delay (S/D) : 9
Write to Read Delay (S) : 5
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
Anymore opinions and suggestions are very much appreciated. Thanks guys!
Hi, like I said, use the core temp readings as they are more accurate as to the temps your CPU is running...Quote:
Originally Posted by rcjian
Chris