Hi, This is a complete guess, but what is the condition of the hard drive in the machine? Have you run a de-frag recently? The reason I suggest this is if the drive that the VMEM is on might be on its last legs. There is another possibility that there is a mem leak somewhere. Martin If you find my information useful, please rate it. :-)

I've been running about 20 websites with SQL server on a 4GB Windows 2003 machine for last 5 years without a glitch or one restart. I just moved to a New 8GB ram WINDOWS 2008 R2 machine. This new server is faster but extremly unstable and is running out of Virtual Memory every 3 days. Just before the time it crashes I see in the error log: ================================================ Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: sqlservr.exe (1292) consumed 248 500 224 bytes, w3wp.exe consumed 233 750 528 bytes svchost.exe (844) consumed 32 579 584 bytes. ================================================ Also: <Channel>Microsoft-Windows-Resource-Exhaustion-Detector/Operational</Channel> -<UserData> - <CommitLimitExhaustion xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://www.microsoft.com/Windows/Resource/Exhaustion/Detector/Events"> <SystemCommitLimit>34320846848</SystemCommitLimit> <SystemCommitCharge>34274426880</SystemCommitCharge> </CommitLimitExhaustion> </UserData> </Event> ============================================= As You see the virtual memory limit is about 32GB and it just ran out. While top 3 processes consume only about 500MB. It's really weird. Does anyone have any clue what's going on here? I also found high level of Remote Desktop "invalid password" logs, it looks like a brute force dicitionary attach on the remote desktop, I changed the default port. Could this RD attack cause the OS to run out of memory? Thanks for any suggestion what may cause this.

Hi, This is a complete guess, but what is the condition of the hard drive in the machine? Have you run a de-frag recently? The reason I suggest this is if the drive that the VMEM is on might be on its last legs. There is another possibility that there is a mem leak somewhere. Martin If you find my information useful, please rate it. :-)

Go through this link http://sqldave.com/?p=213 http://msdn.microsoft.com/en-us/library/ms190730%28v=SQL.100%29.aspx