Low GPU Utilization in Resource Manager

Hey folks, I’ve noticed that in this sim the Windows Resource Manager consistently shows GPU utilization below 10% - even though I know it’s working hard. The GPU fans are going strong, and temps are up in the hard working range. Not a big deal, but really curious how this app could somehow cause this.

Yes, this is a known issue. Try a different resource monitor like hwinfo.com

1 Like

Interesting. I wonder that works! Yeah - it’s not important to monitor that, more just curiosity and how that could happen - how it utilizes the GPU without the OS - or at least Resource Manager - knowing about it. They must be doing some kind of GPU processing that is atypical - not 3D or Copying. It is pretty much maxing out GPU memory which I would expect.

Thanks.

Are you using DX12?

See here :slight_smile:

I have said before that task manager shows only 3d by default but when using DX12 the major gpu load is shown in the ‘graphics 1’ tracer when selected from the options menu.

Yeah - on my system the Graphics_1 option. I’m using the periodic GPU utilization drop to zero to document my system freeze. I’m working with my Internet provider to resolve it as I’ve isolated the problem to either the modem or connectivity to the CO. It’s the easiest way to show the 73 second periodicity of the issue.

I recently enabled DX12 which explains the change in behavior. Thanks for explaining.

Your welcome.

I see nothing :wink:

only:

I just linked a topic which explains the question from the OP in detail. What “graphics_1” is, additonal links to articles which explain all of that.

You are looking in the wrong place I was not referring to in this thread but several others. I have the full reason for this supplied by the devs of MS. Please check before being critical please.

I was’nt critical … I only wondered what you meant.

That different graphic-engines are used is nothing new. It depends also on the driver and in former releases it depends on whether HAGS was enabled or not. I not wonder that DX12 have a similar effect and may be in a next driver release it is back to “normal”. Therefore I linked the topic :slight_smile:

Sorry about that I misunderstood.

1 Like