Hi,We are deploying a Windows 2008 R2 Hyper-v Cluster with three nodes. All three nodes are configured exatly the same. Over the weekend a couple of weeks ago one of the nodes lost connection to the ISCSI storage device we are using for shared storage. Looking at the system a few minutes after the problem, i could see that the storage was avaiable again and the system had no Guest machines, but was using 24 of the 32 GB of the system memory. 24 GB was marked "IN USE" by resource manger but had no corosponding process. a restart of the system cleared the memory, but after looking at the montioring logs i can see a classic memory leak graph but don't know which process caused it. the system did not shutdown because of the memory leak and the only process affected buy the "out of memroy" was the ISCSI iniator, which only lost connection to the Shared storage device. We are using Lefthand for the storage device and microsoft ISCSI initiator 2.08.The system has not shown any signs of a memeory leak since then.

Hi Customer, For the memory leak issue, you can boot the problematic system with clean boot to check if the issue still exists. Steps to clean boot: 1. Click Start->Run...-> type msconfig and press Enter 2. Click Services tab and select Hide All Microsoft Services and Disable All third party Services. 3. Click Startup tab and Disable All startup items 4. Click OK and choose Restart 5. After reboot, check whether the problem still occurs If the memory leak issue still continues in clean boot mode, for the further troubleshooting, You may check in the Task Manager to see which process takes the memory resources. For example, if the SVCHOST takes the memory in climbing, you need to check which services are running with that SVCHOST process. For other processes such as explorer.exe, iexplorer.exe, you need to check which DLL files are launched by the processes. If the process is a service, you can use these steps to find out what applications are using most of the memory: Open Task Manager, click on the Processes tab, look for the process that is using the memory and note its' PID (Process ID). Please note that you may need to go to the View/Select Columns menu and make sure that PID (Process Identifier) is checked. Once you have the PID run the following from a command prompt: tasklist /svc This should give you the application associated with the PID you identified in the previous step. With the previous steps, you can locate which service or application causes this memory leak and system crash issue. If you want to know the root cause of the issue, we need to analyze the performance log and crash dump file. Since the forum is not the best channel to troubleshoot this issue, I would suggest that you contact Microsoft Customer Support service to troubleshoot this issue efficiently. They are the best resource for this kind of issues. You may obtain the phone numbers for specific technology request please take a look at the web site listed below: https://support.microsoft.com/common/international.aspx?iid=174859&iguid=56907522-6886-4238-a70f-a1d06a4473c7_2_2&rdpath=1 Hope the issue will be resolved soon.This posting is provided "AS IS" with no warranties, and confers no rights.