Print driver host for 32bit application has stopped

Question

Hi.
I'm being asked to troubleshoot an issue with very limited access and I'm hoping that someone can point me in the right direction.
Users are connecting to a WIndows 2008 R2 SP1 server using RDP. They are printing to HP Printers from within the RDP session. The Printers are installed onto the server as TCPIP printers. The error is a crash of SPLWOW64.EXE, and it references the file 'HPZUIWN7.DLL'.
The application they are printing from is 32-bit.
My biggest hurdle is the fact that I am expected to solve the problem, but have limited access to the environment and the people who have the required access are more interested in applying blame for the problem than fixing it (exacerbated by the fact that
if I am right in my diagnoses, they are the cause of the problem in the first place.)
I am of the opinion that the issue is 32/64-bit driver conflict related, but am a bit confused as to the recommended configuration for an environment like this. To summarize my question:
On a 64-bit OS that hosts multiple RDP Sessions (which could be from 32 or 64 bit workstations) that is used primarily for a 32-bit application, should we install the 32-bit print drivers, the 64-bit print drivers or both?
NOTE: I have some .DMP files related to the crash, but as of this stage I'd argue that the troubleshooting hasn't gotten to the point to justify trying to debug those yet.
Thanks for your time.
Dan

Answer 1

I'm not sure why the method is the name that it is.  I'm pretty sure MS blocked 16bit app support on 64bit machines.
The failure in the HP UI module is in this method
INVALID_POINTER_READ_c0000005_HPZUIWN7.DLL!CHPCommon::VUpdateResolutionFor16BitApps
They are not checking the memory before using it and it's not a valid pointer and crashes the process.
I'll send this to one of the guys that works for HP but there is not a way for the HP code to get updated like we do with system components.  The Office team has a report on this binary and method crashing office applications in 2012, but
it does not look like the issue was every handed off to HP, not that HP could address it then. 
The FIRST thing I would do is change the resolution you have configured for the printer just to see if that initializes the data I assume the driver is looking for.
The next thing would be trying a different driver for the device.  If you find a newer driver that uses HPZ6RWN7.DLL, it has the same defect.
    Loaded symbol image file: HPZUIWN7.DLL
    Image path: C:\Windows\System32\spool\drivers\x64\3\HPZUIWN7.DLL
    Image name: HPZUIWN7.DLL
    Timestamp:        Mon Jul 13 18:30:51 2009 (4A5BDFCB)
    File version:     0.3.7071.0
    Product version:  61.53.41.7
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    CompanyName:      Hewlett-Packard Corporation
    ProductName:      HP UI
    InternalName:     hpzuiwn7.dll
    ProductVersion:   61.053.41.07
    FileVersion:      61.053.41.07
    PrivateBuild:     61.053.41.07
    SpecialBuild:     61.053.41.07
    FileDescription:  ?????? ????? ????? ???? ?????? ?? Hewlett-Packard Vista
    LegalCopyright:   Copyright« Hewlett-Packard Corp. 1997-2008
Alan Morris Windows Printing Team