winsiderss / systeminformer

A free, powerful, multi-purpose tool that helps you monitor system resources, debug software and detect malware. Brought to you by Winsider Seminars & Solutions, Inc. @ http://www.windows-internals.com
https://systeminformer.sourceforge.io
MIT License
10.53k stars 1.36k forks source link

[Bug] Dedicated memory not clearing itself properly (cache related?) #2073

Closed Dajova closed 1 month ago

Dajova commented 1 month ago

Brief description of your issue

So i've noticed that some apps really like to "mess" with SI to display ludicrous amounts of dedicated video memory usage (even tho it's false). For example: image I'm guessing is that dedicated memory doesn't clear itself properly to display the accurate amount of used video memory.

The app in the screenshot is called Lossless Scaling, having it run for maybe a hour and it reports to be using 10TB+ already. it's not the sole occurrence tho.

Steps to reproduce (optional)

Expected behavior (optional)

Should've figured it would clear itself normally, but it doesn't seem to reflect the accurate numbers after a while.

Actual behavior (optional)

It never stops increasing the video memory, some apps seems to blow out of proportions with this bug.

Environment (optional)

No response

dmex commented 1 month ago

So i've noticed that some apps really like to "mess" with SI to display ludicrous amount

This is a known Windows kernel bug caused by dxgmms2.sys when the machine resumes from sleep, not something caused by applications and not specific to SI but also Task Manager, Process Explorer, Firefox, Google Chrome and anything using the same data for reporting browser GPU usage.

It was reported to Microsoft back in 2017-2018 but they don't care enough to fix the issue 🤷‍♂️

Dajova commented 1 month ago

Hmm alright. Thank you for the info anyway.

dmex commented 1 month ago

Changing ProcessHacker.ExtendedTools.EnableGpuPerformanceCounters to 0 disablers the dxgmms2 counters and avoids the issue with those statistics but unfortunately the kernel doesn't always report statistics via the legacy API