Print driver host for 32bit application has stopped working

Michael

posted Oct 15 '15 at 11:29 pm

[quote user="Art Layton"]I have never run into it. It started after I had to reformat my hard drive because windows 10 corrupted some files and my computer wouldn't start..[/quote]

Sounds like your system still isn't back to normal ... I doubt anyone other than MS can help here, maybe you need to reinstall your printer drivers if this issue doesn't cease. For a start you could try installing a Generic / Text Only printer as default printer using the Windows printer setup to see whether it's caused by a corrupt printer driver.

[quote user="Art Layton"]I have never run into it. It &nbsp;started after I had to reformat my hard drive because windows 10 corrupted some files and my computer wouldn't start..[/quote]Sounds like your system still isn't back to normal ... I doubt anyone other than MS can help here, maybe you need to reinstall your printer drivers if this issue doesn't cease. For a start you could try installing a Generic / Text Only printer as default printer using the Windows printer setup to see whether it's caused by a corrupt printer driver.

			Michael
--
IERenderer's Homepage
PGP Key ID (RSA 2048): 0xC45D831B
S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C

Art Layton

posted Oct 15 '15 at 7:29 pm

I am getting this message in a windows pop-up box when I run Pmail. I am using windows 7 and the latest version of Pmail. Anyone have an idea what is causing this?

Brian Fluet

posted Oct 15 '15 at 7:55 pm

Pegasus Mail is dependent on a printer driver. It uses the one assigned to the default printer. If you intend to install a printer go ahead and do it now. If you aren't ready, the temporary fix is to install a printer using a generic text printer driver.

If you already have a printer installed, is it a remote printer (network, wireless)? If so, make sure it is online and accessible when running Pegasus Mail because some printer drivers poll the physical machine to make sure it is online before responding to the request by Pegasus Mail. Should this not be practical, the workaround is a generic text printer as the default printer.

Pegasus Mail is dependent on a printer driver.&nbsp; It uses the one assigned to the default printer.&nbsp; If you intend to install a printer go ahead and do it now.&nbsp; If you aren't ready, the temporary fix is to install a printer using a generic text printer driver.If you already have a printer installed, is it a remote printer (network, wireless)?&nbsp; If so, make sure it is online and accessible when running Pegasus Mail because some printer drivers poll the physical machine to make sure it is online before responding to the request by Pegasus Mail.&nbsp; Should this not be practical, the workaround is a generic text printer as the default printer.

Art Layton

posted Oct 15 '15 at 7:59 pm

The printer I use is the one Pmail points at to print. I will try to collect more information about the error message.

Michael

posted Oct 15 '15 at 8:49 pm

[quote user="Art Layton"]I am getting this message in a windows pop-up box when I run Pmail. I am using windows 7 and the latest version of Pmail. Anyone have an idea what is causing this?[/quote]

This module seems to be necessary on 64bit versions of Windows for using a printer driver, a restart of Pegasus Mail or your system should fix this since it's loaded and unloaded by Windows when Pegasus Mail starts or finishes. Since it cannot be terminated separately unless with external tools like ProcessExplorer (advanced users only!) the reboot might become unavoidable.

[quote user="Art Layton"]I am getting this message in a windows pop-up box when I run Pmail. I am using windows 7 and the latest version of Pmail. Anyone have an idea what is causing this?[/quote]This module seems to be necessary on 64bit versions of Windows for using a printer driver, a restart of Pegasus Mail or your system should fix this since it's loaded and unloaded by Windows when Pegasus Mail starts or finishes. Since it cannot be terminated separately unless with external tools like <a href="https://technet.microsoft.com/en-us/sysinternals/bb896653" target="_blank" mce_href="https://technet.microsoft.com/en-us/sysinternals/bb896653">ProcessExplorer</a> (advanced users only!) the reboot might become unavoidable.

			Michael
--
IERenderer's Homepage
PGP Key ID (RSA 2048): 0xC45D831B
S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C

Art Layton

posted Oct 15 '15 at 9:28 pm

More details:

Problem signature:

Problem Event Name: APPCRASH

Application Name: splwow64.exe

Application Version: 6.1.7600.16385

Application Timestamp: 4a5bd3ca

Fault Module Name: hpc6r101.dll

Fault Module Version: 0.3.1544.8561

Fault Module Timestamp: 4c9bb483

Exception Code: c0000005

Exception Offset: 0000000000075c13

OS Version: 6.1.7600.2.0.0.768.3

Locale ID: 1033

Additional Information 1: b967

Additional Information 2: b9676427d8f305a3357be0cb1920d6dc

Additional Information 3: ef7c

Additional Information 4: ef7c9ad992ecacded5025e6725746f8c

More details:&nbsp;&nbsp;Problem signature:&nbsp; Problem Event Name: APPCRASH&nbsp; Application Name: splwow64.exe&nbsp; Application Version: 6.1.7600.16385&nbsp; Application Timestamp: 4a5bd3ca&nbsp; Fault Module Name: hpc6r101.dll&nbsp; Fault Module Version: 0.3.1544.8561&nbsp; Fault Module Timestamp: 4c9bb483&nbsp; Exception Code: c0000005&nbsp; Exception Offset: 0000000000075c13&nbsp; OS Version: 6.1.7600.2.0.0.768.3&nbsp; Locale ID: 1033&nbsp; Additional Information 1: b967&nbsp; Additional Information 2: b9676427d8f305a3357be0cb1920d6dc&nbsp; Additional Information 3: ef7c&nbsp; Additional Information 4: ef7c9ad992ecacded5025e6725746f8c&nbsp;

Brian Fluet

posted Oct 15 '15 at 9:50 pm

Being very curious about this I did a bit of research and found this nice explanation in a superuser.com forum post:

Short:

The process gets executed every time a 32-bit application is
accessing one of your installed printers. You could kill the process if
you are not actively printing something. It will simply restart the next
time you want to print something, e.g., from Word (which is a 32-bit
application).

Explanation:

WOW64 is the so called "Windows On Windows 64" layer which enables you to execute 32-bit applications on a 64-bit system.

This is why you have the "classic"
System32
(where all the 64-bit binaries are being stored) and the
SysWOW64
folder for the WOW compatibility layer.

However, 32-bit applications cannot use 64-bit binaries (and therefore also printing drivers) and vice versa.

The
splwow64.exe
is a 64-bit application, therefore able
to speak with 64-bit printing drivers and "translates" the
communication between 32-bit applications and 64-bit drivers.

I am surprised I haven't run into this given the number of 64-bit Win7 PCs here at the office printing to a variety printers from a variety of 32-bit apps. My search didn't give me the impression that this is a wide spread problem so hopefully it was just a fluke.

Being very curious about this I did a bit of research and found this nice explanation in a superuser.com forum post:<div class="post-text" itemprop="text"> <blockquote>Short: The process gets executed every time a 32-bit application is accessing one of your installed printers. You could kill the process if you are not actively printing something. It will simply restart the next time you want to print something, e.g., from Word (which is a 32-bit application). Explanation: WOW64 is the so called "Windows On Windows 64" layer which enables you to execute 32-bit applications on a 64-bit system. This is why you have the "classic" <code>System32</code> (where all the 64-bit binaries are being stored) and the <code>SysWOW64</code> folder for the WOW compatibility layer. However, 32-bit applications cannot use 64-bit binaries (and therefore also printing drivers) and vice versa. The <code>splwow64.exe</code> is a 64-bit application, therefore able to speak with 64-bit printing drivers and "translates" the communication between 32-bit applications and 64-bit drivers.</blockquote> </div>I am surprised I haven't run into this given the number of 64-bit Win7 PCs here at the office printing to a variety printers from a variety of 32-bit apps.&nbsp; My search didn't give me the impression that this is a wide spread problem so hopefully it was just a fluke.

Art Layton

posted Oct 15 '15 at 11:15 pm

I have never run into it. It started after I had to reformat my hard drive because windows 10 corrupted some files and my computer wouldn't start..

I have never run into it. It &nbsp;started after I had to reformat my hard drive because windows 10 corrupted some files and my computer wouldn't start..

Brian Fluet

posted Oct 15 '15 at 11:27 pm

I have never seen it either and have a number of 64-bit Win7 PCs here at the office running a variety 32-bit apps printing to a number of different printers. Hopefully it was just a transient error for you.

I have never seen it either and have a number of 64-bit Win7 PCs here at the office running a variety 32-bit apps printing to a number of different printers.&nbsp; Hopefully it was just a transient error for you.

Related Topics

Pending draft

Confirm move posts

Insufficient permissions

Select a different topic

Edit history