I have an X86 print server that over time becomes pretty much useless and after getting to what's causing it i'm now ready to Debug. Turns out the print spooler Spoolsv.exe had an insane amount of handles. I restarted the spooler and teh server came back to life. I have a monitor setup that will let me know when the spoolsv.exe uses up 12000 handles.
My goal is to do this. Once i get the alert, launch WINDBG and do a kernal debug. At this point i will give it the !poolused 2 command to show much what driver is consuming the most non-paged pool as non-paged pool usage was high on the spoolsv.exe when handle count was high.
Ultimately, i'm trying to figure out what Driver is causing the spoolsv.exe to use sooooo much resources.
Anyone got any advice?