WTF is this?!?!

[Nalgasp3ludas]

Does gta take 28gb of ram?!?!?!?!!??!?!?!?!!?

 

 

[PineyCreek]

Looks like it takes almost 2 GB.  Try sorting the memory column or scrolling.  Unless you have a hidden process or some type of sneaky sneaky malware, you should see it add up to your memory usage.

[Tabs]

You have a MASSIVE driver memory leak buddy.

 

You're using 22.6GB of non-paged pool.

 

I helped someone else on the LTT forums last month with basically the same kind of issue - try to read through my posts on there, using poolmon to determine what driver is leaking, and try to update it if possible.

[Nalgasp3ludas]

1 minute ago, Tabs said:

You have a MASSIVE driver memory leak buddy.

 

You're using 22.6GB of non-paged pool.

 

I helped someone else on the LTT forums last month with basically the same kind of issue - try to read through my posts on there, using poolmon to determine what driver is leaking, and try to update it if possible.

how do I fix this?

 

sorry taught it was your signature im reading it

[JakeNTech]

I have had this before, its a memory leak, my solution was to reinstall windows, not sure if there are other ways of fixing it. 

[PineyCreek]

Just now, Teejo said:

how do I fix this?

If it's a driver memory leak, do what @Tabs said to find it, then update it.  If it's the latest version, try installing an older version.

[Tabs]

Just now, Teejo said:

how do I fix this?

I explained it just there. Find the driver that is leaking, and update or replace it. It could literally be any of a hundred thousand drivers, so I can't give more specific instructions - only you can find out what drivers are running on your system, and which of those is leaking.

[PineyCreek]

I'm seeing a ton of posts around the net about the Killer 2200 card now in relation to this @Tabs, like your earlier posts.

[Nalgasp3ludas]

1 minute ago, PineyCreek said:

I'm seeing a ton of posts around the net about the Killer 2200 card now in relation to this @Tabs, like your earlier posts.

im buying the intel wifi card if this was the problem

[PineyCreek]

1 minute ago, Teejo said:

im buying the intel wifi card if this was the problem

Why?  If you have the Killer E2200 and this was your problem, it's a relatively easy fix.

[Tabs]

Just now, PineyCreek said:

I'm seeing a ton of posts around the net about the Killer 2200 card now in relation to this @Tabs, like your earlier posts.

Yeah, that was definitely the issue in case of the guy I helped last month - swapping the Killer driver for the equivalent Atheros driver solved all the issues with that particular memory leak. 

 

I try not to recommend specific drivers to change though in cases like this, simply because one leaky driver for one system might not be the issue for someone else even if they also have that hardware - a lot of other factors (like driver version, driver source, and even the need for certain functionality) can come into play.

[Tabs]

3 minutes ago, Teejo said:

im buying the intel wifi card if this was the problem

 

2 minutes ago, PineyCreek said:

Why?  If you have the Killer E2200 and this was your problem, it's a relatively easy fix.

 

Yeah, this is an incredibly easy fix. It took a while to narrow down the problem on the case last month, because I had to find a reliable source for the compatible driver (eventually got it from the Microsoft Catalogue), and of course had to find the original faulting driver in the first place.

 

If you *do* have an E2200, since I have confirmed that it has caused a leak in the past and changing to the Atheros driver doesn't hurt performance or functionality, there's no reason not to try to replace it. If it fixes your problem, awesome. If not, you'll still have to run poolmon to find the faulting module and will have lost nothing.

 

If you do replace the driver, remember to reboot afterwards since the Non-Paged Pool won't get freed until the driver is expunged from memory, and rebooting is the simplest way to do that.

[Nalgasp3ludas]

10 minutes ago, Tabs said:

Yeah, that was definitely the issue in case of the guy I helped last month - swapping the Killer driver for the equivalent Atheros driver solved all the issues with that particular memory leak. 

 

I try not to recommend specific drivers to change though in cases like this, simply because one leaky driver for one system might not be the issue for someone else even if they also have that hardware - a lot of other factors (like driver version, driver source, and even the need for certain functionality) can come into play.

Im really trying to understand what that guide says but my english is not that advanced. I went on youtube and I found a guide. It told me to go into regedit and edit some values. So I did it and my non paged ram went from 22gb to 330mbs. If it goes back to 22gb im definetely going to try to find a spanish guide on that. Right now im going to run gta again and do random stuff and see if it goes crazy again

 

 

 

edit: Im going to look for the driver

 

 

[Tabs]

Just now, Teejo said:

Im really trying to understand what that guide says but my english is not that advanced. I went on youtube and I found a guide. It told me to go into regedit and edit some values. So I did it and my non paged ram went from 22gb to 330mbs. If it goes back to 22gb im definetely going to try to find a spanish guide on that. Right now im going to run gta again and do random stuff and see if it goes crazy again

Can you link the guide you used please?

 

If you changed the setting I think you did, you may now find you now get inconsistent performance from your machine due to limiting the total size of the non-paged pool.

 

If that's the case, the driver may still be leaking, but now instead of expanding to fill your RAM, the driver may now simply exhaust the entire pool and cause contention on resources for other drivers.

[Nalgasp3ludas]

4 minutes ago, Tabs said:

Can you link the guide you used please?

 

If you changed the setting I think you did, you may now find you now get inconsistent performance from your machine due to limiting the total size of the non-paged pool.

 

If that's the case, the driver may still be leaking, but now instead of expanding to fill your RAM, the driver may now simply exhaust the entire pool and cause contention on resources for other drivers.

yes sure: 

 

damm windows 10, I dont remember wins 7 having this types of problems :l

 

 

is this the thing I need to do? 

https://www.techpowerup.com/forums/threads/guide-turn-your-killer-e2200-nic-into-qualcomm-atheros-ar8161.198899/

 

 

EDIT: 

I dont have the killer e2400, I have the e2400. Im kind of worried this might be a ram module issue. The laptop is new damm it

[Tabs]

Just now, Teejo said:

damm windows 10, I dont remember wins 7 having this types of problems :l

While I can understand you thinking that Windows is the problem, this is specifically an issue with a driver. If the driver hasn't been built to conform with the driver model of Windows 10 and is using resources in a way that is unacceptable, it really isn't Microsoft's fault. 

 

That is... unless the faulting driver is made by Microsoft. But I somehow doubt it.

 

Driver developers often took a lot of shortcuts back before we had unified driver models (before Vista), and it lead to a lot of security and reliability problems for Windows. These unified models have been improving since then, but that means that the better the models get, the more "bad" drivers get discovered and need to be updated by manufacturers. 

 

 

[Tabs]

Also, I watched the YouTube video you linked, or more accurately, I read the description that said what the video did, since reading for 15 seconds is far more convenient than watching a 4 and a half minute video (I hate those), and unfortunately that will not fix your problems. The suggestion to reboot after performing the steps will already clear your non-paged pool, but it won't stop it growing again due to the leaky driver.

 

If you changed the registry value to impose a limit on the pool size, you'll soon encounter the contention issues I mentioned in my previous post. So unfortunately, that's not a fix. There really is no alternative to actually *fix* this issue than to identify the driver that's faulting and change it.

[Nalgasp3ludas]

3 minutes ago, Tabs said:

While I can understand you thinking that Windows is the problem, this is specifically an issue with a driver. If the driver hasn't been built to conform with the driver model of Windows 10 and is using resources in a way that is unacceptable, it really isn't Microsoft's fault. 

 

That is... unless the faulting driver is made by Microsoft. But I somehow doubt it.

 

Driver developers often took a lot of shortcuts back before we had unified driver models (before Vista), and it lead to a lot of security and reliability problems for Windows. These unified models have been improving since then, but that means that the better the models get, the more "bad" drivers get discovered and need to be updated by manufacturers. 

 

 

I will continue to monitor my lap, if I get a performance issue, or the memory goes crazy again I will check the poolmon guide in spanish

[Tabs]

Just now, Teejo said:

I will continue to monitor my lap, if I get a performance issue, or the memory goes crazy again I will check the poolmon guide in spanish

If you need specific help, feel free to post here or PM me. Unfortunately it's super late here so I can't walk you through the steps right now - but I'm sure lots of other folk can.

 

As to your edit to the earlier post: This is 100% not an issue with your RAM. Paged and Non-Paged pools are purely storage spaces for driver data. That's literally all those pools are used for. If it was a RAM issue, you'd have noticed crashing or corruption whenever your memory was in any way taxed; and since you posted to the thread with more than 30GB of memory in use, that definitely counts as taxed.

[Nalgasp3ludas]

1 minute ago, Tabs said:

If you need specific help, feel free to post here or PM me. Unfortunately it's super late here so I can't walk you through the steps right now - but I'm sure lots of other folk can.

 

As to your edit to the earlier post: This is 100% not an issue with your RAM. Paged and Non-Paged pools are purely storage spaces for driver data. That's literally all those pools are used for. If it was a RAM issue, you'd have noticed crashing or corruption whenever your memory was in any way taxed; and since you posted to the thread with more than 30GB of memory in use, that definitely counts as taxed.

thats good to hear thanks for your help mate, really appreciate it, just one more question. Is the guide I followed going to give me performance issues? I found a reddit user that also told to go into those settings. Aparently e2400 memory leak is a popular google search

[Tabs]

2 minutes ago, Teejo said:

thats good to hear thanks for your help mate, really appreciate it, just one more question. Is the guide I followed going to give me performance issues? I found a reddit user that also told to go into those settings. Aparently e2400 memory leak is a popular google search

It very well could, yes. If you limit the amount of pool space available, it stops the pool growing (and therefore stops the "leak" affecting main memory to the same extent), but then you're forcing all of your drivers - including any leaky ones - to fit in a tiny amount of space. Eventually performance will suffer from this, and possibly quite quickly if you set the limit to a low value.

 

If you follow a guide to replace a driver without having first identified what driver is causing you trouble, you may have to end up going through with manual searching using poolmon anyway.

[Nalgasp3ludas]

10 minutes ago, Tabs said:

It very well could, yes. If you limit the amount of pool space available, it stops the pool growing (and therefore stops the "leak" affecting main memory to the same extent), but then you're forcing all of your drivers - including any leaky ones - to fit in a tiny amount of space. Eventually performance will suffer from this, and possibly quite quickly if you set the limit to a low value.

 

If you follow a guide to replace a driver without having first identified what driver is causing you trouble, you may have to end up going through with manual searching using poolmon anyway.

I begin to do a search and found a guy that had the memory leak after he download something big. I had just downloaded gta v and it was 70gb, Restarting the laptop helped him but when he download something again it got back up. its def a killer e2400 issue then. It prolly been happening to me since I got the laptop but never noticed it.