Printing problem from 32-bit applications via 64-bit driver on Windows 7 x64

[kpp-noc]

Hello.

We have x64 Windows 7, HP P3005n Printer and latest drivers, MS Office 2007.

Please help resolve problem. Thanks

When we print from MS Office to HP P3005n Printer (we try print to local installed network printer  and via network print server) we have windows error:

Faulting application name: splwow64.exe, version: 6.1.7600.16385, time stamp: 0x4a5bd3ca
Faulting module name: hpc6r107.dll, version: 0.3.1544.8232, time stamp: 0x4c6af57c
Exception code: 0xc0000005
Fault offset: 0x0000000000076e77
Faulting process id: 0xe68
Faulting application start time: 0x01cb5aff8c38edd8
Faulting application path: C:\Windows\splwow64.exe
Faulting module path: C:\Windows\system32\spool\DRIVERS\x64\3\hpc6r107.dll
Report Id: fc5e617a-c713-11df-bec0-001e8c7ac28b

Log Name:      Application
Source:        Application Error
Date:          9/23/2010 4:10:50 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      XXX.domain.name
Description:
Faulting application name: splwow64.exe, version: 6.1.7600.16385, time stamp: 0x4a5bd3ca
Faulting module name: hpc6r107.dll, version: 0.3.1544.8232, time stamp: 0x4c6af57c
Exception code: 0xc0000005
Fault offset: 0x0000000000076e77
Faulting process id: 0xe68
Faulting application start time: 0x01cb5aff8c38edd8
Faulting application path: C:\Windows\splwow64.exe
Faulting module path: C:\Windows\system32\spool\DRIVERS\x64\3\hpc6r107.dll
Report Id: fc5e617a-c713-11df-bec0-001e8c7ac28b
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2010-09-23T13:10:50.000000000Z" />
    <EventRecordID>3705</EventRecordID>
    <Channel>Application</Channel>
    <Computer>CHIEF-NT.kp.kpp.com.ua</Computer>
    <Security />
  </System>
  <EventData>
    <Data>splwow64.exe</Data>
    <Data>6.1.7600.16385</Data>
    <Data>4a5bd3ca</Data>
    <Data>hpc6r107.dll</Data>
    <Data>0.3.1544.8232</Data>
    <Data>4c6af57c</Data>
    <Data>c0000005</Data>
    <Data>0000000000076e77</Data>
    <Data>e68</Data>
    <Data>01cb5aff8c38edd8</Data>
    <Data>C:\Windows\splwow64.exe</Data>
    <Data>C:\Windows\system32\spool\DRIVERS\x64\3\hpc6r107.dll</Data>
    <Data>fc5e617a-c713-11df-bec0-001e8c7ac28b</Data>
  </EventData>
</Event>

[vickd]

Hello,

Did you ever find a solution to this issue or is it still occurring? I am at the Vanderbilt University Law School and we're seeting this issue quite a bit. Except it is occurring with Office 2010. The error in the event log is exactly the same.

The full story is that we recently removed a large number of Dell 5210n/5310n printers and replaced them with HP Laserjet p4015dn printers, which are using the HP Universal Printing PCL6 driver for Windows 7 x64. This issue will normally occur if the user opens a Word/Office attachment from Outlook. Once opened, the user may try to print and will receive a message that "no printers are available", "there is a problem with the current printer setup" or the print menu itself will freeze completely.

I have found that removing excess printer drivers that are still "currently in use" will alleviate the pop up messages and the user can then print fine after restarting the spooler. This is still in testing but after about a week, this issue has stopped.

Thus far, if the print menu is freezing, the only recourse is to restart the computer. Additionally, we are testing PCL5 locally for a user and is working with no problems...so far. Again, only been testing this for a couple days.

Any other ideas?

HP support has been crap about this and basically said 'use HP TCP/IP ports', which is obviously not the issue.

[TVarde]

We've had similar issues in 200 user law firm.  Clients on Win7 x64; print server is Windows 2008 Server R2.  Started with PCL5, then switched to PCL6 UPD drivers w/ no improvement. 

Believe best bet at this point is direct IP printing with PS UPD driver.  Not our desired config, but need to get this solved ASAP...very frustrating for users (and IT staff).

Most times, you can kill SPLWOW64.exe process on user's system and be able to print (sometimes requires closing 32bit app at issue before/after killing splwow64 process), but 99% of time can avoid restart.

[Mark_Pot]

We are experience the exact same problems:

We are using HP Desktops running Windows 7 Pro 64x, with Office 2010. The printer we use is the HP Color LaserJet CM2320fxi.

Killing the SPLWOW64.exe from taskmager kind of always solves the problem.

Anyone found a solution yet?

We have tried to install the printer locally, but it keeps on getting stuck. Only seams to happen from Office apps, when printing a test page, no issue accures.

Regards,

Mark

[bibi-]

Hi all,

Do you have allready a solution? I have the sam issue. We work first with the specified HP driver, without some changes, after two month we get the massage "print driver host for 32bit applications has stopped working". The 

Faulting module was

hpzuiwn7.dll. So i replaced all diffrent HP Drivers with de UPD, now I have the same issue only with a other (hpcui111.dll)

EventLog: 

Faulting application name: splwow64.exe, version: 6.1.7601.17514, time stamp: 0x4ce7b4c8

Faulting module name: hpcui111.dll, version: 0.3.1545.9108, time stamp: 0x4d0bd538

Exception code: 0xc0000005

Fault offset: 0x000000000017487f

Faulting process id: 0x1a48

Faulting application start time: 0x01cbdd57a121f6d0

Faulting application path: C:\Windows\splwow64.exe

Faulting module path: C:\Windows\system32\spool\DRIVERS\x64\3\hpcui111.dll

Report Id: 4ed43db0-494b-11e0-8fcb-96b07c8a916c

Have someone a solution?

Cheers

[Mark_Pot]

Last Friday I;ve updated the machines with the issue to Win7 SP1.

So far so good, but I'll keep my fingers crossed for a while 🙂

Mark

[bibi-]

SP1 doesn't help us 😞

[VickMan]

Is anyone from HP going to post up a resolution to this problem? Seems like a major issue!

I am also experiencing the exact same issue with multiple machines!

[imickey503]

GO HERE

mike MVP Links to below

http://answers.microsoft.com/en-us/windows/forum/windows_7-hardware/cannot-connect-to-network-printe...

Here is the soultion it is so simple:

http://answers.microsoft.com/en-us/profile/aeca6813-a9cd-4cdd-8c90-4df6b21e0187

Mike Hall MVP - Windows Desktop Experience http://msmvps.com/blogs/mikehall/

To share a network printer being hosted by a computer running a 32 bit operating system with another computer running a 32 bit operating system, Vista or XP, you would go to Control Panel > ‘Printers’ > ‘Add Printer’ > ‘Add a network printer’.  Apologies if you consider that I am stating the obvious.

Sharing a printer being hosted by a computer running 32 bit Vista or XP with a computer running 64 bit Vista is not obvious, because if you use the above method, it will not work.

So how? First, you need to know the name of the computer which hosts the printer, and the name of the printer to be shared.

Sitting at the host computer: The procedure is the same for Vista and XP

Start > My Computer > Properties > Computer Name tab > Change button. Write down the name that you see here because this is the computer name.

Start > Settings > Printers and Faxes > Right click on the printer to be shared > Properties > Sharing tab. Write down the name that you see here because this is the printer name.

OK. Now sit in front of the Vista 64 computer:

Start > Control Panel > Printers > Add printer > Add a local printer > Click on ‘Create a new port’ > ‘Local Port’ > ‘Next’.

The port name will look like this: \\Computer name\printer name

So enter the names already retrieved, ensuring that you use the same format, then click ‘OK’.

At this point, you will be presented with the ‘Add New Hardware’ process. You can either select the make and model of your printer from the lists or insert your printer installation disk if you can’t find yours. The printer will be added, and you should be able to print a test page.

This should fix it...

imickey503

---