A Stop 0x50 error may occurs in Partmgr.sys after unplugging a network cable in Windows Server 2003

Support for Windows Server 2003 ended on July 14, 2015

Microsoft ended support for Windows Server 2003 on July 14, 2015. This change has affected your software updates and security options. Learn what this means for you and how to stay protected.

After disconnecting a network cable from a network adapter in Windows Server 2003, you may see the following bluescreen:

STOP 0x00000050 (0x00000008, 0x00000000, 0xf74c88cc, 0x00000000)

Note: The address shown in the third argument above may change.

This is a rare timing issue that can occur when disconnecting a network cable from a network adapter while the server is under heavy stress. Having disk performance counters enabled in Performance Monitor may increase the chances of the bluescreen occurring. If you encounter this bluescreen, try disabling disk performance counters in Performance Monitor and do not disconnect the network cable while the server is powered on.
Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

Article ID: 2598819 - Last Review: 08/15/2011 19:12:00 - Revision: 2.0

Microsoft Windows Server 2003 Service Pack 2

  • KB2598819