locked
Print driver host for 32bit applications has stopped working RRS feed

  • Question

  • Hello,

    I have a machine that displaying the following error message: Print driver host for 32bit applications has stopped working
    I have the correct drivers installed, and I have already tried removing/reinstalling them.
    I tried looking up dlxbmzim.dll but found literally nothing.
    We have a Kyocera Mita KN-1650 on a domain server running Windows Server 2k3 Standard, and the workstation is running Windows 7 Pro x64.
    Can anyone shed some light on this?
    Thanks!

    here are the contents of the WER:

    Version=1
    EventType=APPCRASH
    EventTime=129835806930879000
    ReportType=2
    Consent=1
    ReportIdentifier=bcb590f9-b0ed-11e1-9212-08edb900af26
    IntegratorReportIdentifier=bcb590f8-b0ed-11e1-9212-08edb900af26
    Response.type=4
    Sig[0].Name=Application Name
    Sig[0].Value=splwow64.exe
    Sig[1].Name=Application Version
    Sig[1].Value=6.1.7601.17514
    Sig[2].Name=Application Timestamp
    Sig[2].Value=4ce7b4c8
    Sig[3].Name=Fault Module Name
    Sig[3].Value=dlxbmzim.dll
    Sig[4].Name=Fault Module Version
    Sig[4].Value=0.3.0.0
    Sig[5].Name=Fault Module Timestamp
    Sig[5].Value=4863fac9
    Sig[6].Name=Exception Code
    Sig[6].Value=c0000005
    Sig[7].Name=Exception Offset
    Sig[7].Value=0000000000069a75
    DynamicSig[1].Name=OS Version
    DynamicSig[1].Value=6.1.7601.2.1.0.256.48
    DynamicSig[2].Name=Locale ID
    DynamicSig[2].Value=1033
    DynamicSig[22].Name=Additional Information 1
    DynamicSig[22].Value=2efa
    DynamicSig[23].Name=Additional Information 2
    DynamicSig[23].Value=2efa28bbffe8cad8533ab9281826d9bc
    DynamicSig[24].Name=Additional Information 3
    DynamicSig[24].Value=33a9
    DynamicSig[25].Name=Additional Information 4
    DynamicSig[25].Value=33a96634c67abbe7bb4a2b1b3b9b9c82
    UI[2]=C:\Windows\splwow64.exe
    UI[3]=Print driver host for 32bit applications has stopped working
    UI[4]=Windows can check online for a solution to the problem.
    UI[5]=Check online for a solution and close the program
    UI[6]=Check online for a solution later and close the program
    UI[7]=Close the program
    LoadedModule[0]=C:\Windows\splwow64.exe
    LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
    LoadedModule[2]=C:\Windows\system32\kernel32.dll
    LoadedModule[3]=C:\Windows\system32\KERNELBASE.dll
    LoadedModule[4]=C:\Windows\system32\ADVAPI32.dll
    LoadedModule[5]=C:\Windows\system32\msvcrt.dll
    LoadedModule[6]=C:\Windows\SYSTEM32\sechost.dll
    LoadedModule[7]=C:\Windows\system32\RPCRT4.dll
    LoadedModule[8]=C:\Windows\system32\USER32.dll
    LoadedModule[9]=C:\Windows\system32\GDI32.dll
    LoadedModule[10]=C:\Windows\system32\LPK.dll
    LoadedModule[11]=C:\Windows\system32\USP10.dll
    LoadedModule[12]=C:\Windows\system32\WINSPOOL.DRV
    LoadedModule[13]=C:\Windows\system32\IMM32.DLL
    LoadedModule[14]=C:\Windows\system32\MSCTF.dll
    LoadedModule[15]=C:\Windows\system32\RpcRtRemote.dll
    LoadedModule[16]=C:\Windows\system32\secur32.dll
    LoadedModule[17]=C:\Windows\system32\SSPICLI.DLL
    LoadedModule[18]=C:\Windows\system32\credssp.dll
    LoadedModule[19]=C:\Windows\system32\spool\DRIVERS\x64\3\dlxbmziu.dll
    LoadedModule[20]=C:\Windows\system32\SHELL32.dll
    LoadedModule[21]=C:\Windows\system32\SHLWAPI.dll
    LoadedModule[22]=C:\Windows\system32\ole32.dll
    LoadedModule[23]=C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_fa396087175ac9ac\Comctl32.dll
    LoadedModule[24]=C:\Windows\system32\spool\DRIVERS\x64\3\dlxbmkdm.dll
    LoadedModule[25]=C:\Windows\system32\spool\DRIVERS\x64\3\dlxbmzir.xrs
    LoadedModule[26]=C:\Windows\system32\spool\DRIVERS\x64\3\dlxbmzim.dll
    LoadedModule[27]=C:\Windows\system32\SHFOLDER.dll
    LoadedModule[28]=C:\Windows\system32\spool\DRIVERS\x64\3\dlxbmz.xrs
    FriendlyEventName=Stopped working
    ConsentKey=APPCRASH
    AppName=Print driver host for 32bit applications
    AppPath=C:\Windows\splwow64.exe

    Thursday, June 14, 2012 5:21 PM

Answers

All replies

  • This driver file dlxbmzim.dll  is corrupting the memory of the splwow64.exe process and it's terminating.  The software vendor needs to investigate this issue.

    Make sure you send the crash dump files to Microsoft.  They will get routed to the correct vendor.

    I too looked for dlxbmzim and found your other post.  When I see dlnnnn my first thought is Dell. If the file exists on the machine just open the file properties in explorer.  The Copyright information usually lists the software provider name.

    http://answers.microsoft.com/en-us/windows/forum/windows_7-hardware/print-driver-host-for-32bit-applications-has/be981a1d-cddf-403a-b36b-4dbcb7a26d97


    Alan Morris Windows Printing Team

    Friday, June 15, 2012 1:18 AM
    Answerer
  • Thank you, sir!

    I found out they do have a couple Dell printers. I'll verify if this particular user needs those, and if not remove them from her machine. Is there anything else I could do for the short-term to temporarily resolve this until the vendor patches this?

    Thanks!

    Tuesday, June 19, 2012 3:52 PM