Event Id 1000 Source Application Error Spoolsv Exe
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeOnline20132010Other VersionsLibraryForumsGalleryEHLO Blog Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My event id 1000 print spooler windows 7 Forums Answered by: Application Error: Event ID 1000; Faulting application faulting application name spoolsv.exe windows 7 name: PrintIsolationHost.exe Windows Server > Remote Desktop Services (Terminal Services) Question 0 Sign in
Event Id 1000 Spoolsv.exe Server 2012
to vote Hello, dear colleagues! I have problem with printing on RDS (Windows Server 2012 R2). We are executing printer drivers in isolated processes.
Faulting Application Name Spoolsv.exe Server 2012
But sometimesPrintIsolationHost.exe faults 200 times a hour and causes Print Spooler to fail. Examples of errors: Faulting application name: PrintIsolationHost.exe, version: 6.3.9600.16384, time stamp: 0x5215f03c Faulting module name: ntdll.dll, version: 6.3.9600.17114, time stamp: 0x53649e73 Exception code: 0xc0000374 Fault offset: 0x00000000000f87a8 Faulting process id: 0x1347c Faulting application start event id 1000 spoolsv exe server 2008 r2 time: 0x01d0187efb514f3b Faulting application path: C:\Windows\system32\PrintIsolationHost.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report Id: 423cfe70-8472-11e4-95a3-005056a224fb Faulting package full name: Faulting package-relative application ID: Faulting application name: splwow64.exe, version: 6.3.9600.16384, time stamp: 0x5215f01d Faulting module name: ntdll.dll, version: 6.3.9600.17114, time stamp: 0x53649e73 Exception code: 0xc0000374 Fault offset: 0x00000000000f87a8 Faulting process id: 0xae7c Faulting application start time: 0x01d01846b8f40037 Faulting application path: C:\Windows\splwow64.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report Id: 2d5ef196-8472-11e4-95a3-005056a224fb Faulting package full name: Faulting package-relative application ID: Faulting application name: spoolsv.exe, version: 6.3.9600.16384, time stamp: 0x5215d570 Faulting module name: ntdll.dll, version: 6.3.9600.17114, time stamp: 0x53649e73 Exception code: 0xc0000005 Fault offset: 0x0000000000030489 Faulting process id: 0x143b0 Faulting application start time: 0x01d0187a74d7b105 Faulting application path: C:\Windows\System32\spoolsv.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report Id: ddb33928-8472-11e4-95a3-005056a224fb Faulting package full name: Faulting package-relative application ID: Faulting application name: spoolsv.exe, version: 6.3.9600.16384, time stamp: 0x5215d570 Faulting module name: KERNELBASE.dll, version: 6.3.9600.17055,
Login
Analyzer Sample report Advanced filtering Direct links to www.eventid.net Email notifications Scheduled reporting Free for subscribers EventReader Event Viewer Sample report Custom views/filters Servers list, organized http://www.eventid.net/display-eventid-1000-source-Application%20Error-eventno-1475-phase-1.htm in groups Integration with EventID.Net Consolidated view for all logs Free for subscribers Event ID: 1000 Source: Application Error Source: Application Error Maintenance: Recommended maintenance tasks for desktop applications http://jonathanrullan.blogspot.com/2012/11/print-spooler-crashing-hptcpmondll.html Type: Error Description:Faulting application
out. I clicked on Print and suddenly..... No Printers Found. I scratched my head for exactly 3 seconds (not really, but figured I would add some intensity) and started looking into why I had no more printers. The first thing that I looked at was to see if the Print Spooler service was running, of course, it was not. I started it up and it started successfully, I then looked at my SCCM guy and blamed him for a patch that he must have snuck on my computer. I went to print the document again.... No Printers Found. I went and checked the Print Spooler service and it was stopped again. I tried starting it up and it started successfully. This time I waited 15 seconds while refreshing the Services Console and noticed that after 10 seconds, it stopped itself. I then looked at my superhero sidekick and yelled... To the Event Viewer!!! I noticed these two entries under Administrative Events. Log Name: SystemSource: Service Control ManagerDate: 11/15/2012 12:13:42 PMEvent ID: 7034Task Category: NoneLevel: ErrorKeywords: ClassicUser: N/ADescription:The Print Spooler service terminated unexpectedly. It has done this 4 time(s). Log Name: ApplicationSource: Application ErrorDate: 11/15/2012 12:13:42 PMEvent ID: 1000Task Category: (100)Level: ErrorKeywords: ClassicUser: N/ADescription:Faulting application name: spoolsv.exe, version: 6.1.7601.17514, time stamp: 0x4ce7b4e7Faulting module name: HpTcpMon.dll, version: 7.2.5.51, time stamp: 0x4ab0e4d3Exception code: 0xc0000005Fault offset: 0x000000000000ad75Faulting process id: 0x1c54Faulting application start time: 0x01cdc3548a5b770cFaulting application path: C:\Windows\System32\spoolsv.exeFaulting module path: C:\Windows\System32\HpTcpMon.dll Now the second one intrigued me so I went to the path where the dll was located. It was still there with the same modified date as the other HpTcp files. I figured I would do what any risky IT person would do... I renamed the file to HpTcpMon.dllold and went to Services and started the Print Spooler back up. Viola! The Print Spooler started back up and did not stop unexpectedly. I figured I would at least look into what HpTcpMon.dll does and ran across this article... http://support.