Frozen app waiting for spooler ?? RRS feed

  • Question

  • Hi all

    I have a dump from a costumer who regularly gets our application to freeze
    the call stack shown below.
    From stack I assume there is a problem with spooler or printer.

    Question is how to determine the process and thread id that my process is waiting for ?
    ( I assume it is somewhere in the parameters to rpcrt4!NdrClientCall2)
    What could be the reason for not returning from NdrClientCall2 ?

    Kjell Gunnar

     ------ output ------

    Windows XP Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible

    0:000> kbL 20
    ChildEBP RetAddr  Args to Child             
    0012ee04 7c90dacc 77e7cac1 00000b2c 0b8de680 ntdll!KiFastSystemCallRet
    0012ee08 77e7cac1 00000b2c 0b8de680 0b8de680 ntdll!NtRequestWaitReplyPort+0xc
    0012ee54 77e7a33e 0b8de6b8 0012ee74 77e7a36f rpcrt4!LRPC_CCALL::SendReceive+0x228
    0012ee60 77e7a36f 0012ee90 73003e98 0012f26c rpcrt4!I_RpcSendReceive+0x24
    0012ee74 77ef4675 0012eebc 0b8de6cc 00000000 rpcrt4!NdrSendReceive+0x2b
    0012f250 73008ba8 73003e98 73002b8e 0012f26c rpcrt4!NdrClientCall2+0x222
    0012f264 73008b47 0020c6e8 00000008 0b8d6ad0 winspool!RpcStartPagePrinter+0x1b
    0012f29c 77f473db 00232904 0012f2f4 ffffffff winspool!StartPagePrinter+0x38
    0012f2d0 02aea21a ffffffff 00000000 422104d5 gdi32!MFP_StartPage+0x154
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    0012f354 791dd644 7c90d89c 7c80a4cb 0012f374 <Unloaded_ctr.ocx>+0x2aea109
    0012f728 0e92a0f7 00000111 0b823b28 00000001 mscorwks!CallCompileMethodWithSEHWrapper+0x66
    0012f774 7c158440 0c0c7450 0b823b28 0c0c7450 <Unloaded_ctr.ocx>+0xe929fe6
    0012f788 7c1581fd 0c0c7450 00002f4d 00000000 mfc70!_AfxDispatchCmdMsg+0x3d
    0012f7b8 7c1cf83f 00002f4d 00000000 00000000 mfc70!CCmdTarget::OnCmdMsg+0x10a
    0012f7dc 7c158d2f 00002f4d 00000000 00000000 mfc70!CPropertySheet::OnCmdMsg+0x1b
    0012f82c 7c1cf38c 00000000 0042060a 0c0c7450 mfc70!CWnd::OnCommand+0x51
    0012f848 7c157c3e 00002f4d 0042060a 00000110 mfc70!CPropertySheet::OnCommand+0x16
    0012f8dc 7c1579cb 00000111 00002f4d 0042060a mfc70!CWnd::OnWndMsg+0x2f
    0012f8fc 7c15797f 00000111 00002f4d 0042060a mfc70!CWnd::WindowProc+0x22
    0012f95c 7c157900 0c0c7450 00000000 00000111 mfc70!AfxCallWndProc+0x93
    0012f978 7c1578bf 01310550 00000111 00002f4d mfc70!AfxWndProc+0x2b
    0012f9a4 7e418734 01310550 00000111 00002f4d mfc70!AfxWndProcBase+0x39
    0012f9d0 7e418816 7c157886 01310550 00000111 user32!InternalCallWinProc+0x28
    0012fa38 7e42927b 0015a478 7c157886 01310550 user32!UserCallWinProcCheckWow+0x150
    0012fa74 7e4292e3 001381c0 0111dca8 00002f4d user32!SendMessageWorker+0x4a5
    0012fa94 773f7354 01310550 00000111 00002f4d user32!SendMessageW+0x7f
    0012fab4 773f7436 00247e98 00000000 000a0046 comctl32!Button_NotifyParent+0x3d
    0012fad0 773f973b 00247e98 00000001 0012fbc8 comctl32!Button_ReleaseCapture+0xd7
    0012fb60 7e418734 0042060a 00000202 00000000 comctl32!Button_WndProc+0x887
    0012fb8c 7e418816 773f8eb4 0042060a 00000202 user32!InternalCallWinProc+0x28
    0012fbf4 7e42a013 0015a478 773f8eb4 0042060a user32!UserCallWinProcCheckWow+0x150
    0012fc24 7e42a998 ffff031b 0042060a 00000202 user32!CallWindowProcAorW+0x98

    Wednesday, April 13, 2011 2:23 PM

All replies