9
1
Lately, I have been having a problem with a particular printer. Its an HP LaserJet P1006 printer, small compact, almost cute looking, but don't be fooled! For whatever reason, this devil machine hasn't been working on a particular computer that needs it. All my attempts to get it to work for more than a day have all failed, either because the printer is a spawn from hell or the computer just doesn't like it.
Once again the printer is an HP LaserJet P1006 and the OS is Windows 7 32-bit on a Dell Optiplex 790. The symptom is that the document errors out in the queue. Checking the event log I find that there's an error in the Spooler service. The Event ID is 372 and the error code is 87, saying the parameter is incorrect.
What I have tried so far:
- Installed latest drivers
- Tried the HP Diagnostic tool, which apparently thinks everything is fine
- Reinstalled latest drivers
- Uninstalled drivers then reinstalled latest drivers
- Uninstalled drivers and completely wiped out any trace of the drivers existence from the computer, from the PnP package to the print manager to anything on the drive with its name to any trace left on the registry, cackling like a mad medieval king bent on wiping out a rival dynasty. Then reinstalled latest drivers.
- Replaced the USB cable
- Tried several different USB ports
- Begged the printer to work
- Threatened it violence
- Updated to the latest chipset drivers
- Restarted the Print Spooler service
- Turned it off and then on again.
- Wiggled the cord a little bit
- Tried to convince the printer to work through peer pressure, 'All the cool printers are working!'
And the kicker: I replaced the printer with one of the same type and the result? It can print... for awhile, then it ends up like the demon printer. Both of these printers work fine on other machines so it has to be something between the machine and the printer.
Before I completely uninstalled and reinstalled the drivers on the PC, items in the print queue would show up for a second and then disappear without a trace. Now it seems like items are just getting stuck in the print queue with it saying that an error occurred.
How can I bring peace between these two warring factions, the PC and the printers? Is there any hope for this computer, or myself? Or will I be lost to madness in my attempts to fix this problem?
Have you tried a different printer on this computer? It's possible that your spooler service is giving you a headache. What output do you get when you run net start spooler from a command prompt? – Foosh – 2014-11-12T23:26:35.943
1@Foosh He already mentioned trying to restart the Printer Spooler service. – Michael Frank – 2014-11-12T23:28:22.490
@Foosh I have tried a different printer, its the same model though. And I have restarted the Spooler service multiple times, yet still this hellspawn of a printer mocks me! – Superkroot – 2014-11-12T23:31:32.177
@MichaelFrank Sometimes restarting a service from services.msc can be a bit silent vs getting immediate feedback from using the command prompt. – Foosh – 2014-11-12T23:31:32.660
1@Superkroot I meant of course a different model, I did read your question afterall despite what you and MF seem to think... You could check your system event and error log for anything related to the printer, driver, connections, etc. Since this is a USB connection are you experiencing any issues on other USB devices on this machine? Might be a BIOS/UEFI setting that's out of whack. – Foosh – 2014-11-12T23:35:20.107
2Great description of what you tried to fix the problem, but I'm missing exactly what is the problem. What, exactly does or doesn't it do? Is it independent of any specific application? How far does the process get (any activity of any kind on the printer)? Any indications of any kind in the application or printer dialogue? Were you facing east when you spread the goat entrails under the full moon? – fixer1234 – 2014-11-13T00:05:17.747
I had this issue on cheaper USB cables, and on cables 15' or longer. Have you tried a short (3ft or 6ft) cable, from something that is known to be working? – Canadian Luke – 2014-11-13T00:21:26.063
1@fixer1234 Nothing seems to happen other than the document erroring out in the queue. Checking the event log I find that theres an error in the Spooler service. The Event ID is 372 and the error code is 87, saying the parameter is incorrect. I have no idea what this means. Also, gorilla entrails? Do I look like I'm made of ritual sacrifice supplies!? We do all our IT work with vulture bones and cougar blood here! – Superkroot – 2014-11-13T00:54:46.697
@Foosh I will test some other USB devices on the machine to see if there's a difference and then check to see if there's any nifty BIOS problems tomorrow! – Superkroot – 2014-11-13T00:55:41.500
1
have you seen this: http://h20566.www2.hp.com/portal/site/hpsc/template.PAGE/public/psi/troubleshootDisplay/?sp4ts.oid=3435682&spf_p.tpst=psiContentDisplay&spf_p.prp_psiContentDisplay=wsrp-navigationalState%3DdocId%253Demr_na-c02002591-5%257CdocLocale%253Den_US&javax.portlet.begCacheTok=com.vignette.cachetoken&javax.portlet.endCacheTok=com.vignette.cachetoken? This suggests you're not the only one
– mcalex – 2014-11-13T03:41:23.900@mcalex The article you're linking to specifies that the printer stops working after an upgrade to Windows 7. Lower down, under "cause" it even says the problem occurs since Windows 7 tries to use Windows Vista drivers. The OP stated it worked for a few days, thus excluding the possibility of the suggested error-cause. – MahNas92 – 2014-11-14T23:46:39.410
Have you tried deleting the HP drivers and using the Windows generic driver ? – user76732 – 2014-11-15T00:55:56.700