[RESOLVED] Win2008R2 RTM/SP1: STOP 0x27 in rdbss!RxSelectPagingFileObject+9a

  • Article

Status: Resolved

Update 111019: Finally an update on this... KB2584874 will be released in November timeframe (HTP11-11) for this.

We've come across a couple of customers who have machines hitting a STOP 0x27 with the following stack:

5: kd> knL
 # Child-SP RetAddr Call Site
00 fffff880`0aad1590 fffff800`018a1bbb nt!MiCanFileBeTruncatedInternal+0x2e
01 fffff880`0aad1610 fffff880`04a035fa nt!MmCanFileBeTruncated+0x23
02 fffff880`0aad1650 fffff880`04a23dac rdbss!RxSelectPagingFileObject+0x9a
03 fffff880`0aad16a0 fffff880`04a0469c rdbss!RxCommonClose+0x51c
04 fffff880`0aad1740 fffff880`04a21b54 rdbss!RxFsdCommonDispatch+0x870
05 fffff880`0aad1830 fffff880`013ee2cc rdbss!RxFsdDispatch+0x224
06 fffff880`0aad18a0 fffff880`01d4d271 mrxsmb!MRxSmbFsdDispatch+0xc0
07 fffff880`0aad18e0 fffff880`01d4b138 mup!MupiCallUncProvider+0x161
08 fffff880`0aad1950 fffff880`01d4c7fa mup!MupStateMachine+0x128
09 fffff880`0aad19a0 fffff880`017566af mup!MupClose+0x146
0a fffff880`0aad19f0 fffff800`01b7f88e fltmgr!FltpDispatch+0x9f
0b fffff880`0aad1a50 fffff800`0188d514 nt!IopDeleteFile+0x11e
0c fffff880`0aad1ae0 fffff800`01b7a484 nt!ObfDereferenceObject+0xd4
0d fffff880`0aad1b40 fffff800`01b7aa34 nt!ObpCloseHandleTableEntry+0xc4
0e fffff880`0aad1bd0 fffff800`018828d3 nt!ObpCloseHandle+0x94
0f fffff880`0aad1c20 00000000`7777140a nt!KiSystemServiceCopyEnd+0x13

The failure bucket for this error is X640x27_rdbss!RxSelectPagingFileObject+9a.

So far, we have unable to reproduce the problem in-house. In all four customer environments the CommVault backup software (cvmountd.exe) is triggering (not causing!) the problem in rdbss.sys. This could be due to the very high context switching for some of the CommVault (worker) threads. This context could be triggering a race condition, which is at the root of the rdbss issue. The issue itself is a premature free of an FCB.

We now have a private hotfix package that has been running with various customers for several weeks without a problem. The public hotfix is planned for release as part of the October Hotfix Test Pass (HTP11-10).

Should your machines experience this, then please contact me so we can help you out!