 pinscomputer wrote:if you want to try and further debug to isolate the problem to the NSI service, you can try and temporarily move NSI service to its own servichost. see the following video starting at timestamp 6min 51sec and this Microsoft blog: |
| DarkghostX wrote: I will check that out. Is there any danger in doing that? How will it help me to locate the source of what is causing NSI to bug out? |
there should be no problems. the process outlined in the video is built into the operating system. The idea is to move the service to its own servicehost container so that specific service can be monitored instead of all the services that are, by default/design, bundled into a single service when the operating system is launched.
| DarkghostX wrote: A small update, I had a thought after reading people talking about their NSI service problems and decided to try something. I had ESET block off the network, and waited several hours. My guess was correct, the memory did not increase by any noticeable amount. After leaving the network blocked for an extended period of time (more than 12 hours) the NSI memory went from around 335,000 to about 42,000. Does this new info matter? If nothing else at least I have a workaround for the time being but I still want to fix this aggravating issue. Thank you for being willing to help me on this issue, I really appreciate it. |
If you're trying to remove a program and can not find it in the StartUp folder (usually C:\WINDOWS\Start Menu\Programs\StartUp), then it may be launching from one of the registry keys below. To remove it, delete the value associated with the program you want to remove.
[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run]
[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunOnce]
[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunServices]
[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunServicesOnce]
[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\Userinit]
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run]
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\RunOnce]
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\RunServices]
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\RunServicesOnce]
[HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows]
It may also be loaded from the [Load] or [Run] sections of your WIN.INI file, found in the Windows directory.
In Windows 8 (perhaps in Windows 7 also) the description of the computers on your network could be obtained by creating a folder, usually on your desktop, namedNetwork.{208d2c60-3aea-1069-a2d7-08002b30309d}
When you opened this folder all the computers attached to your network were displayed ALONG WITH THE COMPUTER DESCRIPTION.
With many computers on a network the computer description is often needed to know which computer contains the directory to which you want to map a network drive.
In WINDOWS 10 this no longer works. The folder with the name Network.{208d2c60-3aea-1069-a2d7-08002b30309d} can be created. It does say Network (the name of the network). When you open the folder it has an icon for Entire Network. Unfortunately the Entire Network folder is empty. (Opening the standard Windows folder shows the networked computers but does not show the computer description).
I found a response to a similar question for Windows 7 or 8 that said the non-display of the computer description in the standard Windows folder was by design. I never could understand why but the workaround was acceptable.
pinscomputer wrote:
there should be no problems. the process outlined in the video is built into the operating system. The idea is to move the service to its own servicehost container so that specific service can be monitored instead of all the services that are, by default/design, bundled into a single service when the operating system is launched.
there is not enough information to make any informed decision on what does & does not matter. I am not familiar enough with resource monitor to know how you were able to have resource monitor focus an individual service in a svchost container. From my limited use of the resource monitor tool, it appears to show the performance of the entire svchost container, which means resource monitor is giving the performance of more than 1 service. Andrew Richards & Chad Beeder have both made the point that the likelihood of an error in a windows process that has been around for a long time is small. It might happen but probably not. There is more likely an issue in a user mode process. In debugging, you have to start somewhere, look at the results of your testing, then either continue to narrow down the problem in your area of search or change the hypothesis and look elsewhere. |