Selecting objects in rendered mode leads to frozen OS

Version 7.37
What happens when an object is selected under render mode, that is different than other viewport display modes? Would this be a memory related issue?

When my Win11 freezes during this, mouse cursor won’t even move. Hard power cut is needed to reboot.

I tried to strip my project model down to only the object that triggered this issue, so I could upload here. But I couldn’t reproduce the problem when it’s just that one object. Made me think it had to do with a relative large amount of different objects and materials.

Seems odd to me that the mere act of selecting an object would trigger such apparent memory catastrophe…

Hi Will, the next time it happens please try and get a dmp file and send it to us per these instructions. Thanks!

https://wiki.mcneel.com/rhino/manual_rhino_dmp_windows

Hey Japhy I would NOT be able to create the dmp file. PC is completely frozen during such event. There’s also NO dmp or the usual rhino “crash dump” file once I hard-reset computer.
Btw I’m on Intel Arc integrated graphic. CPU is Ultra 7 155H

Yikes, this is indicative of a hardware issue, Rhino is a symptom of something else going one.

1 Like

There could be potential helpful info in the Reliability Monitor details.

not much there…

Given you state you are on Intel Ultra 7 155H (Meteor Lake), yes indeed this will be the Intel Arc (Alchemist) first generation.

Two alternative routes exist to check for hardware/driver faults:

Event Viewer

It’s usually worth opening that location immediately after the restart, and Windows will sometimes splurge a load of information into that viewer; though admittedly not often helpful.

Arc Logs
If you have Intel Arc Control, have you also tried the following instructions:

https://www.intel.com/content/www/us/en/support/articles/000095081/graphics.html

That will give you a series of logs, including where it will encounter errors in OpenGL or whatever it is doing, if I recall correctly; for example:

[2023-08-24 21:35:55.214] [ArcC_e] [error] [class VirtualDevicesVM] SetInputResolution. set input resolution index 0 is out of range 0 !
[2023-08-24 21:35:55.214] [ArcC_e] [error] [class VirtualDevicesVM] SetInputResolution is not successfully!
[2023-08-24 21:35:55.214] [ArcC_e] [error] [class VirtualDevicesVM] UpdateCameras - UpdateCameraResolution is not successfully!

I am guessing the basics are corvered, and that you are on at least driver 32.0.101.6078 (last known WHQL Certified as far as I see)?

I ran Rhino 7 and Rhino 8 on an A770 dGPU for a while.

Thanks David! I’ve looked at the first log you mentioned and I think I’ve found the events near the freeze. That “critical” and the first “error” both say something about a bad power-off. Not sure how to interpret anything else though. What should I look for?

However, from the timestamp, there’s nothing from 2:34pm till 2:50pm. The freeze and reboot couldn’t have taken that long. 5 minutes altogether at most. So if 2:50pm is after reboot, any events relating to the crash should’ve been around 2:45pm maybe. To me this looks like nothing relating to crash was recorded. Thoughts?

My driver is version 31. Perhaps I should try to update. Also I don’t find the Intel Arc control folder mentioned in your second link.

Okay. Perhaps try the latest 32. series WHQL driver, and see if you have more joy.

They have other more recent releases, but none I can see that are certified.

32.0.101.6078/32.0.101.5736 (WHQL Certified) - 24/09/2024