This is what i got from WinDbg Crush Dump.

This is what i got from WinDbg Crush Dump.

kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: b9551012, The address that the exception occurred at
Arg3: cbf26548, Exception Record Address
Arg4: cbf26110, Context Record Address

Debugging Details:

SYSTEM_SKU: LENOVO_MT_80F6_BU_idea_FM_Lenovo B40-80

SYSTEM_VERSION: Lenovo B40-80

BIOS_DATE: 04/24/2015

BASEBOARD_PRODUCT: Lenovo B40-80

BASEBOARD_VERSION: No DPK

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: ffffffffb9551012

BUGCHECK_P3: ffffffffcbf26548

BUGCHECK_P4: ffffffffcbf26110

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced
memory at 0x%p. The memory could not be %s.

FAULTING_IP:
Mod__WskPost+1012
b9551012 8908 mov dword ptr [eax],ecx

EXCEPTION_RECORD: cbf26548 – (.exr 0xffffffffcbf26548)
ExceptionAddress: b9551012 (Mod__WskPost+0x00001012)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000001
Parameter[1]: 00000000
Attempt to write to address 00000000

CONTEXT: cbf26110 – (.cxr 0xffffffffcbf26110)
eax=00000000 ebx=00000000 ecx=b4de958c edx=00000000 esi=8e2dc880 edi=8e2dc8f3
eip=b9551012 esp=cbf2669c ebp=cbf2669c iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
Mod__WskPost+0x1012:
b9551012 8908 mov dword ptr [eax],ecx ds:0023:00000000=???
Resetting default scope

CPU_COUNT: 4

CPU_MHZ: 893

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3d

CPU_STEPPING: 4

DEFAULT_BUCKET_ID: NULL_DEREFERENCE

PROCESS_NAME: System

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at
0x%p. The memory could not be %s.

EXCEPTION_PARAMETER1: 00000001

EXCEPTION_PARAMETER2: 00000000

WRITE_ADDRESS: 00000000

FOLLOWUP_IP:
Mod__WskPost+1012
b9551012 8908 mov dword ptr [eax],ecx

BUGCHECK_STR: AV

ANALYSIS_VERSION: 10.0.10240.9 amd64fre

LAST_CONTROL_TRANSFER: from 81ebdee2 to b9551012

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
cbf2669c 81ebdee2 00000000 8e2dc880 00000000 Mod__WskPost+0x1012
cbf266f8 9118409a 9a70c870 8f431f40 cbf2678c nt!IopfCompleteRequest+0x1d2
cbf26708 8ac7ceb4 8e2dc880 00000000 9a70c870
afd!WskProTLCreateEndpointComplete+0x3a
cbf2678c 8ac7cd2e 9a70c8b4 8e2dc880 b4de9578
tcpip!TcpCreateEndpointWorkQueueRoutine+0x114
cbf267e8 8ac7cafa 8e2dc880 00000002 00000000 tcpip!TcpCreateEndpoint+0x21e
cbf26808 91182095 8e38a5d0 cbf26824 00000000 tcpip!TcpTlProviderEndpoint+0x26
cbf26864 9118194b cbf26888 81ebc183 8e38c268 afd!WskProIRPSocket+0x219
cbf2686c 81ebc183 8e38c268 8e2dc880 8e2dc880
afd!AfdWskDispatchInternalDeviceControl+0x29
cbf26888 91183e21 81ee8048 00010002 00000006 nt!IofCallDriver+0x43
cbf268b4 b95510f8 c1b66218 00000002 00000001 afd!WskProAPISocket+0x75
cbf269e0 821f68dc bb541030 8f9fb000 b25cbbb0 Mod__WskPost+0x10f8
cbf26bc0 82210fde 00000000 cbf26bdc b25cbbb0 nt!IopLoadDriver+0x62a
cbf26be0 81f678c5 b25cbbb0 00000000 e3436140 nt!IopLoadUnloadDriver+0x42
cbf26c30 81ef7d81 820db220 7d23f2fe 00000000 nt!ExpWorkerThread+0xd5
cbf26c70 81fa2641 81f677f0 820db220 00000000 nt!PspSystemThreadStartup+0x5b
cbf26c7c 00000000 00000000 05bffcb0 00000023 nt!KiThreadStartup+0x15

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: Mod__WskPost+1012

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Mod__WskPost

IMAGE_NAME: Mod__WskPost.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 563887a5

STACK_COMMAND: .cxr 0xffffffffcbf26110 ; kb

BUCKET_ID_FUNC_OFFSET: 1012

FAILURE_BUCKET_ID: AV_Mod__WskPost!Unknown_Function

BUCKET_ID: AV_Mod__WskPost!Unknown_Function

PRIMARY_PROBLEM_CLASS: AV_Mod__WskPost!Unknown_Function

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:av_mod__wskpost!unknown_function

FAILURE_ID_HASH: {fdbf5d26-f45c-eb9d-8f0e-b1925c89388c}

Followup: MachineOwner

1: kd> uf Mod__WskPost+1012
Mod__WskPost+0x1012:
b9551012 8908 mov dword ptr [eax],ecx
b9551014 b8160000c0 mov eax,0C0000016h
b9551019 5d pop ebp
b955101a c20c00 ret 0Ch
1: kd> .exr 0xffffffffcbf26548
ExceptionAddress: b9551012 (Mod__WskPost+0x00001012)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000001
Parameter[1]: 00000000
Attempt to write to address 00000000

fix your symbols. I assume Mod__WskPost is your code, you need to set up
symbols correctly.

Mark Roddy

On Thu, Nov 19, 2015 at 9:54 PM, wrote:

> This is what i got from WinDbg Crush Dump.
>
> kd> !analyze -v
>
> *****
>
>
> * Bugcheck Analysis
>
>
>
>
>

>
> SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
> This is a very common bugcheck. Usually the exception address pinpoints
> the driver/function that caused the problem. Always note this address
> as well as the link date of the driver/image that contains this address.
> Arguments:
> Arg1: c0000005, The exception code that was not handled
> Arg2: b9551012, The address that the exception occurred at
> Arg3: cbf26548, Exception Record Address
> Arg4: cbf26110, Context Record Address
>
> Debugging Details:
> ------------------
>
>
> SYSTEM_SKU: LENOVO_MT_80F6_BU_idea_FM_Lenovo B40-80
>
> SYSTEM_VERSION: Lenovo B40-80
>
> BIOS_DATE: 04/24/2015
>
> BASEBOARD_PRODUCT: Lenovo B40-80
>
> BASEBOARD_VERSION: No DPK
>
> BUGCHECK_P1: ffffffffc0000005
>
> BUGCHECK_P2: ffffffffb9551012
>
> BUGCHECK_P3: ffffffffcbf26548
>
> BUGCHECK_P4: ffffffffcbf26110
>
> EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced
> memory at 0x%p. The memory could not be %s.
>
> FAULTING_IP:
> Mod__WskPost+1012
> b9551012 8908 mov dword ptr [eax],ecx
>
> EXCEPTION_RECORD: cbf26548 – (.exr 0xffffffffcbf26548)
> ExceptionAddress: b9551012 (Mod__WskPost+0x00001012)
> ExceptionCode: c0000005 (Access violation)
> ExceptionFlags: 00000000
> NumberParameters: 2
> Parameter[0]: 00000001
> Parameter[1]: 00000000
> Attempt to write to address 00000000
>
> CONTEXT: cbf26110 – (.cxr 0xffffffffcbf26110)
> eax=00000000 ebx=00000000 ecx=b4de958c edx=00000000 esi=8e2dc880
> edi=8e2dc8f3
> eip=b9551012 esp=cbf2669c ebp=cbf2669c iopl=0 nv up ei pl zr na pe
> nc
> cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000
> efl=00010246
> Mod__WskPost+0x1012:
> b9551012 8908 mov dword ptr [eax],ecx
> ds:0023:00000000=???
> Resetting default scope
>
> CPU_COUNT: 4
>
> CPU_MHZ: 893
>
> CPU_VENDOR: GenuineIntel
>
> CPU_FAMILY: 6
>
> CPU_MODEL: 3d
>
> CPU_STEPPING: 4
>
> DEFAULT_BUCKET_ID: NULL_DEREFERENCE
>
> PROCESS_NAME: System
>
> CURRENT_IRQL: 0
>
> ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced
> memory at
> 0x%p. The memory could not be %s.
>
> EXCEPTION_PARAMETER1: 00000001
>
> EXCEPTION_PARAMETER2: 00000000
>
> WRITE_ADDRESS: 00000000
>
> FOLLOWUP_IP:
> Mod__WskPost+1012
> b9551012 8908 mov dword ptr [eax],ecx
>
> BUGCHECK_STR: AV
>
> ANALYSIS_VERSION: 10.0.10240.9 amd64fre
>
> LAST_CONTROL_TRANSFER: from 81ebdee2 to b9551012
>
> STACK_TEXT:
> WARNING: Stack unwind information not available. Following frames may be
> wrong.
> cbf2669c 81ebdee2 00000000 8e2dc880 00000000 Mod WskPost+0x1012
> cbf266f8 9118409a 9a70c870 8f431f40 cbf2678c nt!IopfCompleteRequest+0x1d2
> cbf26708 8ac7ceb4 8e2dc880 00000000 9a70c870
> afd!WskProTLCreateEndpointComplete+0x3a
> cbf2678c 8ac7cd2e 9a70c8b4 8e2dc880 b4de9578
> tcpip!TcpCreateEndpointWorkQueueRoutine+0x114
> cbf267e8 8ac7cafa 8e2dc880 00000002 00000000 tcpip!TcpCreateEndpoint+0x21e
> cbf26808 91182095 8e38a5d0 cbf26824 00000000
> tcpip!TcpTlProviderEndpoint+0x26
> cbf26864 9118194b cbf26888 81ebc183 8e38c268 afd!WskProIRPSocket+0x219
> cbf2686c 81ebc183 8e38c268 8e2dc880 8e2dc880
> afd!AfdWskDispatchInternalDeviceControl+0x29
> cbf26888 91183e21 81ee8048 00010002 00000006 nt!IofCallDriver+0x43
> cbf268b4 b95510f8 c1b66218 00000002 00000001 afd!WskProAPISocket+0x75
> cbf269e0 821f68dc bb541030 8f9fb000 b25cbbb0 Mod
WskPost+0x10f8
> cbf26bc0 82210fde 00000000 cbf26bdc b25cbbb0 nt!IopLoadDriver+0x62a
> cbf26be0 81f678c5 b25cbbb0 00000000 e3436140 nt!IopLoadUnloadDriver+0x42
> cbf26c30 81ef7d81 820db220 7d23f2fe 00000000 nt!ExpWorkerThread+0xd5
> cbf26c70 81fa2641 81f677f0 820db220 00000000 nt!PspSystemThreadStartup+0x5b
> cbf26c7c 00000000 00000000 05bffcb0 00000023 nt!KiThreadStartup+0x15
>
>
> SYMBOL_STACK_INDEX: 0
>
> SYMBOL_NAME: Mod WskPost+1012
>
> FOLLOWUP_NAME: MachineOwner
>
> MODULE_NAME: Mod
WskPost
>
> IMAGE_NAME: Mod WskPost.sys
>
> DEBUG_FLR_IMAGE_TIMESTAMP: 563887a5
>
> STACK_COMMAND: .cxr 0xffffffffcbf26110 ; kb
>
> BUCKET_ID_FUNC_OFFSET: 1012
>
> FAILURE_BUCKET_ID: AV_Mod
WskPost!Unknown_Function
>
> BUCKET_ID: AV_Mod WskPost!Unknown_Function
>
> PRIMARY_PROBLEM_CLASS: AV_Mod
WskPost!Unknown_Function
>
> ANALYSIS_SOURCE: KM
>
> FAILURE_ID_HASH_STRING: km:av_mod wskpost!unknown_function
>
> FAILURE_ID_HASH: {fdbf5d26-f45c-eb9d-8f0e-b1925c89388c}
>
> Followup: MachineOwner
> ---------
>
> 1: kd> uf Mod
WskPost+1012
> Mod__WskPost+0x1012:
> b9551012 8908 mov dword ptr [eax],ecx
> b9551014 b8160000c0 mov eax,0C0000016h
> b9551019 5d pop ebp
> b955101a c20c00 ret 0Ch
> 1: kd> .exr 0xffffffffcbf26548
> ExceptionAddress: b9551012 (Mod__WskPost+0x00001012)
> ExceptionCode: c0000005 (Access violation)
> ExceptionFlags: 00000000
> NumberParameters: 2
> Parameter[0]: 00000001
> Parameter[1]: 00000000
> Attempt to write to address 00000000
>
> —
> WINDBG is sponsored by OSR
>
> OSR is hiring!! Info at http://www.osr.com/careers
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>