nsi memory leaks fixed yet?

Anonymous
2013-06-06T11:33:13+00:00

Does anyone know if there is a fix for nsi service eating up memory yet?I'm really getting tired of having it eat up to 3 gbs or ram all the time.I have a dump file if the need arises.

Windows for home | Windows 11 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

111 answers

Sort by: Oldest
  1. Anonymous
    2013-10-31T04:01:38+00:00

    Through trial and error, I figured it has something to do with the router and network card, or maybe just the router.  Here's the story.

    I've got two Buffalo WHR-G54S routers that act as a common wireless network using WDS mode.  These routers are using a 3rd party firmware called Tomato.  My desktop with the NSI memory leak is plugged in by cable to the primary Buffalo router.  That primary router is also connected to a Cisco cable modem/router, using the Buffalo WAN port.  All my network/internet functions seem to work, except for the NSI memory leak.

    When I unplug the computer's ethernet wire out of the Buffalo router and plug it into an open port on the Cisco, wha-la, the NSI memory consumption is rock solid.  Plug it back into the Buffalo network, and the memory jumps up and begins climbing.

    So, I think it has to do with the Tomato firmware I put on my routers, or the way its set up.  Does anyone else see any commonalities in their setups?

    • Andre

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2013-10-31T10:48:48+00:00

    Srinivas KR,

    Can you please unmark your response as the answer?  This has not worked for anyone involved in this conversation.

    • Liam

    Hi,

     

     

    Since Network Store Interface service (NSI) delivers network notifications (Eg: interface addition/deleting etc) to user mode clients. So I suspect that your issue may be related to Network adapter drivers OR high memory usage of NSI service is mostly caused by third party service or some spyware and adware.

     

    Please follow the methods and check if it works fine.

     

    Method 1:

    I would also suggest you to download and run the latest Microsoft Safety Scanner on your computer and check if it helps:

    http://www.microsoft.com/security/scanner/en-us/default.aspx

    Note: Any data files that are infected may only be cleaned by deleting the file entirely, which means there is a potential for data loss.

     

    Method 2:

    Follow the steps to uninstall and reinstall the network adapter drivers and check if it works fine.

    NOTE: Please make sure you download the latest updated network adapter drivers from the computer manufacturer website before you uninstall the driver.

    a.      Press Windows key + R

    b.      In the run box, type devmgmt.msc and press enter.

    c.       Expand Network Adapters.

    d.      Right click on all the Network Adapters and click on uninstall.

    e.      Restart the computer.

     

    For any Windows related issues please feel free to contact us and we will be glad to help.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2013-11-17T00:41:19+00:00

    I am also experiencing this. It's very very annoying.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2013-11-22T20:40:41+00:00

    These are good troubleshooting steps, but obviously not the answer. You should unmark this as an answer.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2013-11-22T20:54:47+00:00

    I have been working with Microsoft support over the past couple of weeks trying to solve the same issue. The only difference is that my issue is with Server 2008 R2 SP1, which is virtually the same OS. 

    In our case, we have a virtually identical system running in the same environment and that server is not experiencing the same issue. The memory leak only seems to manifest itself when a significant amount of net traffic is generated (this is our monitoring platform). I have tried every single suggestion found in this thread and others to no avail. Recently I discovered that there is a significant difference in the number of Windows Updates installed on the problem system as compared to the healthy one. This has lead me to think that an update is to blame.

    Has anyone looked into this possibility? I will continue to troubleshoot and hound MS support for an answer. When I get one, I'll post it.

    Was this answer helpful?

    0 comments No comments