Status: Resolved

Note: the hotfix now also includes an update for Windows Server 2008 R2.

130624: over the past few months I've seen this bugcheck occur with quite a few customers so I figured perhaps it would help some of you out there as well... I've also added this as a response under Online Crash Analysis. This means that after it has been reviewed and approved, the next time your machine encounters this crash, and you submit the crash information to Microsof when asked (and I hope you all do!), you will get a response in Action Center, pointing you to the relevant KB article. This means that you don't have to log cases for this issue anymore, or that you need to stroll the internet searching for a resolution... How cool is that? :)

Anyway, here is the crash information:

FAILURE_BUCKET_ID:  AV_msdsm!DsmpQueryLoadBalancePolicy

3: kd> knL
 # Child-SP          RetAddr           Call Site
00 fffff880`062d7ec8 fffff800`31086369 nt!KeBugCheckEx
01 fffff880`062d7ed0 fffff800`31084be0 nt!KiBugCheckDispatch+0x69
02 fffff880`062d8010 fffff880`01296e75 nt!KiPageFault+0x260
03 fffff880`062d81a0 fffff880`01296b15 msdsm!DsmpQueryLoadBalancePolicy+0x2a1
04 fffff880`062d8200 fffff880`00a6fa85 msdsm!DsmQueryData+0x22d
05 fffff880`062d8270 fffff880`01072293 mpio!MPIODsmQueryDataBlock+0x1d1
06 fffff880`062d8420 fffff880`00a714f9 WMILIB!WmiSystemControl+0x27f
07 fffff880`062d8510 fffff880`00a55afc mpio!MPIOPdoWmi+0x75
08 fffff880`062d8580 fffff880`01c3d386 mpio!MPIOWmiDispatch+0x94
09 fffff880`062d85f0 fffff880`0137663d CLASSPNP!ClassSystemControl+0x4dd
0a fffff880`062d86c0 fffff800`313b7784 partmgr!PmSystemControl+0x7d
0b fffff880`062d86f0 fffff800`314c6457 nt!WmipForwardWmiIrp+0x13c
0c fffff880`062d8770 fffff800`313b7427 nt!WmipQuerySetExecuteSI+0x27f
0d fffff880`062d8880 fffff800`3147042f nt!WmipIoControl+0x32b
0e fffff880`062d89d0 fffff800`31470db6 nt!IopXxxControlFile+0x7dd
0f fffff880`062d8b60 fffff800`31086053 nt!NtDeviceIoControlFile+0x56
10 fffff880`062d8bd0 000007ff`d4032c1a nt!KiSystemServiceCopyEnd+0x13

Please log a case with Microsoft Support when you encounter this issue!