2016年8月25日星期四

BSOD tcpip.sys -- I've tried many recommendations to resolve this, still no luck [Solved]

BSOD tcpip.sys -- I've tried many recommendations to resolve this, still no luck

I've been getting a BSOD about once a day for the past week.  Every time it sites tcpip.sys.  I've search the internet for potential solutions and have tried such things as update my bios, update my network driver, uninstall daemon tools and install magiciso,
etc.  Unfortunately none of these have resolved the issue.  Any help?  Here are the details from windbg:
 
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation.
All rights reserved.

Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: srv*g:\cache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
Machine Name:
Kernel base = 0xfffff800`0324a000 PsLoadedModuleList = 0xfffff800`0348e670
Debug session time: Tue Feb 12 19:20:01.797 2013 (GMT-8)
System Uptime: 0 days 1:38:44.905
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, fffffa802b200000, 2, 0, fffff88001b0eb26
Probably caused by : tcpip.sys ( tcpip!TcpEnqueueTcbSack+136 )
Followup: MachineOwner
---------
3: 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: fffffa802b200000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88001b0eb26, address which referenced memory
Debugging Details:
------------------

READ_ADDRESS:  fffffa802b200000
CURRENT_IRQL:  2
FAULTING_IP:
tcpip!TcpEnqueueTcbSack+136
fffff880`01b0eb26 468b5cc80e      mov     r11d,dword ptr [rax+r9*8+0Eh]
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
TRAP_FRAME:  fffff8800e85f6d0 -- (.trap 0xfffff8800e85f6d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa801578a7b8 rbx=0000000000000000 rcx=0000000017d2fd97
rdx=000000004ea13659 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001b0eb26 rsp=fffff8800e85f860 rbp=0000000000000000
 r8=0000000002b4eb07  r9=0000000002b4eb07 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz ac po cy
tcpip!TcpEnqueueTcbSack+0x136:
fffff880`01b0eb26 468b5cc80e      mov     r11d,dword ptr [rax+r9*8+0Eh] ds:f71e:fffe=????????
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff800032bf1e9 to fffff800032bfc40
STACK_TEXT: 
fffff880`0e85f588 fffff800`032bf1e9 : 00000000`0000000a fffffa80`2b200000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0e85f590 fffff800`032bde60 : fffffa80`1596f530 00000000`00000000 00000000`00000000 fffffa80`1596f530 : nt!KiBugCheckDispatch+0x69
fffff880`0e85f6d0 fffff880`01b0eb26 : 00000000`17d2f71e 00000000`00000000 fffffa80`1584f8e0 fffff880`05896e00 : nt!KiPageFault+0x260
fffff880`0e85f860 fffff880`01a7130e : 00000000`00000010 00000000`00000010 fffffa80`1596f530 fffffa80`0ecb31a0 : tcpip!TcpEnqueueTcbSack+0x136
fffff880`0e85f9b0 fffff880`01a62b44 : fffffa80`00000006 fffffa80`15780002 fffff880`0e851dc5 fffff880`0e85bb01 : tcpip!TcpTcbCarefulDatagram+0x138e
fffff880`0e85fb60 fffff880`01a61fda : fffffa80`0ce6e490 fffff880`01a5aeb4 fffffa80`0ccf2178 00000000`00000000 : tcpip!TcpTcbReceive+0x694
fffff880`0e85fd10 fffff880`01a6357b : fffffa80`1578a7a2 fffffa80`0ce67000 00000000`00000000 fffff880`0e860000 : tcpip!TcpMatchReceive+0x1fa
fffff880`0e85fe60 fffff880`01a5b547 : fffffa80`0ce6e490 fffffa80`0cd3bb01 fffffa80`00001dc5 00000000`00001dc5 : tcpip!TcpPreValidatedReceive+0x36b
fffff880`0e85ff30 fffff880`01a5b0ba : 00000000`00000000 fffff880`01b6e9a0 fffff880`0e8600f0 fffffa80`154f4030 : tcpip!IppDeliverListToProtocol+0x97
fffff880`0e85fff0 fffff880`01a5a6b9 : fffffa80`0edf1000 fffff880`018f25c4 fffff880`0e860000 fffff880`0e8600e0 : tcpip!IppProcessDeliverList+0x5a
fffff880`0e860090 fffff880`01a5835f : fffffa80`0eb0a1a0 fffffa80`0ce67000 fffff880`01b6e9a0 00000000`0e369601 : tcpip!IppReceiveHeaderBatch+0x23a
fffff880`0e860170 fffff880`01a57952 : fffffa80`0e369b50 00000000`00000000 fffffa80`0e369601 fffff880`00000001 : tcpip!IpFlcReceivePackets+0x64f
fffff880`0e860370 fffff880`01a56dea : fffffa80`0e369620 fffff880`0e8604a0 fffffa80`0e369620 fffffa80`0e350000 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x2b2
fffff880`0e860450 fffff800`032cb968 : fffffa80`15797030 00000000`00004800 fffffa80`15754b50 00000000`00000000 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xda
fffff880`0e8604a0 fffff880`01a574b2 : fffff880`01a56d10 fffff800`032c441d 00000000`00000002 fffff880`035d7100 : nt!KeExpandKernelStackAndCalloutEx+0xd8
fffff880`0e860580 fffff880`019a50eb : fffffa80`0e36d8d0 00000000`00000000 fffffa80`0ecb31a0 fffffa80`00000000 : tcpip!FlReceiveNetBufferListChain+0xb2
fffff880`0e8605f0 fffff880`0196ead6 : fffffa80`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMIndicateNetBufferListsToOpen+0xdb
fffff880`0e860660 fffff880`019377be : fffffa80`0ecb31a0 00000000`00000002 00000000`00000000 00000000`00000000 : ndis!ndisMDispatchReceiveNetBufferLists+0x1d6
fffff880`0e860ae0 fffff880`01937ab3 : fffffa80`0ecb31a0 fffffa80`0ecb31a0 00000000`00000000 fffffa80`0ecb4300 : ndis!ndisDoPeriodicReceivesIndication+0x14e
fffff880`0e860b40 fffff880`01921b7d : 00000000`00010302 00000000`00000002 00000000`00000000 fffffa80`0ecb4388 : ndis!ndisPeriodicReceivesWorker+0x63
fffff880`0e860b70 fffff800`0356034a : 00000000`00000000 fffffa80`15754b50 00000000`00000080 00000000`00000000 : ndis!ndisReceiveWorkerThread+0x1bd
fffff880`0e860c00 fffff800`032b0946 : fffff800`0343be80 fffffa80`15754b50 fffffa80`157f8b50 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0e860c40 00000000`00000000 : fffff880`0e861000 fffff880`0e85b000 fffff880`0e8608c0 00000000`00000000 : nt!KxStartSystemThread+0x16

STACK_COMMAND:  kb
FOLLOWUP_IP:
tcpip!TcpEnqueueTcbSack+136
fffff880`01b0eb26 468b5cc80e      mov     r11d,dword ptr [rax+r9*8+0Eh]
SYMBOL_STACK_INDEX:  3
SYMBOL_NAME:  tcpip!TcpEnqueueTcbSack+136
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: tcpip
IMAGE_NAME:  tcpip.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  50e4f6f4
FAILURE_BUCKET_ID:  X64_0xD1_tcpip!TcpEnqueueTcbSack+136
BUCKET_ID:  X64_0xD1_tcpip!TcpEnqueueTcbSack+136
Followup: MachineOwner
---------
3: kd> lmvm tcpip
start             end                 module name
fffff880`01a00000 fffff880`01c00000   tcpip      (pdb symbols)          g:\cache\tcpip.pdb\F7CE8DCE5FC64F338F0A520ECDC3BC7F2\tcpip.pdb
    Loaded symbol image file: tcpip.sys
    Image path: \SystemRoot\System32\drivers\tcpip.sys
    Image name: tcpip.sys
    Timestamp:        Wed Jan 02 19:11:48 2013 (50E4F6F4)
    CheckSum:         001E19B6
    ImageSize:        00200000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Keys to the Problem BSOD tcpip.sys -- I've tried many recommendations to resolve this, still no luck

Download Error Fixer (Free)

Note: It is recommended that you back up your files and folders before attempting this step:

  • Move the mouse cursor over to the upper right side of the screen.
  • A menu will pop up on the left. Click on the "Settings" feature on the menu.
  • On the Settings window, click on the "Change PC settings."
  • Now, left click on the "Update and recovery" feature.
  • For the next step, left click on the "Recovery" feature.
  • There is an option here saying "Refresh your PC without affecting your files." There, left click on the "Get started" button.
  • Now, follow the instructions on the screen to finish the Refresh process.
  • After the Refresh process has finished restart your Windows 8.1 or Windows 8 device.
  • Check again to see if the error BSOD tcpip.sys -- I've tried many recommendations to resolve this, still no luck has been fixed.

If you do not possess the technical expertise required to accomplish this yourself or do not feel comfortable doing so, download and install a powerful automated tool to get the job done.

Another Safe way to Repair the Problem: BSOD tcpip.sys -- I've tried many recommendations to resolve this, still no luck:

How to Fix BSOD tcpip.sys -- I've tried many recommendations to resolve this, still no luck with SmartPCFixer?

1. Click the button to download SmartPCFixer . Install it on your computer.  Open it, and it will scan your system. The errors will be shown in the list.

2. After the scan is finished, you can see the errors and problems which need to be fixed.

3. The Fixing part is done, the speed of your computer will be much higher than before and the errors have been removed.


Related: How to Download Toshiba Portege R500 HDD/SSD Alert Utility v.2.2.0.0 driver,Way to Update & Download Toshiba Satellite A355-S69403 Motorola Modem Region Select Utility v.2.2.3.0 driver,Where to Download Toshiba Satellite L305-S5926 HW Setup Utility v.2.00.11 driver,[Solved] Download Toshiba Satellite L675-S7115 Laptop Checkup v.2.0.6.22 driver,Method to Download Toshiba Satellite M645-S4080 Media Controller v.1.1.88.1 driver,Best Way to Download NVidia GeForce 6100 VGA Driver v.304.51 Certified,How Can You Update & Download NVidia GeForce 9300/nForce 730i VGA Driver v.310.19 Certified,Method to Download NVidia GeForce GT 330M Driver v.340.65,How Can I Update & Download NVidia GeForce GTX 590 Driver v.280.26 WHQL,Method to Download NVidia Tesla C2050 Driver v.319.17
Read More: How to Fix Error - BSOD BCCode 19 \/ Invalid Page fault :o,How to Fix Problem - Boot & Shutdown performance monitoring not logging in Event Viewer. How to resolve??,How to Resolve - Bluetooth, Not working after upgrading to 8.1?,[Solution] Bluetooth Mouse Not Detectable,How to Fix Problem - Calculating in protected word form?,All diagnostic tools give 0x800700C1, troubleshooting wizard can't continue,all files try to open with adobe,all icons on desktop have changed to Adobe icon and won't open,All functions of my outlook are working except it will not let me "REPLY" or start a "NEW" email,all f1-f12 shortcuts not work
发帖者 时间：

没有评论:

发表评论

订阅： 博文评论 (Atom)