Programs crashing when Vtube Studio is open

[jade vessel]

I've been having a lot of issues with things crashing while I am streaming, and ONLY when I am streaming. My games will crash, Vtube Studio will sometimes go Not Responding or crash altogether, sometimes even Streamlabs crashes too, all just out of the blue, no lag or anything, although the error message I get when Palia crashes is something about 'device hang'. (My PC is never maxed, it's usually sitting around 60% CPU and GPU, 70-80% memory DURING streams.)

I do have an NVIDIA graphics card, I know that there have been issues with Vtube Studio and VSeeFace having an issue with recent NVIDIA updates. I am on the most recent Windows 10 update. And yesterday I completely wiped my computer. Like everything, factory reset it. I did read through the FAQ and searched through some support threads to see if anyone had my issue, there were a few somewhat similar but nothing I haven't done yet. I have uninstalled the virtual camera, I've deleted the gpu file (advice from your twitter account made a few months ago explaining issues with NVIDIA cards), I've set gpu priority, I always check to make sure my games are FPS capped at no higher than 60, I don't have NDI, Spout2, or virtual webcam on. I also use the 'Google Mediapipe' tracking quality if that changes anything. probably forgetting some things but you get the gist.

Now, I've been doing some testing since I wiped it, to whittle down the list of suspects of what it could be. Had my full stream setup open. It crashed, okay so my wipe didn't fix the issue. Closed Stream Avatars, things were still crashing, so it wasn't that. I let Streamlabs and Vtube studio run for a bit, at some point VTS sneaky stopped responding and crashed. Oooookay. Opened it back up. Little while later, streamlabs crashed. Decided to keep Streamlabs closed and just leave Vtube Studio open, and my game is still crashing. So this is either a REALLY interesting coincidence since other things I'm doing crash only when VTS is open, or something in VTS is playing a part in the crashes in some way.

Any other ideas on what it could be and how I can fix it? It's getting extremely discouraging trying to stream when at any moment things can just randomly crash ;-; Thanks!

[glad raft]

You're at 70-80% memory usage in your scenario, have you considered running a memory test to see if your RAM is physically okay or if there's maybe some dead bits in there that only come to bear when thy systemis running low on free memory resources?

[jade vessel]

I can certainly give it a try! i just felt that was pretty unlikely since I got these sticks a few months ago and i don't experience any crashing when i have high memory usage while doing things that don't include having my stream setup open (i.e. when i just have firefox, discord, and clip studio with a file of 600+ layers open). also that i was still experiencing crashing having vtube studio open and lower memory usage (50%)

[jade vessel]

it seems to be some sort of an NVIDIA issue. things are still crashing while i have Vtube Studio open, and only while i have Vtube Studio open. my Event Viewer is giving me a couple of errors, event ID 0 and 13. and saying something about my display driver 'nvlddmkm has stopped responding and has successfully recovered', and according to a lot of Googling, the fixes for that are

• update the drivers
• roll back the drivers
• reinstall NVIDIA software
• clean it??????
• some sort of software issue??
  there doesn't seem to be any sort of guaranteed fix for it or a guaranteed method of figuring out WHAT is causing the error, aside from going through and trying everything one by one and hoping you do the right combination of things to magically fix it.

Now that I know what the issue is, or at least was able to give it some sort of name, after searching, it seems that someone else had my issue/a very similar one and how they fixed it for anyone else that runs across it and WHY it happens:

It basically causes (only with VTube Studio I noticed but it could be with similar Unity Apps) for the TDR to trigger which resets the Videocard drivers
It is a problem which lays at NVIDIA/Microsoft too solve..
I'm now back on the 512.59 driver and I can say that I haven't had crashes so far which is awesome.. Cause this caused my stream to crash```

Gonna try this and hope it fixes my issue too!

[jade vessel]

It....did not work.

so earlier with my crash i received 4 errors:

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

\Device\Video3
Graphics Exception: ESR 0x404490=0x80000001

The message resource is present but the message was not found in the message table
---------------------------------------------------------------------------------------------
The description for Event ID 13 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

\Device\Video3
Graphics Exception:  MISSING_MACRO_DATA

The message resource is present but the message was not found in the message table
---------------------------------------------------------------------------------------------
The description for Event ID 0 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

\Device\Video3
Error occurred on GPUID: a00

The message resource is present but the message was not found in the message table
---------------------------------------------------------------------------------------------
The description for Event ID 0 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

\Device\Video3
Error occurred on GPUID: a00

The message resource is present but the message was not found in the message table
---------------------------------------------------------------------------------------------```
And a warning:
```Display driver nvlddmkm stopped responding and has successfully recovered.```

After doing the above (checking for updates, turning off every single thing I saw about VTS and NVIDIA pooping, and reverting to NVIDIA driver 512.59 which worked for another person experiencing the same issues i am), this crash received these responses:
```Name resolution for the name t-ring-fallbacks2.msedge.net timed out after none of the configured DNS servers responded.
---------------------------------------------------------------------------------------------
Display driver nvlddmkm stopped responding and has successfully recovered.```
Though, i believe the T-ring warning came about a couple minutes before the crash, while the driver stopped working warning came about RIGHT when it happened, so I believe the T-ring warning can be disregarded.

[glad raft]

Name resolution for the name t-ring-fallbacks2.msedge.net timed out after none of the configured DNS servers responded.
t-ring-fallbacks (and q-ring- and a few others) are related to bing / cortana search from the startmenu, you can safely ignore those log entries.

[jade vessel]

I tried out System File Checker, there seemed to be at least one corrupt file on my system no crashes today aside from a weird getting stuck booting the BIOS that eventually resolved itself. think maybe that fixed it fingers crossed!

wish there were an easier way to diagnose this issue.

Going to keep stress testing it and if I don't see anymore crashes in the next day or two i will say it's been solved