F5F Stay Refreshed Software Operating Systems This unusual GPU memory issue on Windows 10 requires investigation.

This unusual GPU memory issue on Windows 10 requires investigation.

This unusual GPU memory issue on Windows 10 requires investigation.

Pages (2): 1 2 Next
G
Gryzzly13
Junior Member
29
12-24-2016, 07:23 PM
#1
G
Gryzzly13
12-24-2016, 07:23 PM #1

B
Ballenknijper
Member
80
12-26-2016, 07:20 PM
#2
It seems 2004 was also referred to as 20H1. I checked my system and found the Desktop Window Manager running at 3.8% CPU with no GPU activity. Both Client Server Runtime Processes were using minimal CPU, around 0.1%. The driver in question is either 461.09 or 461.40.
B
Ballenknijper
12-26-2016, 07:20 PM #2

It seems 2004 was also referred to as 20H1. I checked my system and found the Desktop Window Manager running at 3.8% CPU with no GPU activity. Both Client Server Runtime Processes were using minimal CPU, around 0.1%. The driver in question is either 461.09 or 461.40.

D
Desertical
Junior Member
25
12-29-2016, 07:35 PM
#3
It occurred before another user as well (unclear which). Also, please move the mouse quickly—it increases GPU usage to about 10-15% on my PC. It worked with various mice. By the way, what GPU model are you using?
D
Desertical
12-29-2016, 07:35 PM #3

It occurred before another user as well (unclear which). Also, please move the mouse quickly—it increases GPU usage to about 10-15% on my PC. It worked with various mice. By the way, what GPU model are you using?

A
Affel13
Junior Member
38
12-29-2016, 11:20 PM
#4
I didn’t realize F@H was running at high intensity on my GPUs (about 40% usage). Turning it off and restarting worked. Outcomes: On different monitors, I achieved 1-2% performance for a few seconds before it returned to zero.
A
Affel13
12-29-2016, 11:20 PM #4

I didn’t realize F@H was running at high intensity on my GPUs (about 40% usage). Turning it off and restarting worked. Outcomes: On different monitors, I achieved 1-2% performance for a few seconds before it returned to zero.

S
SayNoToNWO
Posting Freak
879
01-01-2017, 01:17 PM
#5
Sure, it makes sense. This seems related to the 3000 series cards, as they never worked with my older GPUs (the 1000 series).
S
SayNoToNWO
01-01-2017, 01:17 PM #5

Sure, it makes sense. This seems related to the 3000 series cards, as they never worked with my older GPUs (the 1000 series).

N
NaiROolF
Senior Member
685
01-03-2017, 03:58 AM
#6
I also have a GTX 750 in my MC server, though it's running 8.1. I'm going to try it. The outcome was consistent. Very minimal CPU usage, occasional mouse movement and a bit of GPU activity for about 4 seconds.
N
NaiROolF
01-03-2017, 03:58 AM #6

I also have a GTX 750 in my MC server, though it's running 8.1. I'm going to try it. The outcome was consistent. Very minimal CPU usage, occasional mouse movement and a bit of GPU activity for about 4 seconds.

U
USAirways
Member
157
01-04-2017, 08:49 AM
#7
There are several monitors available. Some offer high refresh rates. The 40 C rating isn’t a cause for concern—it might just be a lot of factors at play. Perhaps Ampere heats up more than Pascal, or your cooler design differs. The screenshot displays only about 3% usage. But verify this through a trustworthy method beyond Task Manager, as it tends to misrepresent GPU activity and often fails. Right now my GPU is running at full capacity for several days, yet Task Manager shows under 15%. Use tools like MSI Afterburner or GPU-Z for accurate monitoring. If the idle clocks drop, it means the system is truly idle regardless of Windows’ estimate.
U
USAirways
01-04-2017, 08:49 AM #7

There are several monitors available. Some offer high refresh rates. The 40 C rating isn’t a cause for concern—it might just be a lot of factors at play. Perhaps Ampere heats up more than Pascal, or your cooler design differs. The screenshot displays only about 3% usage. But verify this through a trustworthy method beyond Task Manager, as it tends to misrepresent GPU activity and often fails. Right now my GPU is running at full capacity for several days, yet Task Manager shows under 15%. Use tools like MSI Afterburner or GPU-Z for accurate monitoring. If the idle clocks drop, it means the system is truly idle regardless of Windows’ estimate.

K
Kuelo
Member
55
01-05-2017, 08:53 AM
#8
K
Kuelo
01-05-2017, 08:53 AM #8

T
Tavado
Senior Member
505
01-06-2017, 05:44 PM
#9
It’s not worth checking since it’s meant to be ignored. The task manager is extremely unreliable and should be avoided.
T
Tavado
01-06-2017, 05:44 PM #9

It’s not worth checking since it’s meant to be ignored. The task manager is extremely unreliable and should be avoided.

P
pitbuilder27
Member
50
01-08-2017, 03:54 AM
#10
I verified this situation, and it began unexpectedly, which is unusual. What I did was unintentionally enable "bit locker," and it appears to be active now—though I’m unsure if there’s a link. This started around the same time my idle temperatures rose significantly. I didn’t activate bit locker, so I disabled it right after noticing the change.
P
pitbuilder27
01-08-2017, 03:54 AM #10

I verified this situation, and it began unexpectedly, which is unusual. What I did was unintentionally enable "bit locker," and it appears to be active now—though I’m unsure if there’s a link. This started around the same time my idle temperatures rose significantly. I didn’t activate bit locker, so I disabled it right after noticing the change.

Pages (2): 1 2 Next