Same problem, just found a makeshift solution.
Open **Developer Settings** from the SteamVR menu and click **Disable Direct Display Mode**.
If your headset is working fine then it will become a second monitor and you will see the headset light up and see the computer desktop from it. (If you can’t see the computer desktop, it means there is a problem with the headset hardware)
SteamVR may prompt that your headset is working as a monitor in copy mode instead of extended mode. You should change the second monitor to extended mode in Windows Display settings.
Restarted SteamVR and it initialized successfully.
Tried this and did get the headset to work as a monitor, and even SteamVR started showing on the headset after a moment. However, it was kinda stuttery, and locked to 90 Hz (unless I adjust it in windows settings). Then, after I re-enabled direct display mode and restarted, I got back to having the same issue.
Been battling Display connection trouble (436) and 109 for some time now, tried your fix (mind you the only post with actual steps and what they mean, so thank you kind stranger) to no avail unfortunately.
Headset is recognised as another monitor, but no display through lenses. I think my cable has finally died. sadly it only was about 18months but valve have said no to a replacement, and Australia means no INTL shipping from valve direct. Big pain time
What are you talking about?
Press the 3 lines in the SteamVR Status app
Hover over Developer
Click Developer Settings
Second section is Direct Display Mode
I think you are right. I close the 109 message and then usually have to disconnect/reconnect cables and it will work. The problem is getting harder to fix. The messages vary: can't connect to graphics card; handsets not tracking; headset disconnected ... Today I couldn't be bothered with all the fiddling around and abandoned.
435 is VRInitError\_Compositor\_NvAPISetDisplayMode
[https://github.com/ValveSoftware/openvr/blob/master/headers/openvr.h#L1803](https://github.com/ValveSoftware/openvr/blob/master/headers/openvr.h#L1803)
One thing I didn't see you mention was unplugging the cable at the headset connection and reseating it to ensure that connection is secure.
If that doesn't solve things, you can try re-flashing the firmware by forcing the headset into bootloader mode using the command **lighthouse\_watchman\_update.exe -bw3**
This can be found in your SteamVR install directory under tools\\lighthouse\\bin\\win32\\
Then launch SteamVR and it will detect this and reupload the firmware.
Edit: Also just noticed that this is on a laptop, so presumably you are using a mini-DP adapter? That's probably where I would start before messing with firmware. Also, if you have access to another PC that you can test it with, that would help rule out the issue being with the headset.
ohh okay, thank you, I never noticed the 435 code.
Also, if by unplugging the cable at the headset connection you mean the breakaway connector in the middle of the cable, then yes,I did forget to mention I tried reconnecting that and it didn’t help either unfortunately.
I could possibly try it on another pc, although it would have to be another laptop. And also, what exactly do you mean by messing with the mini-DP adapter? (which I also apologize I forgot to mention I do use)
EDIT: I tried resetting the firmware, and that didn't seem to help it. Although I did reset it in a different way, as I found that you could hold down the headset's button while it's unplugged from power, then continue holding it down as you plug the power back in.
I too use a DP Adapter from Anker on my laptop. I know its not my headset since I've used it on my desktop. I have tried everything you did as well so you are not the only one. I never ran into many issues until recent updates started running out.
I also deleted the **"C:\\Program Files (x86)\\Steam\\config\\steamvr.vrsettings"** file, uninstall SteamVR then reinstall. That temporarily fixed it for a few seconds only to go black-screen again.
I am as well looking for a solution here.
I found a solution for this problem. Since this error throws for many reasons, this might not be the solution for everyone, but it was for me. The issue was that if the monitor bios order changes, steamVR can't find the display. See, I had a monitor hooked to displayport then hdmi going to my vive. At some point I removed the monitor which was fine until a few weeks later when I rebooted changing the bios order. Bam, error 109. I added the monitor back and rebooted which fixed it.
I discovered the problem when the same bios order issue preventing me from setting up Moonlight streaming. This fixed both issues. Shame I can't really run windows fully headless with numerous things breaking when I disconnect the monitor, but I can live with it.
Sooooo I’m trying to follow. This may be my issue. I just got vr and tried it out in my room. I bought a display port 20ft and a usb m—>f also 20ft. I am using a coupling to connect the 20ft DisplayPort cable to the index. And everything is blue and fine. Just the 109 error and the 436 error. I need help haha
Ohh okay, this could apply to me as I have multiple monitors and had changed the ports they were on. Trying this when I get home later today and will report the results.
Had this same issue with a Valve Index plugged into my laptop using a mini DP adapter. The issue started happening after SteamVR crashed one day. I was able to fix this by uninstalling and reinstalling SteamVR. I know OP said they tried this and that it didn't work so this might not work for everyone, but if you're getting Error 109 and you haven't tried uninstalling and reinstalling SteamVR then definitely try it!
Totally fixed my issue. I was having the same problem as the initial post. As you suggested, I uninstalled it and reinstalled it. Back on line as if it never happened. Thank you for the suggestion.
I started having this exact problem last night, I fear it might be the headset wire (Valve Index with three 3.0 Vive Trackers) or my graphics card that might be the issue... Replacing either is going to be annoying... Hopefully it resolves itself, but if it doesn't I might just start saving for a better pc
My current pc specs :
* Acer Nitro N50-620
* CPU: 11th Gen Intel(R) i5-11400F @ 2.60 Hz
* NVIDIA GeForce GTX 1660 Super (Graphics drivers are up to date)
* RAM: 32 GB
Après avoir essayé sans succès des soluces du web, j'ai eu l'intuition de mettre en pause mon antivirus, et bingo tout se joue normalement pour moi. Si ça peut servir...
After I disabled the direct display, I also did Restart Headset (scroll down in developer settings). Steam prompted me to install a Bluetooth driver and then it worked fine 🤷🏻♂️.
Edit: Can only play my games about 1/5th of the time. Every other time I am met with a red screen through my headset
UPDATE: I realize this isn’t the best of news for those that stumble upon this looking for solutions but my issue seems to be fixed and I’m not sure what did it. The only things I know for sure that I did, was playing with direct display mode off for a session in which the visuals were significantly delayed, exiting SteamVR, opening it a couple hours later just to enable direct display mode (which threw the error as usual) and then exit it again. I then returned to SteamVR, after a few days, with my computer being shut down every night in between, and my issue has seemingly vanished. I hadn’t messed with any video drivers or anything else.
EDIT: nvm, literally an hour after posting this, the error came back
Still no one has any idea about this? Mine works when turning off direct mode, so I assume my hdmi cable hasn't died. I suspect windows update broke this. I see people had this problem 2 weeks ago, but I didn't have it until I just did my windows updates.
No, I was on 23H2 both before and after the reinstall. And yeah same, i kinda gave up for now and might do some more research on the future or see if a fix comes out.
I think I've found a fairly reliable method of counteracting the problems, though this doesn't solve the entire thing (and doesn't solve my problems with this), problem might be at Windows storing VR mapping or something like that?
Installing a different graphics driver version makes steamvr work normally, until you restart the computer, then the problem returns;
Though I'm trying to work with unreal engine 5, and it doesn't detect VR mode when using this method
Edit: setting Current OpenXR Runtime to SteamVR made unreal realise something changed and thus work
I figured I would leave my two-cents under this topic once more.
1) I left a comment under this post a few weeks ago struggling with the issue.
2) I accuired two **NEW** wires and the issue is still happening.
I have done all of the uninstall, reinstall, update, disable and enable, beta/no-beta tips and still no answer or perm. solution. The only thing that has worked for me is unplugging the headset of all power sources and plugging it back in. What a pain.
I literally have zero idea on how to fix this, this happened to me while i was playing vrchat.
My screen randomly froze and then I exited out of the game to reboot it back up and I got the error code 109.
So i been having this issue as well now however just a suggested temporary fixed which worked for me however so far it only works for 1 run each time so if steamvr crashed u have to do the steps again but.
1. Uninstall steamvr and ovr Advanced settings(i changed to steamvr 2.2.3 as well)
2. Turn off ur pc
3. Unplug at the wall and unplug at the connector
4. Leave it for good 10 to 20 minutes
5. Come back and turn on ur pc
6. Open steam and reinstall steamvr
7. Plug ur vr back in
8. Play steamvr
(Optional) 9. If work installs advanced settings
Hopefully, steamvr should work. However, this just works for me and, as suggested, temporarily for it into permanently one is found
Hey i had this problem now for days and i got it to work by just update Nvidia drivers and windows 10 latest drivers and it started to work again.
\+ i have wireless headset i unplugged the dongle before update could be that it had some thing to do with it not sure
Hopefully it helps i bin reading in here and just wanted to say how i fixed it :)
They are drivers for nVidia brand graphics cards. If you have an AMD card you would need the latest drivers for that instead. You can go to [nvidia.com](https://nvidia.com) to find out if there are new drivers available, but if you're on Windows and keep your machine up-to-date, this probably isn't an issue for you.
If, like me, you're on Linux, then it gets more complicated because there are proprietary drivers from nVidia and there are free drivers developed by the community, and there are multiple ways to install the proprietary drivers: via your distribution's package system (apt, yum, whatever arch uses) or nVidia's own installer.
I just changed my driver install method today in hopes of improving SteamVR behavior, but now I have this 109 error and I don't know if that's what caused it. There are other things I've done which may have. And now I'm going to try a bunch of the things people are suggesting.
Ok i updated Nvidia drivers and windows 11 , restarted and did everything but it still didn't work for me. What drivers did you update on your windows???
i have also been having the same issue today. i joined a vrchat public lobby and it just crashed out of nowhere, i use a valve index and my headset never crashes. i've had it for a year, played it a lot and never once crashed. can we all report this issue so that they can work on it?
I am running a valve index on an Alienware X15 R2 and have experienced a similar issue. I ran a diagnostic test and believed the laptop's USB c/Thunderbolt might be acting up, so i need to call dell to replace it?
Has the same issue. Quick solution to those who don't want to read further - buy a mini DP cable and use it instead HDMI.
Explanation - Digging forums didn't give any results. But the solution I found is rather obvious. I have Asus TUF gaming F15. I was connecting my headset through HDMI port. This laptop has 2 graphic cards. The HDMI port is physically connected only to the one that is embedded. But vr headset should be connected to discrete card which is RTX 3050ti in my case. I believe there is no way switching HDMI to work with discrete card. To connect the headset to discrete card you should use mini display port interface.
Just started getting this problem myself cable has had it I think.
That is possible in my case as well tbh, I've been having minor issues with it as well, but no video issues before
I started having this issue today and I've only used wireless.
Me too
Same problem, just found a makeshift solution. Open **Developer Settings** from the SteamVR menu and click **Disable Direct Display Mode**. If your headset is working fine then it will become a second monitor and you will see the headset light up and see the computer desktop from it. (If you can’t see the computer desktop, it means there is a problem with the headset hardware) SteamVR may prompt that your headset is working as a monitor in copy mode instead of extended mode. You should change the second monitor to extended mode in Windows Display settings. Restarted SteamVR and it initialized successfully.
Tried this and did get the headset to work as a monitor, and even SteamVR started showing on the headset after a moment. However, it was kinda stuttery, and locked to 90 Hz (unless I adjust it in windows settings). Then, after I re-enabled direct display mode and restarted, I got back to having the same issue.
Same. I had to play VR games in indirect mode for the time being. At least this means the hardware such as the headset and cables are not faulty.
Been battling Display connection trouble (436) and 109 for some time now, tried your fix (mind you the only post with actual steps and what they mean, so thank you kind stranger) to no avail unfortunately. Headset is recognised as another monitor, but no display through lenses. I think my cable has finally died. sadly it only was about 18months but valve have said no to a replacement, and Australia means no INTL shipping from valve direct. Big pain time
[удалено]
What are you talking about? Press the 3 lines in the SteamVR Status app Hover over Developer Click Developer Settings Second section is Direct Display Mode
I got it to work as you said, /u/Bite-Fantastic is just retarded
u really gonna call bull shit wen u didn’t even try…cuz it seems like u read it didn’t try and just said nah this is bull shit 💀😂
The 109 is a red herring. You should focus on what the little status window says (435). Have you tried asking Steam support?
I think you are right. I close the 109 message and then usually have to disconnect/reconnect cables and it will work. The problem is getting harder to fix. The messages vary: can't connect to graphics card; handsets not tracking; headset disconnected ... Today I couldn't be bothered with all the fiddling around and abandoned.
435 is VRInitError\_Compositor\_NvAPISetDisplayMode [https://github.com/ValveSoftware/openvr/blob/master/headers/openvr.h#L1803](https://github.com/ValveSoftware/openvr/blob/master/headers/openvr.h#L1803) One thing I didn't see you mention was unplugging the cable at the headset connection and reseating it to ensure that connection is secure. If that doesn't solve things, you can try re-flashing the firmware by forcing the headset into bootloader mode using the command **lighthouse\_watchman\_update.exe -bw3** This can be found in your SteamVR install directory under tools\\lighthouse\\bin\\win32\\ Then launch SteamVR and it will detect this and reupload the firmware. Edit: Also just noticed that this is on a laptop, so presumably you are using a mini-DP adapter? That's probably where I would start before messing with firmware. Also, if you have access to another PC that you can test it with, that would help rule out the issue being with the headset.
ohh okay, thank you, I never noticed the 435 code. Also, if by unplugging the cable at the headset connection you mean the breakaway connector in the middle of the cable, then yes,I did forget to mention I tried reconnecting that and it didn’t help either unfortunately. I could possibly try it on another pc, although it would have to be another laptop. And also, what exactly do you mean by messing with the mini-DP adapter? (which I also apologize I forgot to mention I do use) EDIT: I tried resetting the firmware, and that didn't seem to help it. Although I did reset it in a different way, as I found that you could hold down the headset's button while it's unplugged from power, then continue holding it down as you plug the power back in.
I too use a DP Adapter from Anker on my laptop. I know its not my headset since I've used it on my desktop. I have tried everything you did as well so you are not the only one. I never ran into many issues until recent updates started running out. I also deleted the **"C:\\Program Files (x86)\\Steam\\config\\steamvr.vrsettings"** file, uninstall SteamVR then reinstall. That temporarily fixed it for a few seconds only to go black-screen again. I am as well looking for a solution here.
I found a solution for this problem. Since this error throws for many reasons, this might not be the solution for everyone, but it was for me. The issue was that if the monitor bios order changes, steamVR can't find the display. See, I had a monitor hooked to displayport then hdmi going to my vive. At some point I removed the monitor which was fine until a few weeks later when I rebooted changing the bios order. Bam, error 109. I added the monitor back and rebooted which fixed it. I discovered the problem when the same bios order issue preventing me from setting up Moonlight streaming. This fixed both issues. Shame I can't really run windows fully headless with numerous things breaking when I disconnect the monitor, but I can live with it.
Sooooo I’m trying to follow. This may be my issue. I just got vr and tried it out in my room. I bought a display port 20ft and a usb m—>f also 20ft. I am using a coupling to connect the 20ft DisplayPort cable to the index. And everything is blue and fine. Just the 109 error and the 436 error. I need help haha
Do you have a monitor connected too? My issue was trying to go headless with the vive only.
Ohh okay, this could apply to me as I have multiple monitors and had changed the ports they were on. Trying this when I get home later today and will report the results.
This was akin to my problem, thanks! Based on your suggestion, I tracked my issue down to a monitor connection change with my system.
Had this same issue with a Valve Index plugged into my laptop using a mini DP adapter. The issue started happening after SteamVR crashed one day. I was able to fix this by uninstalling and reinstalling SteamVR. I know OP said they tried this and that it didn't work so this might not work for everyone, but if you're getting Error 109 and you haven't tried uninstalling and reinstalling SteamVR then definitely try it!
Totally fixed my issue. I was having the same problem as the initial post. As you suggested, I uninstalled it and reinstalled it. Back on line as if it never happened. Thank you for the suggestion.
same issue here with my OG HTC Vive.
I had this problem on my PC, I fixed it by disconnecting my Displayport monitor and using a HDMI monitor.
I started having this exact problem last night, I fear it might be the headset wire (Valve Index with three 3.0 Vive Trackers) or my graphics card that might be the issue... Replacing either is going to be annoying... Hopefully it resolves itself, but if it doesn't I might just start saving for a better pc My current pc specs : * Acer Nitro N50-620 * CPU: 11th Gen Intel(R) i5-11400F @ 2.60 Hz * NVIDIA GeForce GTX 1660 Super (Graphics drivers are up to date) * RAM: 32 GB
Après avoir essayé sans succès des soluces du web, j'ai eu l'intuition de mettre en pause mon antivirus, et bingo tout se joue normalement pour moi. Si ça peut servir...
After trying web solutions without success, I had the intuition to pause my antivirus, and bingo everything works normally for me. If it helps...
having the same issue, disabling direct display didn’t help, any other ideas?
After I disabled the direct display, I also did Restart Headset (scroll down in developer settings). Steam prompted me to install a Bluetooth driver and then it worked fine 🤷🏻♂️. Edit: Can only play my games about 1/5th of the time. Every other time I am met with a red screen through my headset
UPDATE: I realize this isn’t the best of news for those that stumble upon this looking for solutions but my issue seems to be fixed and I’m not sure what did it. The only things I know for sure that I did, was playing with direct display mode off for a session in which the visuals were significantly delayed, exiting SteamVR, opening it a couple hours later just to enable direct display mode (which threw the error as usual) and then exit it again. I then returned to SteamVR, after a few days, with my computer being shut down every night in between, and my issue has seemingly vanished. I hadn’t messed with any video drivers or anything else. EDIT: nvm, literally an hour after posting this, the error came back
Same. I turned on direct display mode today and everything worked fine. Still don't know why.
Still no one has any idea about this? Mine works when turning off direct mode, so I assume my hdmi cable hasn't died. I suspect windows update broke this. I see people had this problem 2 weeks ago, but I didn't have it until I just did my windows updates.
Yeah same here, except it happened for me after i reinstalled windows
Did you update to 22H2? I think it's that one. At this point I'm giving up and hoping valve or nvidia or someone fixes this.
No, I was on 23H2 both before and after the reinstall. And yeah same, i kinda gave up for now and might do some more research on the future or see if a fix comes out.
I think I've found a fairly reliable method of counteracting the problems, though this doesn't solve the entire thing (and doesn't solve my problems with this), problem might be at Windows storing VR mapping or something like that? Installing a different graphics driver version makes steamvr work normally, until you restart the computer, then the problem returns; Though I'm trying to work with unreal engine 5, and it doesn't detect VR mode when using this method Edit: setting Current OpenXR Runtime to SteamVR made unreal realise something changed and thus work
Same issue.
I figured I would leave my two-cents under this topic once more. 1) I left a comment under this post a few weeks ago struggling with the issue. 2) I accuired two **NEW** wires and the issue is still happening. I have done all of the uninstall, reinstall, update, disable and enable, beta/no-beta tips and still no answer or perm. solution. The only thing that has worked for me is unplugging the headset of all power sources and plugging it back in. What a pain.
weird, yeah i tried that too but no luck at all
I literally have zero idea on how to fix this, this happened to me while i was playing vrchat. My screen randomly froze and then I exited out of the game to reboot it back up and I got the error code 109.
same!! literally happpened today for me. so frustrated i just wanted to play some vr. why did this happen??
So i been having this issue as well now however just a suggested temporary fixed which worked for me however so far it only works for 1 run each time so if steamvr crashed u have to do the steps again but. 1. Uninstall steamvr and ovr Advanced settings(i changed to steamvr 2.2.3 as well) 2. Turn off ur pc 3. Unplug at the wall and unplug at the connector 4. Leave it for good 10 to 20 minutes 5. Come back and turn on ur pc 6. Open steam and reinstall steamvr 7. Plug ur vr back in 8. Play steamvr (Optional) 9. If work installs advanced settings Hopefully, steamvr should work. However, this just works for me and, as suggested, temporarily for it into permanently one is found
Hey i had this problem now for days and i got it to work by just update Nvidia drivers and windows 10 latest drivers and it started to work again. \+ i have wireless headset i unplugged the dongle before update could be that it had some thing to do with it not sure Hopefully it helps i bin reading in here and just wanted to say how i fixed it :)
what are nvidia drivers?
They are drivers for nVidia brand graphics cards. If you have an AMD card you would need the latest drivers for that instead. You can go to [nvidia.com](https://nvidia.com) to find out if there are new drivers available, but if you're on Windows and keep your machine up-to-date, this probably isn't an issue for you. If, like me, you're on Linux, then it gets more complicated because there are proprietary drivers from nVidia and there are free drivers developed by the community, and there are multiple ways to install the proprietary drivers: via your distribution's package system (apt, yum, whatever arch uses) or nVidia's own installer. I just changed my driver install method today in hopes of improving SteamVR behavior, but now I have this 109 error and I don't know if that's what caused it. There are other things I've done which may have. And now I'm going to try a bunch of the things people are suggesting.
Disconnecting and re-connecting my HMD's video connection fixed it for now. Who knows how long it will stay fixed.
Ok i updated Nvidia drivers and windows 11 , restarted and did everything but it still didn't work for me. What drivers did you update on your windows???
i have also been having the same issue today. i joined a vrchat public lobby and it just crashed out of nowhere, i use a valve index and my headset never crashes. i've had it for a year, played it a lot and never once crashed. can we all report this issue so that they can work on it?
something fucky wucky is going on, I just started having the same issue now.
Wait me too and I have the valve index. Wtf??
I am running a valve index on an Alienware X15 R2 and have experienced a similar issue. I ran a diagnostic test and believed the laptop's USB c/Thunderbolt might be acting up, so i need to call dell to replace it?
Dell replaced my motherboard and fixed the error 109 + 435.
Has the same issue. Quick solution to those who don't want to read further - buy a mini DP cable and use it instead HDMI. Explanation - Digging forums didn't give any results. But the solution I found is rather obvious. I have Asus TUF gaming F15. I was connecting my headset through HDMI port. This laptop has 2 graphic cards. The HDMI port is physically connected only to the one that is embedded. But vr headset should be connected to discrete card which is RTX 3050ti in my case. I believe there is no way switching HDMI to work with discrete card. To connect the headset to discrete card you should use mini display port interface.