Freigeben über

[RESOLVED] Win2008R2/SP1: STOP 0xA in msiscsi!iSpGetConnectionList+157

  • Artikel

Status: Resolved.

Update 121122: I noticed I did not yet close off this one... :$ It's resolved in KB2536875.

One of my colleagues provided me with this STOP 0xA in msiscsi!iSpGetConnectionList+157, of which the stack shows:

14: kd> knL
 # Child-SP RetAddr Call Site
00 fffff880`0a2c09a8 fffff800`01c78b69 nt!KeBugCheckEx
01 fffff880`0a2c09b0 fffff800`01c777e0 nt!KiBugCheckDispatch+0x69
02 fffff880`0a2c0af0 fffff800`01c8b20c nt!KiPageFault+0x260
03 fffff880`0a2c0c80 fffff800`0211b3f5 nt!IoAcquireRemoveLockEx+0x24
04 fffff880`0a2c0cf0 fffff880`0484014f nt!VerifierIoAcquireRemoveLockEx+0x65
05 fffff880`0a2c0d30 fffff880`0486bac3 msiscsi!iSpGetConnectionList+0x157
06 fffff880`0a2c0de0 fffff880`0486aa8c msiscsi!iSpBuildRequestTimeStatistics+0x77
07 fffff880`0a2c10a0 fffff880`048581a3 msiscsi!iScsiQueryWmiDataBlock+0x3dc
08 fffff880`0a2c1120 fffff880`0485843b msiscsi!ScsiWmipProcessRequest+0x207
09 fffff880`0a2c1190 fffff880`0486a676 msiscsi!ScsiPortWmiDispatchFunction+0x77
0a fffff880`0a2c1200 fffff880`0482fe10 msiscsi!iScsiWmiSrb+0x9e
0b fffff880`0a2c1250 fffff880`01379f29 msiscsi!iScsiStartIo+0x130
0c fffff880`0a2c12d0 fffff880`0138efb9 storport!RaidAdapterPostScatterGatherExecute+0xe9
0d fffff880`0a2c1320 fffff880`013cfaf6 storport!RaidAdapterExecuteXrb+0x29
0e fffff880`0a2c1350 fffff880`013cfd79 storport!RaWmiPassToMiniPort+0x286
0f fffff880`0a2c13b0 fffff880`013cff00 storport!RaWmiIrpNormalRequest+0x49
10 fffff880`0a2c13e0 fffff880`013cffd7 storport!RaWmiDispatchIrp+0x140
11 fffff880`0a2c1440 fffff800`0211f750 storport!RaDriverSystemControlIrp+0x67
12 fffff880`0a2c1480 fffff800`01f158d0 nt!IovCallDriver+0xa0
13 fffff880`0a2c14e0 fffff800`01f0be46 nt!WmipForwardWmiIrp+0x16c
14 fffff880`0a2c1560 fffff800`02050e7f nt!WmipQueryAllData+0x1ca
15 fffff880`0a2c1730 fffff800`01fbf28e nt!WmipQueryAllDataMultiple+0x1af
16 fffff880`0a2c1860 fffff800`0211f750 nt!WmipIoControl+0xb323e
17 fffff880`0a2c19b0 fffff800`01f956b7 nt!IovCallDriver+0xa0
18 fffff880`0a2c1a10 fffff800`01f95f16 nt!IopXxxControlFile+0x607
19 fffff880`0a2c1b40 fffff800`01c78853 nt!NtDeviceIoControlFile+0x56
1a fffff880`0a2c1bb0 00000000`7733ff2a nt!KiSystemServiceCopyEnd+0x13

The problem is caused by a synchronization issue in msiscsi.sys, which is going to be addressed in KB2536875, that is scheduled to be released as part of the June 2011 Hotfix Release Cycle (HTP11-06). Currently one of our customers is validating the private we have provided him with.