Recommended Posts

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.

Link to comment
https://www.neowin.net/forum/topic/1117499-windows-8-high-memory-usage/
Share on other sites

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

Welcome to W8 is buggy club. :)

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.

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.

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?

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.microsof...v=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?

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

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

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?

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

Welcome to W8 is buggy club. :)

really? On my pc im connected before I even log in.

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?

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.

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).

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:

  • Like 2
  • 1 month later...

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:

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Ndu

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.

  • 4 months later...

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

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).

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. :)

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.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • NASA: This asteroid may not kill us but it probably won't be far off either by Sayan Sen Image by Zelch Csaba via Pexels New observations by NASA's James Webb Space Telescope have eliminated the last remaining impact threat posed by asteroid 2024 YR4, ruling out the possibility that the near-Earth object could strike the Moon in December 2032. NASA said observations collected by Webb on February 18 and 26, 2026, enabled scientists to refine the asteroid's orbit enough to "rule out a chance of lunar impact on Dec. 22, 2032." Instead, asteroid 2024 YR4 is now expected to pass the Moon at a distance of about 13,200 miles (21,200 km). The agency stressed that the update "reflects improved precision in our understanding of where the asteroid is expected to be in 2032 rather than a shift in its orbital path." The announcement closes a remarkable chapter in planetary defence that began in late 2024, when the approximately 60-metre-wide asteroid briefly became the most closely watched near-Earth object in the world. Discovered on December 27, 2024, by the ATLAS telescope in Chile, 2024 YR4 initially appeared to have a small chance of colliding with Earth on December 22, 2032. As astronomers gathered more observations, the impact probability briefly climbed to around 3%—the highest ever recorded for an asteroid of its size—before steadily falling as its orbit became better understood. By early 2025, international observations had ruled out any significant risk to Earth. However, astronomers were left with another possibility: a roughly 4% chance that the asteroid could instead strike the Moon. "The probability that asteroid 2024 YR4 will strike the Moon on 22 December 2032 is now approximately 4%," the European Space Agency (ESA) had said last year, noting that "there is a 96% chance that the asteroid will not impact the Moon." ESA said such an impact, while unlikely, would have presented an extraordinary scientific opportunity. "It is a very rare event for an asteroid this large to impact the Moon – and it is rarer still that we know about it in advance. The impact would likely be visible from Earth, and so scientists will be very excited by the prospect of observing and analysing it," said Richard Moissl, Head of ESA's Planetary Defence Office. "It would certainly leave a new crater on the surface. However, we wouldn't be able to accurately predict in advance how much material would be thrown into space, or whether any would reach Earth," he added. The asteroid also exposed an important blind spot in planetary defence. Because 2024 YR4 approached Earth from the direction of the Sun, it remained hidden from ground-based telescopes until after its closest approach. "We looked into how Neomir would have performed in this situation, and the simulations surprised even us," Moissl said. "Neomir would have detected asteroid 2024 YR4 about a month earlier than ground-based telescopes did. This would have given astronomers more time to study the asteroid's trajectory and allowed them to much sooner rule out any chance of Earth impact in 2032." He added, "As an infrared telescope, like Webb, Neomir would have also immediately given us a much better estimate for the asteroid's size, which is very important for assessing the significance of the hazard." The latest NASA observations underscore the value of space-based infrared telescopes in tracking faint asteroids. According to NASA, Webb made "among the faintest ever observations of an asteroid," extending the object's observational record by nearly eight months at a time when it had become too faint for other telescopes. That additional data allowed scientists to eliminate the remaining uncertainty surrounding its 2032 flyby. Although asteroid 2024 YR4 is now confirmed to pose no threat to either Earth or the Moon, scientists say its discovery remains one of the most significant real-world tests of the international planetary defence system, demonstrating how continued observations can rapidly transform an object once considered hazardous into one whose future path is known with high confidence. Source: NASA, ESA This article was generated with some help from AI and reviewed by an editor. Under Section 107 of the Copyright Act 1976, this material is used for the purpose of news reporting. Fair use is a use permitted by copyright statute that might otherwise be infringing.
    • Yup. Google is just scraping the entire internet for their own ad profits without sharing revenue with the sources. It's obviously stealing, but since these sites depend upon Google's search scraps to survive... As for me, I just stopped using Google for anything except Reddit searches. If Reddit's own search wasn't complete crapola, I'd never use Google search again.
    • I had a feeling this was coming. Picked up my first Mac ever last Saturday. Glad I did.
    • In a major surprise there is actually some good deals for the first time in years. At least for me.
  • Recent Achievements

    • Conversation Starter
      Admir earned a badge
      Conversation Starter
    • First Post
      The_Focal_Point earned a badge
      First Post
    • Apprentice
      daryld went up a rank
      Apprentice
    • Contributor
      Carltonbar went up a rank
      Contributor
    • One Month Later
      The_Focal_Point earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      419
    2. 2
      +Edouard
      170
    3. 3
      PsYcHoKiLLa
      130
    4. 4
      Xenon
      69
    5. 5
      neufuse
      69
  • Tell a friend

    Love Neowin? Tell a friend!