Jump to content
AIDA64 Discussion Forum
Squall Leonhart

dedicated/dynamic Video memory utilisation bugs when utilisation is high.

Recommended Posts

It seems when vram usage passes 4GB, the aida64 values for the used GPU begin showing very low numbers.

 

This i what i see in Aida64, where GPU-Z and Nvidia Inspector show >4.8GB used.

Utilization    
GPU    98%
Memory Controller    46%
Video Engine    0%
Bus Interface    5%
Dedicated Memory    609 MB
Dynamic Memory    699 MB

DirectX Video info shows

Direct3D Device Properties    
Total / Free Video Memory    8192 MB / 3385 MB

  • Like 1

Share this post


Link to post
Share on other sites

Thank you, we'll look into this. Do you use 64-bit Windows 10 with latest patches applied?

Share this post


Link to post
Share on other sites

Windows 7 x64 with latest patches.

was running a heavily modded skyrim last night, and video memory up till 4096MB was reported correctly, anything over would start again at 0MB.

 

This might actually be a limitation of windows, i see in Process Explorer the dedicated memory value caps at 4096MB.

GPU-Z / Nvidia Inspector must be getting memory usage info from nvapi then :<

Share this post


Link to post
Share on other sites

The Dedicated Memory and Dynamic Memory information comes from Direct3D statistics API, which doesn't properly support over 4GB video memory under Windows 7.  It was fixed by Microsoft in Windows 8, by extending the counters from 32-bit to 64-bit.  You may want to check the Used Video Memory and Free Video Memory sensor items via OSD Panel or another hardware monitoring module of AIDA64.  They should work better under Windows 7, since they use NVAPI.

Share this post


Link to post
Share on other sites
On ‎2017‎. ‎03‎. ‎25‎. at 11:22 AM, Squall Leonhart said:

Also, AIDA64 doesn't at all show any DirectX Video information for secondary display drivers (devices)

I have a 1080 and 1060 in this machine, only the information for the 1080 is shown.

That's normal, since the classic Direct3D API only handles one 3D accelerator.  It is extended to handle multiple adapters with Direct3D 10, and then Direct3D 12 revamped everything again.  We haven't yet implemented 3 separate code paths for various Direct3D generations (D3D6/7/8/9, D3D10/11, D3D12), since these days AIDA64 users tend to prefer to focus on the direct GPU detection method (Display / GPU page in AIDA64).

Share this post


Link to post
Share on other sites
On 3/27/2017 at 6:58 PM, Fiery said:

The Dedicated Memory and Dynamic Memory information comes from Direct3D statistics API, which doesn't properly support over 4GB video memory under Windows 7.  It was fixed by Microsoft in Windows 8, by extending the counters from 32-bit to 64-bit.  You may want to check the Used Video Memory and Free Video Memory sensor items via OSD Panel or another hardware monitoring module of AIDA64.  They should work better under Windows 7, since they use NVAPI.

They do, however only the VRAM of the 1080 is returned, this probably comes back to the fact only the primary display driver is listed though, so nothing can be done about that

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...