re: [UNRESOLVED] Win2008R2 SP1: STOP 0x3B in RDPDD!CAutoDrvCheck::CAutoDrvCheck+5d

François Uldry — Mon, 10 Jun 2013 00:00:55 GMT

I do have more or less this issue, with a SINGLE cpu.

FOLLOWUP_IP:

RDPDD!CAutoDrvCheck::CAutoDrvCheck+5d

BUCKET_ID: X64_0x3B_RDPDD!CAutoDrvCheck::CAutoDrvCheck+5d

STACK_TEXT:

fffff880`045ab490 fffff960`00ad2500 : 00000000`0000006a fffff800`016d9d32 00000000`00000000 00000000`000000de : RDPDD!CAutoDrvCheck::CAutoDrvCheck+0x5d

fffff880`045ab4c0 fffff960`000768fa : fffff900`c00c2000 00000000`000000de fffff900`c00bf028 fffffa80`00000003 : RDPDD!DrvMovePointerEx+0x28

fffff880`045ab4f0 fffff960`00076600 : fffffa80`0d7ed810 00000000`0000006a fffff900`c00c2000 00000000`00000000 : win32k!vMovePointer+0x7a

fffff880`045ab530 fffff960`0015b6a3 : fffffa80`0f3fa5f0 00000000`00000000 00000000`0000006a 00000822`00c80000 : win32k!GreMovePointer+0x17c

fffff880`045ab5c0 fffff960`0015a081 : fffff900`c0181e04 00000000`00c67d7a fffff900`c0181ca0 00000000`00c67d7a : win32k!xxxMoveEventAbsolute+0x203

fffff880`045ab650 fffff960`00159ed8 : fffff900`c0181ca0 0000006a`000000de 00000000`00000000 00000000`00000286 : win32k!ProcessMouseInput+0x195

fffff880`045ab6c0 fffff800`016c3651 : 00000000`00000100 00000000`00000000 00000000`00000000 00000000`00000001 : win32k!InputApc+0x7c

fffff880`045ab6f0 fffff800`016c681d : fffffa80`0e0013b0 00000000`00000000 fffff960`00159e5c 00000000`00000000 : nt!KiDeliverApc+0x201

fffff880`045ab770 fffff800`016d30da : 00000000`00000000 00000000`00000000 fffffa80`00000000 fffff800`016c6612 : nt!KiCommitThreadWait+0x3dd

fffff880`045ab800 fffff960`000fa708 : fffff900`00000002 fffffa80`0d1511b0 fffff900`00000001 fffff880`0000000d : nt!KeWaitForMultipleObjects+0x272

fffff880`045abac0 fffff960`000fb6d3 : 00000000`00000000 fffff900`c015f500 fffff960`003477c0 00000000`00000004 : win32k!xxxMsgWaitForMultipleObjects+0x108

fffff880`045abb40 fffff960`000b51c4 : fffffa80`00000001 fffffa80`0000000c fffffa80`0e0013b0 fffff6fc`40022a08 : win32k!xxxDesktopThread+0x253

fffff880`045abbc0 fffff960`0013629a : fffffa80`00000001 fffff960`003477c0 00000000`00000020 00000000`00000000 : win32k!xxxCreateSystemThreads+0x64

fffff880`045abbf0 fffff800`016cfe93 : fffffa80`0e0013b0 00000000`00000004 000007ff`fffac000 00000000`00000000 : win32k!NtUserCallNoParam+0x36

fffff880`045abc20 000007fe`fd2c1eea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13

2 years ago when we opened up a paid call with support we got told that single CPU would fix the issue. it NEVER did.

François

re: [UNRESOLVED] Win2008R2 SP1: STOP 0x3B in RDPDD!CAutoDrvCheck::CAutoDrvCheck+5d

Vladislav — Thu, 22 Nov 2012 15:26:18 GMT

I use Windows 2008R2 64-bit, and I see more-or-less the same problems. I can provide some more technical details.

The problem reproduces when creating and destroying sessions rapidly. MSTSC That is, create several sessions, and then destroy them and create new ones rapidly. ActiveX control may be used for this.

Eventually the OS starts to "misbehave" regarding the display driver (RDPDD). This may include the following:

Call to DrvEnablePDEV, whereas the same PDEV is already enabled (i.e. DrvDisablePDEV was not called).

Call to DrvDisableDriver, whereas the driver still manages a PDEV (i.e. DrvDisablePDEV was not called).

Call to DrvDisablePDEV, whereas there are still device bitmap managed (i.e. they were not destroyed by DrvDeleteDeviceBitmap).

It seems like the OS eventually "leaks" the allocated display driver resources. This in turn causes problems in RDPDD (such as page fault and etc.).