F5F Stay Refreshed Power Users Overclocking GPU clock speed fluctuations occur.

GPU clock speed fluctuations occur.

GPU clock speed fluctuations occur.

A
aguzz123123
Senior Member
599
06-24-2018, 11:59 PM
#1
I increased the overclock of my RTX 5080 GPU by 500mhz, kept the memory clock steady, and my PC became unstable. After lowering the speeds back to normal, it fluctuates between 2600 and 300-400 before returning to 2600. All connected devices—mouse, keyboard, headphones, two monitors, and microphone—are functioning properly.
A
aguzz123123
06-24-2018, 11:59 PM #1

I increased the overclock of my RTX 5080 GPU by 500mhz, kept the memory clock steady, and my PC became unstable. After lowering the speeds back to normal, it fluctuates between 2600 and 300-400 before returning to 2600. All connected devices—mouse, keyboard, headphones, two monitors, and microphone—are functioning properly.

I
ItzBlazYT
Junior Member
7
06-25-2018, 02:12 PM
#2
Update your post with complete hardware details and operating system specifics. Provide the power supply information including make, model, wattage, age, and condition (original, build, refurbished, used). List all connected peripherals. Specify whether the network connection is wired or wireless.

A quick note on my observations: it seems this build may not handle the overclocking level effectively. The purpose behind the overclocking wasn’t clear—there could be benefits in certain setups, but no official guidance exists. Supporting documentation for such scenarios isn’t available.

Additionally, based on what I see, there are notable drawbacks for this system.

PSU: make, model, wattage, age, condition
Disk drive(s): make, model, capacity, usage level
Network: wired or wireless
I
ItzBlazYT
06-25-2018, 02:12 PM #2

Update your post with complete hardware details and operating system specifics. Provide the power supply information including make, model, wattage, age, and condition (original, build, refurbished, used). List all connected peripherals. Specify whether the network connection is wired or wireless.

A quick note on my observations: it seems this build may not handle the overclocking level effectively. The purpose behind the overclocking wasn’t clear—there could be benefits in certain setups, but no official guidance exists. Supporting documentation for such scenarios isn’t available.

Additionally, based on what I see, there are notable drawbacks for this system.

PSU: make, model, wattage, age, condition
Disk drive(s): make, model, capacity, usage level
Network: wired or wireless

T
theflyingpig23
Junior Member
10
06-25-2018, 05:45 PM
#3
I just updated it.
T
theflyingpig23
06-25-2018, 05:45 PM #3

I just updated it.

O
Owlman9
Junior Member
3
06-26-2018, 01:56 AM
#4
My recommendation is to employ Task Manager, Resource Monitor, and Process Explorer to assess system performance. Use all three tools sequentially but one at a time. Initially, you should monitor without overclocking and continue with regular activities like working or gaming. Keep the tool windows open for continuous observation. Next, increase overclocking and observe any changes or issues during spikes. Take your time, stay systematic, and avoid making several adjustments simultaneously. The goal is to identify a situation where spikes appear under certain conditions or disappear when they don’t. Alternatively, spikes might occur without any specific condition present. The main aim is to determine what triggers those spikes. Pay attention to error messages, warnings, and any data logged in Reliability History/Monitor or Event Viewer during spike events.
O
Owlman9
06-26-2018, 01:56 AM #4

My recommendation is to employ Task Manager, Resource Monitor, and Process Explorer to assess system performance. Use all three tools sequentially but one at a time. Initially, you should monitor without overclocking and continue with regular activities like working or gaming. Keep the tool windows open for continuous observation. Next, increase overclocking and observe any changes or issues during spikes. Take your time, stay systematic, and avoid making several adjustments simultaneously. The goal is to identify a situation where spikes appear under certain conditions or disappear when they don’t. Alternatively, spikes might occur without any specific condition present. The main aim is to determine what triggers those spikes. Pay attention to error messages, warnings, and any data logged in Reliability History/Monitor or Event Viewer during spike events.