KB4503308
Rhino 5 (64-bit) would not start up anymore.
I figured out it would start
with graphic accelleration disabled (Nvidia GeForce GTX 860M driver up to date) or
by unplugging my Toshiba dynadock U3.0 (divers up to date), or, more specifically,
by using one display via dynadock / Display Link but synchronizing it with the laptop monitor.
My next step will be trying to uninstall the Windows updates, but this ist not a permanent fix, obviously.
As I am very dependent on using both screens via display link with graphic acceleration enabled, I’d appreciate any ideas/help.
Hi Benjamin - is is a crash or a hang on startup? If it’s a full on crash, please make sure to send the crash dump in. If it is a hang, please force a crash dump as outlined here:
And send us the resulting log file. That said, I don’t know what can be done for Rhino 5 - but I’d also look for the file mentioned here:
Hi Pascal,
thank you very much for your reply. First off, setting the laptop display as main (which would be switched off usually, only using two external displays via Display Link) did the trick!
Rhino does not crash as long as the laptop display ist set as main, also if I duplicate it to one of the external displays.
Here is the Crash Dump (the file that appears on desktop after crashing, right?) anyways: RhinoCrashDump.3dm (72.6 KB)
Again, thanks a lot, it is working for me this way!
Benjamin
Hi Benjaimin - it might be worth looking for the Nihimic audio driver and getting rid of that - it should be possible to sett the primary monitor to any.
Just in case this is an audio issue: I remember this window popping up everytime I boot
but showing a dynadock Speaker that says ‘not connected’, like it does for microphones
At some point I just deactivated that, now it’s not showing anymore, the window is still popping up (when booting with the dynadock plugged in.
Anyways, I currently do not have the resources to investigate further. Using the laptop display as main is working for me. I’ll just resign to the fact that the windows update did something and now it’s not working as it used to.
Hi Benjamin - if you at some point want to look at this again, the dump file would be a *.dmp file, not the Rhino file. If you crash and get the crash reporting window, that file will be on your desktop as long as the reporting window is still open. It is deleted when that window is closed.
If Rhino hangs (i.e. doesn’t crash), you can force the creation of a dump file with the instructions that Pascal pointed to.
-wim
