Announcement

Collapse
No announcement yet.

Server 2012 Print Spooler problem

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Server 2012 Print Spooler problem

    We've had 2 of our print servers have the spooler service stop with the below errors. It seems to start back up but is happening more frequently. Can anyone tell from these errors what the problem is

    Faulting application name: spoolsv.exe, version: 6.3.9600.17238, time stamp: 0x53d0c155
    Faulting module name: hpmlm135.dll, version: 0.3.262.0, time stamp: 0x5035ce6d
    Exception code: 0xc0000005
    Fault offset: 0x00000000000018dc
    Faulting process id: 0x123c
    Faulting application start time: 0x01d0db873c6841f6
    Faulting application path: C:\Windows\System32\spoolsv.exe
    Faulting module path: C:\Windows\System32\hpmlm135.dll
    Report Id: a5b005a0-4a63-11e5-80d2-0050569050af
    Faulting package full name:


    Faulting application name: spoolsv.exe, version: 6.3.9600.17238, time stamp: 0x53d0c155
    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
    Exception code: 0xc0000005
    Fault offset: 0x0000005f5e52f440
    Faulting process id: 0xb7c
    Faulting application start time: 0x01d0de706b1d690e
    Faulting application path: C:\Windows\System32\spoolsv.exe
    Faulting module path: unknown
    Report Id: 3afa3770-4a6b-11e5-80d2-0050569050af
    Faulting package full name:
    Faulting package-relative application ID:


    Faulting application name: spoolsv.exe, version: 6.3.9600.17238, time stamp: 0x53d0c155
    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
    Exception code: 0xc0000005
    Fault offset: 0x0000005f5e52f440
    Faulting process id: 0xb7c
    Faulting application start time: 0x01d0de706b1d690e
    Faulting application path: C:\Windows\System32\spoolsv.exe
    Faulting module path: unknown
    Report Id: 3afa3770-4a6b-11e5-80d2-0050569050af
    Faulting package full name:
    Faulting package-relative application ID:

    

  • #2
    Anything in the event logs leading up to the crash
    Anything changed recently (patches, new drivers...)
    Disk space on the spool volume?
    Tom Jones
    MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
    PhD, MSc, FIAP, MIITT
    IT Trainer / Consultant
    Ossian Ltd
    Scotland

    ** Remember to give credit where credit is due and leave reputation points where appropriate **

    Comment


    • #3
      Something I have remembered (or maybe not) from my NT4 days, check the Dependencies tab and see what other Services it relies on. Maybe one of the others is playing hookie and needs to be sorted out. The attacked image if from Windows 7 so it may not match what you have on Server 2012 but have included it in case my post is not clear.

      Click image for larger version

Name:	Dependencies-tab.png
Views:	1
Size:	28.6 KB
ID:	492517
      1 1 was a racehorse.
      2 2 was 1 2.
      1 1 1 1 race 1 day,
      2 2 1 1 2

      Comment


      • #4
        Those entries are the only things n the even logs

        Comment


        • #5
          What, no event numbers?
          Which log?
          assuming the events are in chronological order, it appears to start with an HP driver, so reviewing that would be a good point to start with
          Tom Jones
          MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
          PhD, MSc, FIAP, MIITT
          IT Trainer / Consultant
          Ossian Ltd
          Scotland

          ** Remember to give credit where credit is due and leave reputation points where appropriate **

          Comment


          • #6
            Are the drivers installed properly? Is it practical to reinstall them?
            A recent poll suggests that 6 out of 7 dwarfs are not happy

            Comment

            Working...
            X