I just did it. I never had any problems with flashing (back or newer bios).Quote:
Originally Posted by Nuckin_Futs
Used my USB-Stick and EZ-Flash and it flashed back like it flashes a newer bios. Reboot and volià....
I just did it. I never had any problems with flashing (back or newer bios).Quote:
Originally Posted by Nuckin_Futs
Used my USB-Stick and EZ-Flash and it flashed back like it flashes a newer bios. Reboot and volià....
Anyone else with exception of QX9650 users, have problems with both the Rampage and Maximus formula in clocking a Q9450/X3350? I cannot get anywhere with mine, wondering if maybe we can narrow it down to a board issues with its current BIOS. Or if its flat out the chips fault, I know my maximus can do 490fsb, it did 490x8 with my Q6600G0 with like 1.65v.....
Any input would be greatly appreciated.
Much faster POST with 0308, however I am trying everything to get this damn X3350 to clock worth a damn.
I posted on other ones with the same problem, maybe someone could include their findings with 45nm and the Maximus/Rampage Formula?
I have been trying for hours, it simply wont go over 450mhz FSB.
man stop with the part 2 threads you separating information by doing that.
Ow but a short 'consolidation' post makes it look like he's providing the community with ow so much usefull info :rofl:Quote:
Originally Posted by safan80
Hi to everyone,
Was waiting for Rampage to get here,
I've had many stability problems with my max SE rev. 1.02.
Couple of questions if anyone care to answer before I upgrade to RF bios:
1-Now that RF bios possibility, If was able to get the real Rampage MB do you think I need to upgrade to Rampage MB to get the full features.
2-Is Max rev. 1.02 also compatible with the upgrade.
Cheers
From what I hear alot of Q9450's dont clock that well, seems certain batchs dont like high FSBQuote:
Originally Posted by ChaosMinionX
Marvin, you have no need to be here, you don't even own the required hardware, so kindly keep your opinions to yourself. :D
Saf', if you feel this thread will split info then continue to post exclusively in the first thread. You didn't seem to mind the Maximus Part 2 thread. This thread was just to tidy up the findings and present them in a clearer way without trawling through pages of snippets. It will also be kept up-to-date with the bios files rather than have them scattered all over.
I'm gonna flash the bios back to a P5E. I don't like the Rampage bios at all, it's hella lot more unstable than the P5E bios. With the Rampage bios I had a lot BSODs on the same settings as the P5E.
The only positive thing: A lot less Vdroop.
What settings are causing instabilities? With the Rampage bios you might need more voltage? Also, the Performance Level setting works differently now so make sure Transaction Booster is set to Disabled or Enabled (Level 7 or 8) and see how it goes?
So far, from my brief attempt with a Q9450 L811A506, I was only able to boot at 8x440 since 8x450 result in either a freeze just at OS loading or DET DRAM error... I will continue the testing tonight to see if it is either a FSB wall or a max overclock. Compared to my Q6600, it's a bit disappointing but my folding time is unchanged beteen the two even if the Q6600 clocked a bit higher.
sweet!
Ditto here with a Q9450. I'm feeling there might be a setting causing issues but with the boatload of options, I dunno where to start :eek:Quote:
Originally Posted by ChaosMinionX
Search the forum, you will see alot of Q9450 user are having the same problem, the 9450 dont like high FSBQuote:
Originally Posted by Xilikon
Yes, I noticed that... I also have a P5K-E/Wifi-AP and I might try to see if it is a CPU or board limitation since it seems owners of P5E-VM can clock them much higher.Quote:
Originally Posted by Grnfinger
Quote:
Originally Posted by kup
I have been following the first thread from the start, waffling between doing the conversion and not. I have been doing my taxes for the last few weeks and my 907 MF bios have been stable and have remained that way with my OC for months. But now that you have started this "part 2" thread with the step by step instructions and have finished my taxes, I believe I'm going to take the plunge. I for one am happy you started this thread. Keep up the good work. :up:
Quote:
Originally Posted by ChaosMinionX
My Q9450 is behaving a little differently. I am able to get 450x8, but it's unstable with vcore @ 1.325, but it does boot and get into the OS, so there is promise. However, I have noticed when the "Common Performance Level" is set to 7 the mobo DOES NOT respond and comes back with "overclocking failed".Quote:
Originally Posted by Xilikon
Following GrnFingrs settings, the only way I can use the "Common Performance Level" @ 7 is if I set my strap to 266 and FSB to 266. I'm going to look around in other threads today about CPL, can someone tell me WHY I am unable to do a mild oc or even run stock settings with my Q9450 & CPL 7? What does the CPL buy me? Thanks in advance.
Lower CPL increases memory bandwidth, and decreases memory latency.Quote:
Originally Posted by chawks2
amen i had the same issue i tried everything but it wouldnt go past 440 same thing as you happened to me :down:Quote:
Originally Posted by Xilikon
There are a few people that populate this forum that were hitting 4.0GHz+ with <1.38V on their QX9650's. So I was a little disappointed when it took 1.38V just to get 3.80GHz:(. Its the luck of the draw I guess.Quote:
Originally Posted by dimsdale
It was nice to hit and get stable @ 3.8GHz but it runs a little warm for me @ load. I'd feel better knowing what the official TjMax was for the 45nm Quads and the max safe Vcore these things can sustain and still have some longevity in them. I've heard some speculate that the TjMax was 95 degrees but from what I understand Intel hasn't released any numbers yet.
Later this summer I plan on throwing some money @ an X48 board, some DDR3, and a decent water cooling kit, then I'll push for more. But right now I'm running @ 3.6GHz w/ only 1.31V (1.28V under load)--still testing--which took me 1.45V on my old x6800 DC chip, so I am happy for now.
Definitely, though, you should give the Rampage BIOS a shot. It is up to version 0308 right now and its alot of fun to play with.
what for ClockGen in the SetFSB have the Maximus X38?
Quote:
Originally Posted by Sources
Typo- ITS NOT posting.Quote:
Originally Posted by Sources
So...setting it to Auto gives you a balance? Or does it dynamically change?Quote:
Originally Posted by Stanley Pain
I seem to have my rig (in sig) stable at 3774 GHz and 444 FSB. So I thought I'd post my BIOS settings (1004) in case it might give anyone else some ideas or if anyone cares to comment on any improvements I might make.
I went with the FSB of 444 because it allowed me to select memory speed of 1066. I can't even get to 1080 on these G.Skills without relaxing the timings. So I figured to keep it at 1066 at auto timings.
Looks like at this point these Core 2 procs are more FSB limited than anything else. Having a proc at >4 GHz probably means the proc is waiting a lot to get data in and out of memory. Getting the FSB from 400 to 444 did more for my benchies than most other similar tweaks I've made.
I tried to hit 500x7.5 @ 1:1 DDR1000 a la Nuckin_Futs, but I couldn't even POST with that. That gives me hope it's a config problem, not a massive instability at 500. Nuckin_Futs, if you're out there, would certainly be interested to see what you set to hit that 500 @ 1.1. Are you still running the settings posted at http://www.xtremesystems.org/forums/...ostcount=2704?
Code:Extreme Tweaker
Ai Overclock Tuner : Manual
Ratio CMOS Setting : 8.5
FSB Frequency : 444
FSB Strap to North Bridge : 333
PCI-E Frequency: 100
DRAM Frequency: DDR2-1066
DRAM Command Rate : 2T
DRAM Timing Control: Auto
DRAM Static Read Control: Disabled
Ai Clock Twister : Strong
Transaction Booster : Disabled
Relax : 0
CPU Voltage : 1.400000 (measured 1.38xxxx)
CPU PLL Voltage : Auto
North Bridge Voltage : Auto (measured 1.61)
DRAM Voltage : 2.00 (measured 2.04xx)
FSB Termination Voltage : Auto (measured 1.42?)
South Bridge Voltage : Auto
Loadline Calibration : Enabled
CPU GTL Reference : .63
North Bridge GTL Reference : .67
DDR2 Channel A REF Voltage : Auto
DDR2 Channel B REF Voltage : Auto
DDR2 Controller REF Voltage : Auto
SB 1.5V Voltage : Auto
Day no 2 on OC'ing BIOS 1004 with my Q6600:
I have played with the CPU, PLL, NB, SB, DRAM, and FSB Termination voltage until I am blue in the face!!
My "Initializing USB Controllers" problem would not go away...
I was looking at my USB section in the BIOS, and it listed mouse, keyboard, and USB Hub as devices...
I took my Flash drive, and tried plugging it into the front post of my TJ09. It was dead!! I then took my Case wires for the USB ports, and unplugged them from the USB port on the mobo closest to the SATA ports, and plugged the wire into the other USB port that is closer to the reset button. It worked and my PC's case now has working USB ports.
Normally I have been using my FPD's USB ports. I then unplugged my FPD's USB wire from the back of the PC. I fugured it might be draining some voltage that the Maximus needs?
I do have my USB HP wireless mouse plugged into a USB port, and that's all. (Keyboard is a Dell PS2 type)
I tried my 390 FSB again with my 400 NB Strap. I did successfully boot into windows for the first time with a 390 FSB!
I thought the hard work was over...
The system was not stable, and prime went south in the first minute on multiple cores.
I upped some voltages, and my USB problem seems to be gone, but now I get this with a 390 FSB.
Windows Boot Manager
Windows failed to start. A recent Hardware or Software change might be the cause. To fix the problem:
1) Incert your Windows installation disk and restart your computer.
2) Chose your language settings, and then click "next".
3) Click "Repair your computer".
If you do not have this disc, contact your system administrator or computer manufacturer for assistance.
File:\windows\system32\winload.exe
Status 0xc0000221
info: The file is possibly corrupt. It's header checksum does not match the computed checksum.
My feeling is this is a BS message, due to me just powering the computer off when I receive it, set my FSB back to 380, reboot into windows error free.
Any thoughts? :)
One other thing is I have that annoying red X on my internet connection when I first boot into windows for about 1 minute. Last time this happend t me it was a sound card issue. Using the device manager, I de-installed my "High Definition Audio Device", and re-boot. Windows adds it right back in telling me it installed correctly. If I right click on the "High Definition Audio Device", and select properties/ Driver, and Update driver, and search the net, it responds with "Windows has determined the driver software for your device is up to date".
The X remains for about 1 minute, after the desktop appears on every re-boot. (I think the system is trying to resolve a network driver conflict, then gives up.) ??
I don't know if a funky soundcard driver could be hampering my OC'ing efforts?
I baught Unreal Tournament III, and it lockes up at the Splash screen. I searched the net, most posts have "No knowen cure" for this issue. I found one obsure post about some dude thought it might be sound card related...
I loaded windows, de-installed my "High Definition Audio Device", started Unreal Tournament III and my God... It worked for the first time!! (No sound though). I think this SupremeFX II sound card has driver conflict issues...
It ALWAYS lockes up at the Splash screen if my Sound card is installed, no exceptions.
My little spirit is getting beat down on this...
I think I am looking like 3.4GHz is my limit no matter what I do. High voltages aren't resolving the issue for me...
As it sits now, a 390 FSB will cause windows to load all the way to the desktop, then core dump.
or I get my Windows Boot Manager message...
or it just lockes up.
Could a crappy GX2 driver be holding me back. Remember, I lost my 3.8GHz on install day of the GX2.
It's kicking my butt! :p:
No problem initializing the USB Controller though...