BSOD tcpip.sys

tcpip.sys does not have anything to do with GPU, it is network related.

Click on the button below ....



It will download the DM log collector. Right click on the application and run as administrator. It will generate a .zip file on your desktop. Upload the .zip.
Screenshots and Files - Upload and Post in Seven Forums

Cannot you upload the zip as it is generated?

Download and install Win7 and Server 2008 R2 Auto Installation Program (the first one in the list) from Realtek . Installation instructions are in the downloaded zip.

As you have a feeling as you stated in post #3 better you uninstall Avast as a test basis. Avast is a nice antivirus but sometimes it contributes to BSODs unfortunately. Uninstall Avast using Avast Uninstall Utility. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.

Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known BSOD causer. Uninstall Daemon Tools at first. Then download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :

• Double click to open it.
• Click this button only:
• 
• If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.

Let us know the results.
_______________________________

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {ac0000000c8, 2, 1, fffff8800163c9bf}

Probably caused by : tcpip.sys ( tcpip!UdpSendMessagesOnPathCreation+17f )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000ac0000000c8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff8800163c9bf, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b9100
GetUlongFromAddress: unable to read from fffff800030b91c0
 00000ac0000000c8 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
tcpip!UdpSendMessagesOnPathCreation+17f
fffff880`0163c9bf 40883a          mov     byte ptr [rdx],dil

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  svchost.exe

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

TRAP_FRAME:  fffff88009cf9a70 -- (.trap 0xfffff88009cf9a70)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000ac000000078 rbx=0000000000000000 rcx=fffffa80085e0a90
rdx=00000ac0000000c8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800163c9bf rsp=fffff88009cf9c00 rbp=fffffa8007aec080
 r8=fffffa80085e0880  r9=0000000000000000 r10=fffffa80085e09b0
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
tcpip!UdpSendMessagesOnPathCreation+0x17f:
fffff880`0163c9bf 40883a          mov     byte ptr [rdx],dil ds:00000ac0`000000c8=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e81169 to fffff80002e81bc0

STACK_TEXT:  
fffff880`09cf9928 fffff800`02e81169 : 00000000`0000000a 00000ac0`000000c8 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`09cf9930 fffff800`02e7fde0 : fffffa80`060000ff 00000000`00000008 fffffa80`08c017f0 fffff880`09cfa520 : nt!KiBugCheckDispatch+0x69
fffff880`09cf9a70 fffff880`0163c9bf : fffff880`09cfa520 fffffa80`05df7580 fffffa80`05df7580 fffffa80`081a3ac0 : nt!KiPageFault+0x260
fffff880`09cf9c00 fffff880`0163d16e : fffffa80`05df7580 fffff880`017304b0 fffff880`09cfa540 00000000`00000000 : tcpip!UdpSendMessagesOnPathCreation+0x17f
fffff880`09cf9f80 fffff880`0163d6b5 : fffff880`09cfa4b0 00000000`00003500 00000000`00000001 00000000`00000000 : tcpip!UdpSendMessages+0x1ee
fffff880`09cfa370 fffff800`02e8d878 : fffffa80`05dd8230 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!UdpTlProviderSendMessagesCalloutRoutine+0x15
fffff880`09cfa3a0 fffff880`0163d748 : fffff880`0163d6a0 00000000`00000002 00000000`00000000 fffffa80`081a3a01 : nt!KeExpandKernelStackAndCalloutEx+0xd8
fffff880`09cfa480 fffff880`06cd6e9e : fffffa80`06071e40 fffffa80`05dd8230 00000000`00000000 fffffa80`08ab1f80 : tcpip!UdpTlProviderSendMessages+0x78
fffff880`09cfa500 fffff880`06cd6ad3 : 00000000`0000001d fffff880`09cfaca0 fffff880`09cfa7d0 00000000`0000001d : afd!AfdTLFastDgramSend+0xbe
fffff880`09cfa5a0 fffff880`06cba04c : fffffa80`05dd8230 fffff880`09cfa7d0 fffffa80`0000001d fffff880`0158ad4b : afd!AfdFastDatagramSend+0x2e3
fffff880`09cfa6a0 fffff800`0319ebd3 : 00000000`00000000 fffffa80`08867070 00000000`02a6dbe8 fffffa80`08867001 : afd!AfdFastIoDeviceControl+0x103c
fffff880`09cfaa10 fffff800`0319f6c6 : fffff880`09cfabf8 00000000`00000164 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x373
fffff880`09cfab40 fffff800`02e80e53 : fffff880`09cfaca0 fffffa80`07afb220 fffff880`09cfabf8 00000000`02a6f700 : nt!NtDeviceIoControlFile+0x56
fffff880`09cfabb0 00000000`77c4132a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`02a6db18 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77c4132a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
tcpip!UdpSendMessagesOnPathCreation+17f
fffff880`0163c9bf 40883a          mov     byte ptr [rdx],dil

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  tcpip!UdpSendMessagesOnPathCreation+17f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: tcpip

IMAGE_NAME:  tcpip.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  533f5bd4

IMAGE_VERSION:  6.1.7601.18438

FAILURE_BUCKET_ID:  X64_0xD1_tcpip!UdpSendMessagesOnPathCreation+17f

BUCKET_ID:  X64_0xD1_tcpip!UdpSendMessagesOnPathCreation+17f

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xd1_tcpip!udpsendmessagesonpathcreation+17f

FAILURE_ID_HASH:  {f4a3a832-3eb1-6b8f-ac20-e0e493d5a4e4}

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

Yes.

It is just an onboard network adapter driver.