No reading for GPU. Sysinternals' Process Explorer works fine.

I believe this is because your GPU is switched off by the NVIDIA Optimus technology to preserve power. It will be switched on when there's higher demand on graphics.
HWiNFO doesn't keep the GPU enabled, thus it cannot read any values from it - this is also to preserve power. I'm not sure what exactly Process Explorer reports, but I don't think that's a true value for that GPU (if disabled then even NVIDIA's own drivers don't report anything).
If you run a graphics intensive application, or manually enable that GPU, you'll see that all values will appear in HWiNFO.
 
In that case please attach the HWiNFO debug file capturing the situation when the GPU is loaded.
Also in case you have changed the order of sensor items, you might want to look at the bottom of the sensors list (they might be placed there).
 
Hi, attached.

GPU D3D Usage goes up to 100% but I can't see any entries for the GPU itself.
 

Attachments

  • log.CSV
    5.6 KB · Views: 3
Sorry, I meant the HWiNFO Debug File, which can be created as described here: http://www.hwinfo.com/forum/Thread-IMPORTANT-Read-this-before-submitting-a-report
But according to the log you posted it still seems as if the NVIDIA GPU is disabled and all the work is done by the iGPU in CPU. You might also try to open the NVIDIA Control Panel (which can usually enable the DGPU) to see if the values appear in HWiNFO. Or search for a switch on the machine to manually enable the NVIDIA GPU.
 
Yes, that's it and it confirms my assumptions - your NVIDIA GPU is always disabled.
So it seems the GPU load reported by other tools is the load of the iGPU (in Intel CPU), not the NVIDIA one. The tests you started were in fact running on the iGPU.
Please refer to my previous post for further instructions.
 
And here's one with the GPU forced on in the NVIDIA control panel.
 

Attachments

  • HWiNFO64.DBG
    448.2 KB · Views: 1
Genergy said:
And here's one with the GPU forced on in the NVIDIA control panel.

This one doesn't include sensor data in the dump, but from the short sequence captured there I see that the DGPU is still disabled.
 
Back
Top