Sign in to follow this  
Followers 0

Windows 8 high memory usage

18 posts in this topic

Posted

I wonder if anyone else has come across this: When copying all my flacs from Win8 to my Win7, I notice my Win8 computer memory usage spiked to 97% and slowed to a crawl. The Win7 is ok. Both have 16GB of ram.

poolmon.exe shows the tag wfpn is the culprit. Doing a findstr shows that netio.sys is causing the problem. I restarted all the network services but the ram usage is still 97%. Only a reboot will solve this problem.

The Realtek driver is update for Win8. It's consistently reproducible.

Share this post


Link to post
Share on other sites

Posted

I found W8 to be unstable, especially the networking code which takes about 100x longer to connect.

Welcome to W8 is buggy club. :)
4 people like this

Share this post


Link to post
Share on other sites

Posted

[quote name='ArialBlue' timestamp='1352254765' post='595302299']
I found W8 to be unstable, especially the networking code which takes about 100x longer to connect.

Welcome to W8 is buggy club. :)
[/quote]

Just to check...is it the networking code, or the way the drivers work on Windows 8 for your device?

I ask since one of the things they really focused on was making the network connections come on faster. It's actually one of their huge talking points.

I know on my older machine my connection is always on the instant I bring my machine out of sleep. In Windows 7 slow resume of networks was why I never left sleep on. I just set the monitor to turn off...now I can save power and be ready within about 3 seconds from hitting my spacebar.

Share this post


Link to post
Share on other sites

Posted

[quote name='sspj' timestamp='1352179039' post='595300083']
I wonder if anyone else has come across this: When copying all my flacs from Win8 to my Win7, I notice my Win8 computer memory usage spiked to 97% and slowed to a crawl. The Win7 is ok. Both have 16GB of ram.

poolmon.exe shows the tag wfpn is the culprit. Doing a findstr shows that netio.sys is causing the problem. I restarted all the network services but the ram usage is still 97%. Only a reboot will solve this problem.

The Realtek driver is update for Win8. It's consistently reproducible.
[/quote]

Hi sspj,

I have exact the same issue - when copying big files around LAN, torrents,.. Win8 memory usage constantly grows to 3.8GB (total ram is 4GB) and machine starts to crawl. Only restart helps. I used the same technique with poolmon.exe (http://msdn.microsoft.com/en-us/library/windows/hardware/ff560135%28v=vs.85%29.aspx). The problem is with non-paged pool that grows all the time. The driver tag find by poolmon is "Wfpn", findstr finds "netio.sys"... this is the part of Win8 core (MS actually wrote the [bad] code..) :cry:

My machine is HP Pavilion dv7 laptop. With Win7 it worked like a charm..no memory leaks. I'll probably switch back to Win7...Win8 disappointed me.. :s

Anyone knows how to inform MS about that issue?

Share this post


Link to post
Share on other sites

Posted

[quote name='damkov' timestamp='1352386530' post='595306211']
Hi sspj,

I have exact the same issue - when copying big files around LAN, torrents,.. Win8 memory usage constantly grows to 3.8GB (total ram is 4GB) and machine starts to crawl. Only restart helps. I used the same technique with poolmon.exe ([url="http://msdn.microsoft.com/en-us/library/windows/hardware/ff560135%28v=vs.85%29.aspx"]http://msdn.microsof...v=vs.85%29.aspx[/url]). The problem is with non-paged pool that grows all the time. The driver tag find by poolmon is "Wfpn", findstr finds "netio.sys"... this is the part of Win8 core (MS actually wrote the [bad] code..) :cry:

My machine is HP Pavilion dv7 laptop. With Win7 it worked like a charm..no memory leaks. I'll probably switch back to Win7...Win8 disappointed me.. :s

Anyone knows how to inform MS about that issue?
[/quote]

Might be better to get HP to push out decently coded Win8 drivers, because in all likeliness it will be your driver, not Windows

Share this post


Link to post
Share on other sites

Posted

[quote name='z0phi3l' timestamp='1352388009' post='595306273']
Might be better to get HP to push out decently coded Win8 drivers, because in all likeliness it will be your driver, not Windows
[/quote]

I've tried two options with updating Realtek Gigabit Ethernet LAN drivers:
1. install Win7 drivers (Win8 still not supported) from HP official support site --> memory leak remains
2. install Win8 Realtek latest drivers --> memory leak remains

I've also disabled LAN interface and tried Wlan only --> still memory leak :(

What else can I do?

Share this post


Link to post
Share on other sites

Posted

[quote name='ArialBlue' timestamp='1352254765' post='595302299']
I found W8 to be unstable, especially the networking code which takes about 100x longer to connect.

Welcome to W8 is buggy club. :)
[/quote]

really? On my pc im connected before I even log in.
1 person likes this

Share this post


Link to post
Share on other sites

Posted

[quote name='damkov' timestamp='1352473251' post='595308451']I've tried two options with updating Realtek Gigabit Ethernet LAN drivers:
1. install Win7 drivers (Win8 still not supported) from HP official support site --> memory leak remains
2. install Win8 Realtek latest drivers --> memory leak remains

I've also disabled LAN interface and tried Wlan only --> still memory leak :(

What else can I do?[/quote]

Who makes your wireless card? did you do a clean install? what additional drivers did you install? the reason why I ask it might have something to do with something unrelated with the network card driver itself.

Share this post


Link to post
Share on other sites

Posted

I'd agree it's driver related.

I moved a couple of very large ISOs (my dev environment, office etc etc) in a single hit and didn't have any issues whatsoever.

Try running robocopy to move the files and see if the leak persists. It might give you a functioning work around (although it seems unlikely).

Share this post


Link to post
Share on other sites

Posted

I made a fresh Win8 install on HP Pavilion DV7 (not upgrade), it has integrated Realtek gigabit NIC (RTL8168).

After a lot of investigation I think I found the real culprint of my memory leaks. I booted up machine in "safe mode with networking" - and suddenly memory leak has gone :) So I made a list of loaded network drivers (using DriverView from NirSoft) and compared it with the list of drivers in normal boot. Safe mode did not load the following kernel drivers: lltdio.sys, mslldp.sys, Ndu.sys, rspndr.sys, srv.sys, srv2.sys, srvnet.sys, wanarp.sys.

After disabling Ndu.sys (Windows Network Data Usage Monitoring Driver) with Autoruns and normal boot - voila no more memory leaks!!!! :D
Ndu driver was introduced with Win8 (http://batcmd.com/windows/8/services/ndu/) and is actually quite buggy in combination with Realtek NIC. Microsoft should fix that...let's hope soon. :cool:
2 people like this

Share this post


Link to post
Share on other sites

Posted

Hi damkov - you nailed it. Big thanks for you research. I'm surprised that MS hasn't fix this problem yet.

I changed the registry value instead of using Autoruns:

[size="3"]HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Ndu[/size]

change the Start value to 4 (for disable).

I'm copy over 100GB of data now, memory usage stays at 14%. Normally, it would be 99% by now.

Share this post


Link to post
Share on other sites

Posted

Took me a little while to figure out why my machine was dying on big copies. When I spotted the memory leak, it eventually led me here.

Just registered to say thanks. Good on ya damkov.

Share this post


Link to post
Share on other sites

Posted

yep its Microsoft alright, only fixed on next version of windows they hope you would buy.

Share this post


Link to post
Share on other sites

Posted

I love people who talk out of their back end.

Share this post


Link to post
Share on other sites

Posted

[quote name='sjms' timestamp='1368882088' post='595696536']
I love people who talk out of their back end.
[/quote]
Care to elaborate on that?

Share this post


Link to post
Share on other sites

Posted

[quote name='z0phi3l' timestamp='1352388009' post='595306273']


Might be better to get HP to push out decently coded Win8 drivers, because in all likeliness it will be your driver, not Windows
[/quote]

Now I have to wonder "which" Realtek gigabit adapter you actually have.

There are three known versions of the Realtek gigabit adapter - an OEM/semi-generic version (supplied to several OEMs, including nVidia and HP), the RTL8111D/E (also semi-generic, but supplied to several OEMs and IHVs, including ASUS) and the current RTL8111F. (The RTL8111D, E, and F are supported by Windows 8 directly - they all use the same driver, in fact - the earlier version uses a Windows 7-type driver.)

Also, you may want to grab Realtek's own drivers (yes - they actually DO write drivers themselves) as opposed to HP's drivers. (The rather amusing thing about Realtek's driver is that it is a generic, but WHQL-certified, Windows 7/8 driver for the RTL8111D and later - and it works with at least one NVidia LAN controller that I know of; the one included as part of the 630i nForce chipset.)

That issue is not one I've had (RTL8111E PHY), and I didn't have it with the nForce chipset after switching from nForce LAN drivers to Realtek's own drivers with Windows 7. However, if you are used to Intel PHYs and Intel Ethernet drivers (especially gigabit) you may likely be spoiled - I can admit to feeling that way (Intel PRO1000CT was the precedent to in terms of gigabit to the two Realtek PHYs I referred to).

Share this post


Link to post
Share on other sites

Posted

Old thread but seems like a driver issue as was mentioned... I don't get that with my Thinkpad (Intel 82577LM Gigabit) network card.

I'm guessing this should have been solved by HP/Realtek by now. :)
1 person likes this

Share this post


Link to post
Share on other sites

Posted

btw good job figuring out where the problem was occurring,but i wouldn't be so quick to blame this on a windows problem. yes you disabled a windows driver to remedy the problem, but it could have been the network card driver not playing nice with the windows driver. seems SHoTTa35 doesn't have that problem,and countless other people with different cards don't have that problem.

Share this post


Link to post
Share on other sites
This topic is now closed to further replies.
Sign in to follow this  
Followers 0

  • Recently Browsing   0 members

    No registered users viewing this page.