Quote Originally Posted by cstkl1 View Post
lol poke

from ure voltage scaling
u were never stable in the first place

u want stable do this
pass all 3 in Windows Ultimate 64 Sp1

1. Linx with latest linpack lib
101 rounds with min 3500 mb in diagnostic mode
- testing vcore on on/off mode for high and low

2. Prime95 the official release one
min FFT 12, Max FFT 12, 3 hours min 3500mb in diagnostic mode
- testing vcore on stable run

3. Prime95 the latest beta
Use blend custom 3500mb 12 hours min.
- testing everything.
Those were my logs for borderline stability at 4.7 GHz. I knew from the start that most of those settings were not completely stable. Hence why I mentioned that I mentioned that I'd be running the rig at 4.4 GHz.

From my experience, XX hours of stability under XX test for XX hours at XX GHz doesn't really mean anything.
It's only when you get enough data points to analyze voltage scaling and then appropriately calculate a safety margin to back off do you get something that never fails.

The best example of this are these two that I posted in the log:

4.7 GHz: More than 4 hours LinX + prime stable
4.6 GHz: Fails y-cruncher (100b) 8 hours in
Vcore = BIOS: 1.185, offset +0.020
Load vcore: as high as 1.408

Load-Line Calibration = Ultra High
Current Capability = 100%
Frequency = 350KHz
Phase Control = Manual - Fast
Duty Control = T.Probe

================================

4.7 GHz: More than 4 hours LinX + prime stable
4.6 GHz: Run 1 - Passes y-cruncher (100b) in 36 hours
4.6 GHz: Run 2 - Fails y-cruncher (100b) at 30 hours
4.4 GHz: Passes y-cruncher (250b) in 129 hours
Vcore = BIOS: 1.190, offset +0.025
Load vcore: as high as 1.408

Load-Line Calibration = Ultra High
Current Capability = 100%
Frequency = 350KHz
Phase Control = Manual - Fast
Duty Control = T.Probe
Look at that. 4 hours prime and LinX stable (with AVX)...
And yet it manages to fail a different stability test at a lower speed.