PDA

View Full Version : P5N32E-SLI + E6300 OC (Newbie needs help)


randy915
12-26-2006, 07:31 PM
Ok this is my first time OCing Conroe so naturally there's a lot of new terminologies and technologies on this new platform. This is my setup:

CPU: Intel E6300, Stepping 6, Rev. B2
RAM: Crucial Ballistix PC2-8000 BL2KIT12864AA1005, 2 x 1GB, 5-5-5-15, 2.2v
Mobo: Asus P5N32E-SLI, Bios 0405, Rev. A2
Video: GeForce 7600 GT
CPU Cooling: Stock fan

While waiting for my XtremeSystems account to be verified I tried OCing following some rough examples from others. Attached are 2 shots of CPU-Z showing 2974.9 MHz and it's stable overnight on Final Fantasy XI benchmark and Prime95 on loop (FFXI because it's a PS2 emulated game so primarily based on CPU and RAM).

I tried going more but at 1700 or more FSB (QDR) the system might not POST or crash during burn in. This is where it gets confusing. Here's what my BIOS settings are:

FSB - Memory Clock Mode: [unlinked]
FSB - Memory Ratio: [auto]
FSB (QDR), MHz: [1700]
MEM (DDR), MHz: [1067]

PCI-E Frequencies (MHz): [100]
SPP<->MCP Ref Clock, MHz: [auto]

CPU Multiplier: [7]

Memory tCL (CAS Latency): [5]
tRCD: [5]
tRP: [5]
tRAS: [5]
Command Per Clock (CMD): [auto]
tRRD, tRC, tWR, tWTR, tREF, tRD, tRFC, Async Latency: [auto]

Any type of spread spectrum: [disabled]

CPU Internal Thermal Control: [disabled]
Limit CPUID MaxVal: [disabled]
Enhanced C1 (C1E): [disabled]
Execute Disable Bit: [enabled]
Virtualization Technology: [disabled]
Enhanced Intel SpeedStep(tm) Tech.: [disabled]
LDT Frequency: [5]

VCore Voltage: [1.40000V]
Memory Voltage: [2.200V]
1.2V HT Voltage: [1.55V]
NB Core Voltage: [auto]
SB Core Voltage: [auto]
CPU VTT Voltage: [auto]
DDRII Controller Ref Voltage: [auto]
DDRII Channel A Ref Voltage: [auto]
DDRII Channel B Ref Voltage: [auto]

SLI Broadcast Aperture: [Disabled]
NVIDIA GPU Ex: [enabled]
LinkBoost: [enabled]

SLI-Ready Memory: [disabled]

Take a look at the VCORE @ 1.40000V. Call me stupid but isn't VCORE being reported by CPU-Z as 1.213V? If you were me what would you try at this point? I know I can go higher with my chip but I have no idea what's going on. Any help would be appreciated.

[XC] hipno650
12-26-2006, 08:00 PM
cpu z won't shoe the real vcore so don't get worried about that. i am interested on how far you can push this thing because i might be getting a e6400 (or6420 when they come out) with this board or the dfi rd600 and i would hope to hit 3.5ghz on either board. but it looks not bad to me for your first core 2 oc.

Lestat
12-26-2006, 08:36 PM
FFXI because it's a PS2 emulated game

im sorry what ?

there isnt any emulation of anything going on in FF XI its a PS2 game converted to the PC using PC platform. and switch down to a lowernd video card you will see just how much video card power it uses. its a video card thus it is primarily a video card stresser. infact last i looked FF XI was actually a rather beefy game graphically

now if the cpu is too far out of whack it will crash the benchmark for sure. but its a graphics test thus relies on your card not your cpu.
unless of course the benchmark has a cpu mode where it tests the cpu only, kinda like 3dmark has a cpu mode where it benches the cpu.

on the flip side you do only have a 7600 so it is infact relying heavily on the cpu. but dont take the game and think its a cpu based game as its not, and its not a Ps2 emulated game.

ok
NB Core Voltage: [auto]

raise that up.. whatever its reading now.. raise it up. so if its reading 1.5 now raise it to 1.6

NVIDIA GPU Ex: [enabled]


disable that, that is only for Quatro video cards.

VCore Voltage: [1.40000V]

this board seriosuly undervolts the cpu. you may have it set to 1.4v in the bios but in reality its only like 1.34 or less. in other words raise the vcore to 1.45 or 1.5. its still only going to be about 1.42. and the board also droops like CRAZY. so take that into account.
install the Asus system monitoring program, the one that shows voltages and temps. this will show you what it really is or close to it.

SPP<->MCP Ref Clock, MHz: [auto]

lock this in at 200mhz. you can go higher but i saw zero performance increase by doing so, but i had the eVGA 680i too. but lock it in at 200.

randy915
12-26-2006, 10:48 PM
raise that up.. whatever its reading now.. raise it up. so if its reading 1.5 now raise it to 1.6

this board seriosuly undervolts the cpu. you may have it set to 1.4v in the bios but in reality its only like 1.34 or less. in other words raise the vcore to 1.45 or 1.5. its still only going to be about 1.42. and the board also droops like CRAZY. so take that into account.
install the Asus system monitoring program, the one that shows voltages and temps. this will show you what it really is or close to it.


Thanks for the info. So I did everything you recommended, I went into the BIOS and adjusted VCORE to 1.4125V but in PC Probe II the VCORE show 1.47V. Which one is the actual voltage? Also, what's CPU VTT which is currently at 1.47V as well.

NB CORE right now on [auto] in BIOS is reported as 1.52V, what's the highest I should bump it to?

Which numbers should I trust? Also once I'm done adjusting, what number should I push up? FSB or the memory clock? Currently at 1700 FSB / 1067 MEM.

Attached is a screenshot of all the PC Probe readings.

Again, thanks for your help.

Lestat
12-27-2006, 05:50 AM
i just realised. do you have the 140 dollar P5N32 or the more expensive 300 or 400 dollar version ?

msgclb
12-27-2006, 11:18 AM
Here's my latest settings:


Intel C2D E6400 | Asus P5N32-E SLI, BIOS 0405 | Crucial Ballistix DDR2 1000 2GB (2 x 1GB)

BIOS settings used

AI Tuning: Manual
Nvidia GPU Ex: Disabled
LinkBoost: Disabled

PCIEX16_1 Frequency (Mhz): 100
PCIEX16_2 Frequency (Mhz): 100
PCIEX16_3 Frequency (Mhz): 100
SPP<->MCP Ref Clock, Mhz: 200.0

FSB - Memory Clock Mode: Unlinked
x FSB - Memory Ratio: Not used
FSB (QDR), Mhz: 1700
Actual FSB (QDR), Mhz: 1700.0
MEM (DDR), Mhz: 1067
Actual MEM (DDR), Mhz: 1062.5

CPU Speed: 3.40GHz

CPU Multiplier: 8

tCL (CAS Latency): 5
tRCD: 5
tRP: 5
tRAS: 15
Command Per Clock (CMD): 2T

tRRD: Auto
tRC: Auto
tWR: Auto
tWTR: Auto
tREF: Auto
tRD: Auto
tRFC: Auto
Async Latency: Auto

Vcore Voltage: 1.47500V
Memory Voltage: 2.200V
1.2v HT Voltage: 1.55V
NB Core Voltage: 1.6V
SB Core Voltage: 1.5V
CPU VTT Voltage: 1.5V
DDRII Controller Ref Voltage: Auto
DDRII Channel A Ref Voltage: Auto
DDRII Channel B Ref Voltage: Auto

CPU Spread Spectrum: Disabled
PCIE Spread Spectrum: Disabled
MCP PCIE Spread Spectrum: Disabled
SATA Spread Spectrum: Disabled
LDT Spread Spectrum: Disabled

CPU Internal Thermal Control: Disabled
Limit CPUID MaxVal: Disabled
Enhanced C1 (C1E): Disabled
Execute Disable Bit: Disabled
Virtualization Technology: Disabled
Enhanced Intel Speedstep Tech: Disabled
LDT Frequency: 5x

Voltages-------------- Monitor --- PC Probe
Vcore Voltage--------: 1.47V ---- 1.46V
Memory Voltage-----: 2.25V ---- 2.24V
1.2V HT Voltage-----: 1.61V ---- 1.62V
NB Voltage-----------: 1.61V ---- 1.62V
SB Voltage-----------: 1.53V ---- 1.54V
CPU VTT Voltage-----: 1.56V ---- 1.57V
DDR2 Term. Voltage-: 1.13V ---- 1.14V
3.3V Voltage---------: 3.23V ---- 3.23V
5V Voltage-----------: 5.02V ---- 5.02V
12V Voltage----------: 11.77V -- 11.78V

The one thing I've noticed is that my Vcore doesn't change whether I raise it or lower it. When I run SP2004 as soon as the second core is active it fails.

With FSB (QDR), MHz set to 1200 SP2004 is stable forever.:D (depends on your definition of forever, mine is 12 hours) So somewhere above 1200 SP2004 goes unstable.

These settings are also stable:

FSB - Memory Clock Mode: Unlinked
FSB (QDR), Mhz: 1067
MEM (DDR), Mhz: 1067

I've never seen my CPU temperature go above 36°C. I noticed that on the Asus forum a lot of P5N32-E SLI owners are complaining that their Vcore won't go higher or lower than 1.38V.

Just as I was going to submit this I noticed that there is a new bios for the P5N32-E SLI.


Version 0602 2006/12/27 update
Description 1.Enhance compatibility with Conroe 1333MHz CPU. 2.Add support to n-Tune Voltage and Fan Speed control. 3.Fix Fan stops error when resume from S3 with nTUNE utility installed. 4.Support new CPUs. Please refer to our website: http://support.asus.com/cpusupport/cpusupport.aspx?SLanguage=en-us
1.Enhance compatibility with Conroe 1333MHz CPU.
2.Add support to n-Tune Voltage and Fan Speed control.
3.Fix Fan stops error when resume from S3 with nTUNE utility installed.
4.Support new CPUs. Please refer to our website: http://support.asus.com/cpusupport/cpusupport.aspx?SLanguage=en-us


I'll give this a try soon but I don't see anything about Vcore!

randy915
12-27-2006, 11:31 AM
i just realised. do you have the 140 dollar P5N32 or the more expensive 300 or 400 dollar version ?

I have the $300 version.

Lestat
12-27-2006, 12:10 PM
cant adjust vcore.
see another fine example of Asus' fine R&D dept doing their job.

randy915
12-27-2006, 10:40 PM
cant adjust vcore.
see another fine example of Asus' fine R&D dept doing their job.

WHAT?! :mad: Right now Im at 3.15GHz, can't go any higher. 1750FSB/1067MEM. Is there any way around this? Are you sure the Vcore's locked?

[XC] gomeler
12-27-2006, 10:50 PM
Jeez if the vcore can't be adjusted then that is a really expensive "OEM" board. Perhaps the memory is causing the system to crash? take it out of the equation by dropping it down to 1:1 or lower and see if that helps.

Cyaneed
12-28-2006, 07:59 AM
WHAT?! :mad: Right now Im at 3.15GHz, can't go any higher. 1750FSB/1067MEM. Is there any way around this? Are you sure the Vcore's locked?
I know the Vcore is not locked on my board. Granted I run 1600/800 on my E6600 but the voltage is 1.5875 for stability. Reads 1.46 in PCProbe so thats one helluva lotta drop or a bad sensor read. I'd suggest RMA if your VCore is locked unless you did get a bargain discount basket price and then its probably an OEM board. Once I get my memory straightened out I'm going to give 2000:1000 a run and see if it boots under 1.6v. :rofl: Hey a guy can dream cant he?

msgclb
12-28-2006, 09:29 AM
After updating the bios to 0602 I can now adjust vcore. I checked vcore from 1.35V to 1.5V. At a vcore of 1.5V the Voltage Monitor shows 1.47V and I'd think I could increase it if I have to. I'm currently running Memtest86+ v1.65 with these settings:

AI Tuning: Manual
Nvidia GPU Ex: Disabled
LinkBoost: Disabled

FSB - Memory Clock Mode: Unlinked
x FSB - Memory Ratio: Not used
FSB (QDR), Mhz: 1700
Actual FSB (QDR), Mhz: 1700.0
MEM (DDR), Mhz: 1067
Actual MEM (DDR), Mhz: 1062.5

CPU Speed: 3.40GHz

CPU Multiplier: 8

I'll soon find out if I can get a stable SP2004 with these settings.

msgclb
12-28-2006, 01:38 PM
My P5N32-E SLI bit the dust!:D

It started when I made some bios adjustments but it wouldn't POST. I finally got it to POST by removing the power plug and moving the CLRTC jumper from 1-2 to 2-3. This got me back into the bios but look at these pics.

BIOS 0405
54249

BIOS 0602
54250

Here's what it should look like.
54251

The pics are hard to see as I haven't figured out how to reduce my pics size to fit the attachment requirements. All of the pics were taken with the 'AI Tuning' set to Manual. The 'FSB - Memory Clock Mode' is missing or messed up. It's RMA time.

I'm not sure I want another P5N32-E SLI and paying the extra $100 for a Striker is questionable.

Edit: Everything seems back to normal although I'm still having other problems.