Autosave & System Crashes Rhino 8 - Photographic Evidence

[Zaxxon (Zaxxon77)]

For some time now I’ve been having system crashes while working in Rhino (like full OS level freezes requiring a hard reboot) - lately though a new dynamic has begun to reveal itself that may lend a clue towards the cause(s) - and maybe suggests some path to a solution?

The first clue came when along with the pace and multitude of projects increasing here at the office - my appetite for losing data due crashes had became less than zero. So I increased the frequency of the Autosave feature a bit (in steps but eventually arriving at every ten minutes) - strangely the crash frequency seemed to track proportionally with my increases in Autosave frequency. With a clear pattern starting to emerge I started snapping a pic on my phone of the last thing displayed on the command line (oh - also worth mentioning - these crashes aren’t instigating a Rhino crash log dialog).

Lo and behold - almost every crash has an autosave (luckily) happening immediately before the last operation (often (but not always) a selection operation).

… All of those pics show the things displayed in the command line before the system froze solid over the last week or so.

Could see this even being some thing that isn’t solely being caused by the Rhino application - could be at the OS level where there’s some memory collision happening during the write-to-disk operation.

It does appear there have been others experiencing similar things :

Autosave crashes rhino

This has happened to me twice. I’m working with V-Ray interactive and moving around in a view, toggling forward and backward with “Home” and “End” keys when Rhino freezes and crashes. Looking in the autosave folder shows a TMP file of 0KB and the timestamp is a minute or two before Rhino froze. Any ideas?

Rhino 7 eval for Windows crashing frequently - Autosave to One drive?

Hi - please run the Rhino SystemInfo command and copy-paste the result here. -wim

Rhino 8 crashing while autosaving on Mac (OS Sonoma, Intel chip)

Hi, Even while working on a smaller filer, whenever it attempts to autosave, the model crashes and I need to quit and I lose all my work. Also, even right after saving the file, the window menu says the file is edited. Please help as I haven’t found any relevant posts regarding this yet. I have attached the file and here’s the report: 240318 Building Design.3dm (14.7 MB)

I also wonder if there’s some thing that I’m doing as a user that is exacerbating the situation - since an Autosave is being instigated without my being cognizant that a potentially sensitive operation is about to occur, I’m likely in the midst of something (like selecting a collection of 100’s of objects or whatnot) - maybe it’s that particular coincidence of actions that causes a gear to skip somewhere in the vast chain of operations between application, OS and hardware.

Random thought - if, for some reason the potential for crashes is intractable, (but user activity might be modified) - Could a warning light/screen flash/countdown/siren/beep precede the autosave to alert the unsuspecting operator to pause for a moment?

Here’s my System Info :

Summary

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 10 (10.0.19045 SR0.0) or greater (Physical RAM: 64GB)
.NET 8.0.14

Computer platform: DESKTOP

Standard graphics configuration.
Primary display and OpenGL: NVIDIA GeForce GTX 1060 6GB (NVidia) Memory: 6GB, Driver date: 8-14-2024 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 560.94

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
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: 4x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: High

Vendor Name: NVIDIA Corporation
Render version: 4.6
Shading Language: 4.60 NVIDIA
Driver Date: 8-14-2024
Driver Version: 32.0.15.6094
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 6 GB

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”

[jeremy5 (Jeremy)]

Nice reporting. McNeel may also wish to know your autosave location, the type of disk (local, plugin, network), what if any antivirus you run.

Also, computer crashes often work like compound interest and do increasing damage that increases their likelihood. Have you run chkdsk and memtest on your system? Do you see any errors reported in the Windows system log at the time of the crash?

[Japhy]

Not seeing any recent crash reports. What does your windows reliability monitor details say ? (faulting module)

[CADARTZ]

I would update those GPU drivers they are years old just to rule things out

I have auto save on less frequently also running win 10 no crashes

I will report if i see anything similar.

[Zaxxon (Zaxxon77)]

@jeremy5

Nice reporting. McNeel may also wish to know your autosave location, the type of disk (local, plugin, network), what if any antivirus you run.

Also, computer crashes often work like compound interest and do increasing damage that increases their likelihood. Have you run chkdsk and memtest on your system? Do you see any errors reported in the Windows system log at the time of the crash?

Thanks for these tips, here the location Autosave is using (the default) -

C:Users\Airtop2\AppData\Local\McNeel\Rhinoceros\8.0\AutoSave

I’ve got a mix of NVME and SSD solid state drives on this machine - the OS is running on an NVME M.2 and Rhino files live on a SATA SSD.

No anti-virus running besides the Microsoft one. I’ve just now run chkdsk and turned up no issues, will have a look at Memtest86, looks like memtest isn’t included by default on Win10 - (a while back I do recall running an in-built RAM test routine that is included in the BIOS, (no issues came up)).

Here is one of the Windows logs files that looks like it matches up as a record of crashes :

Event 41 Description - The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

@Japhy

Not seeing any recent crash reports. What does your windows reliability monitor details say ? (faulting module)

This is good to know about - hadn’t used it before - most of the red-X events don’t show Rhino, but here’s one that does :

@CADARTZ

I would update those GPU drivers they are years old just to rule things out

Aha - yes, that’s a good call - will do, had been going with whatever came over in Windows Update - but looks like NVIDIA has newer ones on their site - snagging those now.