Originally Posted by ComputerRestore
Well I contacted AMD about an RMA, so I'll see what they say. I could just exchange it through the store I bought it at because it's been less than 2 weeks, but I'd rather follow-up through AMD so maybe they can improve on the design.
My 3rd Module (5 and 6) is unable to Clock over 4.7Ghz with any sort of stability. My lowest voltage at that setting is 1.4 (only 3 Modules active though). So I wonder what module of yours is failing Stoffie?
I think OCN is messing up - keep ending up double quoting myself and my posts when I go to edit lol.
It doesn't explain why my other cores are able to clock higher with stability at the same settings. I even went as far as disabling cores 3 to 6. This left me with cores 1,2,7,8 with a setting of 4.6Ghz and cores 7 and 8 still failed. Yet I can use cores 1,2,3,4 and overclock to 5Ghz Prime stable.
Something you might want to try:
Within Prime95's folder is a file called local.txt. This file basically tell how Prime95 is to be run. The settings you put in there overrides any detected settings.
You can play with these options:
CpuNumHyperthreads=1 or 2
These two work together, it's designed for Intel CPU's with hyperthreading, but it will work the same with AMD. Sample, you can do NumCPUs=4
This tells Prime that it's a four Core CPU with hyperthreading, eight threads in total. This might help with your cores failing, so in essence for your core 7,8: core 7 will be primary thread and core 8 will be helper thread.
In conjunction with the other two I mention, or by itself you can try:
From Prime's undoc.txt : Where the characters in "0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz()"
represent 64 logical CPU numbers. For example, let's say you have a system
with 8 logical cores with 4 workers each using a helper thread. Also, assume
your system has logical CPUs 0 & 4 on the same physical CPU core, 1 & 5, etc.
If the program is properly determining which logical CPUs share the same physical
CPU, then the program internally generates an affinity scramble string of "04152637".
The program's default policy is to assign the worker and helper threads to the same
physical CPU. If the program is not properly determining which logical CPUs share the
same physical CPU, or you think a different affinity policy would result in better
performance, then set AffinityScramble2 accordingly. Let's say you think
running the helper threads on a different physical core would be better, then
you might set AffinityScramble2=02134657 to test out your theory.
By default the Piledriver cores should be:
You can play with these settings to see if matching different cores help. Sample you can match core0 with core3 or core 5 with core 7,
This example would be: AffinityScramble2=03124657