after countless weeks and hours trying to figure it out I finally did. after the research everyone was mostly giving the same soulution but was not working. the (309) error code have to do with the amd drivers. I don't have amd gpu but I do the cpu so I though maybe it's not that so I ignored it. I went into my installed apps and noticed I had amd adrenaline installed and I don't need it since I don't have amd gpu and I Uninstalled it and boom it works now. either Uninstall it or roll back your drivers if you do have one becuase I have tried absolutely everything and nothing worked except this method.

Same here, it looks like.
Steam VR has been problematic/unworkable for the last 2 months or so.
I think the last version that worked well was 2.3.2 (or 2.3.3)
My setup:
OS: Windows 10 pro (up to date)
Proc: Intel i9, 10Core, 32Gb memory
GPU: NVIDIA 3080Ti (up to date driver)
VR: HTC Vive Pro 2
Monitors: 2 screen, side by side. The application runs on one, not on two screens.
Steam VR 2.3.5 and ViveConsole.
Steam VR is My OpenVR

Current symptoms:
Steam VR takes long to start, about 30% of the time ViveConsole reports an error, so a restart is necessary.
My (left) monitor shows (side by side) the images that were generated for the headset.
The framerate is extremely low, about 1Hz.
My headset shows the default image: A plane with concentric circles and the horizon is a mountain range. In the view center is a window that shows the app running (such as MSFS2020) and “Wait”. In other words, the images visible on the monitor are not visible in the headset.
At that point there is no other option than to restart Steam VR (which takes several minutes) This may lead to a system freeze. The only option then is to restart with the power button.
Sometimes, however, this may work. My headset works, tracking may be slow in the first 30 seconds or so, but then it works. This transition to a working state occurs about 50% of the time.
It may occur that after a few minutes, the framerate in the headset drops to 1 Hz. again.
I’ve seen the: "A key component of SteamVR isn't working properly. Please restart SteamVR." too.
When I terminate the app, sometimes Steam VR closes down as well. When I terminate Steam VR that may take up to a minute until my system unfreezes. And then the tracking stations are left on. Earlier versions of Steam VR would close immediately and put the VR trackers in stand by mode.
I do not understand.
Everything was working nicely in 2.3.2. Why fix it?!? There is a solid engineering practice: “If it aint broke, don’t fix it.”
I saw this coming in the Beta. So then, I could go back to stable releases. But it seems that this Beta has now progressed to a “stable” release. In My case, it is anything but stable. I’ve not been able to run MSFS2020 or DCS World for the last 2 months. (My favorite VR apps)
I would like to revert to 2.3.2 or 2.3.3. But that is (almost) impossible and it will update with the first opportunity it gets.
Do you have any idea what is wrong here? (I did a file verification of Steam VR and ViveConsole and the latter had 3 files that needed to be reacquired. The problems I describe above are after the correction of the ViveConsole files) Is there something wrong with the OpenVR? How do I fix that? Are those updated automatically as well?

Originalmente postado por Dugberry:

Same here, it looks like.
Steam VR has been problematic/unworkable for the last 2 months or so.
I think the last version that worked well was 2.3.2 (or 2.3.3)
My setup:
OS: Windows 10 pro (up to date)
Proc: Intel i9, 10Core, 32Gb memory
GPU: NVIDIA 3080Ti (up to date driver)
VR: HTC Vive Pro 2
Monitors: 2 screen, side by side. The application runs on one, not on two screens.
Steam VR 2.3.5 and ViveConsole.
Steam VR is My OpenVR

Current symptoms:
Steam VR takes long to start, about 30% of the time ViveConsole reports an error, so a restart is necessary.
My (left) monitor shows (side by side) the images that were generated for the headset.
The framerate is extremely low, about 1Hz.
My headset shows the default image: A plane with concentric circles and the horizon is a mountain range. In the view center is a window that shows the app running (such as MSFS2020) and “Wait”. In other words, the images visible on the monitor are not visible in the headset.
At that point there is no other option than to restart Steam VR (which takes several minutes) This may lead to a system freeze. The only option then is to restart with the power button.
Sometimes, however, this may work. My headset works, tracking may be slow in the first 30 seconds or so, but then it works. This transition to a working state occurs about 50% of the time.
It may occur that after a few minutes, the framerate in the headset drops to 1 Hz. again.
I’ve seen the: "A key component of SteamVR isn't working properly. Please restart SteamVR." too.
When I terminate the app, sometimes Steam VR closes down as well. When I terminate Steam VR that may take up to a minute until my system unfreezes. And then the tracking stations are left on. Earlier versions of Steam VR would close immediately and put the VR trackers in stand by mode.
I do not understand.
Everything was working nicely in 2.3.2. Why fix it?!? There is a solid engineering practice: “If it aint broke, don’t fix it.”
I saw this coming in the Beta. So then, I could go back to stable releases. But it seems that this Beta has now progressed to a “stable” release. In My case, it is anything but stable. I’ve not been able to run MSFS2020 or DCS World for the last 2 months. (My favorite VR apps)
I would like to revert to 2.3.2 or 2.3.3. But that is (almost) impossible and it will update with the first opportunity it gets.
Do you have any idea what is wrong here? (I did a file verification of Steam VR and ViveConsole and the latter had 3 files that needed to be reacquired. The problems I describe above are after the correction of the ViveConsole files) Is there something wrong with the OpenVR? How do I fix that? Are those updated automatically as well?

AT this point in time you cannot fix it.
You will have to wait for an update for steamVR.
Unfortunately troubleshooting everything has caused me to verify that it is infact a pure steamvr issue and someone screwed up.

good

Originalmente postado por Dugberry:

Everything was working nicely in 2.3.2. Why fix it?!? There is a solid engineering practice: “If it aint broke, don’t fix it.”
I saw this coming in the Beta.

Did you submit a bug report when you saw it in the beta?

You might try having just one monitor at 1080p during your troubleshooting. Have you tried toggling the openxr setting? Removing all third party apps except vive console?

>"Why fix it"
Valve came out with the new version to fix the things mentioned in the changelog. It is not a reasonable to expect Valve to freeze VR development at 2.3.2 for one person.

This issue is still happening if you're looking

I also had the issue mentioned in the original post and on my system the AMD iGPU driver as well as RTX 4080 drivers were installed, but the iGPU was disabled in Bios (but I never deleted the iGPU drivers).

The issue SteamVR was fixed for me when I used DDU to deinstall the AMD iGPU drivers.

Originally posted by Dugberry:
Same here, it looks like.
Steam VR has been problematic/unworkable for the last 2 months or so.
I think the last version that worked well was 2.3.2 (or 2.3.3)

So, after this valley of tears, I decide to remove and reinstall everything VR. And combed the registry as well.
Setup included the controller bindings, room setup, everything. And ....
Nearly at the end it mentioned a firmware update the HTC Vive Pro 2 ..!..
Obviously, I took that option. And it improved the situation.
At least I havent had the need to reach for the power button since, the system does not freeze anymore. But I have had to restart SteamVR at least once, sometimes two or three times while in MSFS2020 until it works as it should.
Interestingly, SteamVR never showed that the headset needed an update (I checked).
But, at least I can fly again.

SteamVR is trash and hardly works period. Wait for the stable release.

Hey guys, I found the solution for this issue.
Ryzen 5 7600, RTX 4070 Super here. I had my BIOS to CSM instead of UEFI. My Integrated Graphics didn't work, I switched back to UEFI and it's working now

Originalmente postado por OHOHOHOHOHOHCHO:

win 10, R9 3950x, error 309 after upgrading GPU from 6900xt to 4080 super, works fine before the GPU upgrade. Had uninstalled AMD driver but still broken.

Still not working after 1 week. Tried steam beta and steamvr beta, no windows upgrade recently, can't play any PCVR anymore:(

Originalmente postado por OHOHOHOHOHOHCHO:

Originalmente postado por OHOHOHOHOHOHCHO:

win 10, R9 3950x, error 309 after upgrading GPU from 6900xt to 4080 super, works fine before the GPU upgrade. Had uninstalled AMD driver but still broken.

Still not working after 1 week. Tried steam beta and steamvr beta, no windows upgrade recently, can't play any PCVR anymore:(

I've given up. It just doesn't work period.

Originalmente postado por OHOHOHOHOHOHCHO:

Originalmente postado por OHOHOHOHOHOHCHO:

win 10, R9 3950x, error 309 after upgrading GPU from 6900xt to 4080 super, works fine before the GPU upgrade. Had uninstalled AMD driver but still broken.

Still not working after 1 week. Tried steam beta and steamvr beta, no windows upgrade recently, can't play any PCVR anymore:(

Oh, I fixed it! Even tho I uninstalled the AMD GPU driver after switching to NVIDIA, some leftovers of AMD driver was still haunting me. I fixed it simply by uninstalling AMD drivers "again" with DDU, and it did clean something.

I'm getting error codes 424,309 & 109. Everything is updated. Maybe it is some sort of permission problem. As soon I run SteamVR with administrator rights all the errors are gone, and SteamVR connects to my VR Headset. IMHO very strange. Can anyone verify it? Steam Support isn't helpful and IMHO not very competent Thx.

Edit: It works! xD At first I started vrserver.exe as Administrator and then vrstartup.exe as Administrator and tada! I can play games with SteamVR and VD.

@Valve: *facepalm*