Jump to content

Why is Explorer.exe leaking VRAM?

Renton577

So I've noticed on my laptop that Explorer.exe leaks VRAM. I am on Windows 10 and using an Nvidia card. However the Nvidia card is a mobile Kepler Quadro so its using driver 426. I have tested running the system with hybrid graphics on and using the Intel graphics fixes the VRAM leak but I would rather not pipe everything through the integrated graphics. My question is, is there any way to fix the issue or is it just an issue with those Nvidia drivers and I'm going to have to use the Intel?

ROG Strix AMD

---------------

CPU: Ryzen 9 5900HX GPU: AMD RX 6800M RAM: 16GB DDR4 Storage: 512GB + 1TB Intel SSD

Link to comment
Share on other sites

Link to post
Share on other sites

24 minutes ago, Mel0n. said:

What laptop model? 
On my Precision M6700 (i7-3840QM, Quadro K4000, same driver release) I have turned on Nvidia Optimus in the BIOS and set explorer.exe (in C:\Windows) to use the iGPU in Nvidia control panel.

Its an HP Zbook, and yeah using the iGPU fixes the issue but I would rather keep the iGPU off, my system has a Mux switch which allows me to run the system just off the Nvidia chip which if I do that causes the memory leak.

ROG Strix AMD

---------------

CPU: Ryzen 9 5900HX GPU: AMD RX 6800M RAM: 16GB DDR4 Storage: 512GB + 1TB Intel SSD

Link to comment
Share on other sites

Link to post
Share on other sites

  • 1 month later...

I've been digging into this for some  time, there is an object leak occuring in the desktop explorer.exe process on some machines that is antagonised by things like DPI changes, it is GPU driver agnostic but having the shell on a different gpu would mask the issue by preventing it from affecting game function.

 

I have already contacted Renton about it on reddit, but if anyone else is seeing the same thing can they list things such as their configuration on the desktop, shell extension and software used, whether or not it is an upgrade from 7 or 8, etc.

 

Theres a missing variable here as the issue still replicates on a diagnostic startup whilst not being present at all on a second machine.

 

Someone elses resolution involved changing the default image handler (which also changes the in use shell thumbnail provider), but i've had no luck there thus far. have also gone through and disabled all shell extensions too.

Link to comment
Share on other sites

Link to post
Share on other sites

  • 5 weeks later...
  • 2 months later...

Started noticing this too on my Windows 10 AMD desktop and my RX 5600 XT GPU. If I log off and log back in the VRAM resets for a few hours. Saves me from having to reboot the PC. Not sure it is completely driver related I'll keep watching it.

Link to comment
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×