F5F Stay Refreshed Hardware Desktop Unusual inactivity from the Ryzen 3 paired with TeamViewer

Unusual inactivity from the Ryzen 3 paired with TeamViewer

Unusual inactivity from the Ryzen 3 paired with TeamViewer

Pages (2): Previous 1 2
C
CyberPhoenix
Member
167
02-25-2016, 10:58 AM
#11
I haven't stopped to review what I shared either. Alright, let's check if someone else is ready to assist.
C
CyberPhoenix
02-25-2016, 10:58 AM #11

I haven't stopped to review what I shared either. Alright, let's check if someone else is ready to assist.

A
ajaceave
Junior Member
8
02-26-2016, 07:06 AM
#12
You're right, it seems like everyone agrees with the usual view.
A
ajaceave
02-26-2016, 07:06 AM #12

You're right, it seems like everyone agrees with the usual view.

G
Gelox_
Junior Member
5
03-04-2016, 11:00 AM
#13
I just set up an account to discuss this topic again since I found their approach too rigid. Many people still ignore that background processes can consume CPU even when idle. Pachodom’s issue lies in the fact that Cool and throttling doesn’t seem to help when Teamviewer isn’t running. When Teamviewer is active, activity usually increases, yet it appears to decrease here. It’s hard to pinpoint the exact cause, but it might be resolved by adjusting Teamviewer’s power settings. Check your default Windows power plan—especially if it switches to Performance mode after the app closes, meaning you’re always running at full speed. In my case, Teamviewer idle was using excessive CPU for its simple background tasks compared to other remote tools. I stopped using it because of that performance problem. It once was the best option, but they’ve been making similar errors for years.
G
Gelox_
03-04-2016, 11:00 AM #13

I just set up an account to discuss this topic again since I found their approach too rigid. Many people still ignore that background processes can consume CPU even when idle. Pachodom’s issue lies in the fact that Cool and throttling doesn’t seem to help when Teamviewer isn’t running. When Teamviewer is active, activity usually increases, yet it appears to decrease here. It’s hard to pinpoint the exact cause, but it might be resolved by adjusting Teamviewer’s power settings. Check your default Windows power plan—especially if it switches to Performance mode after the app closes, meaning you’re always running at full speed. In my case, Teamviewer idle was using excessive CPU for its simple background tasks compared to other remote tools. I stopped using it because of that performance problem. It once was the best option, but they’ve been making similar errors for years.

Pages (2): Previous 1 2