cancel
Showing results for 
Search instead for 
Did you mean: 

Oculus Rift S "Oculus isn't working correctly", logs show "WSACancelBlockingCall"

baptiste.r1807
Explorer

Hi !

I'm gonna just became crazy, I used my Oculus 1 full year with my setup without any itch that could make the VR impossible to use but now when I try to use the headset I just get on Windows the notification "Oculus isn't working correctly". Of course I have read all of the support page that didn't help me to solve my problem.

Every checkmark on the Oculus software are green, the headset show a white LED and when I put it on my head I just got a black screen without even the LED screen turned on.

I have since tested a dualboot with a fresh Windows 10 install of Windows and everything works normally, I have updated to the exact same version my GPU drivers for both of my Windows 10 installs.

 

Since the errors show some "TCP" problems, I have also tried to use my headset without Windows Fire-Wall without luck.

 

I also got the error "A blocking operation was interrupted by a call to WSACancelBlockingCall." but I don't know what it mean.

 

This is what the logs show me when I start putting the headset on my head :

I can't add my full .txt logs files to this thread "The file type (.zip) is not supported." (tested with .txt, .zip, .log).

 

Line that are the most important are :

 

10/06 12:39:48.006 {!ERROR!} [KMCore] [VISION][CONSTELLATION] R: Requesting reinitialization of 6DoF filter due to large time delta between current and last IMU sample: 601.618602s
10/06 12:39:48.024 {!ERROR!} [xrstreaming] XrspSocketTransport accept failed for TCP retransmit storm workaround: Une opération de blocage a été interrompue par un appel à WSACancelBlockingCall. (10004)
10/06 12:39:48.024 {!ERROR!} [Kernel:Error] OVR Error:
  Code: -6102 -- ovrError_XRStreamingUSBIssue
  Description: XrspSocketTransport accept failed for TCP retransmit storm workaround: Une opération de blocage a été interrompue par un appel à WSACancelBlockingCall. (10004)
  OVRTime: 3013.137248
  Time: 2022-06-10 12:39:48 [24:157:900]

10/06 12:39:48.024 {INFO}    [xrstreaming] Interrupting listen for TCP retransmit storm workaround
10/06 12:39:48.024 {!ERROR!} [xrstreaming] XrspSocketTransport accept failed for TCP retransmit storm workaround: Une opération de blocage a été interrompue par un appel à WSACancelBlockingCall. (10004)
10/06 12:39:48.024 {!ERROR!} [Kernel:Error] OVR Error:
  Code: -6102 -- ovrError_XRStreamingUSBIssue
  Description: XrspSocketTransport accept failed for TCP retransmit storm workaround: Une opération de blocage a été interrompue par un appel à WSACancelBlockingCall. (10004)
  OVRTime: 3013.137402
  Time: 2022-06-10 12:39:48 [24:312:400]

10/06 12:39:51.386 {!ERROR!} [xrstreaming] XrspSocketTransport accept failed for TCP retransmit storm workaround: Une opération de blocage a été interrompue par un appel à WSACancelBlockingCall. (10004)
10/06 12:39:51.386 {!ERROR!} [Kernel:Error] OVR Error:
  Code: -6102 -- ovrError_XRStreamingUSBIssue
  Description: XrspSocketTransport accept failed for TCP retransmit storm workaround: Une opération de blocage a été interrompue par un appel à WSACancelBlockingCall. (10004)
  OVRTime: 3016.500260
  Time: 2022-06-10 12:39:51 [387:170:200]

10/06 12:39:51.386 {INFO}    [xrstreaming] Interrupting listen for TCP retransmit storm workaround
10/06 12:39:51.386 {!ERROR!} [xrstreaming] XrspSocketTransport accept failed for TCP retransmit storm workaround: Une opération de blocage a été interrompue par un appel à WSACancelBlockingCall. (10004)
10/06 12:39:51.386 {!ERROR!} [Kernel:Error] OVR Error:
  Code: -6102 -- ovrError_XRStreamingUSBIssue
  Description: XrspSocketTransport accept failed for TCP retransmit storm workaround: Une opération de blocage a été interrompue par un appel à WSACancelBlockingCall. (10004)
  OVRTime: 3016.500350
  Time: 2022-06-10 12:39:51 [387:260:500]

10/06 12:39:51.386 {WARNING} [xrstreaming] Failed to construct channel for tcpserver,56225
10/06 12:39:51.386 {WARNING} [xrstreaming] Failed to construct channel for tlsserver,56224

10/06 12:40:03.424 {INFO}    [RiftDML:ReportingManager] Reporting event 'oculus_etw_usb_event'
10/06 12:40:03.424 {INFO}    [RiftDML:EtwReportEventInfo] oculus_etw_usb_event
	provider_guid : ETW_PROVIDER_USB3HUB_GUID
	process_id : 17656
	event_id : USBHUB3_ETW_EVENT_CLIENT_INITIATED_RECOVERY_ACTION
	version : 0
	channel : 16
	task : 11
	opcode : 11
	activity_guid : {00000000-0000-0000-0000-000000000000}
	keyword : 4000000000002401
	event_specific_payload : fid_UsbDevice = 00001f7c900b1398, fid_IoctlCode = 00220003, fid_UrbFunction = 0000001e, 

10/06 12:40:04.715 {INFO}    [DML:HMDNormal] HMD Reporting state change: {'State':'NotDetected','IsDetected':0,'IsReady':0,'Mode':'Unknown','IsWirelessReady':0,'IsRebooting':1,'IsFirmwareOutOfDate':0}
10/06 12:40:04.715 {INFO}    [LifeCycle] [Aggregated 23 times] ActiveHardwareChanged::get(session).subscribe() Start
10/06 12:40:19.716 {INFO}    [DML:HMDNormal] HMD Reporting state change: {'State':'NotDetected','IsDetected':0,'IsReady':0,'Mode':'Unknown','IsWirelessReady':0,'IsRebooting':1,'IsFirmwareOutOfDate':0}

 

 

 

 

 

Can I do something to fix this issue ? Thanks in advance for any help !

2 ACCEPTED SOLUTIONS

Accepted Solutions

baptiste.r1807
Explorer

Fixed... It was the Redistribuable Visual C++ for Visual Studio 2015 package that was corrupted (download it here https://www.microsoft.com/fr-FR/download/details.aspx?id=48145)

If you had the same problem and want to know where the errors came from go to Oculus\Support\oculus-diagnostics\CameraCalibrationTool and try to start the CameraTool.exe and if it crash with an error try to fix it like a missing .DLL files (mine was concrt140.dll)

View solution in original post

Glad that I've helped you !

 

Btw weird other problem that I've had is that the headset was just glitching suddenly and restart the Oculus software with a loud noise and gray noise in the headset, I've just changed the cable and it worked again (even if I tested the cable with another headset and another PC ! So think to try to change the cable).

View solution in original post

9 REPLIES 9

baptiste.r1807
Explorer

Fixed... It was the Redistribuable Visual C++ for Visual Studio 2015 package that was corrupted (download it here https://www.microsoft.com/fr-FR/download/details.aspx?id=48145)

If you had the same problem and want to know where the errors came from go to Oculus\Support\oculus-diagnostics\CameraCalibrationTool and try to start the CameraTool.exe and if it crash with an error try to fix it like a missing .DLL files (mine was concrt140.dll)

oH MY GOSH Thank you!! I've been trying to repair this for a month, including a lengthy engagement with Meta suppot and an unfortunate exchange where I sent them my oculus headset and got a refurbished one back (lost all of my fun stickers). I was just about to send them another email that it weirdly enough works on another computer but not the one I've been using it on, did another google search on a whim, found this thread (which I regrettably didn't find originally), and this worked!

 

Slight modification for anyone who already has this Redestributable installed... If you go to control panel -> programs and features, find the 2015 package, click "change" and then "repair", this fixed it for me. The display is back!!

Glad that I've helped you !

 

Btw weird other problem that I've had is that the headset was just glitching suddenly and restart the Oculus software with a loud noise and gray noise in the headset, I've just changed the cable and it worked again (even if I tested the cable with another headset and another PC ! So think to try to change the cable).

jorrit-de-vries
Explorer

Thanks, this pointed me in the right direction. From update v54 there was no display on the Rift-S anymore. Turns out this time it was vcruntime140_1.dll was missing, as shown by running OculusDash.exe this time.

The distributables, which a developer using MSVC should distribute along their app, can be downloaded from https://learn.microsoft.com/en-US/cpp/windows/latest-supported-vc-redist?view=msvc-170

Thank you! I got black screen and the "Oculus isn't working correctly" error message after Oculus forced me to update the drivers, and wasted hours to disconnect, connect cables, restart computer and oculus many times following Oculus support file. Now the files are Microsoft Visual C++ 2015-2022 Redistributable (x64) and Microsoft Visual C++ 2015-2022 Redistributable (x86). I downloaded and installed both files and got the display working again.

d.343488
Honored Guest

it didn't work for me

it didn't work

MetaQuestSupport
Community Manager
Community Manager

Hey there, @d.343488! We hate to hear that you're having trouble with your Oculus Rift S not working for you. We know how important it is to make sure everything is working so you can fully enjoy your VR experience, and we would be happy to help you with this issue!

We see that you mentioned the troubleshooting provided by baptiste.r1807 was not able to help resolve this issue. can get a better understanding of this issue:

  • Could you please let us know what other troubleshooting you've tried to help resolve this issue?
  • Could you also provide us with images of any error messages that you see?
  • Have you also checked to make sure that your PC is updated with the minimum requirements?

Please provide this information whenever you can!

If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!

Hi again, @d.343488! We were just reaching out to see if you still needed some help with the issue you are experiencing with your Oculus Rift S, is so please let us know!

If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!
Get Help
Did this answer your question? If it didn’t, use our search to find other topics or create your own and other members of the community will help out.

Check out some popular posts here:
Getting Help from the Meta Quest Community
Tips and Tricks: Charging your Meta Quest Headset
Tips and Tricks: Help with Pairing your Meta Quest
Trouble With Facebook/Instagram Accounts?