Thanks for checking up on this. We’re still seeking a solution with Prolific.
Based on what we know so far, this does appear to be a driver problem that will require an updated driver package from Prolific.
For background, this is the low-level error/problem (copied out of !analyze -v of the dump)
A driver has requested that an IRP be completed (IoCompleteRequest()), but
the packet has already been completed. This is a tough bug to find because
the easiest case, a driver actually attempted to complete its own packet
twice, is generally not what happened. Rather, two separate drivers each
believe that they own the packet, and each attempts to complete it. The
first actually works, and the second fails. Tracking down which drivers
in the system actually did this is difficult, generally because the trails
of the first driver have been covered by the second. However, the driver
stack for the current request can be found by examining the DeviceObject
fields in each of the stack locations.
From the stack, it looks like the problem is both the Windows Driver Foundation core components (wdf01000.sys from Microsoft) and the Prolific ser2pl64.sys driver are completing the same IRP, which then triggers this crash.
It’s looks like a race condition that happens intermittently on some machines.
Unfortunately, driver updates can take weeks or months typically. If you’re able to hang with us to work through this, thank you. If not, we totally understand and would be happy to give you a full refund. Just let us know at firstname.lastname@example.org if you want to go that route.
There’s still a chance that an existing driver update in the pipeline has already resolved this issue, but there’s been no sign of that yet – so I don’t want to set expectations too high.
Again, my apologies. Just let us know what you’d like. And we’ll keep updating here.