re:

> The crashes can take up to 20 min before they occur, which is why I am
> having a hard time pinning what triggers it.

What are your system thermals like, do they keep climbing over the 20 minutes of activity?

You can keep track with HWMonitor from CPUID.

- Michael

I am watching the temps as use Moi3d.

Right now I am doing stress test, with rendering a heavy scene in Redshift using the 3090, while modeling in Moi3d using the TitanX in open gl. I just discovered I can right mouse on an application and choose the which GPU to use in Open GL.

CPU temps running a flat 60 Celsius with a 30C ambient temp, and fans running on MAX.

Still freezing up, I might get a few degrees spike ....but nothing suspicious.

I have Moi installed on the network, in a dropbox folder. Would this interfere?

Hi 2byts, well it sounds like thermals are not the issue that was worth a check.

re:
> I have Moi installed on the network, in a dropbox folder. Would this interfere?

Probably not.

Can you please generate a crash dump from v3 so I can see if it has the same huge amount of threads created in it by the video driver as is happening to v4?

- Michael

Hi 2byts, I was looking over the crash dump info a little more and I noticed another possible hooking thing: NahimicOSD.dll .

It seems to be part of your audio driver which has several DLLs loaded but the "OSD" part of that one probably means on-screen display so it's another possible source of interference and has also caused crashes in other apps previously too:
https://support.microsoft.com/en-us/topic/office-applications-crash-due-to-nahimic-audio-driver-1a7cdd29-5c89-4579-9043-faa97120ff92
https://github.com/visualboyadvance-m/visualboyadvance-m/issues/623

If you can figure out a way to turn off that piece as well that might be worth a try.

It's a little strange that the audio driver has something that hooks into the video driver display code but that is what it appears to do.

- Michael

It looks like you might be able to find a Nahimic service running which you could disable in Win+R services.msc .

Kind of sounds pretty close to what you are describing:
https://answers.microsoft.com/en-us/windows/forum/windows_10-other_settings/nahimic-audio-issues/7c10e6ec-01bb-49ea-ba21-a93e037dca81



So definitely worth a try disabling that.

- Michael

Is it an MSI motherboard?

Some more info:
https://dovidenko.com/2021/1233/nahimic-uninstalling-blocking-msi-bloatware.html

- Michael

It is an Asus ROG Zenith II Extreme Alpha motherboard.

Thankyou Michael!

I will look into the Nahimic driver during the week when I am modeling.

Motherboard is Asus ROG.


v3 is so stable, I dont know how to crash the software actually! I think the only time I have made it crash was from out of memory during polygon exports. It is literally the most stable 3d application I have ever worked with it.

Hi 2byts, so yeah I guess it is both ASUS as well as MSI that use this Nahimic sound driver that has some kind of display driver hook apparently.

Another comment here about it interfering with Houdini:
https://www.reddit.com/r/ASUS/comments/asot4q/nahimic_service_causing_problems_all_around/

- Michael

I have been reading up on the Nahimic driver, and yeah....

https://www.nvidia.com/en-us/geforce/forums/game-ready-drivers/13/297952/nahimic-and-nvidia-drivers-conflict/

https://discourse.mcneel.com/t/rhino-freezes-on-secondary-monitor-problem-with-the-nihimic-audio-driver-on-the-motherboard/82258/37

Seems it is a bad mix for any 3d app.

Hi 2byts, hopefully that's the answer but we'll see... Bad drivers can always be a problem but this is the first time I've heard of a sound driver that's so bad it messes up the video driver as well.

If that does solve it, you can reset the moi.ini settings back to their defaults which are:

DisplayThreadLimit=
StaticBufferMaxVRAMToUseMB=

those being just blank, and then

GraphicsAPI=Auto

Hope that will work!

- Michael

Disabling Nahimic in services, seems to solve the issue completely. No crashes at all. Thankyou for your assistance Michael.

Hi 2byts, you're welcome! That's great I'm glad you have a solution.

Who would have guessed that it would be the sound driver? The worst sound driver in history it seems...

- Michael

""""""The worst sound driver in history it seems..."""""

I actually rolled on the floor!!!