Prev: GetJob failing with ERROR_INVALID_PARAMETER on Windows 7 RTM
Next: WinUSB_Free() return error and cause WinUSB_Initialize() fail in next power cycle.
From: Jimmy on 6 Oct 2009 20:53
I'm developing a NDIS6 filter driver based on WDK LWF sample. now I got a
BSOD. the call stack is as following:
after checking the NBL paramter in my_driver!FilterReceiveNetBufferLists, I
found it's a looping back packet and it's sourceHandle is equal to my
FilterHandle, but i's NdisPoolHandle is not belong to me. so how can I handle
this Looping back packet in my FilterReceiveNetBufferLists function? just
ignore it? (currently I called NdisFReturnNetBufferLists to let OS free
resource)

....
nt!KiBugCheckDispatch+0x69
nt!kiPageFault+0x260
b57nd60a!UM_ReturnNetBufferList+0x55
my_driver!FilterReceiveNetBufferLists+0x1e1
ndis!ndisDoLoopbackNetBufferList+0x280
ndis!ndisMLoopbackNetBufferLists+0xec
ndis!??::FJGMBFAB::\string'+0x646
ndis!NdisFSendNetBufferLists+0x64
my_driver!mydriverfunc+0x461
nt!pspSystemThreadStartup+0x5a
 | 
Pages: 1
Prev: GetJob failing with ERROR_INVALID_PARAMETER on Windows 7 RTM
Next: WinUSB_Free() return error and cause WinUSB_Initialize() fail in next power cycle.