SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: b60745c8, The address that the exception occurred at
Arg3: b97b1b04, Exception Record Address
Arg4: b97b1800, Context Record Address

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


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

FAULTING_IP:
tcpip!TcpipBufferVirtualAddress+8
b60745c8 f6400605 test byte ptr [eax+6],5

EXCEPTION_RECORD: b97b1b04 -- (.exr 0xffffffffb97b1b04)
ExceptionAddress: b60745c8 (tcpip!TcpipBufferVirtualAddress+0x00000008)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 01000006
Attempt to read from address 01000006

CONTEXT: b97b1800 -- (.cxr 0xffffffffb97b1800)
eax=01000000 ebx=0000999b ecx=11ac8720 edx=00000000 esi=01000000 edi=00000000
eip=b60745c8 esp=b97b1bcc ebp=b97b1bcc iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
tcpip!TcpipBufferVirtualAddress+0x8:
b60745c8 f6400605 test byte ptr [eax+6],5 ds:0023:01000006=??
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: System

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

READ_ADDRESS: 01000006

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from b608d68a to b60745c8

STACK_TEXT:
b97b1bcc b608d68a 01000000 00000010 88bd002b tcpip!TcpipBufferVirtualAddress+0x8
b97b1bec b608e049 00028723 88bdf584 88a69b60 tcpip!XsumSendChain+0x44
b97b1c6c b608de61 89c39008 88a69b60 88cd7940 tcpip!UDPSend+0x3ca
b97b1c90 b608dec7 007b1cb4 88cd7888 88bdf5c4 tcpip!TdiSendDatagram+0xd5
b97b1cc8 b608d713 88cd7940 88cd79d4 89a2da18 tcpip!UDPSendDatagram+0x4f
b97b1ce4 b545441e 89a2da18 88cd7940 88cd79f8 tcpip!TCPDispatchInternalDeviceControl+0xff
WARNING: Stack unwind information not available. Following frames may be wrong.
b97b1d00 b5454450 89a2da18 88cd7940 00000000 avgtdix+0x341e
b97b1d14 804eeeb1 89a2da18 88cd7940 88cd7a1c avgtdix+0x3450
b97b1dac 805ce794 00000002 00000000 00000000 nt!IopfCallDriver+0x31
b97b1ddc 805450ce b60415f8 00000002 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


FOLLOWUP_IP:
avgtdix+341e
b545441e ?? ???

SYMBOL_STACK_INDEX: 6

SYMBOL_NAME: avgtdix+341e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: avgtdix

IMAGE_NAME: avgtdix.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4845452b

STACK_COMMAND: .cxr 0xffffffffb97b1800 ; kb

FAILURE_BUCKET_ID: 0x7E_avgtdix+341e

BUCKET_ID: 0x7E_avgtdix+341e

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

BugCheck 1A, {41790, c0801096, 210, 0}

*** WARNING: Unable to verify timestamp for asusgsb.sys
*** ERROR: Module load completed but symbols could not be loaded for asusgsb.sys
Probably caused by : asusgsb.sys ( asusgsb+ab9 )

Followup: MachineOwner

BugCheck 1000008E, {c0000005, b607d698, b5381948, 0}

Unable to load image avgtdix.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for avgtdix.sys
*** ERROR: Module load completed but symbols could not be loaded for avgtdix.sys


Probably caused by : avgtdix.sys ( avgtdix+341e )

Followup: MachineOwner