Spoolsv.exe / print spooler subsystem hogging RAM and CPU

[nzoomed]

I thought I had a thread on this here a while back but cant find it, anyway 6 months on after a new fuji xerox docucentre was installed on site and about 4 computers (the ones that use it most of the time) end up slowing down to the point that they are unusable.
Restarting the computer every couple of days seems to be the only workaround ive found for now, and speaking to fuji on the matter have not been that helpful.

Tried many different solutions that claim to have worked for some, including but not limited to:

Disabling SNMP status enabled
disabling spooling in the driver and printing directly to the printer.
changing drivers, using postscript drivers, etc
disabling ipv6 (which appeared to work on one system)

issue happens on windows 10 and 11, takes about 2 weeks on average on a system left to run 24/7, slowly uses more and more CPU each day until it hits 100%
Restarting the print spooler is an easy work around and clears the memory, but what could be causing this?
Its only happened after the machine was replaced with a newer model, have removed all old drivers and reinstalled.

I see some people in a similar situation are using scripts to restart the print spooler service once it hits say 100MB of memory.
Not really a fix, but more of a workaround, never seen anything like this before, but appears to be an issue that has presented itself in windows for some years from what I can tell.

I personally feel its related to the drivers, but if it was a common issue, then I would have thought that Fuji would have been on the case.

[Wainuitech]

Dont know if this will be any help or not, But as a guess, it may be old printers that have not been uninstalled and their "leftovers"  are causing the trouble.

Had a Customer whose computers I cleaned out, and all the actual printers ran a lot better.

Some you can do a clean out several ways, others ( home versions) it is actually easier to dive into the reg and manually remove them.

This article, scroll down to Registry -- Give it a crack cant really do any harm ( Famous last words)

Article HERE

Stating the Obvious When completed, reboot and check the actual printer still prints.

[nzoomed]

Dont know if this will be any help or not, But as a guess, it may be old printers that have not been uninstalled and their "leftovers"  are causing the trouble.

Had a Customer whose computers I cleaned out, and all the actual printers ran a lot better.

Some you can do a clean out several ways, others ( home versions) it is actually easier to dive into the reg and manually remove them.

This article, scroll down to Registry -- Give it a crack cant really do any harm ( Famous last words)

Article HERE

Stating the Obvious When completed, reboot and check the actual printer still prints.

I have not gone that far yet, but no harm in giving it a go, will test it out on a single computer first and see how it goes i guess.

[Wainuitech]

Another post I saw suggested look at C:\WINDOWS\system32\spool\PRINTERS Make sure it's clear. If entries are hanging about you need to stop the spool Process 1st delete the entries then restart the spool.

[nzoomed]

Yes i had been reading posts on that too.
Will probably do it one step at a time so I know what gives results.