Hey there,
I use an Arduino uno (smd) for a small project of mine. It's constantly connected to my pc. As long as the pc is running everthing works, but whenever I try to shut it down, I get an BSOD + reboot. This is extremly annoying , and I really need a way to fix this.
Any ideas?
The windows logs say something about an error in the standard usb port driver. I can look that up again if it's important. I also tried other usb ports and another cable... nothing works.
What version of Windows?
What service pack?
What does the error log say?
It there an application or serial monitor connected to the UNO when you shut down?
Windows 7 x64 all updates installed (guess its Service pack 1 then).
There is not application c onnected to the UNO that I know of. Is there a way to check?
I used Bluescreenview for the minidump and it says: BUGCODE_USB_DRIVER as Bug Check String and its USBPORT.sys Adress: USBPORT.sys+16f4b Bugcheckcode0x000000fe
If you need anything else just tell me.
PS I checked the MS Bugcode reference and if I interpret this right it means: "The caller has submitted an IRP that is already pending in the USB bus driver." Sadly I have no clue what that means.
The issue you are seeing looks similar to this issue:
It doesn't look like he ever got a solution, except that he narrowed it down to some sort of PCI device helping to create the issue.
Yes, thx. I read that too, just forgot to link it here. But well... as you said he did get no answer/solution. I'll try to disconnect some other usb devices and to find newer usb drivers. Perhaps its helps.
I am glad for other ideas/fixes though.
Ok I solved the problem. I updated my USB drivers (etron on an asrock z68 pro 3) to a newer (beta) version from their website and I also updated the inf file and the drivers for the arduino. Now everything seems to work just fine.
It's interesting to note that motherboard has USB 3.0 ports.
There have been other reports of odd behavior with USB 3.0 ports. Most of the other issues have been with enumeration.
Anyway, glad you were able to get it resolved.
Last Samurai, could you elaborate more on what exactly you changed in the .inf file? I'm having the same issue you described on a number of machines