ASUS P5K Deluxe - Intel P35 Bearlake + E6600 B1 / Q6600 B3

[ChaosMinionX]

Thanks for all those test shots EVA, they are very helpfull to see the differences in settings. I wonder when the beta bios 403 will be out?

Hopefully soon.

[Truckchase!]

Has anyone noticed that with the 0311 BIOS this board doesn't seem to set Write to Precharge or tWTR correctly when manually specifying memory timings? In my case full AUTO timings result in:

Write to Precharge = 14
tWTR = 11

When timings set to MANUAL in BIOS and tWTR set to 11, (no option to set Write to Pre) I get the following:

Write to Precharge = 22
tWTR = 19

[msgclb]

I was using these BIOS voltages:

CPU Voltage: 1.350v
CPU Voltage Reference: x0.63
CPU Voltage Damper: Enabled
CPU PLL Voltage: 1.50v
DRAM Voltage: 2.30v
FSB Termination Voltage: 1.40v
North Bridge Voltage: 1.55v
North Bridge Voltage Reference: Auto
South Bridge Voltage: 1.20v

And these settings:

• 2.30v = x7 499FSB DDR2-998 5-4-4-9 2-25-2-2-2 = Failed on Test #6 pass 5 & 8

This would have passed the usual Memtest86+ v1.70 2 full passes + 10 loops of Test #5 but I went to bed leaving it running the full tests. When I got back it had run over 20 passes with the above 2 failures. Being not sure what to adjust I made the following changes.

• 2.35v = x7 499FSB DDR2-998 5-4-4-9 2-25-2-2-3 = Passed the 2 full passes + 10 loops of Test #5

The question is what should I have done?

Also is there a link to what would be the most likely cause of each failure?

[xgman]

When I used cpu voltage damper and ref .63 with high cpu voltage, I got a stop at postw ith some sort of cpu error. I left re on auto and damper disabled. Maybe it was because I'm on phase and have to set core at 1.65 to get 1.6 actual. Anyway, I'm not entirely sure which one of those items or both that threw the error.

[Eagleclaw]

Is anyone getting goofy CPU Temp readings with ASUS probe and Speedfan?

I was just up and testing at 3.2ghz and core temp is reading 47 on both cores and speed fan and PC probe were both around 52c, then the alarm goes off and PC probe and speed fan say 85c! But core temp .94 was still reading 47c

After a reboot is seems fine, very strange

[mrcape]

Is anyone getting goofy CPU Temp readings with ASUS probe and Speedfan?

I was just up and testing at 3.2ghz and core temp is reading 47 on both cores and speed fan and PC probe were both around 52c, then the alarm goes off and PC probe and speed fan say 85c! But core temp .94 was still reading 47c

After a reboot is seems fine, very strange

Yes, I got same thing.

[Eagleclaw]

Thanks for the quick reply I appreciate it. I was trusting on what coretemp says more than anything.

Yes, I got same thing.

[Ace-a-Rue]

not bad at all how's everest bandwidth look ?

here is everest on the IP35 at 500 FSB and memory at 500 Mhz with 5-7-7-2-30.

EDIT:..this everest was using my Teamgroup ddr2-1000...the 1st sandra showing 85xx bench score was using Corsair DDR2-1142 stuff...unfortunately for me, one stick bailed out on me yesterday evening...the team group sticks are not as fast as the corsair stuff...the team group scores in sandra memory bench about 200 points lower, at the same clock speed, than the Corsair stuff...could be the EPP, or does that only apply to the Nvidia chipset?

[Alastor2262]

Is anyone getting goofy CPU Temp readings with ASUS probe and Speedfan?

I was just up and testing at 3.2ghz and core temp is reading 47 on both cores and speed fan and PC probe were both around 52c, then the alarm goes off and PC probe and speed fan say 85c! But core temp .94 was still reading 47c

After a reboot is seems fine, very strange

seems that it happens to me when i disabled CPU configuration > PECI settings.

[eva2000]

Thanks for all those test shots EVA, they are very helpfull to see the differences in settings. I wonder when the beta bios 403 will be out?

yeah i'm looking forward to the new bios to squeeze out every ounce of bandwidth / performance i can muster

Has anyone noticed that with the 0311 BIOS this board doesn't seem to set Write to Precharge or tWTR correctly when manually specifying memory timings? In my case full AUTO timings result in:

Write to Precharge = 14
tWTR = 11

When timings set to MANUAL in BIOS and tWTR set to 11, (no option to set Write to Pre) I get the following:

Write to Precharge = 22
tWTR = 19

how you comparing it ? to memset 3.3 beta ? i don't think memset 3.3 beta is reading them correctly sometimes.. what does everest bandwidth/pi or memory intensive benchmarks say when you compare manually set via AUTO for those 2 configs ?

I was using these BIOS voltages:


And these settings:

This would have passed the usual Memtest86+ v1.70 2 full passes + 10 loops of Test #5 but I went to bed leaving it running the full tests. When I got back it had run over 20 passes with the above 2 failures. Being not sure what to adjust I made the following changes.


The question is what should I have done?

Also is there a link to what would be the most likely cause of each failure?

that short procedue test i did isn't no way extensive enough to show memory stability IN memtest just a quick test... usage guide at http://i4memory.com/showthread.php?t=6 for DDR1 still applies to DDR2

When I used cpu voltage damper and ref .63 with high cpu voltage, I got a stop at postw ith some sort of cpu error. I left re on auto and damper disabled. Maybe it was because I'm on phase and have to set core at 1.65 to get 1.6 actual. Anyway, I'm not entirely sure which one of those items or both that threw the error.

you hit the cpu overvoltage error which occurs at vcore > 1.60v with damper enabled you're probably >1.60v vcore with damper disabled you probably <1.60v. Have you tried setting vcore in monitoring to Ignored

here is everest on the IP35 at 500 FSB and memory at 500 Mhz with 5-7-7-2-30.

EDIT:..this everest was using my Teamgroup ddr2-1000...the 1st sandra showing 85xx bench score was using Corsair DDR2-1142 stuff...unfortunately for me, one stick bailed out on me yesterday evening...the team group sticks are not as fast as the corsair stuff...the team group scores in sandra memory bench about 200 points lower, at the same clock speed, than the Corsair stuff...could be the EPP, or does that only apply to the Nvidia chipset?

maybe slower due to 5-7-7-2-30 timings ??

seems that it happens to me when i disabled CPU configuration > PECI settings.

yeah for some core2 cpus which support PECI (not all do), when enabled asus pc probe2/ai suite and bios reported cpu temps might be ~10C lower than what it would be if PECI is disabled or not supported by a core2 cpu.

[Ace-a-Rue]

here is everest on the IP35 at 500 FSB and memory at 500 Mhz with 5-7-7-2-30.

EDIT:..this everest was using my Teamgroup ddr2-1000...the 1st sandra showing 85xx bench score was using Corsair DDR2-1142 stuff...unfortunately for me, one stick bailed out on me yesterday evening...the team group sticks are not as fast as the corsair stuff...the team group scores in sandra memory bench about 200 points lower, at the same clock speed, than the Corsair stuff...could be the EPP, or does that only apply to the Nvidia chipset?

maybe slower due to 5-7-7-2-30 timings ??

i checked with the same memory settings and as you can see, it is falling short by 200 points...hmmmm...i guess corsair is better, at least with their DDR2-1142 stuff.

bottom sandra memory bench is the corsair DDR2-1142 at 495 memory speed and 5-5-5-18-42.

[eva2000]

sub timings used ? AUTO or manually set ? AUTO could be different for the different memories due to SPD programming

[Ace-a-Rue]

i manually set them in the bios...but...doesn't cpuz and memset report them accurately?

[msgclb]

This could be the best that I'll get with my E6600 and OCZ PC2-9200 Flex XLC memory. I'll see if it will stand up to some stress tomorrow.



CPU Voltage: 1.45v
CPU Voltage Reference: Auto
CPU Voltage Damper: Enabled
CPU PLL Voltage: 1.50v
DRAM Voltage: 2.30v
FSB Termination Voltage: 1.30v
North Bridge Voltage: 1.55v
North Bridge Voltage Reference: Auto
South Bridge Voltage: 1.20v

• 435FSB 1044DDR 5:6 4-4-4-12 3-30-3-3-6 passed Memtest86+ v1.70 2 full loops + 10 loops of Test #5 but Windows crashed while loading.

[Truckchase!]

how you comparing it ? to memset 3.3 beta ? i don't think memset 3.3 beta is reading them correctly sometimes.. what does everest bandwidth/pi or memory intensive benchmarks say when you compare manually set via AUTO for those 2 configs ?

Good find. I think you may be right.... I can see no appreciable difference setting those timings using memset and testing using everest. (in both latency and bandwidth)

[eva2000]

i manually set them in the bios...but...doesn't cpuz and memset report them accurately?

Good find. I think you may be right.... I can see no appreciable difference setting those timings using memset and testing using everest. (in both latency and bandwidth)

heh quoting Truckchase! answers Ace-a-Rue's query

E6700 @6x499FSB vs 6x500FSB
Strap change tests



Further strap tests @499FSB vs @500FSB, but this time I'm using E6700 L629B079 B2 retail cpu and dropped cpu multiplier down to 6x so it would be easier for folks to compare with their own tests. I'm running 2x1 GB Crucial Ballistix PC2-8500 @500Mhz 4-4-4-5 2-25-2-2-5 at 2.15v for all tests.

I'm testing 4 configurations:

• 6x499FSB 1:1 boot
• 6x499FSB 1:1 boot setFSB 500FSB
• 6x500FSB 1:1 boot
• 6x500FSB 1:1 boot with Transaction Booster Enabled Level 1

Benchmarks used:

• Everest Ultimate v4.00.1033 beta
• Super Pi v1.50 2M & 8M
• Winrar v3.70 Benchmark
• PCmark05 Memory Test

System

• Intel Core 2 Duo E6700 L629B079 B2
• Corsair Nautilus 500 3/8" ID
• Asus P5K Deluxe 0311 bios
• 128MB Gainward FX5200 PCI
• 2x1GB Crucial PC2-8500 Ballistix dual channel kit in black dimm slots
• 74GB WD Raptor 8MB on SATA 2 port
• Pioneer DVR-08 Burner
• Sony FDD
• 1KW PCP&C SLI psu
• WinXP Pro SP2

6x499FSB vs 6x500FSB

To save everyone from scrolling wheel mouse cramps, here's all the results in one bar chart



Settings Used:

JumperFree Configuration Settings
AI Overclocking: Manual
CPU Ratio Control: Manual
- Ratio CMOS Setting: 6
FSB Frequency: 499 or 500
PCI-E Frequency: 100
DRAM Frequency: DDR2-998 or DDR2-1000
DRAM Command Rate: 2T
DRAM Timing Control: Manual
CAS# Latency: 4
RAS# to CAS# Delay: 4
RAS# Precharge: 4
RAS# Activate to Precharge: 5
TWR: 2
TRFC: 25
TWTR: 2
TRRD: 2
TRTP: 5
DRAM Static Read Control: AUTO

Transaction Booster: AUTO or Enabled
Boost Level: N/A or Level 1
Clock Over-Charging Mode: AUTO

CPU Spread Spectrum: Disabled
PCIE Spread Spectrum: Disabled

CPU Voltage: 1.325v
CPU Voltage Reference: AUTO
CPU Voltage Damper: Enabled
CPU PLL Voltage: 1.50
DRAM Voltage: 2.15
FSB Termination Voltage: 1.40
North Bridge Voltage: 1.55
North Bridge Voltage Reference: AUTO
South Bridge Voltage: 1.20

Advance CPU Settings
CPU Ratio Control: Manual
- Ratio CMOS Setting: 6
C1E Suppport: Disabled
Max CPUID Value Limit: Disabled
Vanderpool Technology: Disabled
CPU TM Function: Disabled
Execute Disable Bit: Disabled
PECI: Enabled

USB Configuration
USB Functions: Enabled
Legacy USB Support: Disabled (need to enable it to detect USB flash drives)

[msgclb]

To save everyone from scrolling wheel mouse cramps, here's all the results in one bar chart

I like those scrolling wheel mouse cramps! Besides I need the exercise.

[Speederlander]

Does playing with the memory sub-timings give any real performance gain?

[rastaseb]

did someone notice that C2D needs more volts at same frequency on P35 boards?
for me :
Xeon 3060 L631B115 at 3.6 (1.33 vcore) on P5B deluxe and P5W64 WS pro,
the same one needs 1.38 to be rock solid on the P5K....rofl!!!!!

[msgclb]

Does playing with the memory sub-timings give any real performance gain?

From my point of view I'd say not by much but it probably depends on your choice of memory, cpu & motherboard. I'd bet that eva2000 can give the definitive answer.

To satisfy my curiosity to the this question I performed a few tests and came up with more questions than answers. I started by using the following BIOS options to find out what the BIOS sets when Auto is used.

AI Overclocking: Auto
CPU Ratio Control: Auto
DRAM Frequency: DDR2-1067
DRAM Command Rate: 2T
DRAM Timing Control: Auto

The first set of timings below are what I deciphered from MemSet 3.3beta for the Auto options. I couldn't figure out what TWR was so I used 6. Are these the timings that the BIOS actually uses with these Auto option?

The next set of timings are what I set to obtain my default performance. Notice that MemSet 3.3beta shows 19 for TWTR with I set 11.

The third set of timings are what I set for my tighter sub-timings. This time MemSet 3.3beta shows 10 for TWTR although I set 2.

So why the discrepancies and any idea why TWR wasn't included in MemSet 3.3beta?

------ 5-5-5-18 (6)-42-11-3-3 ------| ----- 5-5-5-18 6-42-11-3-3 ----- | ----- 5-5-5-9 2-25-2-2 -----


My default Everest and SuperPI benchmark results.


My Everst and SuperPI benchmark results with tighter timings.

• Benchmarks --------- Default --- Tighter Sub-Timings
• ---------------------------------------------------
• Everst Read: ------- 7035 MB/s --- 7060 MB/s
• Everest Write: ----- 4893 MB/s --- 4893 MB/s
• Everest Copy: ----- 5498 MB/s --- 5574 MB/s
• Everest Latency: ----- 74.0 ns ------ 73.6 ns
• SuperPI 32M: --- 20m 30.265s -- 20m 16.406s

So, would I obtain better results if I had a Q6600 or faster CPU?

[CedricFP]

Is there any solution to the crackling problem yet, besides buying a stand alone sound card? It seems to happen when the PC is stressed when overclocked.

[M-XXXX]

I need to know how many cm is betwen NB holes?

[dekruyter]

did someone notice that C2D needs more volts at same frequency on P35 boards?
for me :
Xeon 3060 L631B115 at 3.6 (1.33 vcore) on P5B deluxe and P5W64 WS pro,
the same one needs 1.38 to be rock solid on the P5K....rofl!!!!!

Not here; 1.35 volts for E6600 on the Giga or the P5K.

[dekruyter]

Is there any solution to the crackling problem yet, besides buying a stand alone sound card? It seems to happen when the PC is stressed when overclocked.

I uninstalled Asus audio drivers, and am using Vista x64 HD audio drivers; sournds great.

But, really never had crackling on Asus drivers though.

You could try the native Vista or XP(/) audio drivers.

M

[CedricFP]

I uninstalled Asus audio drivers, and am using Vista x64 HD audio drivers; sournds great.

But, really never had crackling on Asus drivers though.

You could try the native Vista or XP(/) audio drivers.

M

Might try that, but I'm not sure if there are native XP drivers for the onboard.