I know that I have seen this problem around for quite a while now and I have not really found a real answer for the problem or even a good workaround.
So, here is the problem. I have 1 user out of around 150 that will try to print to Outlook 2010 and the preview will say "There was an error when printing started, blah blah blah..." and she cannot print to any printer from outlook. There are about 4 different printers setup on her computer (all network printers on Win08 R2) and none of them will print when this happens. You do not need to restart the spooler but all you have to do to get it to work is restart Outlook and it will print fine and continue to print until it decides it wants to crash again.
Steps I have taken so far: Repair install for Outlook (at the time all that was installed was Outlook 2010 with Office 07). After deployment of the rest of Office 10 and uninstall of Office 07 the problem continued. Removed and re-installed Office 2010, problem persists. Removed drivers through Print management and re-installed, problem persists. Performed an upgrade repair of Windows with our Windows 7 with SP1 disk; next day problem persists. Here is the event log from her computer:Log Name: ApplicationSource: Application ErrorDate: 7/23/2013 8:34:39 AMEvent ID: 1000Task Category: (100)Level: ErrorKeywords: ClassicUser: N/AComputer: computername.domainDescription:Faulting application name: splwow64.exe, version: 6.1.7601.17777, time stamp: 0x4f35fbfeFaulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000Exception code: 0xc0000005Fault offset: 0x0000000000000000Faulting process id: 0x644Faulting application start time: 0x01ce86e478c77ab3Faulting application path: C:Windowssplwow64.exeFaulting module path: unknownReport Id: 9efbb9bf-f39c-11e2-8564-5cac4ccf1b39Event 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="2013-07-23T13:34:39.000000000Z" /> <EventRecordID>21214</EventRecordID> <Channel>Application</Channel> <Computer>computername.domain</Computer> <Security /> </System> <EventData> <Data>splwow64.exe</Data> <Data>6.1.7601.17777</Data> <Data>4f35fbfe</Data> <Data>unknown</Data> <Data>0.0.0.0</Data> <Data>00000000</Data> <Data>c0000005</Data> <Data>0000000000000000</Data> <Data>644</Data> <Data>01ce86e478c77ab3</Data> <Data>C:Windowssplwow64.exe</Data> <Data>unknown</Data> <Data>9efbb9bf-f39c-11e2-8564-5cac4ccf1b39</Data> </EventData></Event>
There is no faulting module name. How am I supposed to find the problem with this? The splwow64.exe has been replaced by the upgrade repair so that cannot be the problem. Also, I have already applied this patch http://support.microsoft.com/kb/2647753/en-us and the problem still persists. What can I do next to find the source of the problem and get rid of it?