SPooler Subsystem App Running Up CPU And Not Printing

Brotuulaan

Honorable
Apr 30, 2013
97
0
10,640
I'm trying to get a document printed off for my wife that she tried printing before I got up today, but I'm having no luck tracing the issue back to the source. I am on a custom-built PC running WIndows 8, and the printer is an HP Deksjet F4140. Here's the situation:

The printer was originally "offline," which is an issue we had a while back (we don't use the printer very often). I think it was a simple matter of deselecting "Use printer offline" in the print queue Printer menu, but I'm not positive as that was a long time ago. Now, the printer is shown as connected but offline, and that option is not selected. There is no communication happening between my computer and the printer besides a check to see if it's plugged in. The check mark is there to indicate that it is connected, and yet the "Offline" indicator is alive and well.

I can cancel all but one document in the queue, which is freaking annoying because it keeps my CPU running up unless I manually end the Spooler Sybsystem App process. But when I do that, the printer disappears from the list, so I can't troubleshoot a darned thing. I don't remember what step I took, but the document now says that its status is "Deleting - Paused - Printing," whatever the heck that means.

***Update***
I just closed the print queue and restarted the service, and the queue is now cleared with the printer back in the list under Devices and Printers.

Thus far, every time I submit a new print job, the Spooler Subsystem App runs my CPU up to 16-21% and just sits there, apparently not doing anything. The only way to make any change is to shut down the process, cancel the print job, and restart the service. And it seems that every time I do this, a new instance of PrintIsolationHost pops up in my processes list.

I've tried deleting and re-adding the device several times, but that doesn't change anything.

Is there any advice for this sort of issue?
 
For some reason, this time going through the process, it added a new instance of the device under the default printer driver title "HP Deskjet F4100 Series," but with a picture of several people where it usually shows the check mark for a positive connection. That appeared when I ended the Spooler process, and it's still here now that I've restarted the service.

Wtf?
 
And now that it's done that, I tried printing to both options to see whether it made a difference. It failed as usual with the printer I've been re-adding every time, but this new ghost device that showed up on its own while shutting stuff down before printed successfully. As I'm typing this, my wife is driving to work with the paper in hand, and my CPU is running up because of the print queue for the intended print device.

Why did it suddenly add a new device when I didn't tell it to, and why has the regular process been failing all this time?