IskandarMa
IskandarMa
it looks like a simple kernel buffer overflow issue happened? the `VBoxUSB.sys` signatured by Oracle and verified with Windows Driver Verifier. so, whom should I expected to solve this problem?
Wow, this is really a impressive analyzing, I'm almost believing this is the real corruption point 😃. OK I will try the suggestion and watch that request count.
Yes you are right, with verbose logging server instance, it does not crash to BSOD anymore. due to logging time consumption? I'm attaching the last parts of the logs, in...
> I know it is quicker to work around it Any idea how to work around this? I can compile and test locally on my environment, this driver problem still...
> That changes the timing/performace, which seems to help Follow this theory, what if I continue adding time consumption on certain steps, could that reducing the crashing possibility ? currently...
Well, sounds a bad situation for me... Looks eventually I have no choice but digging into this project now and trying to figure out what's really going on back there....
These days I noticed the BSOD happens only be relevant to adb debugging, not the transfering stuff, and these two things always happen one by one(install and then debugger attaching...
Not much frequently working with usbipd these days, but still happened once, still keep trying.
currently works fine, barely happen again, close this issue.
BSOD happened many times today, I've updated Windows 11 to latest beta build, not sure if this is related. So, this problem still exists apparently. @dorssel 😔