F5F Stay Refreshed Hardware Desktop Issue with USB-C output on ASROCK B850M PRO RS

Issue with USB-C output on ASROCK B850M PRO RS

Issue with USB-C output on ASROCK B850M PRO RS

A
App_mann
Junior Member
21
05-07-2025, 08:09 AM
#1
Could you suggest some possibilities? I updated the BIOS, drivers, and chipset, but the USB-C port isn’t working.
A
App_mann
05-07-2025, 08:09 AM #1

Could you suggest some possibilities? I updated the BIOS, drivers, and chipset, but the USB-C port isn’t working.

L
Louka_San
Junior Member
13
05-08-2025, 03:30 PM
#2
Which gadget are you evaluating? Does the USB-C connection (when relevant) originate from a trusted manufacturer and is verified to meet specifications? How does USBTreeView display this information?
L
Louka_San
05-08-2025, 03:30 PM #2

Which gadget are you evaluating? Does the USB-C connection (when relevant) originate from a trusted manufacturer and is verified to meet specifications? How does USBTreeView display this information?

R
radiowaveUK
Junior Member
13
05-08-2025, 08:19 PM
#3
Thanks for your prompt response. I attempted to link my Meta Quest 3 VR headset with my mobile phone (Pixel 9). Both devices charge properly, but no data transmission occurs. The cable functioned well on another PC without issues. The USBTreeView displayed unusual behavior—it indicated the port wasn’t being used, then abruptly switched to something else and returned to non-use. It labeled itself as "Reality Labs XRSP Interface" and displayed this for a brief moment.

USB Port4 status: Connection Status 0x09 (Device is enumerating). Port Chain 4-4. Properties 0x0B shows user connectable as yes, debug capability enabled, no multi-companions, and port connector type C detected. Connection Index 0x04 corresponds to Port 4. CompanionIndex 0, linking to a companion hub with a unique identifier.

Device name: USB#ROOT_HUB30#5&a77f9b7&0&0#f18a0e88-c30c-11d0-8815-00a0c906bed8.

Device path details include multiple GUIDs and paths, indicating complex device configuration. The driver key is registered under a specific Windows version, and the kernel name points to a system update.

Connection problems: CM_PROB_PHANTOM (45) detected. Endpoints used: 0. No power state support beyond D0, which allows wake from D0. Overall, the setup appears functional but requires troubleshooting for data flow.
R
radiowaveUK
05-08-2025, 08:19 PM #3

Thanks for your prompt response. I attempted to link my Meta Quest 3 VR headset with my mobile phone (Pixel 9). Both devices charge properly, but no data transmission occurs. The cable functioned well on another PC without issues. The USBTreeView displayed unusual behavior—it indicated the port wasn’t being used, then abruptly switched to something else and returned to non-use. It labeled itself as "Reality Labs XRSP Interface" and displayed this for a brief moment.

USB Port4 status: Connection Status 0x09 (Device is enumerating). Port Chain 4-4. Properties 0x0B shows user connectable as yes, debug capability enabled, no multi-companions, and port connector type C detected. Connection Index 0x04 corresponds to Port 4. CompanionIndex 0, linking to a companion hub with a unique identifier.

Device name: USB#ROOT_HUB30#5&a77f9b7&0&0#f18a0e88-c30c-11d0-8815-00a0c906bed8.

Device path details include multiple GUIDs and paths, indicating complex device configuration. The driver key is registered under a specific Windows version, and the kernel name points to a system update.

Connection problems: CM_PROB_PHANTOM (45) detected. Endpoints used: 0. No power state support beyond D0, which allows wake from D0. Overall, the setup appears functional but requires troubleshooting for data flow.

M
Moi69
Junior Member
12
05-13-2025, 11:24 PM
#4
The bios contains some options about the USB ports. Likely there are adjustments that might turn off the USB-C connection. It seems the default setting is probably correct. Updated on February 5, 2025 by leclod
M
Moi69
05-13-2025, 11:24 PM #4

The bios contains some options about the USB ports. Likely there are adjustments that might turn off the USB-C connection. It seems the default setting is probably correct. Updated on February 5, 2025 by leclod