Moved drive to new computer: I think Windows sees my two Blog v4 tuners as one

[Punkrulz24]

Sorry for the lengthy subject. I'm having a lot of difficulty with the software and I'm not really getting anywhere. I recently built a new computer, and upgraded from a Ryzen 5900x to a 9800X3D. I've moved my drives over to the new computer still keeping the same Windows installation. Unfortunately since doing so, I have been unable to use SDRTrunk. The closest I was able to get was one channel locking, and the other repeatedly locking and unlocking. No audio would play.

Here are the following things I have tried:

• Using Zadig to reinstall the drivers for both Blog v4 tuners.
• Moved one of the tuners from my USB hub directly to my computer.
• Tried both the nightly version as well as 0.6.1 final for SDRTrunk.
• Attempted to delete both Blog v4 from Windows, and also attempted to try to remove every instance of every driver listing for these devices.
• Of course, rebooted several times.
• Certain times while troubleshooting this, I get the following error line and a bunch of errors: USB error 9: error writing byte buffer: Pipe error But not always.

Is there a place I can start trying to figure this out? If I could completely make my computer forget that this all ever existed and start fresh I'd be fine with without a reboot haha.

Thanks!

 

[Punkrulz24]

Resolved:

While I could see each dongle separately I knew that SDRTrunk was seeing the dongles as one device, so it would be confused on the second one. Using rtl_eeprom.exe, have only one device connected and run:

rtl_eeprom.exe -s 00001000

Disconnect that device and connect another one, then run

rtl_eeprom.exe -s 00002000

So on and so forth. Then go back into SDRTrunk and at least in my case I set the secondary one as the preferred channel.

 

[dickie757]

I see you resolved it, but a manual loading of motherboard drivers may have helped. USB chipset drivers especially.

I would still load drivers manually.

 

[Punkrulz24]

I see you resolved it, but a manual loading of motherboard drivers may have helped. USB chipset drivers especially.

I would still load drivers manually.

All drivers: Chipset, audio, wifi, bluetooth, USB, etc have been updated immediately after building the computer. Uncertain why Windows randomly decided to confuse the two devices. But it makes sense if they generically keep the same serial number and for whatever reason this time around Windows says nah they're the same device.