FW 13 Crashing with MX Brio Camera

I’ve seen posts about Logitech keyboard or the receivers, but wondering if anyone has had issues with the MX Brio webcam? Every time I connect the webcam it will end up crashing my FW. Takes about 20-30 seconds after it’s connected to do so.

  • AMD Ryzen 7 7840U w/ Radeon 780M Graphics
  • Installed RAM 64.0 GB
  • Windows 11 Pro 24H2
  • Bios 3.05

Webcam: Buy MX Brio UHD 4K Webcam | Logitech

Any insight to what’s causing this would be awesome!

FWIW, I’m using the Logitech Brio PRO X 4K Webcam with my 13” AMD 7640U running Arch Linux with zero problems.

I’m also having this issue on Windows with my Brio and Framework 13 AMD.

The same camera works fine on the same laptop under Linux (Fedora) as well as my other devices (macOS and Windows devices).

Here’s the “problem report” from Windows:

Source
Windows Camera

Summary
Stopped responding and was closed

Date
‎2025-‎01-‎12 13:36

Status
Report sent

Description
A problem caused this program to stop interacting with Windows.
Faulting Application Path:	C:\Program Files\WindowsApps\Microsoft.WindowsCamera_2024.2408.1.0_x64__8wekyb3d8bbwe\WindowsCamera.exe

Problem signature
Problem Event Name:	MoAppHangXProc
Package Full Name:	Microsoft.WindowsCamera_2024.2408.1.0_x64__8wekyb3d8bbwe
Application Name:	praid:App
Application Version:	2024.2408.1.0
Application Timestamp:	66d7528f
Hang Signature:	7c4f
Hang Type:	2097280
Waiting on Package Full Name:	UNKNOWN
Waiting on Application Name:	svchost.exe:AudioClientRpc
Waiting on Application Version:	0.0.0.0
OS Version:	10.0.26100.2.0.0.256.48
Locale ID:	1033
Additional Hang Signature 1:	7c4fac7c4996917ee8755851c08843ad
Additional Hang Signature 2:	8215
Additional Hang Signature 3:	82158f820a8fec748d87f05b24c6ad17
Additional Hang Signature 4:	7c4f
Additional Hang Signature 5:	7c4fac7c4996917ee8755851c08843ad
Additional Hang Signature 6:	8215
Additional Hang Signature 7:	82158f820a8fec748d87f05b24c6ad17

Extra information about the problem
Bucket ID:	77ebb09ac899ce539a1177e352d9373a (1878414337821456186)

Hi @Aaron_Piotrowski,

Took a quick look at the Logitech website and see that there are multiple downloads and updates for this camera with releases every other month. Hopefully their bloatware is not causing the issue. :person_facepalming:

Though this likely explains why it works fine under Linux as it is using a basic driver for the camera.

I have not downloaded any additional software from the Logitech website; just using whatever drivers come with or are installed automatically by Windows. The webcam works well on my other Windows machines, just not the Framework.

Your other Windows machines use different mainboard components, and the driver stack will not be identical. I would look into getting the software from Logitech, as it is THEIR responsibility to ensure hardware compliance with their products.

It’s not a Logitech issue, did more digging and found this post FW 13 AMD not responsive when connecting monitor via USB-C - Community Support - Framework Community

At the end of the post there’s this: “EDIT2: I disabled the AMD Audio CoProcessor and it worked. I was able to plug my external webcam in and it was recognized and the laptop showed no other issues as described above. So far I am not seeing any negative consequences of disabling the CoProcessor, so for the time being I will keep this disabled.”

I don’t have AMD Audio CoProcessor but I did disable AMD HD Audio Device and AMD USB Audio Device and now I can use the webcam without crashing. I have no idea if this is part of the Framework drivers or if this is an AMD bug, I only have Intel and Qualcomm machines to test on (both of which are just plug and play).

2 Likes

Nice find, will try it out later today.

Is that something you disable in Device Manager?

(Sorry if it’s a dumb question, I’m typically a Linux and Mac user so unfamiliar with Windows troubleshooting)

Did some testing:

  • Disabled both AMD High Definition Audio Device and AMD USB Audio Device disabled and rebooted
  • Webcam worked
  • Enabled AMD USB Audio Device and rebooted
  • Problems came back
  • Enabled AMD High Definition Audio Device and disabled AMD USB Audio Device and rebooted
  • Webcam works

So, at least based on my quick testing, it seems AMD USB Audio Device is the one that’s incompatible with the webcam. Disabling just that device resolved the webcam issue. I’m not sure what the side effects of disabling this might be.

6 Likes

I haven’t come across any side effects that I’m aware of at least. Good to know that it’s just the one device that I need to disable :+1:

I can confirm this issue (and solution) for both a Logitech C720 and C910. Windows 11 24H2 on Framework 13 with AMD Ryzen; framework driver bundle from October 2024.

Detailed error description:
Starting Windows Camera app with only internal camera enabled works fine. I can afterwards connect one of the Logitech cameras and then switch between the two.
But if I first connect one of the Logitech cameras and then start Windows Camera, the app will freeze. Even worse, I’m not able to do a clean reboot, as Windows will get stuck while shutting down.

Disabling AMD USB Audio device also resolved the issue for me. I’m so glad I found your hints!
Just a last thought: both Logitech cameras I tested have a microphone included. This could be the point where things interfere.
Oh, and disabling AMD USB Audio Device does not disable the built-in microphone. Great! Thanks!

Hey Sargun_Vohra, I used your solution and it worked (so far). Thank you very much!

Aaron! Thank you for sharing this! I also disabled the AMD Audio CoProcessor, which prompted a required reboot.

Plugged in the camera, and it loaded right up, and I’m no longer encountering the freezing or bog I once had. Thank you again!

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.

Hello friends!

First time posting was as I am having trouble with my framework and not sure of what to do.

I have an external unbranded USB camera that, when connecting to the Framework, the video recording software (any of them, from windows camera app to OBS) crash out. Even removing the camera doesn’t resolve the problem. If I reset the laptop, it stays stuck in with a black screen for minutes, only shutting down when i manually do it in the button.

The camera works though, I tried on other laptops and desktops (with win10 and win11) and it works just fine. It just creates this problem in my framework. Any ideas people?

I already reset the laptop and installed the drivers from the site for the framework. Even did a second reset and didn’t install the drivers just to make sure it wasn’t a problem on that front…

Any help is appreciated. As mentioned, the camera is unbranded.

It sounds like you’re using Windows?

I’m a Linux guy, so all I can say is, are there system logs you can look at? That’s where I’d start with Linux. I occasionally connect an external USB-A Logitech webcam to my FW13 AMD and it works like a charm.

We’re in the middle of piloting FW laptops for our company and we came across this same problem. Just to let you know your camera being unbranded is not the issue, we had this with a Logitech c920.

I found another forum post on here https://community.frame.work/t/fw-13-crashing-with-mx-brio-camera/62878 That seems to have solved the issue.

It appears to be a driver conflict issue with the built in AMD USB Audio device. If you disable it in the Device Manager you should hopefully be in better shape.

It’s definitely a Windows driver issue as in that post someone with same exact hardware setup but running Linux has no issues.

It appears what happens is the webcam conflicts with the audio device and when you try to reboot it doesn’t properly close Windows down before trying to boot back up getting stuck.

We were thinking the issue was Windows wasn’t booting up properly but now I believe it’s not shutting down properly since Linux users aren’t affected. Which is a relief since it’s not a hardware fault.

Hope that helps!

3 Likes