Have you tried Edge? I'm guessing it won't have the problem since it's 64 bit.The Kyocera drivers are 64 bit. The other printer drivers are 64 bit too, but they do not cause a crash.
We actually don't use Edge since it doesn't work with the Job Accounting built into the Kyocera driver. It doesn't display the popup box to insert a code which results in the job sitting in queue forever. It happens when we print from any modern Windows app, like Photos.Have you tried Edge? I'm guessing it won't have the problem since it's 64 bit.The Kyocera drivers are 64 bit. The other printer drivers are 64 bit too, but they do not cause a crash.
It seems like you're making good progress narrowing it down. I know you said this started after moving to the Fall Creators Update; was that from the Creators Update? Searches suggest some people have had problems with printing going from CU to FCU which suggests something might have changed but I've not seen anyone talking about bug checks during logoff/shutdown. Perhaps a subtle bug leaving a reference to a device context during the client side rendering? It seems like it's getting freed but something still tries to access it on logoff/shutdown. I suppose it could be a Windows bug but I'm not sure why it would only appear when printing to the Kyocera.
Another thought is 32 bit only add-ins or plug-ins but again, I'm not sure why that would only effect the Kyocera printer.
If you haven't already, I think I'd try contacting Kyocera to see if they have a driver update specifically for changes in FCU.
That looks useful! I might try that. Our bluescreen count is down to 7-10 computers. I had gone through and disabled and then re-enabled Client Side Rendering on the Kyocera printers. It seemed to affect quite a few computers. I'm wondering if somehow the CSR function on the computers was corrupted during the FC update. I manually reset the CSR registry key on a couple computers; we'll see how that pans out.