BSOD every time, BCCode:d1

Hi Salman.

Networx is always problematic, as in your case, too

Code:

fffff880`02fc06e8  fffff880`02cd44abUnable to load image \SystemRoot\system32\drivers\networx.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for networx.sys
*** ERROR: Module load completed but symbols could not be loaded for networx.sys
 networx+0x24ab

I would suggest you to uninstall it:

• Start Menu\Programs\NetWorx

At the same time, the Realtek RTL8168C(P)/8111C(P) Family PCI-E Gigabit Ethernet NIC (NDIS 6.20) driver is too old.

Code:

fffff880`04186000 fffff880`041b8000   Rt64win7   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
    Image name: Rt64win7.sys
    Timestamp:        Thu Feb 26 14:34:13 2009 (49A65B0D)
    CheckSum:         000361A5
    ImageSize:        00032000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update it from Realtek ; get the Win7 and WinServer 2008 R2 Auto Installation Program dated 2013/8/1.

Let us know the results. There may be some other causes of your network related BSODs ... will look at those if the problem persists after eliminating the two prima facie causes.
__________________________________________________________________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck D1, {1c, 2, 1, fffff880016fe31e}

Probably caused by : tcpip.sys ( tcpip!TcpBeginTcbSend+33e )

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

0: 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: 000000000000001c, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff880016fe31e, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f06100
GetUlongFromAddress: unable to read from fffff80002f061c0
 000000000000001c Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
tcpip!TcpBeginTcbSend+33e
fffff880`016fe31e f083401c01      lock add dword ptr [rax+1Ch],1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff88002fb2390 -- (.trap 0xfffff88002fb2390)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8006c10f30
rdx=fffffa8006c10fe8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880016fe31e rsp=fffff88002fb2520 rbp=fffff88002fb2630
 r8=fffffa8006c10f20  r9=fffffa8006c10f30 r10=fffffa8006c10e60
r11=fffff88002fb2714 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
tcpip!TcpBeginTcbSend+0x33e:
fffff880`016fe31e f083401c01      lock add dword ptr [rax+1Ch],1 ds:00000000`0000001c=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cd31e9 to fffff80002cd3c40

STACK_TEXT:  
fffff880`02fb2248 fffff800`02cd31e9 : 00000000`0000000a 00000000`0000001c 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`02fb2250 fffff800`02cd1e60 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000001 : nt!KiBugCheckDispatch+0x69
fffff880`02fb2390 fffff880`016fe31e : 00000000`00000001 fffffa80`06913010 fffffa80`06f18800 fffff880`015ca73a : nt!KiPageFault+0x260
fffff880`02fb2520 fffff880`017025c9 : ffff0000`037bd650 ffff0000`037bd640 00000000`00000014 00000000`00000001 : tcpip!TcpBeginTcbSend+0x33e
fffff880`02fb27a0 fffff880`0171e7e6 : 00000000`00000000 fffff800`02fcb401 fffff880`0180f128 fffff800`02d1f85c : tcpip!TcpTcbSend+0x1d9
fffff880`02fb2a20 fffff880`016fddc5 : fffffa80`06926200 00000000`00000000 00000000`00000000 fffff880`009e8100 : tcpip!TcpFlushDelay+0x316
fffff880`02fb2b00 fffff880`016d9eda : fffffa80`0277d490 fffffa80`000056d5 fffff880`0000350b fffff880`02fb350b : tcpip!TcpPreValidatedReceive+0x3e5
fffff880`02fb2bd0 fffff800`02fca9e3 : fffffa80`0276ccf0 00000000`00000006 00000000`00000000 fffffa80`018ba680 : tcpip!IppLoopbackTransmit+0x11a
fffff880`02fb2c80 fffff800`02cde001 : fffff800`02e74200 fffff800`02fca901 fffffa80`018ba600 fffffa80`018ba680 : nt!IopProcessWorkItem+0x23
fffff880`02fb2cb0 fffff800`02f6efee : 00000000`00000000 fffffa80`018ba680 00000000`00000080 fffffa80`01847b30 : nt!ExpWorkerThread+0x111
fffff880`02fb2d40 fffff800`02cc55e6 : fffff880`009e8180 fffffa80`018ba680 fffff880`009f2f40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02fb2d80 00000000`00000000 : fffff880`02fb3000 fffff880`02fad000 fffff880`02fb29e0 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
tcpip!TcpBeginTcbSend+33e
fffff880`016fe31e f083401c01      lock add dword ptr [rax+1Ch],1

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  tcpip!TcpBeginTcbSend+33e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: tcpip

IMAGE_NAME:  tcpip.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4e001123

FAILURE_BUCKET_ID:  X64_0xD1_tcpip!TcpBeginTcbSend+33e

BUCKET_ID:  X64_0xD1_tcpip!TcpBeginTcbSend+33e

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

You are welcome mate :)
Inform us after a week or the occurrence of the next BSOD (as per posting instructions), whichever is earlier :)

Thanks Salman :)
Let us know for any further issue :)