Windows Xp 64bit splwow64 issue (Thunking Spooler crash) RRS feed

  • Question

  • Hello,

    For the last month and half I have been stumped with an error that has been occuring with only our users running Windows XP Professional 64bit.

    The issues is every once an awhile, while they are printing from excel or any ms office application or Adobe an error pops up saying that the Thunking Spooler APIS from 32 to 64 process has stopped working. To correct this I have done following:

    Re-adding the printers
    Restarting the spooler
    Set the application to compatibility mode with an older version of windows
    Add new printers and set to "Print directly to printer" option (this started causing more problems, so I set it back to spool first)
    Also a user pointed out closing all office applications and relaunching them fixed the issue as well

    All of these worked to temporarily fix the issue, but thats it. I need something more permanent.

    I've also looked at the dump file and it just shows:

    Application exception occurred:
            App: C:\WINDOWS\splwow64.exe (pid=6272)
            When: 1/30/2012 @ 13:57:29.058
            Exception number: c0000005 (access violation)

    *----> System Information <----*
            Computer Name: PCPDSM01P16503
            User Name: umst
            Terminal Session Id: 0
            Number of Processors: 4
            Processor Type: EM64T Family 6 Model 26 Stepping 5
            Windows Version: 5.2
            Current Build: 3790
            Service Pack: 2
            Current Type: Multiprocessor Free
            Registered Organization: Aviva Investors North America
            Registered Owner: AINA

    *----> Task List <----*
       0 System Process
       4 Error 0xD0000022
     300 Error 0xD0000022
     348 Error 0xD0000022
     372 Error 0xD0000022
     420 Error 0xD0000022
     432 Error 0xD0000022
     604 Error 0xD0000022
     656 Error 0xD0000022
     700 Error 0xD0000022
     760 Error 0xD0000022
     828 Error 0xD0000022
    1116 Error 0xD0000022
    1132 Error 0xD0000022
    1304 Error 0xD0000022
    1428 Error 0xD0000022
    1516 Error 0xD0000022
    1624 Error 0xD0000022
    1668 Error 0xD0000022
    1796 Error 0xD0000022
    1820 Error 0xD0000022
    1864 Error 0xD0000022
    1976 Error 0xD0000022
    2152 Error 0xD0000022
    2352 Error 0xD0000022
    2700 Error 0xD0000022
    3024 Error 0xD0000022
    2088 Error 0xD0000022
    2744 Error 0xD0000022
    3216 Explorer.EXE
    3488 RUNDLL32.EXE
    3792 ctfmon.exe
    3820 ctfmon.exe
    4028 PNAMAIN.EXE
    4044 Printkey.exe
    4076 WindowsSearch.exe
    4080 almon.exe
    2528 smax4pnp.exe
    2540 Acrotray.exe
    2812 jusched.exe
     812 bxlaui.exe
    3352 bxlartd.exe
    3132 PresentationFontCache.exe
    4380 WINTRV.EXE
    3860 OUTLOOK.EXE
    4504 blpcbbap.exe
    4572 javaw.exe
    5596 bbcomm.exe
    4376 blpsmarthost.exe
    4100 javaw.exe
    4968 javaw.exe
     552 javaw.exe
    4136 javaw.exe
    2124 IeEmbed.exe
    6424 blpcbbap.exe
    3924 ctm_app.exe
    3676 Acrobat.exe
    7056 Error 0xD0000022
    3468 EXCEL.EXE
    6272 splwow64.exe
    6800 java.exe
    3836 WFCRUN32.EXE
    2916 WFICA32.EXE
    6636 blpcbbap.exe
    6952 blpcbbap.exe
    2956 dwwin.exe
    5500 Error 0xD0000022
    5576 drwtsn32.exe

    *----> Module List <----*
    0000000002160000 - 000000000216a000: C:\WINDOWS\system32\Normaliz.dll
    000000003a000000 - 000000003aad0000: C:\WINDOWS\system32\spool\DRIVERS\x64\3\x2coreH8.dll
    000000003d100000 - 000000003d24a000: C:\WINDOWS\system32\spool\DRIVERS\x64\3\x2rpsH8.dll
    000000004c000000 - 000000004c1b6000: C:\WINDOWS\system32\spool\DRIVERS\x64\3\x2utilH8.dll
    000000004d100000 - 000000004d1ae000: C:\WINDOWS\system32\spool\DRIVERS\x64\3\x2comsH8.dll
    000000004d480000 - 000000004e0f1000: C:\WINDOWS\system32\spool\DRIVERS\x64\3\x2guiH8.dll
    000000004e940000 - 000000004e9b0000: C:\WINDOWS\system32\spool\DRIVERS\x64\3\x2wftuH8.dll
    000000004ef40000 - 000000004ef80000: C:\WINDOWS\system32\spool\DRIVERS\x64\3\Xerox\Language Data\V5.0\en-us\x2txtH8.dll
    000000006fa00000 - 000000006fa3f000: C:\PROGRA~2\Sophos\SOPHOS~1\SOPHOS~2.DLL
    000000006fa40000 - 000000006fa51000: C:\Documents and Settings\All Users\Application Data\Sophos Web Intelligence\swi_lsp_64.dll
    0000000077c20000 - 0000000077d2c000: C:\WINDOWS\system32\USER32.dll
    0000000077d40000 - 0000000077eb3000: C:\WINDOWS\system32\kernel32.dll
    0000000077ec0000 - 0000000077ffc000: C:\WINDOWS\system32\ntdll.dll
    0000000100000000 - 000000010000c000: C:\WINDOWS\splwow64.exe
    000007ff3d0e0000 - 000007ff3d17e000: C:\WINDOWS\system32\spool\DRIVERS\x64\3\PSCRIPT5.DLL
    000007ff41960000 - 000007ff41a34000: C:\WINDOWS\system32\spool\DRIVERS\x64\3\PS5UI.DLL
    000007ff4b220000 - 000007ff4b340000: C:\WINDOWS\system32\WININET.dll
    000007ff4b350000 - 000007ff4b4c7000: C:\WINDOWS\system32\urlmon.dll
    000007ff4bdb0000 - 000007ff4bff3000: C:\WINDOWS\system32\iertutil.dll
    000007ff57040000 - 000007ff57071000: C:\WINDOWS\system32\iphlpapi.dll
    000007ff57140000 - 000007ff573c5000: C:\WINDOWS\system32\ole32.dll
    000007ff58af0000 - 000007ff58b4c000: C:\WINDOWS\system32\msctfime.ime
    000007ff5c750000 - 000007ff5c75d000: C:\WINDOWS\System32\wshqos.dll
    000007ff65040000 - 000007ff65089000: C:\WINDOWS\system32\newdev.dll
    000007ff6d200000 - 000007ff6d293000: C:\WINDOWS\system32\hnetcfg.dll
    000007ff76080000 - 000007ff7609e000: C:\WINDOWS\system32\asycfilt.dll
    000007ff763b0000 - 000007ff76435000: C:\WINDOWS\WinSxS\amd64_Microsoft.Windows.WinHTTP_6595b64144ccf1df_5.1.3790.4929_x-ww_32307663\WINHTTP.dll
    000007ff76470000 - 000007ff76734000: C:\WINDOWS\WinSxS\amd64_Microsoft.Windows.GdiPlus_6595b64144ccf1df_1.0.3790.3959_x-ww_B45BA3BE\gdiplus.dll
    000007ff77140000 - 000007ff7714c000: C:\WINDOWS\system32\WS2HELP.dll
    000007ff77170000 - 000007ff7717b000: C:\WINDOWS\system32\wshtcpip.dll
    000007ff771b0000 - 000007ff7722d000: C:\WINDOWS\system32\mswsock.dll
    000007ff77230000 - 000007ff772af000: C:\WINDOWS\system32\uxtheme.dll
    000007ff77310000 - 000007ff77340000: C:\WINDOWS\system32\WS2_32.dll
    000007ff77370000 - 000007ff77408000: C:\WINDOWS\system32\NETAPI32.dll
    000007ff77c90000 - 000007ff77c97000: C:\WINDOWS\system32\SensApi.dll
    000007ff78f10000 - 000007ff78f51000: C:\WINDOWS\system32\WINSPOOL.DRV
    000007ff794e0000 - 000007ff7950f000: C:\WINDOWS\system32\mscms.dll
    000007ff79c20000 - 000007ff79c4c000: C:\WINDOWS\system32\SPOOLSS.DLL
    000007ff7a410000 - 000007ff7a4af000: C:\WINDOWS\system32\MSCTF.dll
    000007ff7b5e0000 - 000007ff7b608000: C:\WINDOWS\system32\Cabinet.dll
    000007ff7c680000 - 000007ff7c78a000: C:\WINDOWS\system32\USERENV.dll
    000007ff7ce50000 - 000007ff7ce91000: C:\WINDOWS\system32\apphelp.dll
    000007ff7d310000 - 000007ff7d316000: C:\WINDOWS\system32\MSIMG32.dll
    000007ff7d340000 - 000007ff7d36a000: C:\WINDOWS\system32\MSASN1.dll
    000007ff7d370000 - 000007ff7d4cf000: C:\WINDOWS\system32\CRYPT32.dll
    000007ff7d4d0000 - 000007ff7d4ea000: C:\WINDOWS\system32\WINSTA.dll
    000007ff7d500000 - 000007ff7d539000: C:\WINDOWS\system32\IMM32.DLL
    000007ff7daa0000 - 000007ff7daac000: C:\WINDOWS\system32\SHFOLDER.dll
    000007ff7dac0000 - 000007ff7dc38000: C:\WINDOWS\system32\SETUPAPI.dll
    000007ff7e380000 - 000007ff7e390000: C:\WINDOWS\system32\PSAPI.DLL
    000007ff7e3a0000 - 000007ff7e3d9000: C:\WINDOWS\system32\credui.dll
    000007ff7e730000 - 000007ff7e770000: C:\WINDOWS\system32\adsldpc.dll
    000007ff7e940000 - 000007ff7e94b000: C:\WINDOWS\system32\WTSAPI32.dll
    000007ff7e950000 - 000007ff7e9b6000: C:\WINDOWS\system32\WLDAP32.dll
    000007ff7e9c0000 - 000007ff7e9e2000: C:\WINDOWS\system32\Secur32.dll
    000007ff7ea10000 - 000007ff7eaee000: C:\WINDOWS\system32\CLBCatQ.DLL
    000007ff7eaf0000 - 000007ff7ebb6000: C:\WINDOWS\system32\COMRes.dll
    000007ff7ebc0000 - 000007ff7ecd6000: C:\WINDOWS\system32\OLEAUT32.dll
    000007ff7ef60000 - 000007ff7effb000: C:\WINDOWS\system32\SHLWAPI.dll
    000007ff7f000000 - 000007ff7f187000: C:\WINDOWS\WinSxS\amd64_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.3790.3959_x-ww_0A7B2435\comctl32.dll
    000007ff7f190000 - 000007ff7fb9a000: C:\WINDOWS\system32\SHELL32.dll
    000007ff7fbf0000 - 000007ff7fbfb000: C:\WINDOWS\system32\VERSION.dll
    000007ff7fc00000 - 000007ff7fc86000: C:\WINDOWS\system32\msvcrt.dll
    000007ff7fc90000 - 000007ff7fd2c000: C:\WINDOWS\system32\GDI32.dll
    000007ff7fd30000 - 000007ff7fec9000: C:\WINDOWS\system32\RPCRT4.dll
    000007ff7fee0000 - 000007ff7ffe5000: C:\WINDOWS\system32\ADVAPI32.dll


    I looked up what what the access violation meant and it just tells me that it is a very generic error.

    Anyway, they are printing to networked Xerox printers using 64bit drivers. We just got them installed towards the end of last year. Xerox already gave us the newest drivers they have and it didn't fix anything. I have another windows xp 64bit machine setup, but I haven't been able to recreate the problem. Even after I had one of the users login to the machine. Which to me also rules out any profile issues. Replacing the machine is not an option either as they these machines were specially ordered to handle there workloads.

    Finally I did read up on the splwow64 proccess. From the beginning we have figured this was the culprit but didn't want to rule anything out. All the research and testing just furthers are belief this is still the case. Since the process can't emulate a print job from 32bit to 64bit, is there any other way around this. Has microsoft created a hot fix for this yet? It seems to be a major problem that it isn't getting addressed.

    • Moved by Leo Huang Thursday, February 16, 2012 3:14 AM Windows XP problem (From:Windows 7 Miscellaneous)
    Tuesday, February 14, 2012 4:59 PM

All replies

  • Sorry, but you are in the WRONG forum!!

    The title of this forum is Windows 7, not Windows XP!

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

    Tuesday, February 14, 2012 6:13 PM
  • Woops!!!!
    Tuesday, February 14, 2012 6:34 PM