• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

*** MSI P6N SLI Platinum OVERCLOCK 650i ***

Page 14 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
I just checked my bios ,def NBv is 1.25 & the SB is 1.5v.
1.5v is the maximium for the NB ,personally I wouldn't run it that high but some people do.I guess it depends how long you plan to keep the mbrd😛

Well you don't need to worry about overclocking your RAM as you won't be ,so you can leave the RAM at def voltage🙂
What was the voltage spec for your old RAM?

I'm just doing a quick test on my Q6600 @3.15GHz ,then latter hopefully @3.3GHz.

Btw I like your sig ,what's it from?
 
Just an update for those running an P6N Platinum with 4GB of RAM in Vista and having X-Fi problems:

Important Driver Update for X-Fi in Vista 64 with 4GB+ system RAM

As I mentioned in a previous post, I had problems with my X-Fi after I installed +2GB for 4GB total with this board in Vista. Board worked fine with just 2GB. As I suspected, there was a problem with the board's ACPI, Vista and X-Fi's drivers and resource/memory allocation.

The X-Fi driver apparently fixes this so that there aren't any initial address conflicts, although that could change if you have excessive peripherals/drivers that require additional physical memory addresses.

This driver fix may or may not resolve PCI bus/SB timing problems however, that are well known and documented for NForce chipsets and the X-Fi resulting in the infamous hissing/cracking/popping problems many have experienced. I do not experience these problems with the new drivers, although I did see them in the past (if I didn't see a BSOD/crash/restart first).

Oh and another friendly reminder to update your BIOS if you plan on running 2GB+ or all 4 dimms populated!
 
This driver fix may or may not resolve PCI bus/SB timing problems however, that are well known and documented for NForce chipsets and the X-Fi resulting in the infamous hissing/cracking/popping problems many have experienced

Not again! ,Nvidia had this problem with the Nfrc2 chipsets! :roll: ,at least on the Asus mbrd anyway ,not sure about others.

Thx for the heads up chizow🙂


FYI ,I couldn't keep my Q6600 stable at 3.15GHz 🙁 ,kept BSOD'ing ,though I am wondering if its some sort of software problem as I wasn't testing it with P95 at the time.
 
My m/b died about a week ago and newegg sent me a replacement. This new one runs MUCH cooler. E6750 o/c to 3.4. NB was bumped up 2 steps as was vcore. core temp reads ~55C under load with prime95. With my first m/b I would be in the mid 60C's
 
My E6750 @ 3.4. vcore and NB are bumped up 2 steps. core temp under no load is ~30C. Under prime 95 it stays around 55C. was prime95 stable over night.
 
Finally got my Q6600 stable at 3.05GHz @1.26v (full load) ,peak CPU temp runnning P95 with small FFTs is 62C ,55C with large FFTs.
A bit dissapointing but it's still fast 🙂, I think my HSF is at its limit & holding it back.
 
I just recently got a ballistix tracer pc 6400 and hope to overclock my e6750 further. I had already reach 3.2ghz under the spec of
1.41vcore +.0625v
1.4NB voltage
all speed spectrum disabled
C1e also disabled
that was with my shitty Kingston PC 6400 ram at 5-5-5-18. Anything over 3.2ghz would be no post for me.
After I swapped the RAM, I can no longer overclock. the same setting I had to reach 3.2 ghz no longer works. I thought it was the ram, so I switched back my Kingston ram and I still can't get to 3.2ghz using the same setting. The computer would not post at all. Currently I'm running at the default 2.66ghz and I'm not happy about it. Is it my motherboard that's holding it back or wut? Any idea?
 
Originally posted by: futurestar99999
I just recently got a ballistix tracer pc 6400 and hope to overclock my e6750 further. I had already reach 3.2ghz under the spec of
1.41vcore +.0625v
1.4NB voltage
all speed spectrum disabled
C1e also disabled
that was with my shitty Kingston PC 6400 ram at 5-5-5-18. Anything over 3.2ghz would be no post for me.
After I swapped the RAM, I can no longer overclock. the same setting I had to reach 3.2 ghz no longer works. I thought it was the ram, so I switched back my Kingston ram and I still can't get to 3.2ghz using the same setting. The computer would not post at all. Currently I'm running at the default 2.66ghz and I'm not happy about it. Is it my motherboard that's holding it back or wut? Any idea?
Click to expand...

Make sure you check your default RAM voltages anytime you swap dimms from different makes. Its a major problem with this chipset and RAM from certain makes. Many times the SPD on dimms don't default to high enough voltages to even POST.

Anytime you swap out dimms its best to revert to failsafe defaults first unless you know for a fact the new dimms need higher voltages than the SPD defaults to. After you swap RAM, check the voltages again to make sure they're running at the mfg. specs; if you're OC'ing the FSB you'll probably need to bump the RAM, NB and CPU voltages as well.

Try bumping the NB to 1.45V if you're trying to run 1600FSB. Personally I haven't had much luck with 650i boards at 1600FSB and some say there's a FSB hole from 1500-1650 or so with these boards.
 
Originally posted by: Assimilator1
This driver fix may or may not resolve PCI bus/SB timing problems however, that are well known and documented for NForce chipsets and the X-Fi resulting in the infamous hissing/cracking/popping problems many have experienced

Not again! ,Nvidia had this problem with the Nfrc2 chipsets! :roll: ,at least on the Asus mbrd anyway ,not sure about others.

Thx for the heads up chizow🙂


FYI ,I couldn't keep my Q6600 stable at 3.15GHz 🙁 ,kept BSOD'ing ,though I am wondering if its some sort of software problem as I wasn't testing it with P95 at the time.
Click to expand...
Sadly, I don't think the SB has changed much, if at all since the NF2 lol. 🙁 Chipsets are definitely the weakest link in terms of progress when you look at the main components in a PC 🙁 That's a nice OC btw considering the low voltage. I'll be looking to upgrade to a Q6600 pretty soon as well. 🙂

Originally posted by: Puffnstuff
I haven't had any problems with my mb and x-fi except for the crappy creative drivers that are few and far between
Click to expand...
Hmmm your sig seems to indicate otherwise. I'm also pretty sure I read a post where you had very similar problems to my own. I only took notice of it because our components were very similar.

I don't think all the blame can be placed on Creative though simply because the problems only arise under certain conditions and configurations. The problems with the X-Fi and NF chipsets are well documented although they don't seem as big a problem as they were with the NF4 chipsets.

For me, the X-Fi ran fine under XP on my P5N-E. Also ran fine with the P6N in Vista with only 2GB. The P6N wouldn't run anything stably and was very sluggish when I added 2GB; updating my BIOS to 1.03 from 1.00 fixed this but broke the X-Fi as a result. Months later, Creative releases a driver that fixes the problem but MS also releases numerous hot fixes that address systems with 4GB+ in that time frame (including some other big problems, like USB devices).

So in the end, there were just problems with resource management (assignment of interrupts or memory addresses etc.) between the board/chipset's ACPI, Vista and Creative's drivers. I'm totally confident the problems could've been fixed with a change to any of those, just as I'm confident a future BIOS or Vista hot fix could break the X-Fi again.
 
hello people. 2nd time poster here. i dont have the time to read through all 17 pages of this thread. im hoping for some quick answers. does anyone know if this mobo has problems with the patriot extreme memory? i made the mistake of buying ram before selecting the mobo i wanted.

im debating between the asus p5n-e sli and this p6n mobo. i've read that the p5n can give me issues with my ram. i have a c2d e6600, 2gb (1gbx2 patriot extreme). thanks for any answers.
 
I use Patriot Extreme Performance Low Latency DDR2 800 with this motherboard and have no problems with it. I've also used regular Patriot memory with it.

You shouldn't have a problem unless you're trying to mix memory types/brands. For example I couldn't use regular Patriot memory with the LL memory at the same time.
 
Originally posted by: Assimilator1
Finally got my Q6600 stable at 3.05GHz @1.26v (full load) ,peak CPU temp runnning P95 with small FFTs is 62C ,55C with large FFTs.
A bit dissapointing but it's still fast 🙂, I think my HSF is at its limit & holding it back.
Click to expand...

I spoke to soon😛
Within hours of running Folding@Home it ended the work unit early citing 'Simulation instability has been encountered' ,that happened 2 more times so it was no coincedence.
Dropping the speed to 3GHz & raising vcore to 1.3v (loaded ,=+0.0625) finally got it stable allowing F@H to run properly.I'm amazed by how much more testing F@H is compared to Prime95!:Q

futurestar99999
Did you have your FSB VTT bumped up previously?

chizow
I'm looking at buying a new HSF as I'm not happy with 'only' 3GHz @1.3v 😉 (running F@H CPU temps peak at about 62C).

 
i've running my e7650 @ 3.4 for about a week without a crash now. had to up vcore and nb by 3 steps. it's been fairly cold so i can't really judge how hot things are running fairly.
 
assimilator1
yes, I had it at 4%, don't think it makes a difference. Now I have it at 0, and I can't overclock with this new ballistix and I will RMA to get a replacement.

Sefu
what are your specs from CPU-Z, ur vcore, NB voltage and all that. When I had my e6750 at 3.2ghz, I had to bump the vcore all the way to 1.42 and NB at 1.4. and Nothing posted after 1600FSB.
 
NB at 1.275 vcore +0.25 - bios

vcore shows 1.072v - cpuz no load

vcore shows 1.280v - cpuz w/ prime 95 after 1 min on small eft test

i can go up to 3.8, but i'm just keeping it at its current setting.

try going up to 1700. mine wouldn't post between 1550-1675 (somewhere in there, those are just guestimates.
 
3.8GHz!?:Q wow!😎

btw re lower vcore with no load that's because you still have a power saving feature on ,possibly C1E?

What speed are you running at now?
 
u konw what's wierd is i have it all turned off, but cpu-z still says that my processor is flipping between x6 and x8 multiplier so I dunno.

I'm at 1700 mhz bus, 3.4 ghz
 
Did you press alt+f4 in the 'cpu features' to bring up C1E?

Btw ,great cpu & mbrd you've got there!😎 high speed & low vcore🙂
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top