Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

USB error 9: error writing byte buffer: Pipe error #1963

Open
croach13 opened this issue Sep 1, 2024 · 1 comment
Open

USB error 9: error writing byte buffer: Pipe error #1963

croach13 opened this issue Sep 1, 2024 · 1 comment
Labels

Comments

@croach13
Copy link

croach13 commented Sep 1, 2024

sdrtrunk Version
master-branch; Nightly

Describe the bug
Each time the software attempts to communicate with either of my RTL-SDRs (one V3, one V4), I receive a "USB error 9: error writing byte buffer: Pipe error". Text files with the console log are attached. This happened with these same SDRs on my old PC (Ryzen 5 3600) as well as my new PC (Ryzen 7 7700X). When these SDRs are connected to an Intel machine with drivers loaded properly, SDRTrunk works great. The waterfall view at the default frequency at startup of the software appears to work correctly, screenshot attached.

To Reproduce
Steps to reproduce the behavior:

  1. Open playlist editor OR the "Tuners" tab.
  2. Make any attempt to change a setting or otherwise communicate with the tuner.

Expected behavior
The SDRs to tune to the correct frequencies and monitor trunked traffic using frequencies pulled from Radio Reference.

Screenshots
Screenshot 2024-08-31 215428

Application Log
See attached.
v0.6.0 log.txt
Nightly log.txt

Desktop (optional - complete the following information):

  • OS: Windows 11 23H2 (OS Build 22631.4037)
  • CPU: Ryzen 7 7700X (8 core/16 thread, 4.5GHz base)
  • Motherboard: MSI PRO B650-P WiFi (BIOS: 1.G1, 8/28/2024)
  • RAM: 32GB 4800MT/s (2x16GB)
  • All drivers on latest versions, just fully updated an hour ago

Additional context
This issue has plagued me across two completely different systems now. Is the problem with me mixing V3 and V4 devices?? Drivers were installed properly using Zadig. Each device works properly in SDRsharp and SDR Console v3.3. The V4 has had it's serial changed from 00000101 to 00000102 using SDR Console after finding an obscure thread that mentioned two RTL-SDRs can cause issues if they are set to the same serial numbers, but this didn't change anything.

@croach13 croach13 added the bug label Sep 1, 2024
@Jeffre19
Copy link

This issue plagued me for the longest time. I tried reinstalling drivers, disabling ports, switching ports, using externally powered hubs, all to no avail.

What solved my problem was the installation of a new internal usb card. There seems to be a problem with some combination of Ryzen CPUs and the on-board motherboard usb ports. Using the pci based usb expansion card solved my problem instantly. For reference I’m running a Ryzen 7 3800X with a ASUS B550 plus. Hoping this solution might work for you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants