Winsock Kernel Access Violation

Hi,
I am developing a kernel mode driver that should send data to a server.
I read about WSK and also found the following examples:

I tries to use wsktcp but I WskProvier.Dispatch->WskSocket causes BSOD because an access violation.

I obviously made the relevant initialization as in WSKStartup (WskRegiser and WskCaptureProviderNPI) and InitWskData works fine.

Although there might be a better approach to implement the requirements, I still want to try the socket solution.

Bugcheck info:
BugCheck 0x7E, {c0000005, 95564a59, 8919a304, 89199ee0}

You have to provide more information. Specifically you need to get the
crash dump into windbg, make sure you have symbols set up correctly for
both windows and your driver, and then run the windbg command “!analyze -v”
and copy all of the output from that here.

Mark Roddy

On Mon, Jul 10, 2017 at 1:32 PM, xxxxx@kayhut.com
wrote:

> Hi,
> I am developing a kernel mode driver that should send data to a server.
> I read about WSK and also found the following examples:
> - Microsoft’s “WSK TCP Echo Server”: github.com/Microsoft/Windows-
> driver-samples/tree/master/network/wsk/echosrv
> - wskudp: code.google.com/archive/p/wskudp
>
> I tries to use wsktcp but I WskProvier.Dispatch->WskSocket causes BSOD
> because an access violation.
>
> I obviously made the relevant initialization as in WSKStartup (WskRegiser
> and WskCaptureProviderNPI) and InitWskData works fine.
>
> Although there might be a better approach to implement the requirements, I
> still want to try the socket solution.
>
> Bugcheck info:
> BugCheck 0x7E, {c0000005, 95564a59, 8919a304, 89199ee0}
>
>
> —
> NTDEV is sponsored by OSR
>
> Visit the list online at: http:> showlists.cfm?list=ntdev>
>
> MONTHLY seminars on crash dump analysis, WDF, Windows internals and
> software drivers!
> Details at http:
>
> To unsubscribe, visit the List Server section of OSR Online at <
> http://www.osronline.com/page.cfm?name=ListServer&gt;
></http:></http:>