F5F Stay Refreshed Hardware Desktop System is unresponsive; performance is deteriorating.

System is unresponsive; performance is deteriorating.

System is unresponsive; performance is deteriorating.

A
169
06-11-2023, 02:12 AM
#1
Occasionally at random times, the system gradually slows down. The video continues playing mostly, but the mouse stops responding. I can access the start menu, yet I can't reach the restart option before it becomes impossible to click. After waiting a few minutes—typically 2 to 4—my OS completely freezes. It doesn’t end with a crash or BSOD; it just slows down steadily. I’m certain it’s not hardware failure, as all parts have been verified over time in separate builds. The build is about two years old. I’ve tried several fixes: reassembling components one by one, swapping parts, installing different GPU drivers, updating BIOS and chipset drivers, running without XMP, and using only 2x8GB RAM with EventViewer at the moment of failure. Results were good—no critical errors. The temperatures stayed normal (GPU 69-73°C, CPU 68-70°C). My next thought is to reinstall the OS, though it would be a hassle. Are there other steps I should try first? Here’s my setup: Windows 10, all up to date as of April 3rd, 2023. Hardware: Gigabyte Aorus Elite X570, Ryzen 7 5800X, Powercolor Red Devil 6900XT, G.Skill DDR4 3600 CL16, 4x8GB RAM, Corsair Hx1000 Platinum PSU, Samsung 970 NVMe 512GB, Intel 660P 1TB NVMe secondary drive, Samsung 850 Pro with 500GB backup drive.
A
ArianaGrandeJr
06-11-2023, 02:12 AM #1

Occasionally at random times, the system gradually slows down. The video continues playing mostly, but the mouse stops responding. I can access the start menu, yet I can't reach the restart option before it becomes impossible to click. After waiting a few minutes—typically 2 to 4—my OS completely freezes. It doesn’t end with a crash or BSOD; it just slows down steadily. I’m certain it’s not hardware failure, as all parts have been verified over time in separate builds. The build is about two years old. I’ve tried several fixes: reassembling components one by one, swapping parts, installing different GPU drivers, updating BIOS and chipset drivers, running without XMP, and using only 2x8GB RAM with EventViewer at the moment of failure. Results were good—no critical errors. The temperatures stayed normal (GPU 69-73°C, CPU 68-70°C). My next thought is to reinstall the OS, though it would be a hassle. Are there other steps I should try first? Here’s my setup: Windows 10, all up to date as of April 3rd, 2023. Hardware: Gigabyte Aorus Elite X570, Ryzen 7 5800X, Powercolor Red Devil 6900XT, G.Skill DDR4 3600 CL16, 4x8GB RAM, Corsair Hx1000 Platinum PSU, Samsung 970 NVMe 512GB, Intel 660P 1TB NVMe secondary drive, Samsung 850 Pro with 500GB backup drive.

D
DeathDark38
Member
211
06-11-2023, 02:12 AM
#2
Check how much memory your system is using, it may be running low and switching to disk storage. The issue could stem from a problem in one of your applications causing memory leaks. Use the task manager, filter by memory consumption, to identify the cause.
D
DeathDark38
06-11-2023, 02:12 AM #2

Check how much memory your system is using, it may be running low and switching to disk storage. The issue could stem from a problem in one of your applications causing memory leaks. Use the task manager, filter by memory consumption, to identify the cause.

C
CurryTiger
Junior Member
49
06-11-2023, 02:12 AM
#3
Thanks! I'll try and have TM open and look for it. RAM usages rarely goes above 60% whenever I've monitored it though. If it is a memory leak, how do I go about it? Just reinstall or?
C
CurryTiger
06-11-2023, 02:12 AM #3

Thanks! I'll try and have TM open and look for it. RAM usages rarely goes above 60% whenever I've monitored it though. If it is a memory leak, how do I go about it? Just reinstall or?

M
Metilwulf
Member
70
06-11-2023, 02:12 AM
#4
TM paused too, ready to track any shifts in RAM consumption. A fresh issue popped up in eventviewer: Dhcp-Client—a connection was blocked for a specific IP address.
M
Metilwulf
06-11-2023, 02:12 AM #4

TM paused too, ready to track any shifts in RAM consumption. A fresh issue popped up in eventviewer: Dhcp-Client—a connection was blocked for a specific IP address.

Y
YkseyHD
Member
59
06-11-2023, 02:12 AM
#5
A memory leak refers to a problem in an app where it consumes increasing amounts of RAM until none remains. You have two choices: notify the developer about the issue or wait for a patch when one is released—avoiding the risk of the operating system freezing. If your device can't reach an IP address, the worst outcome might be inability to connect to the network or internet. It's unclear if EventViewer will assist with a situation where the system appears functional but is gradually slowing down. If RAM usage isn't the problem, a failing drive could be the cause. Consider using tools like CrystalDiskInfo to check each drive’s S.M.A.R.T status; any anomalies should be visible there.
Y
YkseyHD
06-11-2023, 02:12 AM #5

A memory leak refers to a problem in an app where it consumes increasing amounts of RAM until none remains. You have two choices: notify the developer about the issue or wait for a patch when one is released—avoiding the risk of the operating system freezing. If your device can't reach an IP address, the worst outcome might be inability to connect to the network or internet. It's unclear if EventViewer will assist with a situation where the system appears functional but is gradually slowing down. If RAM usage isn't the problem, a failing drive could be the cause. Consider using tools like CrystalDiskInfo to check each drive’s S.M.A.R.T status; any anomalies should be visible there.

T
Torte19
Junior Member
34
06-11-2023, 02:12 AM
#6
Thanks for your patience. Here’s a summary of what you shared:

You’re using CrystalDiskInfo data and WMI commands that all report "OK" for the drives. You’re considering troubleshooting since the OS might be the issue, especially because everything seems fine when booting to a different drive. Someone suggested checking the textdrive instead. You’re open to other options and are planning a fresh install this week, willing to share updates if it helps. Keep learning as you go—OS reinstalls can be tricky, so careful adjustments are wise.
T
Torte19
06-11-2023, 02:12 AM #6

Thanks for your patience. Here’s a summary of what you shared:

You’re using CrystalDiskInfo data and WMI commands that all report "OK" for the drives. You’re considering troubleshooting since the OS might be the issue, especially because everything seems fine when booting to a different drive. Someone suggested checking the textdrive instead. You’re open to other options and are planning a fresh install this week, willing to share updates if it helps. Keep learning as you go—OS reinstalls can be tricky, so careful adjustments are wise.

H
hughesywizard
Member
145
06-11-2023, 02:12 AM
#7
In short... everything is resolved. The new OS installation didn't solve the problem. It turned out the issue was with my PCI-e riser, not that I hadn't verified it during hardware troubleshooting. All components were removed and tested on another PC, which also supports the riser. My BIOS automatically switched to "auto" mode for PCI-e configuration. Although the riser is labeled as a "PCI-e gen4," it only works with gen3. Thanks for your help @Eigenvektor—your patience and clarity made a big difference. The solution was just staying alert to Gigabytes BIOS quirks and oddities...
H
hughesywizard
06-11-2023, 02:12 AM #7

In short... everything is resolved. The new OS installation didn't solve the problem. It turned out the issue was with my PCI-e riser, not that I hadn't verified it during hardware troubleshooting. All components were removed and tested on another PC, which also supports the riser. My BIOS automatically switched to "auto" mode for PCI-e configuration. Although the riser is labeled as a "PCI-e gen4," it only works with gen3. Thanks for your help @Eigenvektor—your patience and clarity made a big difference. The solution was just staying alert to Gigabytes BIOS quirks and oddities...