Thanks for the info played around with vtt & gtl's got my vtt down from 1.351 to 1.3 volts +30 +10 +30 + 10 9 hours prime small ftt occt blend :up:
Printable View
Hi guys,
I managed to find a pretty good Q9300, that is in my signature now (rock stable at 1.34 vcore).
Do you have any settings for 7.5*500. With vcore 1.375 PC get in windows and I managed to make about 10minutes testing with Orthos but then PC freezes. So if you have some settings to stabilize it, i will be very greatfull.
Best reagards
What settings did you use to get into windows at 500 FSB? If you can fill out a template we can go from there and see what it can do.
Depends a bit on how much you want to thrash it, and how it responds, some Quads will not do 500 FSB but I have not got any experience with them - some guys here do though, hopefully they can give you some advice. It will probably take 1.3 - 1.4 vFSB, 1.55 - 1.60 vPLL and 1.37 - 1.45 vcore, but you should be able to get a little more out of it without pushing it that hard.
Almost everything is on Auto, because I really don't understand why I need so much things to twaek. On my older motherboards it was just vcore and everything goest fine :) Now there are so much settings and almost no explanations about what to do exactly, so I prefer to put everything on Auto and try that way.
So here it goes:
BIOS 1802
Ai Overclock Tuner: Manual
OC From CPU Level Up: Auto
Ratio CMOS Setting: 7.5
FSB Frequency: 500
CPU Clock Skew: Auto
NB Clock Skew: Auto
FSB Strap to North Bridge: Auto
DRAM Frequency: DDR2-1000Mhz
DRAM CLK Skew on Channel A1: Auto
DRAM CLK Skew on Channel A2: Auto
DRAM CLK Skew on Channel B1: Auto
DRAM CLK Skew on Channel B2: Auto
DRAM Timing Control: Manual
1st Information:
CAS# Latency: 5 DRAM Clocks
DRAM RAS# to CAS# Delay: 5 DRAM Clocks
DRAM RAS# Precharge: 5 DRAM Clocks
DRAM RAS# Activate to Precharge: 15 DRAM Clocks
RAS# to RAS# Delay: Auto
Row Refresh Recycle Time: Auto
Write Recovery Time: Auto
Read to Precharge Time: Auto
2nd Information:
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
3rd Information:
Write to PRE Delay: Auto
Read to PRE Delay: Auto
PRE to PRE Delay: Auto
All PRE to ACT Delay: Auto
All PRE to REF Delay: Auto
DRAM Static Read Control: Auto
DRAM Read Training: Auto
MEM. OC Charger: Auto
Ai Clock Twister: Auto
Ai Transaction Booster: Manual
Common Performance Level: 9
Pull-in of CHA PH1: Auto
Pull-in of CHA PH2: Auto
Pull-in of CHA PH3: Auto
Pull-in of CHA PH4: Auto
Pull-in of CHA PH5: Auto
Pull-in of CHB PH1: Auto
Pull-in of CHB PH2: Auto
Pull-in of CHB PH3: Auto
Pull-in of CHB PH4: Auto
Pull-in of CHB PH5: Auto
PCIE Frequency: 101
CPU Voltage: 1.365
CPU PLL Voltage: Auto (it is about 1.55 in Hardware monitor, I don't know what is this PLL for)
FSB Termination Voltage: 1.325
DRAM Voltage: 2.19
North Bridge Voltage: 1.50
South Bridge 1.5 Voltage: 1.50
South Bridge 1.1 Voltage: 1.10
CPU GTL Reference (0): Auto
CPU GTL Reference (1): Auto
CPU GTL Reference (2): Auto
CPU GTL Reference (3): Auto
NB GTL Reference: Auto
DDR2 ChA Reference Voltage: Auto
DDR2 ChB Reference Voltage: Auto
North Bridge DDR Reference: Auto
CPU Configuration:
Ratio CMOS Setting: 7.5
C1E Support: Disabled
Max CPUID Value Limit: Disabled
Intel Virtualization Tech: Enabled
Execute Disable Bit: Disabled
Load-Line Calibration: Enabled
CPU Spread Spectrum: Disabled
PCIE Spread Spectrum: Disabled
Auto settings often give components way more voltage than they need; it's best to set them manually. Even on older boards you had to set more than just vcore: vMCH/NB voltage, VTT/FSB Termination voltage and vDIMM/memory voltage were very important to set manually.
well ive had it with asus.i got my rma back for the second time,and this board is warped worse than the previous two.it was sent in an inside out, P5Q3 box.most likely used and repaired,or someone else replacement. this is total BS. im going to call them just to give them exactly what i think of this company right now.total crap
Here is alittle info for you.
Your going to have to argue this point with a supervisor not a phone drone, so insist on a supervisor or your wasting your time.
Asus has a policy called "Non-Repair Grounds" if you send a board in with any of these issues they can refuse to repair it, guess what one of the non repair items are???
Thats right "Board Deformed" so using there own policy ask them how on gods green earth can they send you something that they can refuse to repair themselves. If they can refuse it so can you. Also refuse to send it to the Indiana facility, Send it to Fremont California, that is a much better facility.
http://support.asus.com/service/serv...e=EN-US&no=213
I wish you luck:up:
Any ideas what may be causing this? Any body did see something like this on his machine>? Please do not tell me I am alone with this crap :shocked:.
Also starting from 1802 I got this really annoying 'PLEASE HIT ESCAPE' during boot and counting down seconds till automated boot. Where can I turn it off I can not find option in BIOS.
Thanks
Not entirely sure. Just rebooted the PC Saturday night, standard procedure...and it never POSTed again. Vcore was 1.425 since day 1, never saw temps over 55c (when priming) on water. Thought it was the mobo at first, but turned out to be the CPU. It never acted odd or showed any signs of degradation prior to this. I didn't think it'd last forever at that voltage, but I figured the "death" would atleast be more exciting.
So, I'm now using an e8400 out of my HMPC until I decide on i7 or C2Q, but currently this E8400 or mobo...are clocking pretty craptacular at the moment (see post 2372). Somewhat noticeable difference from 4.5GHz back down to 3.8GHz =/
But I'll fiddle with it more tonight.
Seban i had once on vista when i had my VGA OC'd, this was happening on my P5K deluxe, so i came to a solution puting PCIE = 103+, later i added 2x2sticks of RAM and if using 1,25NB same problem, then upped to 1,4 and problem gone...But it was some bandwith problem or bottleneck somewhere, with the MF2 this problems are gone and my VGA OC it's impressive on lower volts also...
I will try to find out what's causing that on BIOS 1802 wich is i'm runing
Cheers
Sergio
@grnfinger,thanks again for your help and advice i'm going to try getting ahold of someone in charge. hopefully they can help.
Dude, you said "someone in charge"........:rofl::rofl::rofl:
Good luck with THAT.....:up:
im starting to like this board but the NB gets REAL HOT!
and raid is a tad messed up
I just picked one up on a 'too good to pass' deal. still trying to decide whether to keep it or resell. Phil, is that the quad I sent you? I always knew that chip had potential if it was in something other than that crap ds3l I was crunching it in :D
Chipset --> http://downloadcenter.intel.com/Prod...?ProductID=816
Matrix Storage Manager --> http://downloadcenter.intel.com/Prod...ProductID=2101
Hello guys,
I'm currently tweaking my GTL reference voltages to try and get 8,5 x 475 stable with my q9550 C1. Core 0 and Core 1 are rocksolid at the moment, and Core 2 and 3 crashed instantly before I started tweaking, and now can run roughly 10 minutes of prime95 small FFTs using 1,4vCore, 1,38VTT and 1,34 NB. These are nowhere near the lowest possible to get this stable, but I'm overvolting a bit to rule out voltage problems. Now sometimes when I'm tweaking GTL reference voltages, cores I did not expect to be affected by not tinkering with their GTL reference voltages, become totally unstable (3 instant crashed in a row with prime95 small FFTs, which could run 10 minutes+ before just fine). This makes me believe I don't have the right idea of which reference voltages are used for which cores. I've seen 4 different versions:
GTL0: Core 0,1 Data Bus
GTL1: Core 2,3 Data Bus
GTL2: Core 0,1 Address Bus
GTL3: Core 2,3 Address Bus
GTL0: Core 0,2 Data Bus
GTL1: Core 1,3 Data Bus
GTL2: Core 0,2 Address Bus
GTL3: Core 1,3 Address Bus
GTL0: Core 0,1 Data Bus
GTL1: Core 2,3 Address Bus
GTL2: Core 0,1 Data Bus
GTL3: Core 2,3 Address Bus
GTL0: Core 0,2 Data Bus
GTL1: Core 1,3 Address Bus
GTL2: Core 0,2 Data Bus
GTL3: Core 1,3 Address Bus
So which one is the real explanation on what the GTL reference voltages do for quad core CPUs on the Maximus II formula? This is very important to know, since sometimes it just feels I'm changing those settings completely in the dark, without knowing what core's stability the changes are going to affect. I would be very grateful, and I think many more people will be, if someone could tell which is the correct version.
Musho