BSD Wdf01000.sys related BlueScreen

[Ekkehard]

On a client machine several times a  Blue Screen occoured after approx. 20min runtime .

BCCode: 100000d1 BCP1: 17760BE5 BCP2: 00000002 BCP3: 00000001
BCP4: B44BB26C OSVer: 5_1_2600 SP:3.0 Product: 256_1

I am not sure that it is related to the used libusbK driver, but the BSD only occour if my app is running.
Any ideas where to look?

Best regards
Ekkehard

[Travis]

On 6/1/2012 1:47 AM, Ekkehard wrote:
> On a client machine several times a  Blue Screen occoured after approx. 20min
> runtime .
>
> BCCode: 100000d1 BCP1: 17760BE5 BCP2: 00000002 BCP3: 00000001
> BCP4: B44BB26C OSVer: 5_1_2600 SP:3.0 Product: 256_1
>

It looks like this one:
http://msdn.microsoft.com/en-us/library/windows/hardware/ff560244%28v=vs.85%29.aspx

> I am not sure that it is related to the used libusbK driver, but the BSD
> only occour if my app is running.

There are a few things that can cause this, besides buggy code.  For
instance, bad memory (or a bad hard drive which is storing pagefile.sys)

> Any ideas where to look?
>

Try locating the pagefile to a different drive.  You could run a memory
check, but you would have to replace it to know for sure.

Which libusbK functions (specifically) is your application calling?

Usually if the problem is in libusbK.sys, it will tell you so. ;)  I'm
surprised it is reporting a problem in wdf01000.sys.

Any additional information you can give about the PC will help.  I have
an XP machine here not doing anything and I could put it to work on a
test scenario for this.

I can check whether or not there are any IRQL issues in libusbK.sys
using the static driver verifier.

Regards,
Travis



------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Libusb-win32-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

[Travis]

On 6/1/2012 6:35 AM, Travis wrote:
> Any additional information you can give about the PC will help.  I
> have an XP machine here not doing anything and I could put it to work
> on a test scenario for this.

1) Have you set any power management options in the inf.

2) How is power management configured on the PC. IE: Is it set to go to
sleep after a certain amount of inactivity. If so, what is the sleep
time. 20min perhaps? ;)

3) What type of transfers are you using. ISO, BULK, etc.  If ISO, are
you using the "UsbK_IsoWritePipe" or "UsbK_WritePipe" function.

4) Are you using hot-plug detection.

5) How are you configuring your device. EG: is configuration done on
start-up, or are you changing alternate settings mid-stream.

I ran static driver verifier with the KmdfIrql rule:
http://msdn.microsoft.com/en-us/library/windows/hardware/jj126204%28v=vs.85%29.aspx
I didn't see any immediate problems.

I've found one problem with some floating point arithmetic, but this
should only be an issue if you are using "UsbK_WritePipe" with an ISO
endpoint.  I do not think this would cause a DRIVER_IRQL_NOT_LESS_OR_EQUAL.

I'm now running static driver verifier with all the rules;  It is a pig,
so it takes quite a while. ;)

Regards,
Travis





------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Libusb-win32-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

[Xiaofan Chen]

On Fri, Jun 1, 2012 at 9:35 PM, Travis <[hidden email]> wrote:

> On 6/1/2012 1:47 AM, Ekkehard wrote:
>> On a client machine several times a  Blue Screen occoured after approx. 20min
>> runtime .
>>
>> BCCode: 100000d1 BCP1: 17760BE5 BCP2: 00000002 BCP3: 00000001
>> BCP4: B44BB26C OSVer: 5_1_2600 SP:3.0 Product: 256_1
>>
>
> It looks like this one:
> http://msdn.microsoft.com/en-us/library/windows/hardware/ff560244%28v=vs.85%29.aspx
>

The brutal force way is to use windbg to analyze the crash-dump.
http://blogs.technet.com/b/petergal/archive/2006/03/23/422993.aspx



--
Xiaofan

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Libusb-win32-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

[Ekkehard]

The related machine is traveling home, since I am off the following week, I will start searching than. Thanks for the hints so far.
Greetings Ekkehard

[peter wang]

hi Ekkehard and Xiaofan:

        any update for this issue?  I encounter this issue also,  and blue  screen happen every time when you plug out device while ISO-ep is transferring data. but only happened on xp, Win7 is ok.

 

On Sat, Jun 2, 2012 at 3:15 PM, Ekkehard <[hidden email]> wrote:

The related machine is traveling home, since I am off the following week, I
will start searching than. Thanks for the hints so far.
Greetings Ekkehard

--
View this message in context: http://libusb.6.n5.nabble.com/BSD-Wdf01000-sys-related-BlueScreen-tp5709840p5709844.html

Sent from the LibUSB Dev - Win32 mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Libusb-win32-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Libusb-win32-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

[Xiaofan Chen]

On Tue, Jun 12, 2012 at 9:00 AM, peter wang <[hidden email]> wrote:
> hi Ekkehard and Xiaofan:
>         any update for this issue?  I encounter this issue also,  and blue
>  screen happen every time when you plug out device while ISO-ep is
> transferring data. but only happened on xp, Win7 is ok.

Could you try the brutal force method I mentioned before and use
windbg to analyze the crash-dump?
http://blogs.technet.com/b/petergal/archive/2006/03/23/422993.aspx


--
Xiaofan

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Libusb-win32-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

[Ekkehard]

Sorry for the delay, but I was out of office for some days.
The error was (pretty sure) a defective mainboard. The connector of the RAM-Module was buggy, so vibrations could destroy some bits.
Having replaced this, the setup runs now for days without having this BSD error.
Greetings Ekkehard

[Travis]

On 6/11/2012 6:00 PM, peter wang wrote:
> hi Ekkehard and Xiaofan:
>         any update for this issue?  I encounter this issue also,  and
> blue  screen happen every time when you plug out device while ISO-ep
> is transferring data. but only happened on xp, Win7 is ok.
>

Interesting.  This is probably something I can reproduce with an XP VM
machine.  Are you sure you are getting the same BSOD codes as Ekkehard?

Are you reading or writing?  If writing, are you using the
UsbK_IsoWritePipe function or UsbK_WritePipe?

Regards,
Travis


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Libusb-win32-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

[peter wang]

Hi, 

    I used "UsbK_IsoReadPipe" to read data from ISO EP continually.

and below the dump file analyze result from windbg.exe:

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, 2, 1, a50b2c3a}

Probably caused by : wdf01000.sys ( wdf01000!FxIoTarget::RemoveCompletedRequestLocked+56 )

Followup: MachineOwner

---------

0: kd> !analyze -v

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

An attempt was made to access a pageable (or completely invalid) address at an

interrupt request level (IRQL) that is too high.  This is usually

caused by drivers using improper addresses.

If kernel debugger is available get stack backtrace.

Arguments:

Arg1: 00000000, memory referenced

Arg2: 00000002, IRQL

Arg3: 00000001, value 0 = read operation, 1 = write operation

Arg4: a50b2c3a, address which referenced memory

Debugging Details:

------------------

WRITE_ADDRESS:  00000000 

CURRENT_IRQL:  2

FAULTING_IP: 

wdf01000!FxIoTarget::RemoveCompletedRequestLocked+56

a50b2c3a 890a            mov     dword ptr [edx],ecx

CUSTOMER_CRASH_COUNT:  3

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0xD1

TRAP_FRAME:  8055118c -- (.trap 0xffffffff8055118c)

ErrCode = 00000002

eax=88086048 ebx=a5101a8c ecx=00000001 edx=00000000 esi=88086010 edi=8803b010

eip=a50b2c3a esp=80551200 ebp=8055120c iopl=0         nv up ei pl zr na pe nc

cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246

wdf01000!FxIoTarget::RemoveCompletedRequestLocked+0x56:

a50b2c3a 890a            mov     dword ptr [edx],ecx  ds:0023:00000000=????????

Resetting default scope

LAST_CONTROL_TRANSFER:  from a50b2c3a to 805446e0

STACK_TEXT:  

8055118c a50b2c3a badb0d00 00000000 00007125 nt!KiTrap0E+0x238

8055120c a50b3ba5 88086010 87ccc12f 8803b010 wdf01000!FxIoTarget::RemoveCompletedRequestLocked+0x56

8055122c a50b3cde 01086010 89f68520 80551258 wdf01000!FxIoTarget::RequestCompletionRoutine+0x9c

8055123c 804f080d 87fd6f00 87ccc008 88086010 wdf01000!FxIoTarget::_RequestCompletionRoutine+0x35

80551258 804f16b0 87fd6f00 87ccc008 89f68520 nt!IopUnloadSafeCompletion+0x1d

80551288 b8c7c280 8a1dc0ec 805512bc b8c7f2e3 nt!IopfCompleteRequest+0xa2

80551294 b8c7f2e3 8a293030 87ccc008 c000009d USBPORT!USBPORT_CompleteIrp+0x2a

805512bc b8c7f840 8a1dc028 41427063 b8c7f6dc USBPORT!USBPORT_BadRequestFlush+0xa9

805512e0 805021ff 8a1dc70c 8a1dc028 9e0d0c52 USBPORT!USBPORT_DM_TimerDpc+0x164

805513fc 8050231b 8055c0c0 ffdff9c0 ffdff000 nt!KiTimerListExpire+0x14b

80551428 80545e6f 8055c4c0 00000000 00009a97 nt!KiTimerExpiration+0xb1

80551450 80545d54 00000000 0000000e 00000000 nt!KiRetireDpcList+0x61

80551454 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28

STACK_COMMAND:  kb

FOLLOWUP_IP: 

wdf01000!FxIoTarget::RemoveCompletedRequestLocked+56

a50b2c3a 890a            mov     dword ptr [edx],ecx

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  wdf01000!FxIoTarget::RemoveCompletedRequestLocked+56

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: wdf01000

IMAGE_NAME:  wdf01000.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bbf28

FAILURE_BUCKET_ID:  0xD1_wdf01000!FxIoTarget::RemoveCompletedRequestLocked+56

BUCKET_ID:  0xD1_wdf01000!FxIoTarget::RemoveCompletedRequestLocked+56

Followup: MachineOwner

---------

On Tue, Jun 12, 2012 at 10:04 PM, Travis <[hidden email]> wrote:

On 6/11/2012 6:00 PM, peter wang wrote:
> hi Ekkehard and Xiaofan:
>         any update for this issue?  I encounter this issue also,  and
> blue  screen happen every time when you plug out device while ISO-ep
> is transferring data. but only happened on xp, Win7 is ok.
>

Interesting.  This is probably something I can reproduce with an XP VM
machine.  Are you sure you are getting the same BSOD codes as Ekkehard?

Are you reading or writing?  If writing, are you using the
UsbK_IsoWritePipe function or UsbK_WritePipe?

Regards,
Travis

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Libusb-win32-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Libusb-win32-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

[Travis]

On 6/13/2012 8:16 PM, peter wang wrote:
> Hi,
>     I used "UsbK_IsoReadPipe" to read data from ISO EP continually.
>
> and below the dump file analyze result from windbg.exe:

Thanks for the info.
I will dig into this a bit further..

However, this looks suspicious:

> Arguments:
> Arg1: 00000000, memory referenced
> Arg2: 00000002, IRQL
> Arg3: 00000001, value 0 = read operation, 1 = write operation
> Arg4: a50b2c3a, address which referenced memory
>
> Debugging Details:
> ------------------
>
>
> WRITE_ADDRESS:  00000000
>

>  DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
>  An attempt was made to access a pageable (or completely invalid)
address at an
>  interrupt request level (IRQL) that is too high.  This is usually
>  caused by drivers using improper addresses.

So, it would appear that it is accessing an invalid memory address
all-together.

Regards,
Travis


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Libusb-win32-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

[Xiaofan Chen]

On Thu, Jun 14, 2012 at 11:16 AM, peter wang <[hidden email]> wrote:
> Hi,
>     I used "UsbK_IsoReadPipe" to read data from ISO EP continually.
>
> and below the dump file analyze result from windbg.exe:

Thanks for the report. Maybe Travis can see something from the
dump analysis.

I have also forwarded the email to the OSR ntdev mailing list
to check if the experts there have some input or not.


--
Xiaofan

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Libusb-win32-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

[Travis]

On 6/13/2012 8:16 PM, peter wang wrote:
> Hi,
>     I used "UsbK_IsoReadPipe" to read data from ISO EP continually.
>

Thus far, I have not been able to reproduce this issue.  I have tried on
both a *real* XP machine and an VM machine.

I'm using a modified version of the xfer-iso-read example with CY-Stream
device firmware. (altf=3).  I start the application and yank the plug. ;)

Have you tried with a different USB host controller?

Have you tried uninstalling the driver and re-installing with the newest
libusbK-inf-wizard?

Regards,
Travis


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Libusb-win32-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

[Xiaofan Chen]

On Thu, Jun 14, 2012 at 3:51 PM, Xiaofan Chen <[hidden email]> wrote:
> I have also forwarded the email to the OSR ntdev mailing list
> to check if the experts there have some input or not.

The following is the answer from Tim Roberts, a recognized expert
(and MVP) in Windows driver development community.

On Fri, Jun 15, 2012 at 3:06 AM, Tim Roberts <[hidden email]> wrote:

> Xiaofan Chen wrote:
>> Just wondering if there are some suggestions to help
>> debug the following problem. Thanks.
>
> This is showing a null pointer dereference in a timer callback.
> Usually, that means the driver deleted some resource prematurely, while
> someone else was still relying on it.
>
> --
> Tim Roberts, [hidden email]
> Providenza & Boekelheide, Inc.
>

--
Xiaofan

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Libusb-win32-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

[Ekkehard]

I have used the UsbK_IsoReadPipe function on two different USB bridges (Cypress, empia) and several different XP and Win7 (and one single Vista) installations. All are running well, except very few. The few are hardware related issues, so that I am pretty sure that the libusbK stuff is not causing this error - at least under the conditions, reported by me.
Regards
Ekkehard

[Travis]

On 6/14/2012 10:10 PM, Xiaofan Chen wrote:

> On Thu, Jun 14, 2012 at 3:51 PM, Xiaofan Chen<[hidden email]>  wrote:
>> I have also forwarded the email to the OSR ntdev mailing list
>> to check if the experts there have some input or not.
> The following is the answer from Tim Roberts, a recognized expert
> (and MVP) in Windows driver development community.
>
> On Fri, Jun 15, 2012 at 3:06 AM, Tim Roberts<[hidden email]>  wrote:
>> Xiaofan Chen wrote:
>>> Just wondering if there are some suggestions to help
>>> debug the following problem. Thanks.
>> This is showing a null pointer dereference in a timer callback.
>> Usually, that means the driver deleted some resource prematurely, while
>> someone else was still relying on it.
>>

libusbK doesn't use any timers. IE:
http://msdn.microsoft.com/en-us/library/windows/hardware/ff550050%28v=vs.85%29.aspx

libusbK creates WDF objects (resources) that are rooted to a parent
object, usually WDFDEVICE.  It doesn't delete these objects
automatically for just this reason.  When the parent is deleted, it  
free's the object's siblings.  Most objects are freed by WDF when the
device is disconnected because they all end up rooting to WDFDEVICE.


Hopefully Peter is still with us because despite my efforts I cannot
reproduce this problem.
I'm am interested to hear if he can reproduce this on a different host
controller and/or computer.

Regards,
Travis


Regards,
Travis


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Libusb-win32-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

[Maurer-2]

Hello Travis,

perhaps a WaitForSingleObject or similar?

Best regards,

Martin

----- Original Message -----
From: "Travis" <[hidden email]>
To: <[hidden email]>
Sent: Friday, June 15, 2012 10:48 PM
Subject: Re: [Libusb-win32-devel] BSD Wdf01000.sys related BlueScreen

> On 6/14/2012 10:10 PM, Xiaofan Chen wrote:
>> On Thu, Jun 14, 2012 at 3:51 PM, Xiaofan Chen<[hidden email]>  wrote:
>>> I have also forwarded the email to the OSR ntdev mailing list
>>> to check if the experts there have some input or not.
>> The following is the answer from Tim Roberts, a recognized expert
>> (and MVP) in Windows driver development community.
>>
>> On Fri, Jun 15, 2012 at 3:06 AM, Tim Roberts<[hidden email]>  wrote:
>>> Xiaofan Chen wrote:
>>>> Just wondering if there are some suggestions to help
>>>> debug the following problem. Thanks.
>>> This is showing a null pointer dereference in a timer callback.
>>> Usually, that means the driver deleted some resource prematurely, while
>>> someone else was still relying on it.
>>>
>
> libusbK doesn't use any timers. IE:
> http://msdn.microsoft.com/en-us/library/windows/hardware/ff550050%28v=vs.85%29.aspx
>
> libusbK creates WDF objects (resources) that are rooted to a parent
> object, usually WDFDEVICE.  It doesn't delete these objects
> automatically for just this reason.  When the parent is deleted, it
> free's the object's siblings.  Most objects are freed by WDF when the
> device is disconnected because they all end up rooting to WDFDEVICE.
>
>
> Hopefully Peter is still with us because despite my efforts I cannot
> reproduce this problem.
> I'm am interested to hear if he can reproduce this on a different host
> controller and/or computer.
>
> Regards,
> Travis
>
>
> Regards,
> Travis
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Libusb-win32-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel 

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Libusb-win32-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

[JamesO]

I have also observed the same issue on both Windows XP and Windows 7 machines.  I am using the libusb0.sys api.  Specifically, my application is using usb_submit_async to queue read requests to the driver.  If the application is not running, the crash is not observed.  The BSOD occurs when entering standby and hibernate, reporting DRIVER_IRQL_NOT_LESS_OR_EQUAL.

My driver version is 3.0.5.10

[Travis]

On 6/28/2012 7:54 AM, JamesO wrote:
> I have also observed the same issue on both Windows XP and Windows 7
> machines.  I am using the libusb0.sys api.  Specifically, my application is
> using /usb_submit_async/ to queue read requests to the driver.  If the
> application is not running, the crash is not observed.  The BSOD occurs when
> entering standby and hibernate, reporting DRIVER_IRQL_NOT_LESS_OR_EQUAL.

I haven't been able to reproduce the BSOD reported by Peter Wang, but
this report is a bit different.
Ekkehard deduced his problem was most likely a faulty memory bank.

> My driver version is 3.0.5.10
>

1) Upgrade to RC13 (v3.0.5.13) and make sure the issue still exists.
2) Make sure the libusb-win32 (libusb0.sys) filter driver is *not*
installed.

If the problem still occurs, give me as much information as possible
about your software, device, and how it works.

Regards,
Travis



------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Libusb-win32-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

[JamesO]

Hi Travis, thanks for the prompt reply.  I love the driver, thanks for
all the work.

> 1) Upgrade to RC13 (v3.0.5.13) and make sure the issue still exists.

I have upgraded to RC13, this still has the issue.

> 2) Make sure the libusb-win32 (libusb0.sys) filter driver is *not*
> installed.

I have removed libusb0.sys from the driver directory.  The issue persists.


> If the problem still occurs, give me as much information as possible
> about your software, device, and how it works.
>

I have now managed to induce the same failure mode with a few minor
modifications to the xfer-stream example provided in the developer
kit.  I have changed the VID / PID to identify my device, disabled
EXAMPLE_USE_BENCHMARK_CONFIGURE (not relevant to my hardware) and set
the endpoint to 0x86.  As I understand it, this should then queue read
requests to the USB host.

When I run the test and enter standby, I get the same BSOD message.

My hardware will not be providing data to read requests during the test period.

I have a dual PC setup with one PC in kernel debug mode at the moment.
 I will provide further information as it comes available. If there
are any tests I can perform on this setup please let me know (I am new
to Windows Kernel Mode debugging).   I have seen this issue on >3
different PCs so far (all I have tested).  They are all Dell
hardware..

Kind Regards,

James.