Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
It did this yesterday and I saw this error number for the first time but couldn't find any information relating to it, so would be useful to know what it means and what the fix is.
As usual I managed to get my unit working again by trying different things, restarting SteamVR, restarting PC, fiddling with the headset parts a bit, etc. but I am still not sure what the root cause was/is or what this new error number means.
I disabled my camera when I had the issue and have not seen it since, so looks like that could well be the root cause. Hopefully it'll be fixed in the next update or two.
(Steam VR 1.2.4...1.2.6, Machine: Lenovo Ideapad Y910, 6820HK, 16GB Ram, GTX1070, Win10)
A lot of internetresearche solve the Problem for me:
Just installed "Microsoft Visual C++" and my Vive works staple.
It works, thanks.
i installed it from here:
https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads
Update/reinstall your GPU drivers.
Update your BIOS/other drivers.
Try a different USB port (USB 2.0 recommended for VIVE users)
Verify the SteamVR files/reinstall.
Delete any EXTRA plugins you may have installed like SteamVR Input Emulator etc.
You should be careful with this if you have an AMD 10xx or 20xx ryzen and a motherboard with 370x or 470x
when the ryzen 30xx arrives is possible that the companyes upload an update of BIOS that delete the compatibility with old ryzens because this mother boards have low space for enable the compatibility with the new CPUs and the olds at the same.
Got my first Vive 6 moths ago, on the sixth month it started to give me the -102 making every game a frustrating battle. Sometimes it was fine for a couple of hours and then it started giving the -102 again. Chatted for a week with Vive, steam and the supplier. Ended up sending it back. They confirmed a hardware problem. Got an entirely new set.
2 weeks in, starting giving me the -102 on the second set.
Just to be clear. No reflecting surfaces in the room. Latest bios mono version. Tried all the USB ports. I really would like to know what the hell is going on.
Hey guys, I WAS struggling with this issue for a whole week!
It really annoyed me because I finally cleaned up my bedroom and made ample space to use "Room-scale" VR.
I noticed that the headset would lose tracking if it wasn't facing the base stations directly. If I turned away, it would go blue screen and SteamVR would display the (-102) error code.
Sometimes it wouldn't even track at all, a slight movement and i'll get a permanent blue screen from my headset.
I did see other people say to update their graphics drivers, although the difference was that I went to Device Manager, right clicked "Display Adapters" and searched for drivers there.
Unfortunately that driver update was not the latest drivers, I had to go to my NVIDIA GeForce Experience (Your graphics cards manufacturers control panel) and update the drivers through there. It was a 500mb driver update so there definitely was some important packages included.
And.... TADA NO MORE -102 errors, my VR works like a charm!
I hope this helps at this one more person!
Anyway, I'm going to copy/paste this to all other forums that discuss this issue hoping that it'll help at least one other person.
Tags for other people to discover:
102 -102 error steamVR steam VR STEAMVR blue screen bluescreen
I've tried the following...
- Updating my graphics drivers - they are already the latest
- Updating my USB/MoBo drivers - also all already the latest
- Checking all the cables are nice and snug - yes, they are!
- Trying all the different USB ports - USB is working fine in a 2.0 port (as recommended)
- Uninstalled my virus software (Avast)
- Installed x86 AND 64bit C++
- Uninstalled and reinstallled the Vive software
- Uninstalled and reinstalled the USB device drivers
- Disabled the front camera
- Disconnected all unused USB devices
- Turned off USB power saving
- Set sensors to A mode (as opposed to b & c)
No frickin' dice what-so-ever. :( :( :(
I am pretty cross to be honest.
Any other ideas I might try?