Jump to content

Vive Wireless - Error 10001.9 and 10001.5


Recommended Posts

Posted

I posted a while back about an 10001.9 error I was getting with my regular Vive and the Wireless Adapter Kit but I couldn´t find a solution.  So here I go again...

This is how the problem happens: I can use my Vive for a few minutes and then suddenly the Vive screen turns gray and I see the error 10001.9 at the Vive Wireless window.  If I close it and try reopening it, I get the error 10001.5.  The only way to solve it is shutting down and rebooting (restarting doesn´t work, when I try it, it freezes the computer in the process).

Has anyone found a solution yet?

@Synthesis

Posted

Sorry but I don’t think that this is a common problem and it normally should be solved by referring to the manual’s troubleshooter  I suggest you work with Vive support and see if you can identify the cause.  Could be a driver or maybe a hardware defect. Who knows?

Hard to believe you have suffered with this problem for so long.

  • 2 months later...
Posted

Just wanted to pop in here and say that I've had this problem since I've had it (about a year now). I just reboot a lot and eventually bits "stable" for that play time. Have never found a fix. And as far as I know, no one has, they just give up and either don't use the wireless or deal with it.

  • 1 month later...
Posted

Same here. Been dealing with this issue since purchasing the wireless VR. Found this in a log file in the system info program:

 

[2020-05-10 13:11:32.053 -7 0x4A84 INFO LOG] MCU Update Closed. Wait for 3 seconds.
[2020-05-10 13:11:35.082 -7 0x4A84 INFO LOG] [SetCosmosAudio] Launch OK.
[2020-05-10 13:11:35.099 -7 0x4A84 INFO LOG] Connection Status set to 5(CONNECTION_STATUS_CONNECTED)
[2020-05-10 13:11:39.261 -7 0x4064 INFO LOG] (ControlCenter)CallbackDeviceStatus : SDK_WIGIGFSM_STATE_UNINITIALIZED(1), reason = SDK_CURRENT_STATE_REASON_REQUESTED_BY_APPLICATION(9)
[2020-05-10 13:11:41.264 -7 0x4064 INFO LOG] (ControlCenter)CallbackDeviceStatus : SDK_WIGIGFSM_STATE_UNINITIALIZED(1), reason = SDK_CURRENT_STATE_REASON_REQUESTED_BY_APPLICATION(9)
[2020-05-10 13:11:41.265 -7 0x1060 INFO LOG] [SetCosmosAudio] Terminate OK.
[2020-05-10 13:11:41.265 -7 0x1060 INFO LOG] Show error code : 10001.9
[2020-05-10 13:11:41.280 -7 0x1060 INFO LOG] Connection Status set to 6(CONNECTION_STATUS_NOT_READY)
[2020-05-10 13:11:41.280 -7 0x1060 INFO LOG] Show error code : 10001.9
[2020-05-10 13:11:41.296 -7 0x1060 INFO LOG] Connection Status set to 6(CONNECTION_STATUS_NOT_READY)
[2020-05-10 13:11:41.465 -7 0x4064 INFO LOG] (ControlCenter)CallbackDeviceStatus : SDK_WIGIGFSM_STATE_ERROR(0), reason = SDK_CURRENT_STATE_REASON_PLATFORM_ERROR(15)
 

So it's possible to figure out the cause. Seems to be something to do with the intel software.

  • 1 month later...
  • 3 weeks later...
Posted

Same here. Yesterday it was working. Today, it suddenly stopped working.

No Windows updates (this was the previous cause of trouble with vive wireless).

And apparently, no reaction from VIVE in 6 months....

  • 10 months later...
Posted

It appears the app can now recover from this condition VS requiring a full reboot.  Still very clunky as it takes a good 20 seconds to recover.  Here is my log file from a recent instance.

Quote

[2021-05-31 06:13:29.949 -6 0x363C INFO LOG] (ControlCenter)CallbackDeviceStatus : SDK_WIGIGFSM_STATE_UNINITIALIZED(1), reason = SDK_CURRENT_STATE_REASON_REQUESTED_BY_APPLICATION(9)
[2021-05-31 06:13:29.949 -6 0x32E4 INFO LOG] [SetCosmosAudio] Terminate OK.
[2021-05-31 06:13:29.949 -6 0x32E4 INFO LOG] Show error code : 10001.9
[2021-05-31 06:13:29.952 -6 0x32E4 INFO LOG] Connection Status set to 6(CONNECTION_STATUS_NOT_READY)
[2021-05-31 06:13:30.383 -6 0x363C INFO LOG] (ControlCenter)CallbackDeviceStatus : SDK_WIGIGFSM_STATE_UNINITIALIZED(1), reason = SDK_CURRENT_STATE_REASON_REQUESTED_BY_APPLICATION(9)
[2021-05-31 06:13:30.383 -6 0x32E4 INFO LOG] Show error code : 10001.9
[2021-05-31 06:13:30.385 -6 0x32E4 INFO LOG] Connection Status set to 6(CONNECTION_STATUS_NOT_READY)
[2021-05-31 06:13:30.613 -6 0x363C INFO LOG] (ControlCenter)CallbackDeviceStatus : SDK_WIGIGFSM_STATE_UNINITIALIZED(1), reason = SDK_CURRENT_STATE_REASON_COMMAND_IN_PROGRESS(12)
[2021-05-31 06:13:30.613 -6 0x32E4 INFO LOG] Show error code : 10001.12
[2021-05-31 06:13:30.616 -6 0x32E4 INFO LOG] Connection Status set to 6(CONNECTION_STATUS_NOT_READY)
[2021-05-31 06:13:31.018 -6 0x363C INFO LOG] (ControlCenter)CallbackDeviceStatus : SDK_WIGIGFSM_STATE_STOPPED(3), reason = SDK_CURRENT_STATE_REASON_NOT_SCANNING(16)
[2021-05-31 06:13:31.021 -6 0x363C INFO LOG] (ControlCenter)CallbackDeviceStatus : SDK_WIGIGFSM_STATE_SCANNING(4), reason = SDK_CURRENT_STATE_REASON_REQUESTED_BY_APPLICATION(9)
[2021-05-31 06:13:31.023 -6 0x32E4 INFO LOG] Connection Status set to 2(CONNECTION_STATUS_SCANNING)
[2021-05-31 06:13:34.238 -6 0x363C INFO LOG] (ControlCenter)CallbackDeviceStatus : SDK_WIGIGFSM_STATE_CONNECTING(5), reason = SDK_CURRENT_STATE_REASON_AUTO_PROFILE_FOUND(4)
[2021-05-31 06:13:34.240 -6 0x32E4 INFO LOG] Connection Status set to 3(CONNECTION_STATUS_CONNECTING)
[2021-05-31 06:13:34.501 -6 0x363C INFO LOG] (ControlCenter)CallbackDeviceStatus : SDK_WIGIGFSM_STATE_CONNECTED(7), reason = SDK_CURRENT_STATE_REASON_SUCCEED_TO_CONNECT(13)

 

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...