![]() In the details pane (on the right side), double-click DisableIdleStop. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\RemoteRegistry ![]() Open the run command box by pressing the Windows key R. To work around this issue, follow these steps: The Remote Registry service is designed to stop running after the connection has been idle for 10 minutes. To do this, open cmd prompt and type 'cd C:\Windows\System32\drivers' to go to the drivers. Now look which pooltag uses most memory as shown here: Now open a cmd prompt and run the findstr command. The issue occurs in the Endpoint Mapper Logic component. The issue occurs in the Endpoint Mapper Logic component. Run poolmon by going to the folder where WDK is installed, go to Tools (or C:\Program Files (x86)\Windows Kits\8.1\Tools\圆4) and click poolmon.exe. Additionally, PoolMon analysis may show that the Windows Notification Facility (WnF) tag is consuming all the available paged pool memory. This memory leak occurs after about 10 minutes of system uptime and eventually causes the system to hang.Īdditionally, PoolMon analysis may show that the Windows Notification Facility (WnF) tag is consuming all the available paged pool memory. On a Windows-based computer, you notice that more system memory and paged pool memory are being consumed than expected. This article provides a workaround for a memory leak issue in the remote registry service that causes Windows to hang. ![]() ![]() Memory leak in the remote registry service causes Windows to hang
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |