Printer settings could not be saved. Operation could not be completed(error 0x0000070c)

[capitan]

I seem to be having many horrible problems on one machine with the print
subsystem. It's a windows 7 pro 64bit SP1 machine with an HP1022
Laserjet printer installed. It kills the print spooler with too many
varying errors to list* - it happens when printing from outlook, word or
adobe the most. One of the items I've found to try and fix this problem
is to set the settings in the printer properties of the 1022 printer to
'print directly to the printer'. but it won't let me save those
settings, it gives me the error in the subject. I've already tried
removing and reinstalling the 1022 and most other printers, and it still
will not let me save the setting. Any suggestions on this one?

* Here is where I will try to explain the other printing errors. When
the user tries to print to the 1022 printer connected to the computer
via usb, the print spooler service dies and he needs to reboot before he
can continue to print. It does not have these issues everytime he tries
to print, only sometimes. If I remove the 1022 and give him a direct IP
connection to our Xerox copier, he has the same issue but only needs to
restart the app in order to go on and continue printing. The spooler
service also dies when he goes into his citrix desktop (syswow64). I
will list the copy paste info from the event log below. Can anyone
please help me with this? It's really driving me batty.

Log Name: Application
Source: Application Error
Date: 10/16/2012 8:32:53 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: laptop
Description:
Faulting application name: PrintIsolationHost.exe, version:
6.1.7600.16385, time stamp: 0x4a5bd3b1
Faulting module name: ZSR.dll, version: 6.20.1625.0, time stamp: 0x462fe8cf
Exception code: 0xc0000005
Fault offset: 0x000000000002b54c
Faulting process id: 0xfa0
Faulting application start time: 0x01cdaba2b53f48a4
Faulting application path: C:\Windows\system32\PrintIsolationHost.exe
Faulting module path: C:\windows\system32\spool\DRIVERS\x64\3\ZSR.dll
Report Id: fc13ca34-1795-11e2-b667-415645000030


Log Name: Application
Source: Application Error
Date: 10/15/2012 8:31:08 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: laptop
Description:
Faulting application name: spoolsv.exe, version: 6.1.7601.17777, time
stamp: 0x4f35fc1d
Faulting module name: localspl.dll, version: 6.1.7601.17841, time stamp:
0x4fb09595
Exception code: 0xc0000005
Fault offset: 0x00000000000a926a
Faulting process id: 0xd4c
Faulting application start time: 0x01cdaacc26d578d9
Faulting application path: C:\windows\System32\spoolsv.exe
Faulting module path: C:\windows\System32\localspl.dll
Report Id: 9335cb0f-16cc-11e2-b41e-415645000030

Log Name: Application
Source: Application Error
Date: 10/15/2012 8:05:00 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: laptop
Description:
Faulting application name: splwow64.exe, version: 6.1.7601.17777, time
stamp: 0x4f35fbfe
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp:
0x4ec4aa8e
Exception code: 0xc0000374
Fault offset: 0x00000000000c40f2
Faulting process id: 0xe18
Faulting application start time: 0x01cdaad5ac850fd8
Faulting application path: C:\windows\splwow64.exe
Faulting module path: C:\windows\SYSTEM32\ntdll.dll
Report Id: ec7bf78a-16c8-11e2-b41e-415645000030

I have tried the fixes below:

http://www.mailbeyond.com/printers-...print-spooler-service-terminated-unexpectedly

http://support.microsoft.com/kb/2647753


I have also tried manually fully removing all traces of the drivers and
redownloading them and reinstalling using the below procedure:

Clear Printer Spooler files and enable the spooler service

===================

1. Click Start, click Run, type "Services.msc" (without the quotation
marks) in the open box and click OK.

2. Double-click "Printer Spooler" in the Services list.

3. Click Stop and click OK.

4. Click Start, click Run, type "%WINDIR%\system32\spool\printers" in
the open window, and delete all files in this folder.

5. Click Start, click Run, type "Services.msc" (without the quotation
marks) in the open box and click OK.

6. Double-click "Printer Spooler" in the Services list.

7. Click on Start. In the Startup Type list, make sure that "Automatic"
is selected and click OK.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

open regedit (e.g. click Start, key regedit and press Enter)

navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows
NT x86\Drivers

under this key, there will be the keys Version-2 and Version-3 (one or
the other of these may be absent - not a problem)
the sub-keys under these contain the printer driver configuration
information
delete all the sub-keys inside Version-2 and Version-3, but not these
keys themselves

open a Command Prompt window

key the commands:
net stop spooler

open Windows Explorer

navigate to %systemroot%\system32\spool\printers\ and delete any files
there.
By default, this is where the print spooler stores print files.

navigate to %systemroot%\system32\spool\drivers\w32x86
(%systemroot% is usually Windows, but it might be winnt or something
else; this is set when the OS is installed).

inside w32x86, there will be folders with the names 2 and 3 (one or more
of these may be absent - not a problem)
delete all of the files and sub-folders in each of the 2 and 3 folders,
but not the folders themselves
inside w32x86, there may be other folders with names starting with
"hewlett_packard", "hphp" or something else; delete these folders also

restart the print spooler (see steps above)

Reinstall printer(s)


I also tried removing Acrobat from the machine for a few days since
ZSR.dll identifies as an adobe file.

I also tried right-clicking on the 1022 printer and clicking
troubleshoot and I've tried using the HP printer diagnostic utility, and
neither can locate any problem.

Unfortunately, none of the above items seems to have helped the
problem in anyway.

 

[Paul]

I seem to be having many horrible problems on one machine with the print
subsystem. It's a windows 7 pro 64bit SP1 machine with an HP1022
Laserjet printer installed. It kills the print spooler with too many
varying errors to list* - it happens when printing from outlook, word or
adobe the most. One of the items I've found to try and fix this problem
is to set the settings in the printer properties of the 1022 printer to
'print directly to the printer'. but it won't let me save those
settings, it gives me the error in the subject. I've already tried
removing and reinstalling the 1022 and most other printers, and it still
will not let me save the setting. Any suggestions on this one?

* Here is where I will try to explain the other printing errors. When
the user tries to print to the 1022 printer connected to the computer
via usb, the print spooler service dies and he needs to reboot before he
can continue to print. It does not have these issues everytime he tries
to print, only sometimes. If I remove the 1022 and give him a direct IP
connection to our Xerox copier, he has the same issue but only needs to
restart the app in order to go on and continue printing. The spooler
service also dies when he goes into his citrix desktop (syswow64). I
will list the copy paste info from the event log below. Can anyone
please help me with this? It's really driving me batty.

Log Name: Application
Source: Application Error
Date: 10/16/2012 8:32:53 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: laptop
Description:
Faulting application name: PrintIsolationHost.exe, version:
6.1.7600.16385, time stamp: 0x4a5bd3b1
Faulting module name: ZSR.dll, version: 6.20.1625.0, time stamp: 0x462fe8cf
Exception code: 0xc0000005
Fault offset: 0x000000000002b54c
Faulting process id: 0xfa0
Faulting application start time: 0x01cdaba2b53f48a4
Faulting application path: C:\Windows\system32\PrintIsolationHost.exe
Faulting module path: C:\windows\system32\spool\DRIVERS\x64\3\ZSR.dll
Report Id: fc13ca34-1795-11e2-b667-415645000030


Log Name: Application
Source: Application Error
Date: 10/15/2012 8:31:08 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: laptop
Description:
Faulting application name: spoolsv.exe, version: 6.1.7601.17777, time
stamp: 0x4f35fc1d
Faulting module name: localspl.dll, version: 6.1.7601.17841, time stamp:
0x4fb09595
Exception code: 0xc0000005
Fault offset: 0x00000000000a926a
Faulting process id: 0xd4c
Faulting application start time: 0x01cdaacc26d578d9
Faulting application path: C:\windows\System32\spoolsv.exe
Faulting module path: C:\windows\System32\localspl.dll
Report Id: 9335cb0f-16cc-11e2-b41e-415645000030

Log Name: Application
Source: Application Error
Date: 10/15/2012 8:05:00 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: laptop
Description:
Faulting application name: splwow64.exe, version: 6.1.7601.17777, time
stamp: 0x4f35fbfe
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp:
0x4ec4aa8e
Exception code: 0xc0000374
Fault offset: 0x00000000000c40f2
Faulting process id: 0xe18
Faulting application start time: 0x01cdaad5ac850fd8
Faulting application path: C:\windows\splwow64.exe
Faulting module path: C:\windows\SYSTEM32\ntdll.dll
Report Id: ec7bf78a-16c8-11e2-b41e-415645000030

I have tried the fixes below:

http://www.mailbeyond.com/printers-...print-spooler-service-terminated-unexpectedly


http://support.microsoft.com/kb/2647753


I have also tried manually fully removing all traces of the drivers and
redownloading them and reinstalling using the below procedure:

Clear Printer Spooler files and enable the spooler service

===================

1. Click Start, click Run, type "Services.msc" (without the quotation
marks) in the open box and click OK.

2. Double-click "Printer Spooler" in the Services list.

3. Click Stop and click OK.

4. Click Start, click Run, type "%WINDIR%\system32\spool\printers" in
the open window, and delete all files in this folder.

5. Click Start, click Run, type "Services.msc" (without the quotation
marks) in the open box and click OK.

6. Double-click "Printer Spooler" in the Services list.

7. Click on Start. In the Startup Type list, make sure that "Automatic"
is selected and click OK.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

open regedit (e.g. click Start, key regedit and press Enter)

navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows
NT x86\Drivers

under this key, there will be the keys Version-2 and Version-3 (one or
the other of these may be absent - not a problem)
the sub-keys under these contain the printer driver configuration
information
delete all the sub-keys inside Version-2 and Version-3, but not these
keys themselves

open a Command Prompt window

key the commands:
net stop spooler

open Windows Explorer

navigate to %systemroot%\system32\spool\printers\ and delete any files
there.
By default, this is where the print spooler stores print files.

navigate to %systemroot%\system32\spool\drivers\w32x86
(%systemroot% is usually Windows, but it might be winnt or something
else; this is set when the OS is installed).

inside w32x86, there will be folders with the names 2 and 3 (one or more
of these may be absent - not a problem)
delete all of the files and sub-folders in each of the 2 and 3 folders,
but not the folders themselves
inside w32x86, there may be other folders with names starting with
"hewlett_packard", "hphp" or something else; delete these folders also

restart the print spooler (see steps above)

Reinstall printer(s)


I also tried removing Acrobat from the machine for a few days since
ZSR.dll identifies as an adobe file.

I also tried right-clicking on the 1022 printer and clicking
troubleshoot and I've tried using the HP printer diagnostic utility, and
neither can locate any problem.

Unfortunately, none of the above items seems to have helped the problem
in anyway.

It helps at a time like this, to have a diagram of the printing system.
The only bookmark I've got, is to a diagram for an older picture
of printing. I'm not aware of a version of this figure for
Windows 7. And the only reference to "PrintIsolationHost" I
could find, was in Japanese.

http://blogs.technet.com/b/askperf/archive/2007/06/19/basic-printing-architecture.aspx

The spooler could be tipping over (at least, that's what the errors
point to), but it could be something with a particular printer
that is doing it. In the above architecture diagram, you can see
the printer "is a fair distance" from the spooler, but the
blowback can tip it over.

*******

In the www.mailbeyond.com thread, one thing that caught my eye was:

"Bonjour crashed a lot before this happened. Disabled Bonjour now
to see if that works. Anyone have it installed as well?"

And that's a suggestion that perhaps a network printing path is
upsetting things. Printing has many tentacles. You could try
uninstalling Apple iTunes, to get rid of Bonjour (it's
a sub-package that comes with iTunes). Bonjour is a way of discovering
resources on the network. (Perhaps similar to the SSDP thing used
in Windows ?). If you pick apart the iTunes installer, inside
it consists of maybe five different packages, and you may be
able to add or remove Bonjour separately. It's been a while
since I dissected the iTunes package (bloat). On Windows 7
at least, they shouldn't need to install their own CD/DVD
burning software, so that should eliminate at least one
sub-package.

The Wikipedia articles didn't tie this stuff together very well,
but SSDP (Windows) and Bonjour *may* be doing something similar for you.
I can't really be sure. I thought you could install SSDP separately
for Windows 7 (to make printer icons show up in some Explorer window).

http://en.wikipedia.org/wiki/Zero_configuration_networking
http://en.wikipedia.org/wiki/Simple_Service_Discovery_Protocol
http://en.wikipedia.org/wiki/Bonjour_(software)

*******

You could try reinstalling the printer software package, but
set it up as a "local printer only" somehow. Just to see if
that's a way to avoid the inability to save settings later
when you try to "print directly" to it.

As for the rebooting, you'd think if you "stop" the spooler
service, clean out the grease pit, then "start" the spooler
again, it should work. I don't know if printer drivers have
"state information", as the spooler should be the thing
that tracks state. The printer driver should really be
stateless. Maybe you could make a little batch file, to
"automate" the cleaning out of the grease pit (spool
directory).

*******

The "Subject:" of your posting, was this.

Printer settings could not be saved.
Operation could not be completed (error 0x0000070c)

I can find one reference to this, as...

1804 0x0000070C The specified datatype is invalid. ERROR_INVALID_DATATYPE

Almost as if an attempt is being made to store something in
the registry, which doesn't match the datatype of that registry
key. I think I've had something similar to this happen, when
I was installing a "print to file only" driver. During the installation
of the printer, I was supposed to click a button for local
printing of some sort, and then things went better after
that. I didn't bother doing a "before and after" comparison
of the registry, to see what had changed. But perhaps your
error has something to do with the change in the printer,
not being properly handled when it comes to the registry
key being used. (And maybe this is why I made the crazy
suggestion to specify "local printing" during the setup
of the printer driver during installation. That vague
memory...)

If you wanted to debug that (some prob with registry),
Sysinternals Process Monitor can be used to monitor
read/write to the registry, and just before something bombs out,
you'd be able to see the "guilty" registry key being read.
In this case though, you'd need to know what piece of
Windows software, is making the change. Is it the printer
driver ? Or something else ? If you don't "filter" on a
particular executable making registry accesses, and just
capture all registry access, you get perhaps 200 accesses per
second, and will have a rapidly filling log to
look through. The trick to using this, is "getting
good at specifying a filter". I once had to scroll
through about 100,000 captured events, to find the
one that was tipping over my sound card. So if you
can't filter things well, you'll be overwhelmed with
log cruft.

http://technet.microsoft.com/en-us/sysinternals/bb896645

Paul

 

[KCB]

I seem to be having many horrible problems on one machine with the print
subsystem. It's a windows 7 pro 64bit SP1 machine with an HP1022 Laserjet
printer installed. It kills the print spooler with too many varying
errors to list* - it happens when printing from outlook, word or adobe the
most. One of the items I've found to try and fix this problem is to set
the settings in the printer properties of the 1022 printer to 'print
directly to the printer'. but it won't let me save those settings, it
gives me the error in the subject. I've already tried removing and
reinstalling the 1022 and most other printers, and it still will not let
me save the setting. Any suggestions on this one?

* Here is where I will try to explain the other printing errors. When
the user tries to print to the 1022 printer connected to the computer via
usb, the print spooler service dies and he needs to reboot before he can
continue to print. It does not have these issues everytime he tries to
print, only sometimes. If I remove the 1022 and give him a direct IP
connection to our Xerox copier, he has the same issue but only needs to
restart the app in order to go on and continue printing. The spooler
service also dies when he goes into his citrix desktop (syswow64). I will
list the copy paste info from the event log below. Can anyone please help
me with this? It's really driving me batty.

Log Name: Application
Source: Application Error
Date: 10/16/2012 8:32:53 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: laptop
Description:
Faulting application name: PrintIsolationHost.exe, version:
6.1.7600.16385, time stamp: 0x4a5bd3b1
Faulting module name: ZSR.dll, version: 6.20.1625.0, time stamp:
0x462fe8cf
Exception code: 0xc0000005
Fault offset: 0x000000000002b54c
Faulting process id: 0xfa0
Faulting application start time: 0x01cdaba2b53f48a4
Faulting application path: C:\Windows\system32\PrintIsolationHost.exe
Faulting module path: C:\windows\system32\spool\DRIVERS\x64\3\ZSR.dll
Report Id: fc13ca34-1795-11e2-b667-415645000030


Log Name: Application
Source: Application Error
Date: 10/15/2012 8:31:08 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: laptop
Description:
Faulting application name: spoolsv.exe, version: 6.1.7601.17777, time
stamp: 0x4f35fc1d
Faulting module name: localspl.dll, version: 6.1.7601.17841, time stamp:
0x4fb09595
Exception code: 0xc0000005
Fault offset: 0x00000000000a926a
Faulting process id: 0xd4c
Faulting application start time: 0x01cdaacc26d578d9
Faulting application path: C:\windows\System32\spoolsv.exe
Faulting module path: C:\windows\System32\localspl.dll
Report Id: 9335cb0f-16cc-11e2-b41e-415645000030

Log Name: Application
Source: Application Error
Date: 10/15/2012 8:05:00 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: laptop
Description:
Faulting application name: splwow64.exe, version: 6.1.7601.17777, time
stamp: 0x4f35fbfe
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp:
0x4ec4aa8e
Exception code: 0xc0000374
Fault offset: 0x00000000000c40f2
Faulting process id: 0xe18
Faulting application start time: 0x01cdaad5ac850fd8
Faulting application path: C:\windows\splwow64.exe
Faulting module path: C:\windows\SYSTEM32\ntdll.dll
Report Id: ec7bf78a-16c8-11e2-b41e-415645000030

I have tried the fixes below:

http://www.mailbeyond.com/printers-...print-spooler-service-terminated-unexpectedly

http://support.microsoft.com/kb/2647753


I have also tried manually fully removing all traces of the drivers and
redownloading them and reinstalling using the below procedure:

Clear Printer Spooler files and enable the spooler service

===================

1. Click Start, click Run, type "Services.msc" (without the quotation
marks) in the open box and click OK.

2. Double-click "Printer Spooler" in the Services list.

3. Click Stop and click OK.

4. Click Start, click Run, type "%WINDIR%\system32\spool\printers" in the
open window, and delete all files in this folder.

5. Click Start, click Run, type "Services.msc" (without the quotation
marks) in the open box and click OK.

6. Double-click "Printer Spooler" in the Services list.

7. Click on Start. In the Startup Type list, make sure that "Automatic" is
selected and click OK.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

open regedit (e.g. click Start, key regedit and press Enter)

navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows
NT x86\Drivers

under this key, there will be the keys Version-2 and Version-3 (one or the
other of these may be absent - not a problem)
the sub-keys under these contain the printer driver configuration
information
delete all the sub-keys inside Version-2 and Version-3, but not these keys
themselves

open a Command Prompt window

key the commands:
net stop spooler

open Windows Explorer

navigate to %systemroot%\system32\spool\printers\ and delete any files
there.
By default, this is where the print spooler stores print files.

navigate to %systemroot%\system32\spool\drivers\w32x86
(%systemroot% is usually Windows, but it might be winnt or something else;
this is set when the OS is installed).

inside w32x86, there will be folders with the names 2 and 3 (one or more
of these may be absent - not a problem)
delete all of the files and sub-folders in each of the 2 and 3 folders,
but not the folders themselves
inside w32x86, there may be other folders with names starting with
"hewlett_packard", "hphp" or something else; delete these folders also

restart the print spooler (see steps above)

Reinstall printer(s)


I also tried removing Acrobat from the machine for a few days since
ZSR.dll identifies as an adobe file.

I also tried right-clicking on the 1022 printer and clicking troubleshoot
and I've tried using the HP printer diagnostic utility, and neither can
locate any problem.

Unfortunately, none of the above items seems to have helped the problem
in anyway.

The HP Print and Scan Doctor has replaced the diagnostic utility. It might
be worth a try:
http://ftp.hp.com/pub/softlib/software12/COL44682/Im-108448-1/HPPSdr.exe

 

[capitan]

The HP Print and Scan Doctor has replaced the diagnostic utility. It
might be worth a try:
http://ftp.hp.com/pub/softlib/software12/COL44682/Im-108448-1/HPPSdr.exe

Hi KCB, thanks for your reply. This is the utility from HP I've tried
to no luck.

 

[capitan]

It helps at a time like this, to have a diagram of the printing system.
The only bookmark I've got, is to a diagram for an older picture
of printing. I'm not aware of a version of this figure for
Windows 7. And the only reference to "PrintIsolationHost" I
could find, was in Japanese.

http://blogs.technet.com/b/askperf/archive/2007/06/19/basic-printing-architecture.aspx

The spooler could be tipping over (at least, that's what the errors
point to), but it could be something with a particular printer
that is doing it. In the above architecture diagram, you can see
the printer "is a fair distance" from the spooler, but the
blowback can tip it over.

*******

In the www.mailbeyond.com thread, one thing that caught my eye was:

"Bonjour crashed a lot before this happened. Disabled Bonjour now
to see if that works. Anyone have it installed as well?"

Good thought, but itunes and bonjour are not on this machine.

*******

You could try reinstalling the printer software package, but
set it up as a "local printer only" somehow. Just to see if
that's a way to avoid the inability to save settings later
when you try to "print directly" to it.

the 1022 printer is installed as a local printer only connected via USB
and will not save it's settings.

As for the rebooting, you'd think if you "stop" the spooler
service, clean out the grease pit, then "start" the spooler
again, it should work. I don't know if printer drivers have
"state information", as the spooler should be the thing
that tracks state. The printer driver should really be
stateless. Maybe you could make a little batch file, to
"automate" the cleaning out of the grease pit (spool
directory).

Nothing stays in the print queue because it crashes and stops everytime
it has a problem printing (but as I stated, the issue is inconsistent
and it does not always have a problem printing a file everytime)

*******

The "Subject:" of your posting, was this.

Printer settings could not be saved.
Operation could not be completed (error 0x0000070c)

I can find one reference to this, as...

1804 0x0000070C The specified datatype is invalid. ERROR_INVALID_DATATYPE

Almost as if an attempt is being made to store something in
the registry, which doesn't match the datatype of that registry
key. I think I've had something similar to this happen, when
I was installing a "print to file only" driver. During the installation
of the printer, I was supposed to click a button for local
printing of some sort, and then things went better after
that. I didn't bother doing a "before and after" comparison
of the registry, to see what had changed. But perhaps your
error has something to do with the change in the printer,
not being properly handled when it comes to the registry
key being used. (And maybe this is why I made the crazy
suggestion to specify "local printing" during the setup
of the printer driver during installation. That vague
memory...)

If you wanted to debug that (some prob with registry),
Sysinternals Process Monitor can be used to monitor
read/write to the registry, and just before something bombs out,
you'd be able to see the "guilty" registry key being read.
In this case though, you'd need to know what piece of
Windows software, is making the change. Is it the printer
driver ? Or something else ? If you don't "filter" on a
particular executable making registry accesses, and just
capture all registry access, you get perhaps 200 accesses per
second, and will have a rapidly filling log to
look through. The trick to using this, is "getting
good at specifying a filter". I once had to scroll
through about 100,000 captured events, to find the
one that was tipping over my sound card. So if you
can't filter things well, you'll be overwhelmed with
log cruft.

http://technet.microsoft.com/en-us/sysinternals/bb896645

Paul

Hi Paul and thanks for your reply. When I google each of these errors,
the splwow64 error seems to indicate driver corruption. The ZSR.dll
file indicates problems caused by Acrobat, and still researching the
other error. One of my issues is that I can't seem to find a common
denominator between all these different errors, nor can I find any hint
of anyone else having this kind of issues with 2 or more of these same
issues at once, so I can try to address each error individually, but
that does not fix my other problems.

Do you think I should try system file checker scan? Any other thoughts?
Thanks again for your help, I'm really hoping to not have to rebuild
this machine again just to fix this issue!

 

[Paul]

Hi Paul and thanks for your reply. When I google each of these errors,
the splwow64 error seems to indicate driver corruption. The ZSR.dll
file indicates problems caused by Acrobat, and still researching the
other error. One of my issues is that I can't seem to find a common
denominator between all these different errors, nor can I find any hint
of anyone else having this kind of issues with 2 or more of these same
issues at once, so I can try to address each error individually, but
that does not fix my other problems.

Do you think I should try system file checker scan? Any other thoughts?
Thanks again for your help, I'm really hoping to not have to rebuild
this machine again just to fix this issue!

Yeah, that's one of the suggestions here. I've not tried SFC on
Windows 7 yet. On WinXP it was pretty painful to get working
right, and took a couple registry changes first.

http://answers.microsoft.com/en-us/...-probelm/52376d39-d29a-4385-8260-01a044e69cd2

I think in that thread, it's something printer specific. Adobe
Reader should only be providing things to stuff in the spool,
rather than being on the other side of the spooler and
accepting output. If there was a print to PDF option
or something, then you might have suspicions it had
something to do with the Adobe stuff.

Paul