Need a Driver Developer

usasma · Apr 3, 2013

BSOD while entering Sleep

This person is a driver developer and has source and .pdb files.
I can't send him a PM directing him here - as he's a new member and can't use PM's

Anyone care to have a look? He's looking for the line in the code where the crash occurs.

niemiro · Apr 3, 2013

Well, here is the stack trace:

Code:

2: kd> !sysnative.rs
0xfffff880`02d2dba8  0xfffff801`f5c43637 nt! ?? ::FNODOBFM::`string'+0x13c00
[B]0xfffff880`02d2dc00  0xfffff880`08b52130 qcusbwwan!NdisQueryPacket+0xe0
0xfffff880`02d2dc10  0xfffff880`08b52130 qcusbwwan!NdisQueryPacket+0xe0[/B]
0xfffff880`02d2dc28  0xfffff801`f5b14f11 nt!KeUpdateRunTime+0x51
0xfffff880`02d2dc58  0xfffff801`f5a25e84 hal!HalpTimerClockInterrupt+0x50
0xfffff880`02d2dc88  0xfffff801`f5ae3bca nt!KiInterruptDispatchNoLockNoEtw+0x1aa
0xfffff880`02d2dda8  0xfffff801`f5cde504 nt!ExAllocatePoolWithTag+0x4cc
0xfffff880`02d2ddf8  0xfffff801`f5ad9602 nt!KxWaitForSpinLockAndAcquire+0x12
0xfffff880`02d2de48  0xfffff801`f5b160e5 nt!KeAcquireSpinLockRaiseToDpc+0x35
[B]0xfffff880`02d2de78  0xfffff880`08b5314e qcusbwwan!MPSendNetBufferListsEx+0x36e[/B]
0xfffff880`02d2df58  0xfffff880`01cf4355 wfplwfs!L2InspectNetBufferLists+0xb5
[B]0xfffff880`02d2df68  0xfffff880`08b521e5 qcusbwwan!NdisQueryPacket+0x195[/B]
0xfffff880`02d2dfa8  0xfffff880`01cf5230 wfplwfs!L2NdisFSendNetBufferLists+0x80
0xfffff880`02d2dfd0  0xfffff880`01cf5300 wfplwfs!LwfLowerSendNetBufferListsComplete+0x50
0xfffff880`02d2dfe8  0xfffff880`01cf540f wfplwfs!LwfLowerSendNetBufferLists+0x9f
0xfffff880`02d2e058  0xfffff880`0187076a ndis!ndisInvokeNextSendHandler+0x22a
0xfffff880`02d2e0f8  0xfffff880`01a9c27f tcpip!WfpProcessOutTransportStackIndication+0x800
0xfffff880`02d2e168  0xfffff880`0187097b ndis!NdisSendNetBufferLists+0x12b
0xfffff880`02d2e198  0xfffff880`01cf5370 wfplwfs!LwfLowerSendNetBufferLists+0x0
0xfffff880`02d2e248  0xfffff880`01aacecd tcpip!IppFragmentPackets+0x49d
0xfffff880`02d2e288  0xfffff880`01aab6bd tcpip!IppFindOrCreatePath+0x20d
0xfffff880`02d2e318  0xfffff880`01a9c96e tcpip!WfpInspectSendNonTcpDatagram+0x15e
0xfffff880`02d2e338  0xfffff880`00c00000 msrpc!GsDriverEntry  (msrpc+0x0)+0x0
0xfffff880`02d2e378  0xfffff880`01be4b90 tcpip!Ipv4Global+0x0
0xfffff880`02d2e3a8  0xfffff880`01ab2924 tcpip!IppDispatchSendPacketHelper+0x94
0xfffff880`02d2e3b0  0xfffff880`01be4b90 tcpip!Ipv4Global+0x0
0xfffff880`02d2e3e8  0xfffff801`f5cdd2ba nt!ExFreePoolWithTag+0x2aa
0xfffff880`02d2e428  0xfffff880`01ae3edb tcpip!IppInspectLocalDatagramsOut+0x43b
0xfffff880`02d2e4c8  0xfffff880`01ab32c6 tcpip!IppPacketizeDatagrams+0x2b6
0xfffff880`02d2e4d0  0xfffff880`01be4b90 tcpip!Ipv4Global+0x0
0xfffff880`02d2e508  0xfffff801`f5ad95ad nt!ExAllocatePoolWithTagPriority+0x5d
0xfffff880`02d2e520  0xfffff880`01be4b90 tcpip!Ipv4Global+0x0
0xfffff880`02d2e558  0xfffff880`01ac8a0a tcpip!IppCompleteAndFreePacketList+0xf6
0xfffff880`02d2e590  0xfffff880`01bf2c00 tcpip!IgmpSessionState+0x0
0xfffff880`02d2e5c8  0xfffff880`01be4b90 tcpip!Ipv4Global+0x0
0xfffff880`02d2e5d8  0xfffff880`01ae17cb tcpip!IppSendDatagramsCommon+0x6eb
0xfffff880`02d2e618  0xfffff801`f5cdd2ba nt!ExFreePoolWithTag+0x2aa
0xfffff880`02d2e628  0xfffff880`01aaf2c2 tcpip!IppChecksumDatagram+0xe2
0xfffff880`02d2e658  0xfffff880`0197371a NETIO!NetioAllocateAndReferenceNetBufferList+0x7a
0xfffff880`02d2e6a0  0xfffff880`01bf2c00 tcpip!IgmpSessionState+0x0
0xfffff880`02d2e748  0xfffff880`01a7e7ba tcpip!IppQueueMulticastDiscoveryRecord+0xc6
0xfffff880`02d2e760  0xfffff880`01be4b90 tcpip!Ipv4Global+0x0
0xfffff880`02d2e798  0xfffff880`01a7e3e9 tcpip!IppProcessMulticastDiscoveryTimeoutEvents+0x2d5
0xfffff880`02d2e7a8  0xfffff880`01be4b90 tcpip!Ipv4Global+0x0
0xfffff880`02d2e7c8  0xfffff801`f5ba2f00 nt!PerfInfoLogInterrupt+0x70
0xfffff880`02d2e7f8  0xfffff880`01be4b90 tcpip!Ipv4Global+0x0
0xfffff880`02d2e848  0xfffff880`06905627 srvnet!RtlUnicodeStringCopyStringEx+0x117
0xfffff880`02d2e868  0xfffff801`f5ae2ee6 nt!KiScanInterruptObjectList+0xb6
0xfffff880`02d2e888  0xfffff880`01bf2c00 tcpip!IgmpSessionState+0x0
0xfffff880`02d2e908  0xfffff880`01bbdbe8 tcpip!in4addr_alligmpv3routersonlink+0x0
0xfffff880`02d2e9a0  0xfffff880`034ce480 tdx!TdxDeviceList+0x0
0xfffff880`02d2e9b8  0xfffff801`f5cdd2ba nt!ExFreePoolWithTag+0x2aa
0xfffff880`02d2e9c8  0xfffff880`034bc33f tdx!TdxProcessInterfaceChangeRoutine+0x22f
0xfffff880`02d2ea98  0xfffff801`f5eb92b9 nt!ObpRemoveObjectRoutine+0x69
0xfffff880`02d2eaf8  0xfffff801`f5adfd29 nt!ObfDereferenceObject+0x89
0xfffff880`02d2eb38  0xfffff880`0356ab8e afd!AfdFreeEndpointResources+0x21e
0xfffff880`02d2eb90  0xfffff801`f5d67f80 nt!KiInitialPCR+0x2f80
0xfffff880`02d2ebb8  0xfffff801`f5af3774 nt!ExpBuiltinPriorities+0x4
0xfffff880`02d2ebc0  0xfffff801`f5cf2fc0 nt!ExNode0+0x0
0xfffff880`02d2ebd8  0xfffff801`f5af3774 nt!ExpBuiltinPriorities+0x4
0xfffff880`02d2ebe8  0xfffff880`01a7eba0 tcpip!IppMulticastWorkerRoutine+0x0
0xfffff880`02d2ebf8  0xfffff880`01a7ec2b tcpip!IppMulticastWorkerRoutine+0x8b
0xfffff880`02d2ec08  0xfffff801`f5b1ec4b nt!KeRemoveQueueEx+0x26b
0xfffff880`02d2ec10  0xfffff880`0356af10 afd!AfdFreeEndpoint+0x0
0xfffff880`02d2ec48  0xfffff801`f5ad545b nt!IopProcessWorkItem+0x5f
0xfffff880`02d2ec58  0xfffff880`0353ca80 afd!AfdDoWork+0x0
0xfffff880`02d2ec68  0xfffff801`f5cf30d0 nt!ExNode0+0x110
0xfffff880`02d2ec70  0xfffff801`f5d01d00 nt!WmipEventWorkQueueItem+0x0
0xfffff880`02d2ec80  0xfffff801`f5ad53fc nt!IopProcessWorkItem+0x0
0xfffff880`02d2ec88  0xfffff801`f5cf2fc0 nt!ExNode0+0x0
0xfffff880`02d2eca8  0xfffff801`f5cf30d0 nt!ExNode0+0x110
0xfffff880`02d2ecb8  0xfffff801`f5b22391 nt!ExpWorkerThread+0x142
0xfffff880`02d2ecc0  0xfffff801`f5cf30d0 nt!ExNode0+0x110
0xfffff880`02d2ecd0  0xfffff801`f5ad53fc nt!IopProcessWorkItem+0x0
0xfffff880`02d2ed30  0xfffff801`f5a6f000 nt!`string' <PERF> (nt+0x0)+0x0
0xfffff880`02d2ed48  0xfffff801`f5a91521 nt!PspSystemThreadStartup+0x59
0xfffff880`02d2ed60  0xfffff801`f5b22250 nt!ExpWorkerThread+0x0
0xfffff880`02d2ed98  0xfffff801`f5acfdd6 nt!KxStartSystemThread+0x16
0xfffff880`02d2eda0  0xfffff801`f5d65180 nt!KiInitialPCR+0x180

niemiro · Apr 3, 2013

Right, I think I got this right (still a bit ropey with WinDBG)

Code:

2: kd> u MPSendNetBufferListsEx+0x36e
qcusbwwan!MPSendNetBufferListsEx+0x36e [[B]d:\wdk_8k\qmi2\win\qcdrivers\ndis\mptransmit.c @ 325[/B]]:
fffff880`08b5314e ??              ???
                                    ^ Memory access error in 'u MPSendNetBufferListsEx+0x36e'

niemiro · Apr 3, 2013

P.S. I usually cheat with driver development and just use VisualDDK: VisualDDK - Create and debug driver projects directly from Visual Studio

usasma · Apr 3, 2013

Thanks Richard!

niemiro · Apr 3, 2013

usasma said:
Thanks Richard!

No problem, I just hope I got it right (I am not that confident with this sort of stuff so hope someone will check it!)

Vir Gnarus · Apr 3, 2013

This kind of inquiry is probably better left directed to a place like OSR, which is a website catering to driver developers and has mailing lists that he can use to ask in.

How'd you get the pdb to load in Windbg, Niemiro? I'm having the most difficult time getting Windbg to see it.

mgrzeg · Apr 3, 2013

One more output:

Code:

Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Roboczy\Dumps\eightforums\bsod-crashes-debugging23226-bsod-while-entering-sleep.htm\SF_03-04-2013\SF_03-04-2013\040113-16567-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*C:\websymbols*http://msdl.microsoft.com/downloads/symbols
Executable search path is: 
Windows 8 Kernel Version 9200 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9200.16384.amd64fre.win8_rtm.120725-1247
Machine Name:
Kernel base = 0xfffff803`bf06c000 PsLoadedModuleList = 0xfffff803`bf336a60
Debug session time: Mon Apr  1 09:20:13.958 2013 (UTC + 2:00)
System Uptime: 0 days 0:04:36.809
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 133, {0, 283, 282, 0}
*** WARNING: Unable to verify timestamp for qcusbwwan.sys
*** ERROR: Module load completed but symbols could not be loaded for qcusbwwan.sys
Probably caused by : qcusbwwan.sys ( qcusbwwan+5f14e )
Followup: MachineOwner
---------
0: kd> .sympath+ C:\Roboczy\Dumps\eightforums\bsod-crashes-debugging23226-bsod-while-entering-sleep.htm\qcusbwwan
Symbol search path is: srv*C:\websymbols*http://msdl.microsoft.com/downloads/symbols;C:\Roboczy\Dumps\eightforums\bsod-crashes-debugging23226-bsod-while-entering-sleep.htm\qcusbwwan
Expanded Symbol search path is: srv*c:\websymbols*http://msdl.microsoft.com/downloads/symbols;c:\roboczy\dumps\eightforums\bsod-crashes-debugging23226-bsod-while-entering-sleep.htm\qcusbwwan
0: kd> .reload /f qcusbwwan.sys
Unable to load image \SystemRoot\system32\DRIVERS\qcusbwwan.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for qcusbwwan.sys
0: kd> lmvm qcusbwwan
start             end                 module name
fffff880`08a09000 fffff880`08af8000   qcusbwwan M (private pdb symbols)  c:\roboczy\dumps\eightforums\bsod-crashes-debugging23226-bsod-while-entering-sleep.htm\qcusbwwan\qcusbwwan.pdb
    Loaded symbol image file: qcusbwwan.sys
    Image path: \SystemRoot\system32\DRIVERS\qcusbwwan.sys
    Image name: qcusbwwan.sys
    Timestamp:        Fri Feb 22 11:57:29 2013 (51274F19)
    CheckSum:         000EEBF1
    ImageSize:        000EF000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
0: kd> k
Child-SP          RetAddr           Call Site
fffff803`c0d50f38 fffff803`bf2405df nt!KeBugCheckEx
fffff803`c0d50f40 fffff803`bf111f11 nt! ?? ::FNODOBFM::`string'+0x13ba4
fffff803`c0d50fc0 fffff803`bf112d98 nt!KeUpdateRunTime+0x51
fffff803`c0d50ff0 fffff803`bf022eba nt!KeUpdateTime+0x3f9
fffff803`c0d511e0 fffff803`bf0e0bca hal!HalpTimerClockInterrupt+0x86
fffff803`c0d51210 fffff803`bf0d6602 nt!KiInterruptDispatchNoLockNoEtw+0x1aa
fffff803`c0d513a0 fffff803`bf1130e5 nt!KxWaitForSpinLockAndAcquire+0x12
fffff803`c0d513d0 fffff880`08a6814e nt!KeAcquireSpinLockRaiseToDpc+0x35
fffff803`c0d51400 fffff880`08a671e5 qcusbwwan!MPSendNetBufferListsEx+0x36e [d:\wdk_8k\qmi2\win\qcdrivers\ndis\mptransmit.c @ 325]
fffff803`c0d514f0 00000000`00000001 qcusbwwan!NdisQueryPacket+0x195 [c:\program files\windows kits\8.0\include\km\ndis.h @ 2934]
fffff803`c0d51540 fffffa80`05b85d20 0x1
fffff803`c0d51548 fffffa80`0506e000 0xfffffa80`05b85d20
fffff803`c0d51550 fffff880`01ce4300 0xfffffa80`0506e000
fffff803`c0d51558 fffff803`c0d515e0 wfplwfs!LwfLowerSendNetBufferListsComplete+0x50
fffff803`c0d515a8 fffffa80`04f65240 0xfffff803`c0d515e0
fffff803`c0d515b0 00000000`00000103 0xfffffa80`04f65240
fffff803`c0d515b8 fffff880`00000000 0x103
fffff803`c0d515c0 fffffa80`04f65240 0xfffff880`00000000
fffff803`c0d515c8 fffffa80`05061c80 0xfffffa80`04f65240
fffff803`c0d515d0 fffffa80`051681a0 0xfffffa80`05061c80
fffff803`c0d515d8 fffff880`018fb76a 0xfffffa80`051681a0
fffff803`c0d515e0 fffff880`018fb97b ndis!ndisInvokeNextSendHandler+0x22a
fffff803`c0d516f0 fffff880`01a9becd ndis!NdisSendNetBufferLists+0x12b
fffff803`c0d517d0 fffff880`01aa1924 tcpip!IppFragmentPackets+0x49d
fffff803`c0d51930 fffff880`01aa22c6 tcpip!IppDispatchSendPacketHelper+0x94
fffff803`c0d51a50 fffff880`01ad07cb tcpip!IppPacketizeDatagrams+0x2b6
fffff803`c0d51b60 fffff880`01a8a6df tcpip!IppSendDatagramsCommon+0x6eb
fffff803`c0d51d20 fffff880`01a89819 tcpip!UdpSendMessagesOnPathCreation+0x90f
fffff803`c0d52140 fffff880`01a8ba88 tcpip!UdpSendMessages+0x259
fffff803`c0d52550 fffff803`bf127df5 tcpip!UdpTlProviderSendMessagesCalloutRoutine+0x15
fffff803`c0d52580 fffff803`bf128d85 nt!KeExpandKernelStackAndCalloutInternal+0xe5
fffff803`c0d52680 fffff880`01a8bc70 nt!KeExpandKernelStackAndCalloutEx+0x25
fffff803`c0d526c0 fffff880`03ae81f6 tcpip!UdpTlProviderSendMessages+0x70
fffff803`c0d52740 fffff880`03ae762f tdx!TdxSendDatagramTransportAddress+0x2e6
fffff803`c0d52830 fffff880`03b17f20 tdx!TdxTdiDispatchInternalDeviceControl+0x7f
fffff803`c0d52a30 fffff880`03b22640 netbt!SendNameServiceRequest+0x5a4
fffff803`c0d52ae0 fffff880`03b16396 netbt!MSnodeRegCompletion+0xf0
fffff803`c0d52b60 fffff803`bf1138b4 netbt!TimerExpiry+0x66
fffff803`c0d52bb0 fffff803`bf113ed5 nt!KiProcessExpiredTimerList+0x214
fffff803`c0d52cf0 fffff803`bf113d88 nt!KiExpireTimerTable+0xa9
fffff803`c0d52d90 fffff803`bf10de76 nt!KiTimerExpiration+0xc8
fffff803`c0d52e40 00000000`00000000 nt!KiRetireDpcList+0x1f6
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
 component can usually be identified with a stack trace.
Arg2: 0000000000000283, The DPC time count (in ticks).
Arg3: 0000000000000282, The DPC time allotment (in ticks).
Arg4: 0000000000000000
Debugging Details:
------------------

DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
BUGCHECK_STR:  0x133
PROCESS_NAME:  svchost.exe
CURRENT_IRQL:  d
TAG_NOT_DEFINED_c000000f:  FFFFF803C0D52FB0
LAST_CONTROL_TRANSFER:  from fffff803bf2405df to fffff803bf0e7040
STACK_TEXT:  
fffff803`c0d50f38 fffff803`bf2405df : 00000000`00000133 00000000`00000000 00000000`00000283 00000000`00000282 : nt!KeBugCheckEx
fffff803`c0d50f40 fffff803`bf111f11 : 00000000`00000000 fffff803`bf362180 fffff803`c0d510f0 fffff780`00000320 : nt! ?? ::FNODOBFM::`string'+0x13ba4
fffff803`c0d50fc0 fffff803`bf112d98 : ffffffff`ffd0b270 fffff803`bf04c502 fffff803`c0d510f0 00000000`00000000 : nt!KeUpdateRunTime+0x51
fffff803`c0d50ff0 fffff803`bf022eba : ffffffff`ffd0b270 fffff803`bf04c502 fffffa80`05070250 00000000`00000002 : nt!KeUpdateTime+0x3f9
fffff803`c0d511e0 fffff803`bf0e0bca : 00000000`a4fdb7dc 00000000`fd12a39a fffff803`bf04c580 00000000`00000000 : hal!HalpTimerClockInterrupt+0x86
fffff803`c0d51210 fffff803`bf0d6602 : 00000000`0000003b fffffa80`04f65270 fffffa80`04f65240 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x1aa
fffff803`c0d513a0 fffff803`bf1130e5 : 00000000`00000002 00000000`00000002 fffffa80`051681a0 fffffa80`05b85d20 : nt!KxWaitForSpinLockAndAcquire+0x12
fffff803`c0d513d0 fffff880`08a6814e : 00000000`0000073d fffff803`c0d51699 fffff803`c0d51470 00000000`000007ff : nt!KeAcquireSpinLockRaiseToDpc+0x35
fffff803`c0d51400 fffff880`08a671e5 : fffffa80`0506e000 fffffa80`05b85d20 fffffa80`00000000 fffffa80`00000001 : qcusbwwan!MPSendNetBufferListsEx+0x36e [d:\wdk_8k\qmi2\win\qcdrivers\ndis\mptransmit.c @ 325]
fffff803`c0d514f0 00000000`00000001 : fffffa80`05b85d20 fffffa80`0506e000 fffff880`01ce4300 fffffa80`00000000 : qcusbwwan!NdisQueryPacket+0x195 [c:\program files\windows kits\8.0\include\km\ndis.h @ 2934]
fffff803`c0d51540 fffffa80`05b85d20 : fffffa80`0506e000 fffff880`01ce4300 fffffa80`00000000 00000000`00000000 : 0x1
fffff803`c0d51548 fffffa80`0506e000 : fffff880`01ce4300 fffffa80`00000000 00000000`00000000 fffff880`01ce440f : 0xfffffa80`05b85d20
fffff803`c0d51550 fffff880`01ce4300 : fffffa80`00000000 00000000`00000000 fffff880`01ce440f 00000000`00000000 : 0xfffffa80`0506e000
fffff803`c0d51558 fffff803`c0d515e0 : fffffa80`04f65240 00000000`00000103 fffff880`00000000 fffffa80`04f65240 : wfplwfs!LwfLowerSendNetBufferListsComplete+0x50
fffff803`c0d515a8 fffffa80`04f65240 : 00000000`00000103 fffff880`00000000 fffffa80`04f65240 fffffa80`05061c80 : 0xfffff803`c0d515e0
fffff803`c0d515b0 00000000`00000103 : fffff880`00000000 fffffa80`04f65240 fffffa80`05061c80 fffffa80`051681a0 : 0xfffffa80`04f65240
fffff803`c0d515b8 fffff880`00000000 : fffffa80`04f65240 fffffa80`05061c80 fffffa80`051681a0 fffff880`018fb76a : 0x103
fffff803`c0d515c0 fffffa80`04f65240 : fffffa80`05061c80 fffffa80`051681a0 fffff880`018fb76a fffffa80`0506e000 : 0xfffff880`00000000
fffff803`c0d515c8 fffffa80`05061c80 : fffffa80`051681a0 fffff880`018fb76a fffffa80`0506e000 fffffa80`05b85d20 : 0xfffffa80`04f65240
fffff803`c0d515d0 fffffa80`051681a0 : fffff880`018fb76a fffffa80`0506e000 fffffa80`05b85d20 fffffa80`00000000 : 0xfffffa80`05061c80
fffff803`c0d515d8 fffff880`018fb76a : fffffa80`0506e000 fffffa80`05b85d20 fffffa80`00000000 00000000`00000001 : 0xfffffa80`051681a0
fffff803`c0d515e0 fffff880`018fb97b : fffffa80`051681a0 00000000`00000000 00000000`00000002 fffffa80`05b85d20 : ndis!ndisInvokeNextSendHandler+0x22a
fffff803`c0d516f0 fffff880`01a9becd : fffff880`01bd3b02 fffffa80`05b85e80 fffffa80`00000000 fffffa80`00000000 : ndis!NdisSendNetBufferLists+0x12b
fffff803`c0d517d0 fffff880`01aa1924 : fffff880`01bd3b90 00000000`00000000 fffffa80`03900000 fffffa80`00000800 : tcpip!IppFragmentPackets+0x49d
fffff803`c0d51930 fffff880`01aa22c6 : fffff880`01bd3b90 fffffa80`04a4c0c8 fffffa80`02f81100 a5e60aad`c91dbc00 : tcpip!IppDispatchSendPacketHelper+0x94
fffff803`c0d51a50 fffff880`01ad07cb : 00000000`00000000 fffffa80`03906328 fffff803`c0d51e80 fffffa80`03906248 : tcpip!IppPacketizeDatagrams+0x2b6
fffff803`c0d51b60 fffff880`01a8a6df : 00000000`00000004 fffff880`01bd3b90 fffffa80`02d07010 00000000`00000000 : tcpip!IppSendDatagramsCommon+0x6eb
fffff803`c0d51d20 fffff880`01a89819 : fffffa80`04ec2640 fffffa80`054dfd74 fffff803`c0d52790 fffff880`01bd3b90 : tcpip!UdpSendMessagesOnPathCreation+0x90f
fffff803`c0d52140 fffff880`01a8ba88 : fffffa80`056f9710 fffff803`bf127df5 fffff803`c0d526f0 fffff803`bf01ce2b : tcpip!UdpSendMessages+0x259
fffff803`c0d52550 fffff803`bf127df5 : 00000000`00000001 00000000`00000000 fffff880`009bf180 fffff803`bf2effc0 : tcpip!UdpTlProviderSendMessagesCalloutRoutine+0x15
fffff803`c0d52580 fffff803`bf128d85 : fffff880`01a8ba74 fffff803`c0d526f0 00000000`00000010 00000004`00000005 : nt!KeExpandKernelStackAndCalloutInternal+0xe5
fffff803`c0d52680 fffff880`01a8bc70 : 00000000`00000003 00000000`0000002f 00000000`00000000 fffffa80`03deb730 : nt!KeExpandKernelStackAndCalloutEx+0x25
fffff803`c0d526c0 fffff880`03ae81f6 : fffffa80`054dfd70 fffff803`c0d527c9 fffffa80`05bdcdce 00000000`000007ff : tcpip!UdpTlProviderSendMessages+0x70
fffff803`c0d52740 fffff880`03ae762f : fffffa80`03b39602 fffffa80`05113a00 fffffa80`05113b18 fffffa80`041cb708 : tdx!TdxSendDatagramTransportAddress+0x2e6
fffff803`c0d52830 fffff880`03b17f20 : fffffa80`05113a00 fffffa80`05113a00 fffffa80`05bdcbe0 fffffa80`0516a730 : tdx!TdxTdiDispatchInternalDeviceControl+0x7f
fffff803`c0d52a30 fffff880`03b22640 : fffffa80`03aee060 fffffa80`050d8730 fffffa80`04bc9a70 00000000`00000000 : netbt!SendNameServiceRequest+0x5a4
fffff803`c0d52ae0 fffff880`03b16396 : fffffa80`00000000 fffffa80`050d87b0 00000000`00000001 fffffa80`050d8730 : netbt!MSnodeRegCompletion+0xf0
fffff803`c0d52b60 fffff803`bf1138b4 : fffff803`c0d52c89 fffffa80`00001000 fffff803`c0d52e80 fffffa80`04b90f45 : netbt!TimerExpiry+0x66
fffff803`c0d52bb0 fffff803`bf113ed5 : fffff803`bf364f00 fffff803`bf0dd4f8 fffff803`c0d52e00 00000000`000000d8 : nt!KiProcessExpiredTimerList+0x214
fffff803`c0d52cf0 fffff803`bf113d88 : fffff803`bf362180 fffff803`bf364f80 fffffa80`00000003 00000000`000027c0 : nt!KiExpireTimerTable+0xa9
fffff803`c0d52d90 fffff803`bf10de76 : fffff803`bf362180 00000000`7d2be8bf fffffa80`0399b9c0 00000000`00000025 : nt!KiTimerExpiration+0xc8
fffff803`c0d52e40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiRetireDpcList+0x1f6

STACK_COMMAND:  kb
FOLLOWUP_IP: 
qcusbwwan!MPSendNetBufferListsEx+36e [d:\wdk_8k\qmi2\win\qcdrivers\ndis\mptransmit.c @ 325]
fffff880`08a6814e ??              ???
FAULTING_SOURCE_LINE:  d:\wdk_8k\qmi2\win\qcdrivers\ndis\mptransmit.c
FAULTING_SOURCE_FILE:  d:\wdk_8k\qmi2\win\qcdrivers\ndis\mptransmit.c
FAULTING_SOURCE_LINE_NUMBER:  325
SYMBOL_STACK_INDEX:  8
SYMBOL_NAME:  qcusbwwan!MPSendNetBufferListsEx+36e
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: qcusbwwan
IMAGE_NAME:  qcusbwwan.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  51274f19
BUCKET_ID_FUNC_OFFSET:  36e
FAILURE_BUCKET_ID:  0x133_DPC_qcusbwwan!MPSendNetBufferListsEx
BUCKET_ID:  0x133_DPC_qcusbwwan!MPSendNetBufferListsEx
Followup: MachineOwner
---------

niemiro · Apr 3, 2013

Vir Gnarus said:
This kind of inquiry is probably better left directed to a place like OSR, which is a website catering to driver developers and has mailing lists that he can use to ask in.

How'd you get the pdb to load in Windbg, Niemiro? I'm having the most difficult time getting Windbg to see it.

I did exactly what mgrzeg did, except that he did a load more stuff on top of what I did

I created a folder with the .pdb in, did .sympath+ on the folder, and then did .reload /f qcusbwwan.sys.

I then did a rawstack dump, took the relevant entries, and bunged them into u, but here is where mgrzeg did a much neater job than me. Thanks a lot @mgrzeg, I have learned some cool stuff from your output.

Richard

mgrzeg · Apr 3, 2013

I've checked also other dumps and there are more faulting lines:

Code:

File: 040113-16567-01.dmp
FAULTING_SOURCE_FILE:  d:\wdk_8k\qmi2\win\qcdrivers\ndis\mptransmit.c
FAULTING_SOURCE_LINE_NUMBER:  325
File: 040113-16582-01.dmp
FAULTING_SOURCE_FILE:  d:\wdk_8k\qmi2\win\qcdrivers\ndis\mpusb.c
FAULTING_SOURCE_LINE_NUMBER:  3015
File: 040113-16832-01.dmp
FAULTING_SOURCE_FILE:  d:\wdk_8k\qmi2\win\qcdrivers\ndis\mpusb.c
FAULTING_SOURCE_LINE_NUMBER:  3015
File: 040113-16957-01.dmp
FAULTING_SOURCE_FILE:  d:\wdk_8k\qmi2\win\qcdrivers\ndis\mptransmit.c
FAULTING_SOURCE_LINE_NUMBER:  413
File: 040113-17004-01.dmp
FAULTING_SOURCE_FILE:  d:\wdk_8k\qmi2\win\qcdrivers\ndis\mpusb.c
FAULTING_SOURCE_LINE_NUMBER:  3015
File: 040113-17628-01.dmp
FAULTING_SOURCE_FILE:  d:\wdk_8k\qmi2\win\qcdrivers\ndis\mpusb.c
FAULTING_SOURCE_LINE_NUMBER:  181
File: 040113-17659-01.dmp
FAULTING_SOURCE_FILE:  d:\wdk_8k\qmi2\win\qcdrivers\ndis\mptransmit.c
FAULTING_SOURCE_LINE_NUMBER:  413
File: 040113-17674-01.dmp
FAULTING_SOURCE_FILE:  d:\wdk_8k\qmi2\win\qcdrivers\ndis\mptransmit.c
FAULTING_SOURCE_LINE_NUMBER:  325
File: 040113-17721-01.dmp
FAULTING_SOURCE_FILE:  d:\wdk_8k\qmi2\win\qcdrivers\ndis\mptransmit.c
FAULTING_SOURCE_LINE_NUMBER:  413
File: 040113-17799-01.dmp
FAULTING_SOURCE_FILE:  d:\wdk_8k\qmi2\win\qcdrivers\ndis\mptransmit.c
FAULTING_SOURCE_LINE_NUMBER:  413
File: 040113-17908-01.dmp
FAULTING_SOURCE_FILE:  d:\wdk_8k\qmi2\win\qcdrivers\ndis\mptransmit.c
FAULTING_SOURCE_LINE_NUMBER:  413
File: 040113-18018-01.dmp
FAULTING_SOURCE_FILE:  d:\wdk_8k\qmi2\win\qcdrivers\ndis\mptransmit.c
FAULTING_SOURCE_LINE_NUMBER:  413
File: 040213-15506-01.dmp
FAULTING_SOURCE_FILE:  d:\wdk_8k\qmi2\win\qcdrivers\ndis\mptransmit.c
FAULTING_SOURCE_LINE_NUMBER:  413
File: 040213-16146-01.dmp
FAULTING_SOURCE_FILE:  d:\wdk_8k\qmi2\win\qcdrivers\ndis\mptransmit.c
FAULTING_SOURCE_LINE_NUMBER:  325
File: 040213-16442-01.dmp
FAULTING_SOURCE_FILE:  d:\wdk_8k\qmi2\win\qcdrivers\ndis\mptransmit.c
FAULTING_SOURCE_LINE_NUMBER:  325
File: 040213-16629-01.dmp
FAULTING_SOURCE_FILE:  d:\wdk_8k\qmi2\win\qcdrivers\ndis\mpusb.c
FAULTING_SOURCE_LINE_NUMBER:  181
File: 040213-16723-01.dmp
FAULTING_SOURCE_FILE:  d:\wdk_8k\qmi2\win\qcdrivers\ndis\mptransmit.c
FAULTING_SOURCE_LINE_NUMBER:  325
File: 040213-16879-01.dmp
FAULTING_SOURCE_FILE:  d:\wdk_8k\qmi2\win\qcdrivers\ndis\mpusb.c
FAULTING_SOURCE_LINE_NUMBER:  181
File: 040213-17440-01.dmp
FAULTING_SOURCE_FILE:  d:\wdk_8k\qmi2\win\qcdrivers\ndis\mptransmit.c
FAULTING_SOURCE_LINE_NUMBER:  325
File: 040313-15178-01.dmp
FAULTING_SOURCE_FILE:  d:\wdk_8k\qmi2\win\qcdrivers\ndis\mptransmit.c
FAULTING_SOURCE_LINE_NUMBER:  325
File: 040313-15319-01.dmp
FAULTING_SOURCE_FILE:  d:\wdk_8k\qmi2\win\qcdrivers\ndis\mptransmit.c
FAULTING_SOURCE_LINE_NUMBER:  325
File: 040313-15459-01.dmp
FAULTING_SOURCE_FILE:  d:\wdk_8k\qmi2\win\qcdrivers\ndis\mptransmit.c
FAULTING_SOURCE_LINE_NUMBER:  325
File: 040313-16052-01.dmp
FAULTING_SOURCE_FILE:  d:\wdk_8k\qmi2\win\qcdrivers\ndis\mptransmit.c
FAULTING_SOURCE_LINE_NUMBER:  325
File: 040313-16645-01.dmp
FAULTING_SOURCE_FILE:  d:\wdk_8k\qmi2\win\qcdrivers\ndis\mpusb.c
FAULTING_SOURCE_LINE_NUMBER:  181
File: 040313-17222-01.dmp
FAULTING_SOURCE_FILE:  d:\wdk_8k\qmi2\win\qcdrivers\ndis\mptransmit.c
FAULTING_SOURCE_LINE_NUMBER:  325

m.g.

usasma · Apr 3, 2013

Thanks all for your help! I've (hopefully) sent him off to OSR for additional assistance.
He's not a native English speaker so I'm not sure how much I bungled up with copy/paste.

Need a Driver Developer

usasma

Retired Admin

niemiro

Senior Administrator, Windows Update Expert

niemiro

Senior Administrator, Windows Update Expert

niemiro

Senior Administrator, Windows Update Expert

usasma

Retired Admin

niemiro

Senior Administrator, Windows Update Expert

Vir Gnarus

BSOD Kernel Dump Expert

mgrzeg

BSOD Kernel Dump Senior Analyst

niemiro

Senior Administrator, Windows Update Expert

mgrzeg

BSOD Kernel Dump Senior Analyst

usasma

Retired Admin