The following is a Primus(R) eServer solution:

ID: emc207833
Domain: EMC1
Solution Class: 3.X Compatibility

Goal       ETA emc207833: PowerPath, Non-EMC Product: Microsoft MPIO causes memory leak in Multi-
Path Windows environments including native MPIO, EMC PowerPath and MPIO solutions from other
vendors based on Microsoft MPIO.

Fact       EMC Technical Advisory

Fact       OS: Microsoft Windows 2003 SP1 (x86, x64, and IA64)

Fact       OS: Microsoft Windows 2003 SP2 (x86, x64, and IA64)

Fact       Application SW: Microsoft MPIO 1.21

Fact       Application SW: Microsoft MPIO 1.22

Fact       EMC Software:  PowerPath 5.2 Build 146

Fact       EMC Software:  PowerPath 5.2 SP1

Symptom    Memory leak attributed to PowerPath 5.2 or 5.2 SP1 due to the Microsoft MPIO tag showing
steady increase in usage of non-paged memory pool. This can lead to applications stopping, or to a blue
screen when the non-paged memory pool becomes fully depleted.

Cause      
This issue is caused by a memory leak in the Microsoft MPIO driver (there are two different memory
leaks):
Microsoft MPIO 1.21:   Installed with PowerPath 5.2
Occurs only in Windows 2003 SP1/SP2 clustered environments. 
Occurs only on I/O on cluster reserves. In summary, this issue will only occur on configurations where
SCSI reservations are present (For example, Microsoft Cluster, etc.).
Refer to knowledgebase solution emc193379 for more information.
Microsoft MPIO 1.22:   Installed with PowerPath 5.2 SP1
Occurs in 2003 SP1/SP2, clustered and non-clustered environments.  
It can be triggered by any software installed on the server that is capable of calling either of the
following function calls: IOCTL_MPIO_PASS_THROUGH_PATH and
IOCTL_MPIO_PASS_THROUGH_PATH_DIRECT 
It is currently known to be triggered by EMC Navisphere Agent 6.26 or the HP Management agent "Fibre
Array Information agent" v7.60.
Refer to knowledgebase solution emc204506 for more information.

Fix        Fix (Prefered Method)

Upgrade to PowerPath 5.3 - this ships with MPIO 1.23. Both memory leaks are resolved in this version of
MPIO. MPIO 1.23 can also be downloaded from either Powerlink (Powerpath for Windows Utilities)
or directly from Microsoft webpage. 
Workaround Solution A:
Use the EMC MPIOUpdate Utility to upgrade to MPIO 1.23 (Please note the previous utility to
downgrade MPIO to version 1.18 has been replaced by this new one).  This requires only a single reboot
and can be done on either PowerPath 5.2 or PowerPath 5.2 SP1. 
Note: You must delete any PowerPath custom file (powermt.custom) that is already on the host before
installing the MPIOUpdate Utility.
Note: If using the iSCSI initiator, if you update the iSCSI initiator, do not enable the "Microsoft
MPIO Multipathing Support for iSCSI" option. Enabling this option will update the existing MPIO driver.
This utility can be downloaded from the PowerPath download page on Powerlink in the PowerPath for
Windows Utilities section at the bottom.
Workaround Solution B:
The resolution depends on the Microsoft MPIO version:
Microsoft MPIO 1.21:   Installed with PowerPath 5.2
                                          Downgrade to PowerPath 5.1 (installs Microsoft MPIO 1.18).
                                          Upgrade to PowerPath 5.2 SP1 (installs Microsoft MPIO 1.22).  However, this
may introduce the second memory leak.
Microsoft MPIO 1.22:   Installed with PowerPath 5.2 SP1
                                          Downgrade to PowerPath 5.1 (installs Microsoft MPIO 1.18) or stop and disable
the offending service(s).  I.E., EMC Navisphere Agent 6.26 or HP Management agent "Fibre Array
Information agent" v7.60.
Note: Stopping and disabling the offending service(s) resolves the issue.  However, if new or unknown
applications are installed that call these function calls then the issue will reappear.
Installing PowerPath 5.1 on top of PowerPath 5.2 / 5.2 SP1 will not necessarily downgrade the MPIO
version.
The correct method to use to downgrade would be to uninstall PowerPath 5.2 / 5.2 SP1, reboot, install
PowerPath 5.1 and reboot.
The Installation Guide recommends that the installation be done with a single path present.