[R82XX] PLL not locked! rtlsdr_demod_write_reg failed with -9

[AtomicInternet2]

Hello, and thank you for this cool project to play around with! I'm getting an error from the rtl_tcp interface that seems like it would prevent rtlamr from working properly. Hopefully I've just misconfigured something (or used the wrong driver) and someone knowledgeable can point out my error.
 
I'm on Windows 11 which is likely my issue. I have installed the Zadig driver for my Nooelec NESDR Mini R820T SDR & DVB-T USB device:

Thank you for any insight you can provide!

The rtl_tcp output is:
Found 1 device(s):
0: Realtek, RTL2838UHIDIR, SN: 00000001

Using device 0: Generic RTL2832U OEM
Found Rafael Micro R820T tuner
[R82XX] PLL not locked!
Tuned to 100000000 Hz.
listening...
Use the device argument 'rtl_tcp=127.0.0.1:1234' in OsmoSDR (gr-osmosdr) source
to receive samples in GRC and control rtl_tcp parameters (frequency, gain, ...).
client accepted! PROTON 50049
set freq 912380000
rtlsdr_demod_write_reg failed with -9
r82xx_write: i2c wr failed=-9 reg=17 len=1
r82xx_set_freq: failed=-9
set sample rate 2359296
[R82XX] PLL not locked!
set gain mode 0

And the rtlamr output is:
C:\Users\atomi\Downloads\rtl-sdr-64bit-20240728>rtlamr -msgtype=all
09:01:58.653025 decode.go:45: CenterFreq: 912380000
09:01:58.653555 decode.go:46: SampleRate: 2359296
09:01:58.653555 decode.go:47: DataRate: 32768
09:01:58.653555 decode.go:48: ChipLength: 72
09:01:58.653555 decode.go:49: PreambleSymbols: 32
09:01:58.653555 decode.go:50: PreambleLength: 4608
09:01:58.653555 decode.go:51: PacketSymbols: 736
09:01:58.653555 decode.go:52: PacketLength: 105984
09:01:58.653555 decode.go:59: Protocols: scm,scm+,idm,r900
09:01:58.653555 decode.go:60: Preambles: 00000000000000001110010101100100,111110010101001100000,0001011010100011,01010101010101010001011010100011
09:01:58.653555 main.go:124: GainCount: 29

[AtomicInternet2]

I actually just found this helpful article for anyone else experiencing this issue.
https://updatedideas.com/fixing-the-error-rtl-sdr-demod-write-reg-failed-with-9/

I switched to a different USB port on my machine (USB 3.1 vs 3.0) and the error has disappeared.

So try a different USB port if you have this happen. I've also seen low power (insufficient power supply) as another cause.