A8N-E, x2 3800+, very wierd vcore problem.

kawsy

Junior Member
Nov 22, 2005
17
0
0
I asked recently in this thread about whether it was safe to run my x2 3800+ past 2500 with a vcore of 1.5 volts. I decided to go back and try some different fsb/multiplier combinations that would work with a lower voltage and discovered that maybe I needed such a high voltage because my vcore reads <=1.4 or >=1.5 regardless of what I choose in the bios. What I found:

Vcore set to ... Vcore(bios monitor)
1.3 ................ 1.28 - 1.29
1.3125 ........... 1.29 - 1.31
1.325 ............. 1.31 - 1.32
1.3375 ........... 1.32 - 1.34
1.35 ............... 1.34 - 1.36
1.3625 ........... 1.36
1.375 ............. 1.37
1.3875 ........... 1.37 - 1.39
1.40 ............... 1.39
1.4125 ........... 1.39 - 1.4
1.425 ............. 1.39
1.4375 ........... 1.37 - 1.4
1.45 ............... 1.39
1.4625 ............ 1.39 - 1.4
1.475 ............. 1.48 - 1.5
1.4875 ............ 1.50 - 1.52
1.5 ................. 1.50 - 1.52
1.5125 ............ 1.52 - 1.53

:Q

I tried this running stock 2GHz and the results were the same. I suppose it could be bad sensors but since the low and high readings are fairly accurate and 1.475 (1.50 monitored) is the first voltage I get any stability with at 2.5GHz and since thats right where the jump occurs, I'm thinking not. I also tried replacing the power supply which was a 420 single rail with a 550 dual rail and its the same. Maybe the board is bad?
 

Hyperlite

Diamond Member
May 25, 2004
5,664
2
76
Motherboards rarely supply the exact voltage specified in the BIOS. On my nf7-s, CPU-Z reports my Vcore as .05 lower than BIOS at times. i would definantly not exceed 1.5v, but what are your temps like?
 

kawsy

Junior Member
Nov 22, 2005
17
0
0
Temperature doesn't exeed 49C with dual prime small fft..

It's not that the voltages don't match that bothers me, it's the big jump in monitored voltage between 1.4625 and 1.474 and how selecting 1.3875-1.4626 gives me the exact same voltage, 1.39.
 

kawsy

Junior Member
Nov 22, 2005
17
0
0
For anyone else who runs into this. The problem seems to have been fixed by updating to the lastest beta bios for my board 1010.03.