Time for you to do … exactly nothing for a month, because Microsoft has pushed out another UR for Windows 8, Windows RT, and Windows Server 2012. So make sure this sucker is unapproved and sits like that for a month until some other sucker has tested it for you. If there is a problem (and based on the last 12 months, there probably is one or more) then let that other person find the issue, report it, and Microsoft re-issue a fixed update rollup.
After digging into the contents of the update, we can see that there are networking fixes and a cluster fix. The latter is KB2876391, "0x0000009E" Stop error on cluster nodes in a Windows Server-based multi-node failover cluster environment.
Assume that you have a Windows Server 2008 R2 Service Pack 1 (SP1) or Windows Server 2012-based multi-node failover cluster that uses the Microsoft Device Specific Module (MSDSM) and Microsoft Multipath I/O (MPIO). The following events occur at almost the same time:
- A new instance of an existing device arrives. Specifically, a new path to an MPIO disk is generated.
- MSDSM finishes an I/O request. The request was the last outstanding I/O request.
In this scenario, some cluster nodes crash. Additionally, you receive a Stop error message that resembles the following:
STOP: 0x0000009E (parameter1, parameter2, parameter3, parameter4)
- This Stop error describes an USER_MODE_HEALTH_MONITOR issue.
- The parameters in this Stop error message vary, depending on the configuration of the computer.
- Not all "Stop 0x0000009E" errors are caused by this issue.
This issue occurs because a remove lock on a logical unit number (LUN) is obtained two times, but only released one time. Therefore, the Plug and Play (PnP) manager cannot remove the device, and then the node crashes.
The hotfix is included in the UR. Despite what the Premier Sustained Engineering author wrote, this is not just for “Windows Server 2008 R2 SP1-based multi-node failover cluster environment” but it is also for WS2012.