Windows 10 crashing related to printing

Hi all, anyone else getting hit with this possible windows 10 update print bug?
Full system crash, blue screen.
Rhino 6, feb 21 release.
Try to print, crash.
Try to print from layout crash
Try to change the active printer in layout properties.
A teammate just started having this issue after this morning’s windows update which looks like it has an Adobe DC update included.

Just tried v7 no issues printing there so far. edit: correction, similar problem there printing to a physical printer.

Hello - are you crashing printing in any other program? Do you see it when printing to pdf from Rhino’s pdf driver?

Hi Pascal,
No crashing in other programs, so far. EDIT: crashed when printing from acrobat reader as well. Definitely not isolated to Rhino.
Yes crashing with Rhino PDF.

Please run SystemInfo and post the results.
Hopefully something will jump out.


I’m pretty sure this is a Windows thing, but just to be thorough, here is a paste from coworkers v7:

Rhino 7 SR4 2021-3-8 (Rhino 7, 7.4.21067.13001, Git hash:master @ ed629035202f07e8b84a3ee211479ca20bb81b73)
License type: Commercial, build 2021-03-08
License details: Cloud Zoo

Windows 10.0.19042 SR0.0 or greater (Physical RAM: 32Gb)

Computer platform: DESKTOP

Standard graphics configuration.
Primary display and OpenGL: NVIDIA Quadro K5000 (NVidia) Memory: 4GB, Driver date: 9-22-2020 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 452.39
> Accelerated graphics device with 4 adapter port(s)
- Windows Main Display attached to adapter port #0
- Secondary monitor attached to adapter port #1

OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: On
Redraw scene when viewports are exposed: On

Anti-alias mode: 4x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: High

Vendor Name: NVIDIA Corporation
Render version: 4.6
Shading Language: 4.60 NVIDIA
Driver Date: 9-22-2020
Driver Version:
Maximum Texture size: 16384 x 16384
Z-Buffer depth: 24 bits
Maximum Viewport size: 16384 x 16384
Total Video Memory: 4 GB

Rhino plugins that do not ship with Rhino

Rhino plugins that ship with Rhino
C:\Program Files\Rhino 7\Plug-ins\Commands.rhp “Commands” 7.4.21067.13001
C:\Program Files\Rhino 7\Plug-ins\rdk.rhp “Renderer Development Kit”
C:\Program Files\Rhino 7\Plug-ins\RPC.rhp “RPC”
C:\Program Files\Rhino 7\Plug-ins\RhinoRenderCycles.rhp “Rhino Render” 7.4.21067.13001
C:\Program Files\Rhino 7\Plug-ins\RhinoRender.rhp “Legacy Rhino Render”
C:\Program Files\Rhino 7\Plug-ins\rdk_etoui.rhp “RDK_EtoUI” 7.4.21067.13001
C:\Program Files\Rhino 7\Plug-ins\rdk_ui.rhp “Renderer Development Kit UI”
C:\Program Files\Rhino 7\Plug-ins\NamedSnapshots.rhp “Snapshots”
C:\Program Files\Rhino 7\Plug-ins\IronPython\RhinoDLR_Python.rhp “IronPython” 7.4.21067.13001
C:\Program Files\Rhino 7\Plug-ins\RhinoCycles.rhp “RhinoCycles” 7.4.21067.13001
C:\Program Files\Rhino 7\Plug-ins\Toolbars\Toolbars.rhp “Toolbars” 7.4.21067.13001
C:\Program Files\Rhino 7\Plug-ins\3dxrhino.rhp “3Dconnexion 3D Mouse”
C:\Program Files\Rhino 7\Plug-ins\Displacement.rhp “Displacement”

You’re short on VRAM for 2 monitors, but that shouldn’t cause crashes.
Your GPU drivers aren’t that old but there are newer ones available.

If you print to the RhinoPDF “printer” does that crash too?

yes Rhino PDF also crashes the machine

See if that driver update makes any difference.

If it still crashes, are you sending in crash reports with your email address added?
I’m not finding any.

the machine is blue screening so no official auto report has a chance to be created.

Applications should not be able to cause a “blue screen” Windows crash.
I suspect that Rhino crashing is a symptom of a deeper upstream Windows problem. My guess is it is likely to be in something realted to the Windows printing setup.
If you have unused printers or other oddities, I’d remove them.

Is Windows up to date?
Are there failed updates in the Check for Updates install log?

1 Like

Drivers are few things that can blue screen Windows these days. A graphics driver and printer driver are being used when printing raster output while only the printer driver is being used when the output is vector. Do you crash when printing purely vector output?

Looks like resolved with windows update/rollback/hotfix. This was related to the Kyocera printer bug mentioned above I think. But not entirely sure.