Rhino Crashes on Start with Optimus & Intel Enabled

Rhino Rhino for Windows
, , , ,
1

This week I discovered Rhino 8 was unable to start except in Safe Mode. After some trial and error, I’ve been able to keep it from crashing by one of three ways:

  1. Disabling Rhino Cycles plugin,
  2. Disabling Rhino Cycles GPU mode (RhinoCyclesDisableGpu, run RhinoCyclesEnableGpu to reverse it),
  3. Disabling Optimus in the BIOS, connecting the monitor/dock to the USB-C ports managed by the Nvidia adapter, and then disabling the Intel display driver in Device Manager.

If I disable the Intel display driver before disabling Optimus, Rhino will run but only in OpenGL 1.1. Weirdly, if having disabled Optimus I then uninstall the Intel Driver (and remove it by command-line), Rhino will still crash until I disable the Microsoft Basic Display Driver that took its place. It also crashes if both drivers are uninstalled, though I imagine it would work if I disabled the one that replaces Intel but left the other one going…

So far, the solution I’ve settled with is #3. This is a workstation laptop, it’s usually plugged into power, and I always want to use the Nvidia video adapter anyway.

At one point I had Optimus enabled, but I also enabled Direct Output Mode. As far as I can tell, this is similar to turning off Optimus completely except the main laptop screen remains with Intel. Turning the Intel driver off in this state would either: de-activate that screen or, leave it on somehow and make everything on every screen choppy. What it did seemed left up to chance so at that point I gave up on Optimus completely.

I’m not surprised this is happening. Windows Update screwed up the Intel driver a week ago, forcing everything into software rendering until the driver was updated. Everything else still worked after that, including Blender. Only Rhino remained affected. From a search here I see I’m not the only one who’s had that experience.

The system’s a Dell Pro Max 18 Plus MB18250, here’s the output from System Info:

Rhino 8 SR33 2026-7-7 (Rhino 8, 8.33.26188.13001, Git hash:master @ 482f88a83547c62cde64d78ea8a8690b7349f289)
License type: Commercial, build 2026-07-07
License details: Cloud Zoo

Windows 11 (10.0.26100 SR0.0) or greater (Physical RAM: 63GB)
.NET 8.0.21

Computer platform: LAPTOP - Plugged in [100% battery remaining]

Non-hybrid graphics configuration.
Primary display and OpenGL: NVIDIA RTX PRO 4000 Blackwell Generation Laptop GPU (NVidia) Memory: 16GB, Driver date: 7-10-2026 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 596.86

Integrated accelerated graphics device with 4 adapter port(s)

  • Secondary monitor is laptop’s integrated screen or built-in port
  • Secondary monitor attached to adapter port 1
  • Windows Main Display attached to adapter port #2
    Primary OpenGL: NVIDIA RTX PRO 4000 Blackwell Generation Laptop GPU (NVidia) Memory: 16GB, Driver date: 7-10-2026 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 596.86

Integrated accelerated graphics device with 4 adapter port(s)

  • Secondary monitor is laptop’s integrated screen or built-in port
  • Secondary monitor attached to adapter port 1
  • Windows Main Display attached to adapter port #2

Secondary graphics devices.
[DISABLED] Intel(R) Graphics (Intel) Memory: 2GB, Driver date: 7-17-2026 (M-D-Y).

Integrated graphics device with 0 adapter port(s)

  • There are no monitors attached to this device. Laptop lid is probably closed

OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: On
GPU Tessellation is: On
Redraw scene when viewports are exposed: On
Graphics level being used: OpenGL 4.6 (primary GPU’s maximum)

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

Vendor Name: NVIDIA Corporation
Render version: 4.6
Shading Language: 4.60 NVIDIA
Driver Date: 7-10-2026
Driver Version: 32.0.15.9686
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 16303 MB

Rhino plugins that do not ship with Rhino

Rhino plugins that ship with Rhino
C:\Program Files\Rhino 8\Plug-ins\Commands.rhp “Commands” 8.33.26188.13001
C:\Program Files\Rhino 8\Plug-ins\rdk.rhp “Renderer Development Kit”
C:\Program Files\Rhino 8\Plug-ins\RhinoRenderCycles.rhp “Rhino Render” 8.33.26188.13001
C:\Program Files\Rhino 8\Plug-ins\rdk_etoui.rhp “RDK_EtoUI” 8.33.26188.13001
C:\Program Files\Rhino 8\Plug-ins\NamedSnapshots.rhp “Snapshots”
C:\Program Files\Rhino 8\Plug-ins\MeshCommands.rhp “MeshCommands” 8.33.26188.13001
C:\Program Files\Rhino 8\Plug-ins\RhinoCycles.rhp “RhinoCycles” 8.33.26188.13001
C:\Program Files\Rhino 8\Plug-ins\Toolbars\Toolbars.rhp “Toolbars” 8.33.26188.13001
C:\Program Files\Rhino 8\Plug-ins\3dxrhino.rhp “3Dconnexion 3D Mouse”
C:\Program Files\Rhino 8\Plug-ins\Displacement.rhp “Displacement”
C:\Program Files\Rhino 8\Plug-ins\SectionTools.rhp “SectionTools”

Here’s a graphics configuration from earlier, before I switched off Optimus, switched ports, and updated the Intel driver:

Hybrid graphics configuration.
Primary display: Intel(R) Graphics (Intel) Memory: 2GB, Driver date: 4-16-2026 (M-D-Y).

Integrated graphics device with 4 adapter port(s)

  • Secondary monitor is laptop’s integrated screen or built-in port
  • Secondary monitor attached to adapter port 1
  • Windows Main Display attached to adapter port #2
    Primary OpenGL: NVIDIA RTX PRO 4000 Blackwell Generation Laptop GPU (NVidia) Memory: 16GB, Driver date: 7-10-2026 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 596.86

Integrated accelerated graphics device with 4 adapter port(s)

  • Video pass-through to primary display device

(At some point that worked, but then it stopped working… probably when Windows broke the Intel driver.)

Before figuring this stuff out I also did several other things:

  • Tried to update Windows (it’s fully updated),
  • Updated Nvidia video driver,
  • Repaired every Visual C++ Redistributable,
  • Uninstall and re-installed every Visual C++ Redistributable,
  • Installed Visual C++ Redistributable version 14.44.35211 (had to uninstall 14.51.36247 to do this, and I put it back when it didn’t work),
  • Deleted the Rhino Cycle shader cache,
  • Uninstall and re-installed Rhino 8 (deleted registry keys and lingering file directories),
  • Reset default windows layout in Rhino,
  • Ran the reset command,
  • Installed Rhino 8 BETA,
  • Disabled Optimus in the BIOS (this didn’t work at first because the dock/hub remained on the wrong port and I still had the Intel driver enabled),
  • Loaded Cycles while in safe mode and clicked Reset Defaults.

Although it’s all fine now, I would like to not need to leave Intel video disabled. That feels like a half-baked solution. I’ll try anyone’s suggestions if they have an idea.

2

Hi Christian,

Thanks for the thorough writeup. The Windows Update that broke the Intel driver is the key detail here. What you’re describing (OpenGL 1.1 fallback, crashes surviving the Basic Display Driver swap) matches a driver install that never re-registered its OpenGL ICD, and the Cycles GPU device scan at startup is what trips over it. That’s why RhinoCyclesDisableGpu also works around it.

Disabling the Intel adapter shouldn’t be needed once the driver stack is actually clean. Lets try this:

  1. Download the current Intel graphics driver for the machine from Dell (or Intel’s site) first, and the NVIDIA driver as well.
  2. Uninstall the Intel driver with a full removal, DDU in safe mode is the reliable way, an in-place update is not enough here.
  3. Clean install the Intel driver, then the NVIDIA driver (use the “clean installation” checkbox in the NVIDIA installer).
  4. Re-enable Optimus in the BIOS and put the dock back where you want it.
  5. Run RhinoCyclesEnableGpu and restart Rhino.

If it still crashes on start after that, please post the newest crash dump from %LOCALAPPDATA%\McNeel\Rhinoceros\8.0\RhinoDotNetCrash.txt along with a fresh systeminfo. Thanks!

3

I’ve chosen not to run DDU on this machine. While I have administrator access, installs and usage is monitored. I’ve been using pnputil to remove drivers.

  1. At the start: Optimus is off in the BIOS. Cycles GPU is enabled in Rhino.
  2. Uninstalled Intel driver using uninstaller (not in safe mode because it wouldn’t work).
  3. On reboot Windows installed Intel driver from 4/16/2026 (expected, I just wanted all of the Intel software removed).
  4. Started Rhino out of curiosity and it crashed.
  5. Rebooted into Safe Mode and ran pnputil to remove Intel driver,
    1. in command line: pnputil /enum-drivers > drivers.txt
    2. find (Ctrl+F) entries in Notepad for “Display” that have the provider name “Intel Corporation”
    3. make note of the .inf file name/number for use in the next step…
  6. Ran in command line (administrator): pnputil /delete-driver noted-oem#.inf /uninstall
  7. Restarted Windows back to regular mode. Windows then uses “Microsoft Basic Display Adapter” in place of the Intel driver, though it’s marked with an exclamation point. Properties state “This device cannot start. (Code 10)”.
  8. Ran Rhino out of curiosity and it crashed (note that at this point I’m still using the same Nvidia driver and Optimus remains disabled).
  9. Disabled Microsoft Basic Display Adapter and Rhino is able to start (I reenabled it right after).
  10. Ran new Intel driver installer dated August 13th, clean install checked.
  11. Did not restart system despite the request of the installer. Ran Rhino instead… (it worked!)
    1. Restarted system, ran Rhino again… (it worked!)
    2. Also noteworthy: the “Intel Graphics Software” program works now too (prior to this install it did not).
    3. I could have stopped here but continued on…
  12. Installed Nvidia “New Feature Branch” / July 30th driver, “Perform clean installation” checked.
  13. Ran Rhino… (it worked!). Checked Rhino Render options… (not only is CUDA and Optix present, but Intel’s OneAPI is as well, though that was probably there since #11.)
  14. Restarted to BIOS and enabled Optimus’s hybrid configuration.
  15. Rhino continues to be able to start and run.
  16. Plugged USB-C hub/dock back to the right side. As of this step I have returned to the original configuration.
  17. Rhino continues to work, CUDA/Optix/OneAPI continue to be available.

Thanks for your help, Japhy! Removing the Intel driver in safe-mode might have made all the difference, though it could also be the driver Intel just came out with last Thursday.

I’ll leave Optimus Hybrid Mode active for now, but may turn it off or use Direct Mode in the future, as doing so might have solved an old intermittent stuttering problem I was having with AutoCAD. I’ll update this post with a small note on that once I am sure.