VRChat not closing
closed
MotoFckr9k
Most of the time VRChat does not close properly and has to be force quit though task manager. This happens to me in vr and desktop mode. VRChat just freezes and never actually closes. This happens almost every time I try to close it.
Log In
Tupper - VRChat Head of Community
closed
Closing due to age and having a newer, more up to date post.
Rainbow Ram
I use this app for when I play on desktop, it basically turns ctrl+alt+f4 into a kill switch instantly closing the program. https://stefansundin.github.io/superf4/
MikeCore
all the time.
Lelan Leonard
Oh my god it allllways like allllways does that to me
Tupper - VRChat Head of Community
This should be greatly improved due to the latest release, VRChat 2020.1.1. There were a few bugs causing the client to hang on close.
We're still occasionally observing it, but it should be occurring far less often.
Jeffrey Pohl
Tupper - VRChat Head of Community: Still Crashing itself on exit every. single. time.
LunarLapNeko
Tupper - VRChat Head of Community: still happens , the game seems to be unable to unload and just waits for windows process control to close it ( especially after visiting UDON worlds the game will not close (the log shows at least 25 errors related to UDON conflicts ), VRChat.exe also tend to create up to 15 new instances of itself when it hangs
Call me cute💕💕💕
Tupper - VRChat Head of Community: it is way better with latest update takes way less time many thanks to you and all devs :)
Leader MaXx
Tupper - VRChat Head of Community: the latest update fixed it for me much love for you and for devs and thank you for the hard work :)
L
LuCypher
I have a similar issue but the VRChat.exe cannot even be force quit. It always says access denied even as administrator. I cannot debug the executable because the instance is already gone. When I look at the process structure there is only a single thread around.
It is from "C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_22f76d3b12d7bde2\nvwgf2umx.dll" the start address is "nvwgf2umx.dll!NVAPI_Thunk+0x7aa23c". The thread is in a suspended state and waiting for handle 0x5e4 which cannot be queried. It is probably already closed or discarded.
The stack trace for the thread:
0, ntoskrnl.exe!KeWaitForSingleObject+0x36dd
1, ntoskrnl.exe!KeWaitForSingleObject+0x1cc8
2, ntoskrnl.exe!KeWaitForSingleObject+0xab4
3, ntoskrnl.exe!KeWaitForSingleObject+0x255
4, ks.sys!KsReleaseCachedMdl+0x32f3
5, ks.sys!KsReleaseCachedMdl+0xbd5
6, ks.sys!KsReleaseCachedMdl+0x2020
7, ks.sys!KsPublishDeviceProfile+0x1840
8, ks.sys!KsEdit+0x52f6
9, ks.sys!KsEdit+0xf30
10, ks.sys!KsDefaultDispatchPnp+0x348
11, ntoskrnl.exe!IofCallDriver+0x59
12, ksthunk.sys+0x15de
13, ksthunk.sys+0x1023
14, ntoskrnl.exe!IofCallDriver+0x59
15, ntoskrnl.exe!ProbeForWrite+0x19d
16, ntoskrnl.exe!NtQueryInformationToken+0x2630
17, ntoskrnl.exe!ObfDereferenceObjectWithTag+0xc9
18, ntoskrnl.exe!ObOpenObjectByNameEx+0x1037
19, ntoskrnl.exe!PsQueryProcessAttributesByToken+0xbc5
20, ntoskrnl.exe!PsQueryProcessAttributesByToken+0x861
21, ntoskrnl.exe!PsQueryProcessAttributesByToken+0xd89
22, ntoskrnl.exe!PsWow64GetProcessMachine+0x1273
23, ntoskrnl.exe!SeGetCachedSigningLevel+0x1113
24, ntoskrnl.exe!KeWaitForSingleObject+0x39c1
25, ntoskrnl.exe!KeSynchronizeExecution+0x3370
26, ntoskrnl.exe!setjmpex+0x7c1f
27, ntdll.dll!ZwWaitForSingleObject+0x14
28, KernelBase.dll!WaitForSingleObjectEx+0x93
29, nvwgf2umx.dll!OpenAdapter12+0x30bea6
30, nvwgf2umx.dll!NVAPI_Thunk+0x7aa28c
31, kernel32.dll!BaseThreadInitThunk+0x14
32, ntdll.dll!RtlUserThreadStart+0x21
VRChat is version w_2019.3.2p2 build 864.
I'm running the game on NVidia RTX2080 with the 436.30 DCH driver and Ryzen 9 3900X on Windows 10 Pro 1909 (18363.535). This issue only happens with VRChat.
EDIT: Also tried driver 441.66 (the currently newest one) and it still happens. The start address changed to nvwgf2umx.dll!NVAPI_Thunk+0x7bb8cc on this version.
The stack trace for 441.66:
0, ntoskrnl.exe!KeWaitForSingleObject+0x36dd
1, ntoskrnl.exe!KeWaitForSingleObject+0x1cc8
2, ntoskrnl.exe!KeWaitForSingleObject+0xab4
3, ntoskrnl.exe!KeWaitForSingleObject+0x255
4, ks.sys!KsReleaseCachedMdl+0x32f3
5, ks.sys!KsReleaseCachedMdl+0xbd5
6, ks.sys!KsReleaseCachedMdl+0x2020
7, ks.sys!KsPublishDeviceProfile+0x1840
8, ks.sys!KsEdit+0x52f6
9, ks.sys!KsEdit+0xf30
10, ks.sys!KsDefaultDispatchPnp+0x348
11, ntoskrnl.exe!IofCallDriver+0x59
12, ksthunk.sys+0x15de
13, ksthunk.sys+0x1023
14, ntoskrnl.exe!IofCallDriver+0x59
15, ntoskrnl.exe!ProbeForWrite+0x19d
16, ntoskrnl.exe!NtQueryInformationToken+0x2630
17, ntoskrnl.exe!ObfDereferenceObjectWithTag+0xc9
18, ntoskrnl.exe!ObOpenObjectByNameEx+0x1037
19, ntoskrnl.exe!PsQueryProcessAttributesByToken+0xbc5
20, ntoskrnl.exe!PsQueryProcessAttributesByToken+0x861
21, ntoskrnl.exe!PsQueryProcessAttributesByToken+0xd89
22, ntoskrnl.exe!PsWow64GetProcessMachine+0x1273
23, ntoskrnl.exe!SeGetCachedSigningLevel+0x1113
24, ntoskrnl.exe!KeWaitForSingleObject+0x39c1
25, ntoskrnl.exe!KeSynchronizeExecution+0x3370
26, ntoskrnl.exe!setjmpex+0x7c1f
27, win32u.dll!NtGdiDdDDIDestroyAllocation2+0x14
28, d3d11.dll!D3D11CoreRegisterLayers+0xc14a
29, d3d11.dll+0x2f60f
30, nvwgf2umx.dll!NVAPI_Thunk+0x37bdb
31, nvwgf2umx.dll!NVAPI_Thunk+0x1049d6
32, nvwgf2umx.dll!NVAPI_Thunk+0x11e426
33, nvwgf2umx.dll!OpenAdapter12+0x311757
34, nvwgf2umx.dll!NVAPI_Thunk+0x7bb91c
35, kernel32.dll!BaseThreadInitThunk+0x14
36, ntdll.dll!RtlUserThreadStart+0x21
EDIT2: Also tried beta branch with Unity 2018.4 version w_2019.4.1 build 884. Still happens there.
OneVoltTen
This is expecially frustrating when in VR, as you have to manually close it when it freezes. It would be very nice for VRChat to gracefully exit.
Tupper - VRChat Head of Community
in progress
This is in-progress on the 2018 Open Beta build.
Hanging on application exit got worse in 2018, so we investigated it more deeply. We found some things that may cause it. We're implementing some fixes there, and hopefully it also fixes the issues that were reported here. Not sure!
Either way, marking this in-progress for now.
akalink
Tupper - VRChat Head of Community: excellent to hear, I’ve yet to get the game to close properly in 2018 beta
Legoman99573
Closing the game now traps your mouse in desktop when pressing the X button and alt + f4. It should just close, not stay connected. This has been going on for years and its only gotten worse where the game doesnt close unless you kill it in task manager.
Load More
→