Also Ram and Hard Disk can have some issue.
Memtest and chkdsk should be performed as well.
everything else works like a charme, only rhino is fucked up.
Japhy,
any clue what rhino destroyed while crashing? obviously it was not the driver.
help would be really appreciated, I cant work with rhino at the moment, which is a little bit stressful for me.
Benjamin
Donât know if you did or not but, to see if the fault is from last service release candidate, I would uninstall Rhino, restart SO, check updates and install Rhino 8.5
If the program works I would see if installing 8.6 the problem occours againâŚ
I remember also that in the past McNeel had an Installation Cleaner to clear all registry keys after uninstalling⌠could be useful if uninstalling by itself isnât working.
Rhino looks fine, the driver looks up-to-date, unless you can find a certain file that is a reproducible problem thereâs not much McNeel can do, you need to do some detective work.
Japhy says theyâve gotten no crash reports, that frankly indicates the problem is a hardware failure, Rhino isnât even being allowed to fail gracefully. Check the system logs! Try the recommendation about the clean driver reinstallation, etc.
Iâve re-visited all the the information youâve provided so far.
Rhino appears to be the symptom of something bigger going on with computer.
a few thingsâŚ
There are reports of issues with this particular build of windows Windows 10 10.0.19045
Did you try to roll back to an early driver.
Disconnect any peripherals for troubleshooting.
puh I am angry now, so better I write nothing. 
How 'bout you work on trying to narrow down the source of the crashes? A lot of advice has been offered here, but thereâs nothing anyone else can do at the moment, itâs on you. I had an AMD CPU randomly cause reboots a while back and just had to give up and switch to Intel, apparently it was âjust a thingâ with them that happens sometimes. Then the Intel motherboard started cooking my SSDs⌠Just googling indicates your Threadripper being an occasionally temperamental beast, with reports of them âjust going bad.â
This is true, I also found the same reports of problems with this Windows build.
It could well be that you have a perfect storm of problems, where Rhino is the trigger, but perhaps not the cause.
Older Threadrippers can have remarkable degradation, instability, RAM problems, and it may be just that Rhino has finally tripped it over; and its particular threading triggers the hardware failure. Itâs not new (see recent AMD X3D blowups and new Intel 14900 clock crashes).
The 2080 itself has various issues, which again, combined with the Threadripper, may just be a perfect storm.
Out of curiosity, can you get access to Rhino 7 instead? Perhaps if you are convinced it is a Rhino problem, then it may be useful to see if Rhino 7 causes the same problem.
If you can get past the anger, and find a cause, then it will help other users and McNeel with similar hardware or Rhino problems in the future.
David,
Rhino 7 worked nicely, just Rhino 8 had this problem.
I was setting up a new system and now Rhino 8 is working too. Obviously these crashes from the release candidate, which occurred often, damaged something and made rhino 8 believe that this service is somehow blocked, whatever. I really dont know what exactly happend, but now everything seems fine.
the machine is 4 years old, its capable of lot of things and I never had any problems with it in 3dsmax, AutoCad oder older versions of Rhino, which makes me believe that, according to the other documentations of crashes / freezes here in the forum, that r8 has still some serious issues.
anyway, I am defintily thinking about upgrading a little bit., at least the graphics card (i love rhino raytracing viewport).
this âblame the user strategyâ is a very old and boring one, but yeah, sure sometimes its the users fault too.
have a nice evening,
Benjamin
Youâre. Not. Listening. Ordinary program bugs donât make your computer just up and reboot in 2024. There is something wrong. That only one program(so far)is making it happen doesnât change that. You need to find out where itâs coming from, how to start has been mentioned repeatedly. Also make sure your backup procedures are working.
The only strategy is trying to help. If there was even the smallest clue towards something actionable we would be all over it. My money is on video driver (safe mode is fine)
Jim,
thx for your ideas. I will try to monitor the temperature and perform some test on the hardware. Lets see if there is something going on on this side.
Benjamin
There should be some sign in the Windows system logs (Search âevent viewerâ in Start) as to what the source of the crashes is, or what Windows thinks the source is.
Japhy,
i have been working with rhino for a long time and i have never experienced such poor performance in any version. if you read through the other threads, there seems to be a lot of frustration about this.
thatâs just the way it is now, we have to get through it. 
Benjamin
well, I guess they are gone for the moment due to a new win setup. If the system crashes again, because I click something in r8 
, i will have a look on the logs, thanks for that.
Benjamin
itâs obviously not just my system that was affected by this bug:
But that âserver busyâ message has nothing to do with anything youâve been talking about this whole thread.
That comes up as a rule when you have multiple Rhino sessions open and one is so tied-up in a task it wonât let Windows launch another for Windows reasons, I think it has to ask the open Rhinos if itâs a multi-document program or something. NOTHING to do with crashes or reboots or general bugs. Nothing. It doesnât even make sense, youâre complaining about Rhino not opening but the presence of such a message indicates clearly that you in fact have Rhino open!
What does the System log in Windows Event Viewer say about the cause of your reboots? If my computer was randomly rebooting I would not be trying to argue with people on the Internet that itâs a Rhino 8 bugâwhich there would be tons of messages from others if that was the case!âI would be at Defcom 1 making sure my backups are good and looking for any hardware I can swap out to try to isolate the cause before I lose work! Ordinary program bugs donât make Windows reboot!
Jim,
i really appreciate your support, but i think the discussion is slipping a bit into a not very nice area. do you think iâm a bit of an idiot? if so, i would prefer you not to contribute to my thread any more, if thatâs ok with you. if the answer is no, we can continue discussing which phenomenon we are on the trail of here.
in both cases we have the server busy error message, which i have not seen in this form in recent years. i sometimes work with up to 6 instances of rhino and have not really had any problems with r6 or r7 in this regard. it may be that this message occurred in older versions, yes i can remember.
in both cases, rhino r8 can no longer be closed normally but must be closed with the task manager.
what a strange coincidence, donât you think? i canât tell you how this is related to the crash, iâm not a hardware technician, (are you?) the bug is the same in all cases, it occurs with the same version, within a few days.
Benjamin
The âServer busyâ window is a common Windows thing that just means Rhino is momentarily really âtied-up.â That might be as a result of some sort of bug, but itâs probably just really busy and if you wait a bit, it will go away. It has nothing to do with actual Rhino crashes or Windows rebooting. Why are you trying to argue with me about this? The fact other people post about this âproblemâ doesnât make it one.