This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
**Original Title**Upgraded to Windows 7 and installed print driver, now when I try to print, I get this message: 'Print driver host for 32 bit applications has stopped working'
I just upgraded from Windows XP to Windows 7(64 bit) and have a Xerox Phaser 6180MFP. I downloaded the 64 bit driver and installed it. The test page printed out just fine during installation. Now I'm trying to print from Word 2003 and from Internet Explorer 8 and all I get is a message that 'print driver host for 32bit applications has stopped working'. The system cannot solve the problem and I can't find anything helpful on the microsoft support site.
Can anyone help?
Thanks.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Most likely the Lexmark driver is corrupting the memory of the splwow64.exe process. Launch the 64bit version of IE rather than the 32bit version. The splwow64 process is only used by 32bit applications.
Alan Morris Windows Printing Team; Search the Microsoft Knowledge Base here: http://support.microsoft.com/search/Default.aspx?adv=1
Xerox has new driver for Phaser 6130 that fixes the issue dated 3-25-2011
I'm back!
My apologies for the troubles people have been encountering when contacting support for help with this issue. My original posting should have included additional information regarding how to receive support when calling from outside North America.
To find the correct contact information for your country, go to Xerox.com and check to make sure the country setting in the top right corner reflects your country. Then, click on the Contact Us link. You will see a list of phone numbers under the Customer Service heading. I have included an example of what you would see for the UK. When you call the Welcome Center for technical assistance, please request to be directed to 2nd level support. Our 2nd level support representatives can access the beta drivers you need to fix this problem. We expect to have the drivers available publicly on Xerox.com soon. In the meantime, this route should get you the assistance you need.
| Customer Service |
|---|
| For General enquiries call us on 0870 873 3873 or<br>email us. Non-technical enquiries only. <br><br> <br><br>For Account enquiries call us on <br><br>0870 400 8904/5 or email us. <br><br>Account and Machine Serial number required <br><br> <br><br>For technical enquiries please call our Welcome Centre on 0870 900 5501 <br><br>A Machine Serial Number is required <br><br> <br><br>For Paper, Consumables and other Supplies call 0870 900 5503 |
|---|
Hi Alan
I have the same problem. Windows 7, Xerox printer (Phaser 6280DN) using drivers downloaded from windows update. It works OK with 64 bit applications (internet explorer 64 bit, and print test page all work ok). However, when using any other application (in this case Open Office 3.1.1), I get the same "Print Driver Host for 32 bit applications has stopped working" error.
Below is one of my report.wer outputs as requested for previous poster.
Any guidance on how to resolve would be greatly appreciated.
Chris
Version=1
EventType=APPCRASH
EventTime=129056989676190080
ReportType=2
Consent=1
UploadTime=129056991473313236
ReportIdentifier=36d5bc79-ec99-11de-8e82-0024e8e7e3f6
IntegratorReportIdentifier=36d5bc78-ec99-11de-8e82-0024e8e7e3f6
Response.BucketId=7235262
Response.BucketTable=4
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=splwow64.exe
Sig[1].Name=Application Version
Sig[1].Value=6.1.7600.16385
Sig[2].Name=Application Timestamp
Sig[2].Value=4a5bd3ca
Sig[3].Name=Fault Module Name
Sig[3].Value=xrpscznr.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=0.3.1281.4208
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=4845160c
Sig[6].Name=Exception Code
Sig[6].Value=c000041d
Sig[7].Name=Exception Offset
Sig[7].Value=0000000000011bc7
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7600.2.0.0.768.3
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=2057
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=5be7
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=5be7fb6df65c067feab9c766c1248bcc
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=7acd
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=7acd5c79374bbfd6c00bdc9b47b127ae
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\guard64.dll
LoadedModule[16]=C:\Windows\system32\fltlib.dll
LoadedModule[17]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[18]=C:\Windows\system32\secur32.dll
LoadedModule[19]=C:\Windows\system32\SSPICLI.DLL
LoadedModule[20]=C:\Windows\system32\credssp.dll
LoadedModule[21]=C:\Windows\system32\spool\DRIVERS\x64\3\UNIDRV.DLL
LoadedModule[22]=C:\Windows\system32\ole32.dll
LoadedModule[23]=C:\Windows\system32\spool\DRIVERS\x64\3\UNIDRVUI.DLL
LoadedModule[24]=C:\Windows\system32\VERSION.dll
LoadedModule[25]=C:\Windows\system32\OLEAUT32.dll
LoadedModule[26]=C:\Windows\system32\shell32.dll
LoadedModule[27]=C:\Windows\system32\SHLWAPI.dll
LoadedModule[28]=C:\Windows\system32\CRYPTBASE.dll
LoadedModule[29]=C:\Windows\system32\uxtheme.dll
LoadedModule[30]=C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7600.16385_none_fa645303170382f6\comctl32.dll
LoadedModule[31]=C:\Windows\system32\apphelp.dll
LoadedModule[32]=C:\Windows\system32\CLBCatQ.DLL
LoadedModule[33]=C:\Windows\system32\PROPSYS.dll
LoadedModule[34]=C:\Windows\system32\spool\DRIVERS\x64\3\PSCRIPT5.DLL
LoadedModule[35]=C:\Windows\system32\mscms.dll
LoadedModule[36]=C:\Windows\system32\USERENV.dll
LoadedModule[37]=C:\Windows\system32\profapi.dll
LoadedModule[38]=C:\Windows\system32\spool\DRIVERS\x64\3\PS5UI.DLL
LoadedModule[39]=C:\Windows\system32\spool\DRIVERS\x64\3\xrpscznu.dll
LoadedModule[40]=C:\Windows\system32\spool\DRIVERS\x64\3\xrpscznr.dll
LoadedModule[41]=C:\Windows\system32\spool\DRIVERS\x64\3\xrpsczne.fpl
LoadedModule[42]=C:\Windows\system32\Ws2_32.DLL
LoadedModule[43]=C:\Windows\system32\NSI.dll
LoadedModule[44]=C:\Windows\system32\DNSAPI.dll
LoadedModule[45]=C:\Windows\system32\IPHLPAPI.DLL
LoadedModule[46]=C:\Windows\system32\WINNSI.DLL
LoadedModule[47]=C:\Windows\system32\rasadhlp.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Print driver host for 32bit applications
AppPath=C:\Windows\splwow64.exe
This post started with a working Xerox printer in XP , I will assume 32bit since chgoman did not state 64bit so your issue is different than the initial post.
However, since the failures you see are also in the application, this typically indicates memory corruption by the UI components of the driver. If you can use a driver that's included in Windows 7 for your device (and it fails), then I can pass on the issue to the HP print driver group here at Microsoft. If the driver is not included in Windows 7, then I can bounce the issue off the HP group but they don't develop or test any drivers from HP.com and they will just forward to Boise to find out if it's a known issue.
If you have a Windows Error Report file named report.wer for the application or splwow64 process under \programdata\microsoft\windows\wer\reportqueue send the contents back. This will hopefully point to the modual name.
If you installed the newer HP driver without first removing the old one (delete printer, delete driver), then you can have compatibilty failures with some HP drivers.
Alan Morris Windows Printing Team Search the Microsoft Knowledge Base here: http://support.microsoft.com/search/Default.aspx?adv=1
