Hence I had to download the new software, uninstall the old Killer Manager software and install the new Killer Control Center software and then everything appears to be working fine with no more memory leaks. The new software they provided is renamed Killer Control Center as a replacement. The KillerNetworking site also mentioned that the Killer Network Manager software was not working with the Windows 10 Fall Creators Update and was no longer supported. I then checked out the KillerNetworking site and they provided a November update for the Killer Network software. When i checked out the Dell Support Drivers page no new driver/fix was listed. I believe that with the Fall Creators Windows 10 Update, a problem has emerged with the Killer Network Manager software/drivers causing a memory leak.
Latest cumulative update for Windows 8.1 does not address it.This post is for the benefit of all Alienware owners who have Killer network cards installed including both Ethernet and wireless. It must have appeared in Windows 8.1 and was only later fixed in Windows 10. While I can't say with 100% certainty, it's likely the Windows 10 update article I linked speaks of the resolution of the same bug. The network adapter drivers can be ruled out since the only requirement is that the network adapters are part of the network bridge and the behavior can be consistently reproduced with different network adapters. Windows Performance Toolkit confirmed that the leaks happen in ndis.sys and that the allocations have "NDnd" tag. I haven't seen anyone posting about this particular problem, the only known issue with similar symptoms occurs with outdated Ethernet Killer drivers.Īnd this: ( Addressed issue with memory leaks in the nonpaged pool with the "NDnd" tag, which causes the OS to crash.) Reboot is the only way to reclaim that memory. Basically, when using network adapters in bridged mode and copying files from a file share, non-paged pool usage keeps rising with more files copied (Task Manager->Performance tab->Memory). I've recently come across a very nasty bug in Windows 8.1, specifically in its NDIS kernel driver (ndis.sys).
0 kommentar(er)
