F5F Stay Refreshed Power Users Overclocking I attempted to apply AMD Auto Overclock, but my computer suddenly freezes.

I attempted to apply AMD Auto Overclock, but my computer suddenly freezes.

I attempted to apply AMD Auto Overclock, but my computer suddenly freezes.

Pages (2): Previous 1 2
X
xDonjox
Junior Member
38
01-30-2026, 09:10 AM
#11
By profile do you refer to saved overclocking configurations? These saved profiles aren't removed when resetting CMOS, so you'll need to reapply them. I wouldn't do that unless you've verified the system with fully standard BIOS settings. If it continues to behave poorly under stock BIOS and fresh display drivers also using stock configurations, there may be an issue with the hardware.

Also, make sure your monitor settings are correct. I found my monitor has distinct configurations for FreeSync (standard and Ultra) that might influence GPU performance. Adjusting these settings could be beneficial.
X
xDonjox
01-30-2026, 09:10 AM #11

By profile do you refer to saved overclocking configurations? These saved profiles aren't removed when resetting CMOS, so you'll need to reapply them. I wouldn't do that unless you've verified the system with fully standard BIOS settings. If it continues to behave poorly under stock BIOS and fresh display drivers also using stock configurations, there may be an issue with the hardware.

Also, make sure your monitor settings are correct. I found my monitor has distinct configurations for FreeSync (standard and Ultra) that might influence GPU performance. Adjusting these settings could be beneficial.

B
byDemon14
Junior Member
17
01-30-2026, 09:10 AM
#12
As recommended, avoid using the previous profile. Set your configurations from the beginning. You can reinitialize the BIOS settings now that you've cleared the CMOS. Did you remove the battery during the CMOS clearance? This might explain why the old profile persisted. Once the CMOS is cleared, the previous profile should disappear. If necessary, you can save it to a USB drive for testing. Then reset the defaults or clear CMOS while the battery is off.
B
byDemon14
01-30-2026, 09:10 AM #12

As recommended, avoid using the previous profile. Set your configurations from the beginning. You can reinitialize the BIOS settings now that you've cleared the CMOS. Did you remove the battery during the CMOS clearance? This might explain why the old profile persisted. Once the CMOS is cleared, the previous profile should disappear. If necessary, you can save it to a USB drive for testing. Then reset the defaults or clear CMOS while the battery is off.

F
Fred10244
Posting Freak
937
01-30-2026, 09:10 AM
#13
This approach works temporarily with stock BIOS configurations and display drivers. I attempted to reset the monitor settings, which helped, but the problem reappeared when FreeSync was reactivated. My monitor supports AMD FreeSync Premium Pro, yet no alternative options are visible. I briefly reset it by shorting CMOS pins to return to BIOS defaults. I plan to remove the battery next, though I’m hesitant because my GPU prevents me from doing so easily. It explains why my previous profile remains active. Thanks!
F
Fred10244
01-30-2026, 09:10 AM #13

This approach works temporarily with stock BIOS configurations and display drivers. I attempted to reset the monitor settings, which helped, but the problem reappeared when FreeSync was reactivated. My monitor supports AMD FreeSync Premium Pro, yet no alternative options are visible. I briefly reset it by shorting CMOS pins to return to BIOS defaults. I plan to remove the battery next, though I’m hesitant because my GPU prevents me from doing so easily. It explains why my previous profile remains active. Thanks!

L
lisa2144
Junior Member
13
01-30-2026, 09:10 AM
#14
Clear CMOS and start over.
L
lisa2144
01-30-2026, 09:10 AM #14

Clear CMOS and start over.

H
HugsandTickles
Junior Member
46
01-30-2026, 09:10 AM
#15
Yes, the GPU needs to be taken out. Make sure to lower the tiny retention clip mechanism down before removing it from the IO end, and just lightly move it.
H
HugsandTickles
01-30-2026, 09:10 AM #15

Yes, the GPU needs to be taken out. Make sure to lower the tiny retention clip mechanism down before removing it from the IO end, and just lightly move it.

J
jxzuzuzo
Posting Freak
750
01-30-2026, 09:10 AM
#16
Thanks! I removed the CMOS battery and reset everything, but the problem persists. I thought about my earlier post and realized I might have been vague about what was causing it. My problems with idle games appeared even before I increased the overclock, but then they started affecting other apps like Steam and Discord after the auto-overclock failure. It seems things got much worse afterward, but it’s possible something was still wrong with my GPU before that. Could you suggest some other steps I could try to resolve this? Thanks again!
J
jxzuzuzo
01-30-2026, 09:10 AM #16

Thanks! I removed the CMOS battery and reset everything, but the problem persists. I thought about my earlier post and realized I might have been vague about what was causing it. My problems with idle games appeared even before I increased the overclock, but then they started affecting other apps like Steam and Discord after the auto-overclock failure. It seems things got much worse afterward, but it’s possible something was still wrong with my GPU before that. Could you suggest some other steps I could try to resolve this? Thanks again!

C
chaospony
Member
149
01-30-2026, 09:10 AM
#17
I was using two monitors, and I noticed the problem no longer occurs. Is FreeSync turned off when using two monitors? That would explain why disabling it resolved the issue. It also functions correctly without the second monitor connected. My old monitor is 1920x1080p at 60Hz. It's nice to have a simple solution, but I'm curious about what might be causing this problem.
C
chaospony
01-30-2026, 09:10 AM #17

I was using two monitors, and I noticed the problem no longer occurs. Is FreeSync turned off when using two monitors? That would explain why disabling it resolved the issue. It also functions correctly without the second monitor connected. My old monitor is 1920x1080p at 60Hz. It's nice to have a simple solution, but I'm curious about what might be causing this problem.

A
adamgames2016
Member
133
01-30-2026, 09:10 AM
#18
Which monitor models were used? Were you replicating or adding to what was already present?
A
adamgames2016
01-30-2026, 09:10 AM #18

Which monitor models were used? Were you replicating or adding to what was already present?

R
RJBboy
Junior Member
47
01-30-2026, 09:10 AM
#19
I believe I discovered my second monitor, which is an LG HD TV:
https://www.lg.com/us/tvs/lg-22LF4520-led-tv
It's not certain if it's the exact model, but the size and appearance match mine. My main monitor is a Gigabyte M28U. I was expanding my setup by using both monitors together most of the time; I attempted mirroring to check the effect. Unfortunately, it didn't work well because the resolutions are quite different, though I didn't encounter any problems.
R
RJBboy
01-30-2026, 09:10 AM #19

I believe I discovered my second monitor, which is an LG HD TV:
https://www.lg.com/us/tvs/lg-22LF4520-led-tv
It's not certain if it's the exact model, but the size and appearance match mine. My main monitor is a Gigabyte M28U. I was expanding my setup by using both monitors together most of the time; I attempted mirroring to check the effect. Unfortunately, it didn't work well because the resolutions are quite different, though I didn't encounter any problems.

D
60
01-30-2026, 09:10 AM
#20
I read that turning off deep sleep settings in MorePowerTool might help, so I tried that as I wanted to avoid OCing with MPT. It seems like that actually fixed this issue, so I suppose it's a problem with deep sleep then. Do you think that something is stiill wrong with my hardware though since it started happening recently? Thanks!
D
Doctor_Fallout
01-30-2026, 09:10 AM #20

I read that turning off deep sleep settings in MorePowerTool might help, so I tried that as I wanted to avoid OCing with MPT. It seems like that actually fixed this issue, so I suppose it's a problem with deep sleep then. Do you think that something is stiill wrong with my hardware though since it started happening recently? Thanks!

Pages (2): Previous 1 2