SOLVED: avrdude problem on windows 8

USB AVR Programmer and SPI interface. Adafruit's USBtinyISP.

Moderators: adafruit_support_bill, adafruit

Please be positive and constructive with your questions and comments.
Locked
User avatar
osbock
 
Posts: 151
Joined: Tue Jan 23, 2007 1:12 pm

SOLVED: avrdude problem on windows 8

Post by osbock »

At first I thought it was a USBtinyISP problem, but I get the BSOD even with it unplugged.
running:
avrdude -c usbtiny -p m328p
results in a reboot with the error: WDF_Violation
It was working fine a few days ago, so I suspect some update has borked things up. Anyone else experiencing this on windows 8 (Lenovo Y510P).
I also recently updated the nvidia driver too.
EDIT UPDATE: I don't know what went wrong, but I solved it by reinstalling the driver from files on MightyOhm's site. In spite of the claims that it was signed, I had to disable device signing to get it to install, but anyway, it's working now.
Last edited by osbock on Wed Oct 30, 2013 1:02 am, edited 1 time in total.

User avatar
osbock
 
Posts: 151
Joined: Tue Jan 23, 2007 1:12 pm

Re: avrdude problem on windows 8

Post by osbock »

Looks like the problem is in accessing libusb. (it doesn't crash if just running without -c usbtiny)
I realize this probably isn't the proper forum (could someone suggest one?) I suspect I won't be the only one with this problem, so I figure it's prudent to bring it up here too.
Here's the windbg analysis:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

WDF_VIOLATION (10d)
The Kernel-Mode Driver Framework was notified that Windows detected an error
in a framework-based driver. In general, the dump file will yield additional
information about the driver that caused this bug check.
Arguments:
Arg1: 000000000000000d, A power irp was received for the device but the irp was not
requested by the device (the power policy owner). Possibly there
are multiple power policy owners. Only one driver in the stack can
be the power policy owner. A KMDF driver can change power policy
ownership by calling the DDI WdfDeviceInitSetPowerPolicyOwnership.
Arg2: fffffa800c668ad0, Device object pointer.
Arg3: fffffa8009005010, Power Irp.
Arg4: fffffa800c66be40, Reserved.

Debugging Details:
------------------

*** WARNING: Unable to verify timestamp for libusb0.sys
*** ERROR: Module load completed but symbols could not be loaded for libusb0.sys

BUGCHECK_STR: 0x10D_d

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER: from fffff8800113ed6f to fffff8035fe66440

STACK_TEXT:
fffff880`009879c8 fffff880`0113ed6f : 00000000`0000010d 00000000`0000000d fffffa80`0c668ad0 fffffa80`09005010 : nt!KeBugCheckEx
fffff880`009879d0 fffff880`011206f2 : 00000000`00000002 0000057f`f3987ff8 fffffa80`0c668ad0 ffff28ef`f020a802 : Wdf01000!FxPkgFdo::DispatchDeviceSetPower+0xb3
fffff880`00987a20 fffff880`0111f79a : fffffa80`09005010 fffffa80`09005010 fffffa80`09005010 00000000`00000000 : Wdf01000!FxPkgPnp::Dispatch+0x2aa
fffff880`00987a80 fffff880`0111f866 : fffffa80`09005010 fffffa80`090054d0 fffffa80`0c668ad0 fffffa80`090054d0 : Wdf01000!FxDevice::Dispatch+0x19a
fffff880`00987ac0 fffff880`07f99946 : fffffa80`09005488 fffffa80`090054d0 fffffa80`0c69a1a0 fffffa80`0c6a4424 : Wdf01000!FxDevice::DispatchWithLock+0xa6
fffff880`00987b00 fffffa80`09005488 : fffffa80`090054d0 fffffa80`0c69a1a0 fffffa80`0c6a4424 fffffa80`09005010 : libusb0+0x3946
fffff880`00987b08 fffffa80`090054d0 : fffffa80`0c69a1a0 fffffa80`0c6a4424 fffffa80`09005010 fffff880`07f97479 : 0xfffffa80`09005488
fffff880`00987b10 fffffa80`0c69a1a0 : fffffa80`0c6a4424 fffffa80`09005010 fffff880`07f97479 00000000`00000001 : 0xfffffa80`090054d0
fffff880`00987b18 fffffa80`0c6a4424 : fffffa80`09005010 fffff880`07f97479 00000000`00000001 fffff880`00987be0 : 0xfffffa80`0c69a1a0
fffff880`00987b20 fffffa80`09005010 : fffff880`07f97479 00000000`00000001 fffff880`00987be0 fffffa80`0c69a1a0 : 0xfffffa80`0c6a4424
fffff880`00987b28 fffff880`07f97479 : 00000000`00000001 fffff880`00987be0 fffffa80`0c69a1a0 fffffa80`090050b8 : 0xfffffa80`09005010
fffff880`00987b30 00000000`00000001 : fffff880`00987be0 fffffa80`0c69a1a0 fffffa80`090050b8 fffffa80`09005000 : libusb0+0x1479
fffff880`00987b38 fffff880`00987be0 : fffffa80`0c69a1a0 fffffa80`090050b8 fffffa80`09005000 fffff803`5ff416d4 : 0x1
fffff880`00987b40 fffffa80`0c69a1a0 : fffffa80`090050b8 fffffa80`09005000 fffff803`5ff416d4 fffff880`00987be0 : 0xfffff880`00987be0
fffff880`00987b48 fffffa80`090050b8 : fffffa80`09005000 fffff803`5ff416d4 fffff880`00987be0 fffffa80`0c69a050 : 0xfffffa80`0c69a1a0
fffff880`00987b50 fffffa80`09005000 : fffff803`5ff416d4 fffff880`00987be0 fffffa80`0c69a050 00000000`00000000 : 0xfffffa80`090050b8
fffff880`00987b58 fffff803`5ff416d4 : fffff880`00987be0 fffffa80`0c69a050 00000000`00000000 00000000`00000000 : 0xfffffa80`09005000
fffff880`00987b60 fffff803`5fe38fd9 : 00000000`00000000 fffffa80`075da040 00000000`00000000 fffff880`03100f40 : nt!PopIrpWorker+0x284
fffff880`00987c10 fffff803`5feed7e6 : fffff880`030f5180 fffffa80`075da040 fffff880`03100f40 fffffa80`075df040 : nt!PspSystemThreadStartup+0x59
fffff880`00987c60 00000000`00000000 : fffff880`00988000 fffff880`00982000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
libusb0+3946
fffff880`07f99946 ?? ???

SYMBOL_STACK_INDEX: 5

SYMBOL_NAME: libusb0+3946

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: libusb0

IMAGE_NAME: libusb0.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4c50e4f0

FAILURE_BUCKET_ID: 0x10D_d_libusb0+3946

BUCKET_ID: 0x10D_d_libusb0+3946

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x10d_d_libusb0+3946

FAILURE_ID_HASH: {02a5a358-8676-8924-1a08-56f5fa44d226}

Followup: MachineOwner
---------

User avatar
adafruit_support_bill
 
Posts: 88096
Joined: Sat Feb 07, 2009 10:11 am

Re: SOLVED: avrdude problem on windows 8

Post by adafruit_support_bill »

Looks like a missing handler in libusb0.sys. Possibly for some new power management feature in Win8. A good resource for windows kernel-mode driver information is Open System Resources: http://www.osronline.com/

Locked
Please be positive and constructive with your questions and comments.

Return to “USBtinyISP”