F5F Stay Refreshed Power Users Overclocking Overclock returning to Stock?

Overclock returning to Stock?

Overclock returning to Stock?

D
dsy217
Member
113
07-30-2016, 02:22 AM
#1
6700K
Overclocking Update
Yesterday I adjusted my CPU after realizing I didn’t win the silicon lottery. I applied a 4.5Ghz tweak on the TPU section using Asus Dual Intelligent Processors software. I achieved around 1.280v and could still test lower on Aida 64. However, I was only running the CPU stress test. When I turned off GPU and HDD tests, I had to raise the voltage to 1.310 to successfully stress test for an hour. Everything seems fine so far.

Today I powered on my PC and noticed it’s back to normal speed. What’s going on?
Does the Asus software not retain the settings?
Isn’t it meant to preserve the configuration when starting my computer? Or do I need to manually save the settings in UEFI?
D
dsy217
07-30-2016, 02:22 AM #1

6700K
Overclocking Update
Yesterday I adjusted my CPU after realizing I didn’t win the silicon lottery. I applied a 4.5Ghz tweak on the TPU section using Asus Dual Intelligent Processors software. I achieved around 1.280v and could still test lower on Aida 64. However, I was only running the CPU stress test. When I turned off GPU and HDD tests, I had to raise the voltage to 1.310 to successfully stress test for an hour. Everything seems fine so far.

Today I powered on my PC and noticed it’s back to normal speed. What’s going on?
Does the Asus software not retain the settings?
Isn’t it meant to preserve the configuration when starting my computer? Or do I need to manually save the settings in UEFI?

I
iRaine
Posting Freak
800
07-30-2016, 02:42 AM
#2
Asus is known for such issues. Usually, this means your custom build didn't launch properly. Try reducing the settings.
I
iRaine
07-30-2016, 02:42 AM #2

Asus is known for such issues. Usually, this means your custom build didn't launch properly. Try reducing the settings.

W
WoofyMonster
Member
121
07-31-2016, 12:54 AM
#3
Asus is known for such issues. Usually, this means your custom build didn't start properly. Try using lower settings.
W
WoofyMonster
07-31-2016, 12:54 AM #3

Asus is known for such issues. Usually, this means your custom build didn't start properly. Try using lower settings.

J
johcor
Member
54
08-02-2016, 07:58 AM
#4
1. Ensure UEFI is being utilized.
2. Did you press F10 and save prior to rebooting?
If yes, then the system detected the OC to be too high during a cold boot, and reset it to the standard setting for proper startup.
J
johcor
08-02-2016, 07:58 AM #4

1. Ensure UEFI is being utilized.
2. Did you press F10 and save prior to rebooting?
If yes, then the system detected the OC to be too high during a cold boot, and reset it to the standard setting for proper startup.

2
25daniel
Member
177
08-03-2016, 06:31 PM
#5
I only made minor adjustments to the Asus Software. I tested with Aida64 while using HWMonitor to monitor temperatures. The results were satisfactory, and the computer ran smoothly at 4.5Ghz afterward. If the UEFI believes the system is too overclocked at boot, it reverts to the stock settings? Would changing the values directly in the UEFI and rebooting help?
2
25daniel
08-03-2016, 06:31 PM #5

I only made minor adjustments to the Asus Software. I tested with Aida64 while using HWMonitor to monitor temperatures. The results were satisfactory, and the computer ran smoothly at 4.5Ghz afterward. If the UEFI believes the system is too overclocked at boot, it reverts to the stock settings? Would changing the values directly in the UEFI and rebooting help?

U
UMadCauseImNot
Junior Member
13
08-04-2016, 10:00 PM
#6
If pushing it to the limit causes resets, it's best to ease back on the OC. I've encountered this with an ASUS 2011v3 board that lost its OC settings after more than a few cold starts (the fix came from using an MSI). It's also possible another component is causing the issue. In any case, reducing the OC should be a safe approach.
U
UMadCauseImNot
08-04-2016, 10:00 PM #6

If pushing it to the limit causes resets, it's best to ease back on the OC. I've encountered this with an ASUS 2011v3 board that lost its OC settings after more than a few cold starts (the fix came from using an MSI). It's also possible another component is causing the issue. In any case, reducing the OC should be a safe approach.

E
190
08-08-2016, 09:43 PM
#7
Sure, I'll make sure to try that when I get home. Thanks!
E
Ender_Girl_LAF
08-08-2016, 09:43 PM #7

Sure, I'll make sure to try that when I get home. Thanks!