GA-P31-ES3G Vcore issue

Blacksilex

New member
Hi, everyone :)

I'm terribly in need of help, i hope someone can help me

I have GA-P31-ES3G paired w/ E4500.

I noticed that speedfan & CPU-Z tell me that my Vcore is 1.28V (EIST & C1E disabled) while the fact is it's set to normal in bios (it's supposed to be 1.315V-1.325V right!?)

What frustrates me is that even though i rise the Vcore, speedfan -& CPU-Z keep telling me that the Vcore is 1.28V. i think this is why it failed orthos at 3GHz even when i set the Vcore 1.48V in bios.

Is there someone who uses the same board as i do ?

if so, please tell me what i missed or what setting & bios do u use to get stable OCing.

Any help or info will be greatly appreciated ..

Note: I'm using bios F6
 
i think this is called vdrop, when the voltage is different from the bios and the real readings. i think you should do the pencil mod but it means that your motherboard wont be under warranty. basically you get a pencil ,colour in something (i think its a resistor) and the graphite will allow more electricity to flow through or something. but its also reversible, you just need to clean it up with a bit of alcohol.

btw

go in google and look it up.
 
Thanks 4 d reply j.woody :)

My problem is not d Vdroop, but that d Vcore remains the same (1.28V) even if i set higher Vcore in the bios.

I did checked d web & no much info is found about this mobo.

looks like it's completely my fault thinking that all gigabyte MB is flawless

I wish there r some people in this forum who owns the same MB.

I wonder if i buy E5200, the Vcore adjustment in bios will work somehow....
 
Yup, i did

when i bought it for the first time it was using bios F4, Vcore can't be changed,

then i flashed it to the F6 (latest bios), problem remains

then i flashed it to the F2 (first bios), problem is still there :(

I hope it's because this mobo doesn't like my E4500, so if anyone who has this mobo paired w/ E5200 can inform me that d Vcore works & that it OCs nicely, I'll be very grateful to him/her, & then buy E5200 right away :D
 
I wouldn't worry. As long as it is set in the BIOS and the BIOS reads it as a higher value. You're fine. My Striker is set to 1.4v in the BIOS and reads 1.296v in CPUZ. Do NOT trust CPUZ to be accurate at all.
 
name='°TheMadDutchDude°' said:
I wouldn't worry. As long as it is set in the BIOS and the BIOS reads it as a higher value. You're fine. My Striker is set to 1.4v in the BIOS and reads 1.296v in CPUZ. Do NOT trust CPUZ to be accurate at all.

errr... i think speedfan & CPU-Z tell me the truth

Because my CPU temp after 1 hour of orthos at 1.28V was around 64'C, and when i set Vcore in bios to 1.48V it was also around 64'C after 1 hour of orthos
 
Have you disabled CPU functions in BIOS like EIST and C1E. thes will throttle back your CPU if not disabled
 
name='Blacksilex' said:
errr... i think speedfan & CPU-Z tell me the truth

Because my CPU temp after 1 hour of orthos at 1.28V was around 64'C, and when i set Vcore in bios to 1.48V it was also around 64'C after 1 hour of orthos

Time for a new motherboard then I suppose! :p

Very strange. Is there a newer or BETA version of the BIOS that still provides you with voltage control? It may be that the motherboard doesn't want to play ball for some reason.
 
Well, looks like it's a bios flaw

I found out that other MB from gigabyte (EP35-DS3L) also has the same problem

here is the thread:

overclock.net/intel-motherboards/340935-gigabyte-ep35-ds3l-vcore-issue-read.html

I've sent message to gigabyte about my problem & ask 4 a bios 2 fix d problem

I hope they will reply in a short time and provide me w/ a new bios.
 
Dude, please just use full English rather than cutting it off. It makes it easier to read for all of us.

I don't know if they're going to be able to help you with this. It is a fairly old board and as there is no BIOS out for it that will give you proper control over the volts, they aren't going to make one specially for you.
 
The problem really is that cpu-z gives people the impression that the mobo reading/setting is way off and they call it vdroop.

They even go to the extent of sticking a volt meter on the mobo and trying a reading from there to confirm it for them.

The facts that matter are what the mobo says it's giving the cpu (or ram etc) as it is what the mobo is designed to do. Not what a 3rd party probe says. Things like temps - fair enough, actual volts no.
 
Back
Top