Hello,
The tile says all pretty much but let me try and break it down a bit.
I got a stable OC at 4.6Ghz with 1.351v in bios and 1.36v in CPU-Z.
The vcore never went higher than 1.36v in cpu-z and hwMonitor during any stress test and system was rock solid stable. In bios this was set to Adaptive mode with max vcore manually set to 1.351v. LLC Auto. No XMP.
Today, I updated the bios to the latest version because this update included the manual option for adjusting fclk.
So after the bios update I had to manually re-enter the previous settings. After the system booted, I checked cpu-Z and hwMonitor and was suprised my vcore jumping into 1.4v+. Before the bios update with the same settings the vcore never broke 1.36v. But now after the update it goes over 1.4v.
If I change from Adaptive to Manual mode I could control the peak vcore. But with Adaptive mode I can't seem to control the vcore.
If I keep it at manual mode the vcore doesn't drop down even at idle. Just stays at the fixed number.
Has any one else got this problem after the bios update?
The tile says all pretty much but let me try and break it down a bit.
I got a stable OC at 4.6Ghz with 1.351v in bios and 1.36v in CPU-Z.
The vcore never went higher than 1.36v in cpu-z and hwMonitor during any stress test and system was rock solid stable. In bios this was set to Adaptive mode with max vcore manually set to 1.351v. LLC Auto. No XMP.
Today, I updated the bios to the latest version because this update included the manual option for adjusting fclk.
So after the bios update I had to manually re-enter the previous settings. After the system booted, I checked cpu-Z and hwMonitor and was suprised my vcore jumping into 1.4v+. Before the bios update with the same settings the vcore never broke 1.36v. But now after the update it goes over 1.4v.
If I change from Adaptive to Manual mode I could control the peak vcore. But with Adaptive mode I can't seem to control the vcore.
If I keep it at manual mode the vcore doesn't drop down even at idle. Just stays at the fixed number.
Has any one else got this problem after the bios update?