"ASUS P5Q Deluxe discussion".

[Mumid]

They should just do away with it all together.

When i get my new CPU i hope a good one and i will then know if my MOBO is screwy or my Q6600 degraded in 2-3 weeks of folding, linpacking, orthosing and whatever else.... to only be able to 3.4ghz with it now linpack stable and not my 3.6ghz in 2-3 weeks THE THING WAS NEW .. so in three weeks of it time at 3.6ghz it now can't do it stable linpack that is and i not know if it can orthos 12 hours as i care not to try.

My new one E8600 dual-core yeah . hope she is good and if i can do 4.0-4.3 that will be nice, but is this MOBO screwing up CPU's and/or degrading them FAST.

Do you think that you might be stressing your mobo and cpu too much running linpack etc all the time when it is brand new? I mean this program puts on abnormal amount of load onto a system. I like to treat my new hardware like a new car lol, give it a bit of time to settle in before pushing it like mad! For me though memtest, orthos and occt is enough.

[BeastNotro]

Do you think that you might be stressing your mobo and cpu too much running linpack etc all the time when it is brand new? I mean this program puts on abnormal amount of load onto a system. I like to treat my new hardware like a new car lol, give it a bit of time to settle in before pushing it like mad! For me though memtest, orthos and occt is enough.

In never ran linpack until about 2 weeks of having the CPU as i never even knew about linpack .. so linpack i only been using maybe 1 week to 1 1/2, but not everyday .... but i did do it for 3-4 days in a row and not 24/7, but )3-6) times 5-10 loops each .... then maybe 3 days later i ran again newer version 1.4 at that time and she failed, so i upped the PPL and NB a little and she passed ... then i tried what a few days or so later 1.5.1 and she failed.. hmm .. i try 1.4 again and she failed....

But of course 3.4ghz SHE pass again with flying colors.

CPU degraded is what i am thinking and it may have taken 1-2 weeks of me testing and FOLDING the crap out of it ... that it did (what would of happened in 3-6 months) in 1-2 weeks is all.. is what i am thinking.

Now as for the E8600 i want to find it MAX ASAP as i hate taking 2 weeks to find out a CPU is a DUD...

Hey 3.4ghz is nothing to be sad about on a Q6600, but i want 4.0 ghz or betetr ... on any CPU right now and it appears the dual-cores are more proned fro thsi to happen.

So Q6600 is SOLD still in my rig until new CPU arrives .. so long Q6600 and one day i will either get another Quad-Core or upgrade to Nehalem, next year is my goal to upgrade to Nehalem ... so i just having fun for now on my rig and CPU's.

[Blasar]

Hi there!!

Here i am again with another doubt.

I´m using Prime95 and MemTest to test the stability of the system. All tests run smoothly, until it reaches to the blend test, where i get an error in the core#2 after a few minutes.
What can it be? vNB? vFSB? vRAM? RAM timings?



Rig specs:

Q6600 (cooled by Tuniq)
P5Q Deluxe
GSKILL PC2-8500 PK F2-8500CL5D-4GBPK
Powercolor HD4870
2x Seagate 250GB@RAID0
Corsair HX620



BIOS settings:

AI Overclock tuner: Manual
CPU Ratio Setting: 8X
FSB Frequency: 425
FSB Strap to North Bridge: 266
PCI-E Frequency: 100
DRAM Frequency: 1066
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

CAS# Latency: 5
DRAM RAS# to CAS# Delay: 5
DRAM RAS# Precharge: 5
DRAM RAS# Activate to Precharge: 15
RAS# to RAS# Delay : AUTO
Row Refresh Cycle Time: AUTO (defaults to 52)
Write Recovery Time: AUTO
Read to Precharge Time: AUTO

DRAM Static Read Control: Disabled
DRAM Read Training: AUTO
MEM. OC Charger: AUTO
AI Clock Twister: Moderate
AI Transaction Booster: 8
PULL-INS: All Disabled

CPU Voltage: 1.29
CPU GTL Voltage Reference (0/2): 0.630
CPU GTL Voltage Reference (1/3): 0.670
CPU PLL Voltage: 1.54
FSB Termination Voltage: 1.36
DRAM Voltage: 2.00
NB Voltage: 1.26
NB GTL Reference: 0.630
SBridge Voltage: 1.10
PCIE SATA Voltage: 1.50

Load Line Calibration: Enabled
CPU Spread Spectrum: Disabled
PCIE Spread Spectrum: Disabled
CPU Clock Skew: AUTO
NB Clock Skew: AUTO
CPU Margin: Optimized

Advance CPU Settings
CPU Ratio Setting: 8
C1E Support: Disabled
Max CPUID Value Limit: Disabled
Intel Virtualization Tech: Disabled
CPU TM Function: Disabled
Execute Disable Bit: Disabled

[Pntgrd]

Blasar, have you tried upping the CPU GTL Voltage Reference (0/2): 0.630 to 0.067. A lot of times raising this setting will help when it is always the same core failing.

[Blasar]

Blasar, have you tried upping the CPU GTL Voltage Reference (0/2): 0.630 to 0.067. A lot of times raising this setting will help when it is always the same core failing.

I´ve tried that and the result was the same, error in core#2 after a few minutes in the blend test

I don´t know what is making this happen, but i´m counting on you guys to help me out

Regards.

[WildstarOCT]

Hi there!!

Here i am again with another doubt.

I´m using Prime95 and MemTest to test the stability of the system. All tests run smoothly, until it reaches to the blend test, where i get an error in the core#2 after a few minutes.
What can it be? vNB? vFSB? vRAM? RAM timings?

More VCore my man, that's what you need. You're too low unless you have a golden Q6600. Try 1.325-1.350.

[truehighroller]

More VCore my man, that's what you need. You're too low unless you have a golden Q6600. Try 1.325-1.350.

Same thing I was thinking.