Nathan Kidd

Reproducing here also, killing our product for any of our customers on AMD with this driver. **OS:** Server 2019 **GPU:** RX6600 **amfrtdrv32.dll file version**: 31.0.1.14043.7000 (tested Catalyst 23.2.1 and 23.4.1)

Also reproducing with: **OS**: Server 2019 **GPU**: V620 **amfrtdrv64.dll file version**: 31.0.14043.7000 ``` ExceptionAddress: 00007ffd163639d2 (amfrtdrv64+0x00000000000339d2) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 0000000000000000 Attempt to...

Also reproducing with Catalyst 22.12.1 and V620, Server 2019.

Using UsbDk 1.0.22 and libusb master (1.0.26+) and a SCR331 smart card reader I reproduce the same WDF_VIOLATION bluescreen on Win10 and Win11. As hinted in #97 I see between...

Confirm 1.0.21 avoids the bluescreen. Reproduced by roughly: 1. libusb attach with specific device ID (04E6:E001) 2. Triggers inside libusb_get_string_descriptor() call but I haven't yet stepped down to the exact...

If there's additional testing or info that's useful to add here please let me know. At the moment I'm on a different path to see if I can get away...