First Rhino, then GUI crash when handling (large) Mesh Objects

rhino6

(Fabio) #1

Hi all,

Whenever I handle larges Mesh Objects in Rhino 6, my computer tends to crash. I am relatively sure it is caused by my graphics car (Radeon Pro WX 4100) as at first Rhino crashes, then the GUI. The only resolve is then to do a hard reset of my HP Z4 Workstation.

This is a really annoying problem and kills my productivity as I need Rhino to edit Mesh Objects. Is there anything I can adjust in my Rhino settings to counter this problem?

With kind regards,

Fabio


(Steve Baer) #2

If the entire operating system is crashing, this is almost certainly a crash in the GPU driver. Have you tried updating your driver to the latest available?


(Fabio) #3

Hi Steve,

I am using the latest AMD Enterprise Drivers from 23/05/2018. If the drivers are the only factor in this story, then I’ll have to wait for the new driver version.

Is there anyway I can help Mcneel in diagonising or something so maybe you guys can relay it to the devs at AMD? Or is there anyway I can force my system to create a crash report? Because there is no info whatshowever generated :frowning:

I really want to help!


(Steve Baer) #4

@jeff do you have any ideas of what to try next?


(Nathan 'jesterKing' Letwory) #5

I think these are the drivers @jeff mentioned were unstable. I also am still at 17.Q4, but @jeff will know better.


(Jeff Lasor) #6

Yep… I would try rolling back to the 17.Q4 drivers and see if things are any better. I’m still working with AMD on the 18.Qx drivers issue…hopefully hear something today.


(Jeff Lasor) #7

@fabio1 If you can’t find the previous drivers page…here it is:

https://support.amd.com/en-us/download/workstation/previous?os=Windows%2010%20-%2064

I would try the 17.Q4 or 17.Q4.1 drivers.

-J


(Fabio) #8

Hi,

It seems to be working for the moment. I will update this post/report back EoB.

EDIT: about 11 business days later… I can report Rhino is still working flawlessly with the 17.Q4.1 drivers. So anyone reading this: The 18.Q2 drivers are not OK for Rhino 6, so hold your horses and revert to 17.Q4(.1) and see if future drivers are the solution as per recommendations by @jeff

Thank you all for the rapid respons and excellent support, as always :). This tight community is one of the reasons I Always like to spend my money on McNeels products :slight_smile:!!

Thank you!

Fabio