I would just like to add to this discussion that i got the blue screen of death twice during Make2D in R8. It was a very heavy file, but i never had rhino blue screen before…
Rhino 8 SR0 2023-10-31 (Rhino 8, 8.0.23304.09001, Git hash:master @ 20e15cf9bd66e6676f849f22e485cb3e82a8beac) License type: Evaluation, build 2023-10-31 License details: Cloud Zoo Expires on: 2024-02-05 Windows 11 (10.0.22621 SR0.0) or greater (Physical RAM: 96Gb) .NET 7.0.0 Computer platform: DESKTOP Standard graphics configuration. Primary display and OpenGL: NVIDIA GeForce RTX 4090 (NVidia) Memory: 24GB, Driver date: 10-26-2023 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 546.01 > Accelerated graphics device with 4 adapter port(s) - Windows Main Display attached to adapter port #0 Secondary graphics devices. Intel(R) UHD Graphics 770 (Intel) Memory: 1GB, Driver date: 7-24-2023 (M-D-Y). > Integrated graphics device with 4 adapter port(s) - There are no monitors attached to this device! OpenGL Settings Safe mode: Off Use accelerated hardware modes: 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: 10-26-2023 Driver Version: 126.96.36.19901 Maximum Texture size: 32768 x 32768 Z-Buffer depth: 24 bits Maximum Viewport size: 32768 x 32768 Total Video Memory: 24564 MB Rhino plugins that do not ship with Rhino C:\ProgramData\McNeel\Rhinoceros\7.0\Plug-ins\Datasmith Rhino Exporter (d1fdc795-b334-4933-b680-088119cdc6bb)\DatasmithRhino7.rhp "Datasmith Exporter" 188.8.131.52 C:\Users\Primoz\AppData\Roaming\McNeel\Rhinoceros\packages\8.0\NVIDIADenoiser\0.4.3\NVIDIADenoiser.Windows.rhp "NVIDIADenoiser.Windows" 0.4.3.0 C:\Users\Primoz\AppData\Roaming\McNeel\Rhinoceros\packages\8.0\AutoCameraTarget\2.2.0\Libx.Fix.AutoCameraTarget.rhp "AutoCameraTarget" 184.108.40.206 C:\Users\Primoz\AppData\Roaming\McNeel\Rhinoceros\packages\8.0\Corgi\0.5.6\Corgi.rhp "Corgi" 0.5.5.0 Rhino plugins that ship with Rhino C:\Program Files\Rhino 8\Plug-ins\Commands.rhp "Commands" 8.0.23304.9001 C:\Program Files\Rhino 8\Plug-ins\WebBrowser.rhp "WebBrowser" C:\Program Files\Rhino 8\Plug-ins\rdk.rhp "Renderer Development Kit" C:\Program Files\Rhino 8\Plug-ins\RhinoScript.rhp "RhinoScript" C:\Program Files\Rhino 8\Plug-ins\AnimationTools.rhp "AnimationTools" C:\Program Files\Rhino 8\Plug-ins\IdleProcessor.rhp "IdleProcessor" C:\Program Files\Rhino 8\Plug-ins\RhinoRenderCycles.rhp "Rhino Render" 8.0.23304.9001 C:\Program Files\Rhino 8\Plug-ins\RhinoRender.rhp "Legacy Rhino Render" C:\Program Files\Rhino 8\Plug-ins\rdk_etoui.rhp "RDK_EtoUI" 8.0.23304.9001 C:\Program Files\Rhino 8\Plug-ins\NamedSnapshots.rhp "Snapshots" C:\Program Files\Rhino 8\Plug-ins\MeshCommands.rhp "MeshCommands" 8.0.23304.9001 C:\Program Files\Rhino 8\Plug-ins\RhinoCycles.rhp "RhinoCycles" 8.0.23304.9001 C:\Program Files\Rhino 8\Plug-ins\RhinoCode\RhinoCodePlugin.rhp "RhinoCodePlugin" 8.0.23304.9001 C:\Program Files\Rhino 8\Plug-ins\Toolbars\Toolbars.rhp "Toolbars" 8.0.23304.9001 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"
Sadly, I can’t post the file because the content is confidential and i signed an NDA.
On the SR version it blue screened twice, but on the SRC version 8.1 it didn’t (yet).
What was the error message on each BSOD? (If you didn’t record it you may still find the code in the system’s Event Log).
A while back I had a couple of BSOD’s that I ignored. Things got progressively worse until my PC became unbootable in standard mode. I ran Memtest3 to check the memory and found it needed to be clocked back slightly (it was running at its specced speeds, but on my system, with my motherboard that was just too much). Because I’d ignored the initial signals, memory failures had the opportunity to corrupt files which accelerated towards meltdown. Thing is, this showed up in Rhino because it was the app that exercised my PC the most, but Rhino wasn’t at fault.
You may find this resource helpful: Stop error, bug check, or blue screen error troubleshooting - Windows Client | Microsoft Learn
BSODs in 2023 mean something has physically gone flakey with your computer.
Insufficient power, cooling, something. Make2D does use all cores, so…cpu cooling? I dunno, who knows, but it’s not to be ignored. Your PC is faulty.
The stop code was: CLOCK WATCHDOG TIMEOUT
That means you have a system problem. Unfortunately there are lots of possible causes for that error, including:
Overclocking the CPU too much, overclocking the memory too much, faulty hardware, faulty drivers, corrupted system files, bios errors.
I would start by running memory and system diagnostics. Then check your bios and drivers are up to date. Then check your system files per Microsoft’s instructions and check Windows Update is up to date. Then reduce any overclocking.
Or dump the problem on your pc supplier…