I am on a ud4; make sure you enable llc in bios; that helps my vdroop to drop from 1.40 to 1.38-1.39 underload...I run at 4.8 with no issues on the ud4. UD5 and UD7 have more levels of llc; so if you are taking your ud3 back when you get the revised chipset after the recall; see if you can up to a ud5 or so; that will help with the oc stability as the bios has more options for llc. I only have on or off settings for llc on my ud4:(

My ud 3 only has on and off too but even with that enabled I had to set a vcore of 1.38 to achieve an 4.5ghz oc with CPUz reporting the actual voltage under load to the CPU as 1.308 so the ud 3 has major vdroop. I hope that future bios updates fix this as I wont be overclocking until then.

You could always give more v core so the load vcore is higher, but still lower than idle? That is what I had to do on my ud4...1.40 idle 1.38-.39 load; temps are 20-55 max, so not an issue....I hope!

You could always give more v core so the load vcore is higher, but still lower than idle? That is what I had to do on my ud4...1.40 idle 1.38-.39 load; temps are 20-55 max, so not an issue....I hope!

But is my vdroop normal because I need to put 1.38 vcore to get a 4.5 ghz overclock and under load the vcore drops all the way to 1.308 so I don't want to have a 1.38 vcore at idle for a 4.5 ghz overclock. Also, why is my vdroop so big? I read others with ud3 have huge vdroop but why. And do you think it can get better with a bios update or am I just stuck with this vdroop until I switch mobos.

But is my vdroop normal because I need to put 1.38 vcore to get a 4.5 ghz overclock and under load the vcore drops all the way to 1.308 so I don't want to have a 1.38 vcore at idle for a 4.5 ghz overclock. Also, why is my vdroop so big? I read others with ud3 have huge vdroop but why. And do you think it can get better with a bios update or am I just stuck with this vdroop until I switch mobos.

Some chips require more voltage to get up there...that is a big vdroop; if you play FSX mostly the cpu will be at !00% so the vcore will be lower then idle....I would say get a higher rated mobo when you do the recall; maybe a ud5 as they have better llc options. As your cpu needs lots of juice that may be the best idea as we all have to dismantle these things and get the updated chipset... I have neverendless cold boot issues on my ud4; that have made me use a non pll offical bios so now I am at 4.5; 4.8 is and was stable as heck once the thing boots!

Some chips require more voltage to get up there...that is a big vdroop; if you play FSX mostly the cpu will be at !00% so the vcore will be lower then idle....I would say get a higher rated mobo when you do the recall; maybe a ud5 as they have better llc options. As your cpu needs lots of juice that may be the best idea as we all have to dismantle these things and get the updated chipset... I have neverendless cold boot issues on my ud4; that have made me use a non pll offical bios so now I am at 4.5; 4.8 is and was stable as heck once the thing boots!

I think I can the CPU to 4.5 on 1.31 vcore it's this vdroop that's killing me. I just hope gigabyte can fix it in a bios update.

Okay I have found a workaround. For those having the same problem , here's what I did. Instead of setting my own vcore, I set vcore to normal. This gave me access to the dvid. Even with this at zero, I am having virtually no vdroop and have reached 4.5ghz with the vcore at 1.296 under load and very low on idle as I have the dynamic vcore set and I am using all the c states and EIST.