- ESXi Multiplathing Options
- DELL PowerConnect - What does "iscsi enable" do?
- VMware - LabManager - CannotAccessNetwork error deploying VM
- Nagios - Switch Interface Traffic
- How To - Linux Server Performance
- Notes - Building New ESXi Host for iSCSI with Jumbo Frames
- Microsoft Office Version Numbers (XP, 2003, 2007, 2010)
- ESXi Custom Welcome Screen Text
- PHP - Read Data from a CSV file
- PHP - Input Variables from URL
Fix - WMI Memory Leak
- TidBits:
I noticed the EventLog error below on two new Windows 2008 R2 servers recently deployed. Also I saw the memory utilization was quite high on a server that has not been rolled out yet. The WMIPRVSE.EXE was using > 350 megs of memory.
A little research led me to a Microsoft Hotfix. Hotfix installed, servers restarted, and memory seems much improved. Will monitor for the apphang, but looks good thus far.
KB Article - The "Win32_Service" WMI class leaks memory in Windows Server 2008 R2 and in Windows 7
URL - http://support.microsoft.com/kb/981314
Event Log Entry
Log Name: Application Source: Application Error Date: 9/20/2010 8:43:41 PM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer:Description: Faulting application name: wmiprvse.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc794 Faulting module name: ole32.dll, version: 6.1.7600.16385, time stamp: 0x4a5be01a Exception code: 0xc0000005 Faulting application name: wmiprvse.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc794 Faulting module name: ole32.dll, version: 6.1.7600.16385, time stamp: 0x4a5be01a Exception code: 0xc0000005 Fault offset: 0x00000000000204e4 Faulting process id: 0xb10 Faulting application start time: 0x01cb57b661b70187 Faulting application path: C:\Windows\system32\wbem\wmiprvse.exe Faulting module path: C:\Windows\system32\ole32.dll Report Id: 475ff9b1-c519-11df-aa64-005056ac4510Fault offset: 0x00000000000204e4
- MWalker's blog
- Login to post comments
-
