Memory Leak in NonPaged Pool on Windows 10.

[ZawadaZSE]

Hello everyone,

I'm experiencing huge memory leak problem on my Windows 10 host. Previously I had Windows 8.1 and recently I've upgraded to 10. After upgrade my non paged pool slowly grows until it reach 3 GB. I've search what could cause this behavior. I've used poolmon to check which tag is responsible for this leak and found two tags 1,2 GB each, FMic and Irp. After further investigation someone pointed Virtualbox Network Driver as a source of the problem. I've uninstalled Virtualbox and problem had been solved.

Now I've installed Virtualbox 5.0.12 and problem is back (even if no vm is running).

Have anyone had this problem? Should I give you more detail about my configuration?

Thanks,
James

[scottgus1]

It's not likely any of the users could help fix this, you'd do best to post on the Bugtracker and have the developers take a look. Post logs & complete info.

[mpack]

I have a vague memory that an IRP is a message packet passed to a device driver. FMic sounds like a microphone device. VirtualBox will certainly use an audio device if configured to do so, but that doesn't mean that VBox is at fault. In fact I don't know why VirtualBox would get involved with anything at the audio driver level on your host: so my guess would be, you have a badly written host audio driver.

[wilko]

FYI
I'm having the same problem: Windows 10 host, VirtualBox 5.0.14 r105127, I have 16GB RAM which grows to being 70% used seconds after starting my one VM (which is currently hardly used).

This is not something I can easily solve or research for 2 reasons: as a long time linux user Windows is a big mystery for me and every step requires a lot of extra research, which gets me to the second reason, I simply lack the time.

I will try some simple steps, if that fails, I'll just go on and hope I don't get bsod again because all memory got eaten by the big poolmonster.

- try latest test build
- try older versions
- keep installing host updates as they come along

Last resort:
- get rid of Windows

**edit. that said, this 70% may just be the normal lazy memory allocation. Doesn't explain suddenly running out of memory though.

[mosaic]

I'm experiencing a large non-paged pool leak using Virtual Box 5.2.6 (and previous versions) on Windows 10 host.
My symptoms are well described by this post:

https://answers.microsoft.com/en-us/win ... 088?auth=1

Anyone else seeing this?
Known issue or fix?