The VRLink Driver encountered a fatal error: [EOS] Threads never reset, Waited 10s. Timed out.

[NeonPixel]

ISSUE
I'm using Steam Link on a Quest 2 to connect to SteamVR,
After about 2 -10 minutes games time out or crash (depends on case) or SteamVR crashes with the error: "The VRLink Driver encountered a fatal error: [EOS] Threads never reset, Waited 10s. Timed out."
This error appeared after i reinstalled windows 10 on my PC

OS
Tired: Windows 10 & 11 Pro

USUAL STEPS FOR THE ERROR TO APPEAR
-Open Steam Link on Quest 2
-Connect to PC
-Open VRChat
-Wait around between ~5-15 minutes
-Game times out
-Reconnects to ether the session i was in, my home world or sent to VRChat default home world
-Does it multiple times
-Steam VR Crashes

THINGS I TRIED PERSONALLY
-All the Steps on the troubleshoot page
-Reinstall the game, steam vr, even steam itself (cleaned all folders)
-Updated all drivers available
-Tried previous, current and beta version on both Steam VR and Steam Link and all the combination those
-Switched to Windows 11 and tried all of them again with the same results
-Different PC (It works fine)
-Different connect, Used AirLink (Works Fine)

PERSONAL CONCLUSION SO FAR
Given that i tried so many things, can make a list if needed, i came to the conclusion that there's something that triggered this error to happen in between Steam Link and SteamVR after i reinstalled Windows 10 on my PC, as far as i'm aware there was no update to ether of these apps wile i did the reinstall and after trying the precious versions on both of these apps with the same timeouts and error i'm at a dead-end.


UPDATE 1: After reinstalling windows now the problem is gone, all i have to deal with is the error 451 here and there for a few seconds then the error fixes itself.

UPDATE 2: After all this time it fixed itself, idk what i did but it now works without a problem.

[Chickenwing]

Just found out that I got the exact same thing, just that it happens like after some seconds. Gave more testing and it changes, but never more than like 15 Seconds. So Steam Link at least is not usable like this. Air Link also works for me.

[Chickenwing]

So what I did and seems to work for me is: Go to settings -> remote play-> deactivate hardware encoding, set render threads to a fixed number

[NeonPixel]

Publicado originalmente por Chickenwing:

So what I did and seems to work for me is: Go to settings -> remote play-> deactivate hardware encoding, set render threads to a fixed number

Sorry for taking so long to reply, didn't get much time to go over thing again.

I gave it a try and also played around with the settings, still dose the same, game times out constantly, then sometimes steam vr crashes with the error, rn it's mostly time outs.

What i noticed is that one of the logical processors (13) is being used around 80-90% while the rest don't do much, i have a Ryzen 7 5800x3d so 8 cores 16 logical.

[Raphata]

Publicado originalmente por NeonPixel:

Publicado originalmente por Chickenwing:

So what I did and seems to work for me is: Go to settings -> remote play-> deactivate hardware encoding, set render threads to a fixed number

Sorry for taking so long to reply, didn't get much time to go over thing again.

I gave it a try and also played around with the settings, still dose the same, game times out constantly, then sometimes steam vr crashes with the error, rn it's mostly time outs.

What i noticed is that one of the logical processors (13) is being used around 80-90% while the rest don't do much, i have a Ryzen 7 5800x3d so 8 cores 16 logical.

I'm late to the party, but have you tried Windows key + R -> msconfig -> System Initialization -> Advanced Options -> Check "Number of processors" -> set to the maximum number available?
Sorry if the options does not have this exact name. My Windows is in brazilian portuguese.

[LordPicasoNL]

Publicado originalmente por Raphata:

Publicado originalmente por NeonPixel:

Sorry for taking so long to reply, didn't get much time to go over thing again.

I gave it a try and also played around with the settings, still dose the same, game times out constantly, then sometimes steam vr crashes with the error, rn it's mostly time outs.

What i noticed is that one of the logical processors (13) is being used around 80-90% while the rest don't do much, i have a Ryzen 7 5800x3d so 8 cores 16 logical.

I'm late to the party, but have you tried Windows key + R -> msconfig -> System Initialization -> Advanced Options -> Check "Number of processors" -> set to the maximum number available?
Sorry if the options does not have this exact name. My Windows is in brazilian portuguese.

Nobody pls don't do that. It made my PC super slow when booting.

[Raphata]

Coming back to say that Steam Support has no idea how to help and closed the ticket. They sent HL: Alyx devs my issue and I need to hope for a fix in the future.

[NeonPixel]

Publicado originalmente por Raphata:

Publicado originalmente por NeonPixel:

Sorry for taking so long to reply, didn't get much time to go over thing again.

I gave it a try and also played around with the settings, still dose the same, game times out constantly, then sometimes steam vr crashes with the error, rn it's mostly time outs.

What i noticed is that one of the logical processors (13) is being used around 80-90% while the rest don't do much, i have a Ryzen 7 5800x3d so 8 cores 16 logical.

I'm late to the party, but have you tried Windows key + R -> msconfig -> System Initialization -> Advanced Options -> Check "Number of processors" -> set to the maximum number available?
Sorry if the options does not have this exact name. My Windows is in brazilian portuguese.

It is not something i commander doing, as it can have a big impact on how fast your PC can boot up, usually nobody should mess with the boot options unless necessary.

[NeonPixel]

Publicado originalmente por Raphata:

Coming back to say that Steam Support has no idea how to help and closed the ticket. They sent HL: Alyx devs my issue and I need to hope for a fix in the future.

Yep, Steam support for SteamVR doesn't know what is causing the issue, I've been told to do the things from the troubleshooting page twice, while it is understandable to mention it once, the second time i got a copy paste of a portion from it, even tho i mentioned that i have already tried all of it and i wound't be sending a Ticket if anything i found/ did worked.

Needles to say, they send me here to put a post up, maybe someone else had to deal with this problem.

[Mindbender]

Unfortunately I've encountered the very same error.

Alyx always wirked on this machine, but now after a few months I've tried it again and now I got the same.

I don't know if it's related but I've noticed that directly after starting the game I'm just seeing the grey rocks background in my headset but on the pc monitor the menu is already shown, it took I would guess 10-20 seconds for the main menu to show up on my headset.

[rethus777]

Same error for me on I5 13th gen, RTX 4060 and "No Man's Sky"
Can play round about 10, 20, 30 minutes (differ each time) than the game crash.

[V??oid Fiend]

Idk if you are still having this problem but the way I fixed it on my end was to go to settings>remote play and turn off low latency networking, HEVC video, and AV1 Video while leaving hardware decoding on

[Leon]

Publicado originalmente por MAGA I.C.E.:

Idk if you are still having this problem but the way I fixed it on my end was to go to settings>remote play and turn off low latency networking, HEVC video, and AV1 Video while leaving hardware decoding on

YOu way to fix dont work sadly

[Raphata]

Publicado originalmente por Mindbender:

Unfortunately I've encountered the very same error.

Alyx always wirked on this machine, but now after a few months I've tried it again and now I got the same.

I don't know if it's related but I've noticed that directly after starting the game I'm just seeing the grey rocks background in my headset but on the pc monitor the menu is already shown, it took I would guess 10-20 seconds for the main menu to show up on my headset.

Do you use a cable between your PC and VR? Do you use Virtual Desktop? I read in another thread that this must help... but I was not able to test it yet and have been saving some money to try Virtual Desktop first.

[Juakin]

Try the following. worked for me:
https://imgur.com/a/vrHcFYb

[GG]

it happens when i try to set my Steamlink Target bandwidth to Manual （350Mbs or over 200Mbs. I'm fixed it by set it back to auto. as I observed it would Automatically upscaled to 350 bitrate and it is working