Question Memory leak after Windows 10 update

Sep 29, 2018
36
0
30
0
I updated the Windows 10 May update this month and have had a huge memory leak since, to the point where I can't play any games (it just freezes).

I've run poolmon and found the files that are causing the memory leak are all Windows 10 related such as: fileinfo.sys., fltmgr.sys, crashdmp.sys, ntfs.sys, and loads more. I googled these and most of them seem to be related to the blue screen of death? Which I don't have. However, I'm not sure how to fix/repair this.

I tried uninstalling the Windows update I installed and going back to the previous version, but every time I turn on my computer, Windows automatically installs them again (even if I turn off automatic updates in services.msc).

I've updated all my other drivers and they are fine, but how do I fix Windows related drivers?

Many thanks!
 

Colif

Win 10 Master
Moderator
windows drivers don't normally cause memory leaks. I suspect leak is still one of your other drivers.

crashdmp is to do with bsod, the others look like file system drivers to me. Could be those files are reacting to the leak, as if its ram, the PC will try to close down anything it doesn't need to make space for the driver thats always asking for more ram but not releasing the ram its already got , and dump it to the page file (might explain why ntfs is there). Eventually WIndows will run out of resources it can give and crashes.

what is your PC?
can you download and run Driverview - all it will show is currently running drivers
http://www.nirsoft.net/utils/driverview.html
when you run it, go into view tab and set it to hide all MIcrosoft drivers, will greatly reduce numbers.
take a screenshot, upload to an image sharing website and show link here.

you can try running this
right click start button
choose powershell (admin)
type SFC /scannow and press enter
once its completed, copy/paste this command into same window:
Repair-WindowsImage -Online -RestoreHealth and press enter
SFC fixes system files, second command cleans image files, re run SFC if it failed to fix all files and restart PC
 
Sep 29, 2018
36
0
30
0
windows drivers don't normally cause memory leaks. I suspect leak is still one of your other drivers.

crashdmp is to do with bsod, the others look like file system drivers to me. Could be those files are reacting to the leak, as if its ram, the PC will try to close down anything it doesn't need to make space for the driver thats always asking for more ram but not releasing the ram its already got , and dump it to the page file (might explain why ntfs is there). Eventually WIndows will run out of resources it can give and crashes.

what is your PC?
can you download and run Driverview - all it will show is currently running drivers
http://www.nirsoft.net/utils/driverview.html
when you run it, go into view tab and set it to hide all MIcrosoft drivers, will greatly reduce numbers.
take a screenshot, upload to an image sharing website and show link here.

you can try running this
right click start button
choose powershell (admin)
type SFC /scannow and press enter
once its completed, copy/paste this command into same window:
Repair-WindowsImage -Online -RestoreHealth and press enter
SFC fixes system files, second command cleans image files, re run SFC if it failed to fix all files and restart PC
Thank you for the reply.

My make is a Ryzen 7 1700x, GTX 1060 6GB, with 8GM of RAM.

I did your steps. I've uploaded the results of the DriverView here: https://ibb.co/cyCPKK6 (won't let me insert link via images).

The results of the SFC /scannow said "Windows Resource Protection found corrupt files but was unable to fix some of them. For online repairs, details are included in the CBS log file...". So I looked at the files and it says it cannot repair 'Windows Defender PowerShell module files' but after googling that it seems it's a bug so I don't think that could be affecting my memory?
 
Last edited:

Colif

Win 10 Master
Moderator
i was hoping driverview would show more than 3 dates. Normally its older drivers that cause leaks, not always but normally

it could be the Logitech wingman drivers as i expect they aren't new, given one LGS driver is from 2015
the wingman virtual bus enumerator drivers are from 2016 - logitech haven't updated these drivers in 3 years as even the latest LGS will include them

nothing else stands out as being a normal cause. Nvidia drivers normally have other signs so i doubt its them. IF you had Killer internet it would be dead easy as they do cause leaks. But you don't.
 
Sep 29, 2018
36
0
30
0
i was hoping driverview would show more than 3 dates. Normally its older drivers that cause leaks, not always but normally

it could be the Logitech wingman drivers as i expect they aren't new, given one LGS driver is from 2015
the wingman virtual bus enumerator drivers are from 2016 - logitech haven't updated these drivers in 3 years as even the latest LGS will include them

nothing else stands out as being a normal cause. Nvidia drivers normally have other signs so i doubt its them. IF you had Killer internet it would be dead easy as they do cause leaks. But you don't.
I ended up doing a fresh install of Windows 10 and that didn't fix it. I also uninstalled the Logitech software and updated to their new G Hub version but the problem still exists.

I've noticed that the Wifi adapter I use (GC-WB1733D-I) may be the issue. On the Gigabyte website in the latest driver version for the adapter, it says it "(Note) Win10 ver.1709 \ver.1803 supported" and doesn't mention being 1903 supported, but could this really be it? is there a way I can disable it or something to find out?

Here's what the poolmon results are in case you can spot something I can't: https://ibb.co/ZTdbFxN

Thanks
 
Sep 29, 2018
36
0
30
0

Colif

Win 10 Master
Moderator
I am not sure how you read poolmon or I would

What motherboard do you have?
how new are wacom router drivers?

on a clean install, it can only be a driver you installed since. Tried running driverview since? i can work out driver dates based on driver versions if need be.

try running driver verifier and see if it finds anything - its normally for BSOD but it might show a bad driver - see 2nd post here, follow precautions - https://forums.tomshardware.com/threads/handy-details-to-include-in-blue-screen-of-death-posts.3468965/ - Do step 1 of post 1 as well before running in case it does cause a BSOD - it is its job, test drivers and make them crash
 
Sep 29, 2018
36
0
30
0
I am not sure how you read poolmon or I would

What motherboard do you have?
how new are wacom router drivers?

on a clean install, it can only be a driver you installed since. Tried running driverview since? i can work out driver dates based on driver versions if need be.

try running driver verifier and see if it finds anything - its normally for BSOD but it might show a bad driver - see 2nd post here, follow precautions - https://forums.tomshardware.com/threads/handy-details-to-include-in-blue-screen-of-death-posts.3468965/ - Do step 1 of post 1 as well before running in case it does cause a BSOD - it is its job, test drivers and make them crash
MSI B350 PC Mate.
Not sure but I ended up uninstalling the program before I saw your reply anyway so doesn't seem like that's the issue.

I just reran driverview and there is way more stuff on there then previously, not even sure why but here are the links: https://ibb.co/x8JYChk
https://ibb.co/FXfL0SS

It seems the ones that are highlighted red are the same 'driver names' that poolmon said was responsible for leaking memory. But I've literally updated the drivers?
I will try your second option later tonight

Thank you
 
Sep 29, 2018
36
0
30
0
Download and run LIve update 6, it will check you have latest drivers for board - its 3rd link on th utility page: https://www.msi.com/Motherboard/support/B350-PC-MATE#down-driver&Win10 64

more drivers cause you didn't go into views and hide all MIcrosoft drivers. Run it after running MSI Live update 6, if it doesn't find any new drivers, or they don't fix problem.
MSI Live update 6 said my drivers were out of date, so I updated them but no change. DriverView still shows all non-microsoft drivers in red like the first link I showed you. No change :/
 

ASK THE COMMUNITY

TRENDING THREADS