PDA

View Full Version : What could be causing this? P5N32-E


ewitte
12-11-2006, 08:49 AM
I recently noticed that though my CPU clocks pretty high and remains stable the memory goes to crap anything past about 3.8Ghz or 1690FSB (422). Anything that hits the CPU and doesn't touch the memory much increases in score while memory dependent apps drop. BTW nothing is getting even barely warm to the touch with 120mm fans all over the place.

System Specs
Asus P5N32-E SLI
E6600
2GB Team 667 3-3-3-8

Tried
Vcore - Doesn't matter. Even going from 1.4v to 1.5v with good temps doesn't help.

VTT - I've tried everything between 1.35 and 1.55v and it works about the same.

NB - Tried 1.4v to 1.55v.

Memory - 2.2v same as 2.3v

Memory - Dropped to 600Mhz and same thing happened. CPC doesn't matter.

Everest results at 3.75Ghz, memory 700 3-3-3-10-1T. slightly over 10000MB/s and 46ns on latency test.

Everest results at 3.85Ghz, memory 600-700. Slightly over 8000MB/s with about 76ns latency.

Other thing that happens. I can drop back down to working settings and it remains low until I power off for about 1 hour.

I can get the CPU up and running even 3d apps (2k6, 2k5, etc) over 4Ghz.

Luis_GT
12-12-2006, 06:20 PM
http://www.xtremesystems.org/forums/showthread.php?t=125463

that may help...

ewitte
12-12-2006, 07:30 PM
Let me try 1699 and see if it still exists. I guess I need to figure out what all of the other settings are detecting at so I can manually set those for over 1699.

Luis_GT
12-12-2006, 07:36 PM
good luck... in the mean time I may fry my E6600... 3.92ghz with 1.7v...

ewitte
12-13-2006, 04:18 AM
No go. I set to 1699 and it worked fine. Then I went in and set EVERY SINGLE memory timing. Verified in everest about 45.5ns latency. Then I jumped up to 1750 and went in and the reading came out 65ns again. Maybe whatever they are doing will be given an option in BIOS with a future revision. Probably strap set to 1333.

Lestat
12-13-2006, 05:36 AM
yeah looks like its jumping the 1333 bus and taking a ride.

but also remember that even though it may boot and run tests, ram that your pushing too hard will cause tests to be lower as its erroring out internally but isnt causing windows to error out.
its not often that you see it but it does happen.

Yoxxy
12-13-2006, 07:31 AM
Wow nice advice, I never knew that.

ewitte
12-13-2006, 07:59 AM
I'll have to run memtest before going onto Orthos. Something tells me my current 840Mhz 3-4-3-12-1T isn't stable :D. Maybe back off to 2.2v from 2.3v and find the max stable at 840 1T and drop to 800Mhz. I'm just going to have to live with 1699 unless they put a BIOS out that fixes it.

Lestat
12-13-2006, 09:44 AM
try clockgen for 680i see if it lets you overclock using that past the point where the performance goes bad, but it keeps the performance high.

if it works and your performance is high then you know the 1333 strap is kickin in as the system has to reboot to make the 1333 take effect, i am not aware that the 1333 strap can be turned on on-the-fly. so by using clockgen you bypass that and force it to stay 1066 strap.

ewitte
12-13-2006, 09:52 AM
Is there a clockgen that works with this board? Mine comes up with sliders but says 1800Mhz and moving them doesnt' do anything.