Bug 1140582

Created attachment 936472 [details]
sysdata.xml

Created attachment 936476 [details]
memory.dmp part

Created attachment 936477 [details]
memory.dmp part

Created attachment 936478 [details]
memory.dmp part

To get the memory dmp, run: cat MEMORY.dmp.xz.* | unxz > MEMORY.DMP



Details from "Windows has recovered from an unexpected shutdown" dialog:
Problem signature:
  Problem Event Name:	BlueScreen
  OS Version:	6.1.7601.2.1.0.256.27
  Locale ID:	1033

Additional information about the problem:
  BCCode:	10d
  BCP1:	00000006
  BCP2:	00000004
  BCP3:	87F579C4
  BCP4:	9403A450
  OS Version:	6_1_7601
  Service Pack:	1_0
  Product:	256_1

Files that help describe the problem:
  C:\Windows\Minidump\091114-19624-01.dmp
  C:\Users\shadowman\AppData\Local\Temp\WER-1462852-0.sysdata.xml

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

David, please provide kernel memory dump if possible.

Thanks,
Dmitry

This is a problem reported by driver verifier.

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: 00000006, A fatal error was made in handling a WDF request. In this case,
	Parameter 2 further specifies the type of fatal error that has
	been made, as defined by the enumeration WDF_REQUEST_FATAL_ERROR.
Arg2: 00000004, The driver has completed a framework request, but has
	written more bytes to the output buffer than are specified
	in the IRP.
Arg3: 87f579c4, A pointer to a
	WDF_REQUEST_FATAL_ERROR_INFORMATION_LENGTH_MISMATCH_DATA
	structure, which contains a pointer to the IRP, a WDF
	request handle value, an IRP major function, and the
	number of bytes attempted to be written.
Arg4: 9403a450, Reserved.

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


BUGCHECK_STR:  0x10D_6

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre

DPC_STACK_BASE:  FFFFFFFF87F5C000

LAST_CONTROL_TRANSFER:  from 85665c84 to 82afce98

STACK_TEXT:  
87f57988 85665c84 0000010d 00000006 00000004 nt!KeBugCheckEx+0x1e
87f579a4 85683945 00000006 00000004 87f579c4 Wdf01000!FxVerifierBugCheck+0x21
87f579e4 85616dc5 00000000 8a8dc170 8af3bd90 Wdf01000!FxRequest::Vf_VerifyCompleteInternal+0x147
87f57a14 85611e86 8af3bd90 00000000 d52ad31c Wdf01000!FxRequest::CompleteInternal+0x36
87f57a38 a60019a7 9403a538 8af3bd90 00000000 Wdf01000!imp_WdfRequestCompleteWithInformation+0x106
87f57a4c a60055a9 a600554a 8af3bd90 750c4268 UsbDk!CWdfRequest::~CWdfRequest+0x19 [c:\cygwin64\tmp\build\source\usbdk\usbdk\wdfrequest.h @ 38]
87f57a68 85617419 750c4268 3763da28 d52ad2ec UsbDk!<lambda_f83b7675b4145a3e70da3fb5690660d8>::<helper_func_stdcall>+0x5f [c:\cygwin64\tmp\build\source\usbdk\usbdk\redirectorstrategy.cpp @ 499]
87f57a90 85614163 d59a8e28 c89c25d0 8a628c58 Wdf01000!FxRequestBase::CompleteSubmitted+0xf1
87f57abc 8561423c c89c25d0 c282b098 87f57af4 Wdf01000!FxIoTarget::RequestCompletionRoutine+0x140
87f57acc 82aa1183 8a628c58 d59a8e28 8af3bd90 Wdf01000!FxIoTarget::_RequestCompletionRoutine+0x33
87f57af4 82d50cd4 8a628c58 d59a8e28 c282b098 nt!IopUnloadSafeCompletion+0x4a
87f57b24 82a96093 8a628c58 d59a8e28 87f57b98 nt!IovpLocalCompletionRoutine+0x14b
87f57b68 82d50b64 8a9340f0 c89cf350 8a934028 nt!IopfCompleteRequest+0x128
87f57bd0 8c70a30d 82a587e8 c89cf350 00000000 nt!IovCompleteRequest+0x133
87f57c00 8c70af55 8af7c3e8 d59a8e28 8a9596f0 USBPORT!USBPORT_Core_iCompleteDoneTransfer+0x6e0
87f57c2c 8c70b6f6 8a934028 8a9340f0 8a934a98 USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x33b
87f57c54 8c7079ce 8a934028 8a934a98 8a934002 USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xbc
87f57c78 82a95935 8a934aa4 8a934002 00000000 USBPORT!USBPORT_Xdpc_Worker+0x173
87f57cd4 82a95798 87f3b120 87f40800 00000000 nt!KiExecuteAllDpcs+0xf9
87f57d20 82a955b8 00000000 0000000e 5ec68bff nt!KiRetireDpcList+0xd5
87f57d24 00000000 0000000e 5ec68bff 0008c25d nt!KiIdleLoop+0x38


STACK_COMMAND:  kb

FOLLOWUP_IP: 
UsbDk!CWdfRequest::~CWdfRequest+19 [c:\cygwin64\tmp\build\source\usbdk\usbdk\wdfrequest.h @ 38]
a60019a7 c3              ret

FAULTING_SOURCE_LINE:  c:\cygwin64\tmp\build\source\usbdk\usbdk\wdfrequest.h

FAULTING_SOURCE_FILE:  c:\cygwin64\tmp\build\source\usbdk\usbdk\wdfrequest.h

FAULTING_SOURCE_LINE_NUMBER:  38

FAULTING_SOURCE_CODE:  
    34:         if (m_Request != WDF_NO_HANDLE)
    35:         {
    36:             WdfRequestCompleteWithInformation(m_Request, m_Status, m_Information);
    37:         }
>   38:     }
    39: 
    40:     template <typename TObject>
    41:     NTSTATUS FetchInputObject(TObject &objectPtr, size_t *Length = nullptr)
    42:     {
    43:         return WdfRequestRetrieveInputBuffer(m_Request, sizeof(*objectPtr), (PVOID *)&objectPtr, Length);


SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  UsbDk!CWdfRequest::~CWdfRequest+19

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: UsbDk

IMAGE_NAME:  UsbDk.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  53f0536c

IMAGE_VERSION:  0.2.1.0

FAILURE_BUCKET_ID:  0x10D_6_VRF_UsbDk!CWdfRequest::_CWdfRequest+19

BUCKET_ID:  0x10D_6_VRF_UsbDk!CWdfRequest::_CWdfRequest+19

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x10d_6_vrf_usbdk!cwdfrequest::_cwdfrequest+19

FAILURE_ID_HASH:  {2d13c92c-4d89-2bb5-d584-5527cd83af30}

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


3: kd> dd 87f579c4
87f579c4  750c4268 d59a8e28 00000040 00000042
87f579d4  85666804 8af3bdd8 8af3bd02 8af3bd9c
87f579e4  87f57a14 85616dc5 00000000 8a8dc170
87f579f4  8af3bd90 00000000 9403a4e0 d59a8e28
87f57a04  856803fb d59a8fdc 9403a402 750c4268
87f57a14  87f57a38 85611e86 8af3bd90 00000000
87f57a24  d52ad31c 00000000 c89c25d0 87f57a5c
87f57a34  87f57a5c 87f57a68 a60019a7 9403a538

Fixed at v0.03-1.

Tried multiple times in v0.03-1 build, the BSOD never occured again.