[SOLVED] USB A device crashing Windows 11

Not that you want to be a test subject any longer; I am curious if the same issues happen with the Intel Core Ultra 1 Framework Laptop 13. If you were willing to return your AMD model at least the memory and SSD works between the two mainboards if you bought the DIY setup. I suspect the issue may not persist with the Intel chipset. There have been a number of oddities that only get brought up on AMD systems.

The latest consumer updates or whatever it is being called in Windows Update (The optional one that is not installed by default and you have to click on it for the “latest experience”) is not a final release; installing those gives users the false sense that it is fully tested and it is NOT. It is being used to expand their testbed before they push it as a full release.

Not saying that is the cause here, though with all the complexities of modern operating systems; sometimes less complication is more beneficial. I do not want extra features if it means having buggy symptoms of the core functionality of a device.

I suspect the issue may not persist with the Intel chipset.

I strongly suspect the same, however I’ve had the laptop since March so I won’t be switching :smiley:

The latest consumer updates or whatever it is being called in Windows Update

They’re called “Preview” - Stupidly that’s the only difference in the name so they’re easy to mistake for an update you actually want and are displayed even when you’re on the General Availability update channel. That said, I’m on the latest GA (non-preview) update.

1 Like

Same issue with the USB 2.0 hub. Time for a ticket!

FIXED! Thanks to @Vincent_Llora, I followed the post here to disable “AMD Audio Coprocessor” in device manager.

Hilarious that I found this on the day the USB hub arrived but I’m pleased I’ve got it sorted, regardless.

3 Likes

Hi.
Does that imply that there is a crash bug in the “AMD Audio Co-processor” driver in Windows 11 ?

I’m not entirely sure. It’s either that, or some kind of conflict with certain audio hardware. I’m not well versed enough in this to give an educated opinion, apologies!

If I hadn’t shipped my laptop off for return yesterday, I would’ve tried that as well (after seeing you mention it). Thanks for sharing your troubleshooting steps and results, hopefully it’ll help others as well. And hopefully the root cause can be resolved!

1 Like

I’ve reached out and not gotten a confirmation that there is a bug, but I think it is more of a conflict of two drivers trying to do the same job.

2 Likes

@AltCoyne Glad you got the issue fixed. I know it surely was frustrating for me.

Just a thought that might help others in the community: edit the title of your original post with [FIXED] we might need your help back at the beginning so that others with a similar issue can get it solved quickly by going to that discussion.

2 Likes

I had this issue too on win 11 fw16, thanks for sharing the fix! This issue came up for me when I tried to use a radio-based FPV Receiver, which acted as a USB 2.0 camera. I was half convinced that it had some kind of malware in it, as it basically broke most of my computer immediately after plugging it in. I couldn’t launch Chrome, OBS, or VLC, though it was successfully recognized in device manager. These issues would persist after I unplugged the camera, and would be fixed by a restart (which took a little longer than usual), but they would all return after trying to plug in the camera again. Another weird symptom is that my start menu would only ever open after every second click. The camera worked just fine on my sister’s mac, which led me to googling and finding this post.

2 Likes

I thought it read, “I was so pleased that I snorted…”. I laughed out loud and had to re-read it to catch my mistake.