tcpip.sys BSOD , how do i fix this?

[Tank997]

This BSOD caused by driver "tcpip.sys" happened to me today in the middle of a BF3 game. Anyone know what caused this and how i can fix it?

 

[Tank997]

just had another one, please can anyone give me some info?

 

[writhziden]

http://www.sevenforums.com/general-...ows-7-64bit-boot-loops-waking-sleep-mode.html
http://www.sevenforums.com/crashes-debugging/221199-2-bsods-today-please-help-2.html

Why do you keep starting new threads?

Your current crash is network related based on your analysis (ours says differently) and possibly related to the sleep issue gregrocker tried to help you with.

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\Tank997\Tank997\033112-20966-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02e52000 PsLoadedModuleList = 0xfffff800`03096650
Debug session time: Sat Mar 31 16:27:29.717 2012 (UTC - 6:00)
System Uptime: 0 days 6:28:00.576
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {3452, 574e000, fffff7000109c988, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+356b3 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000003452, The subtype of the bugcheck.
Arg2: 000000000574e000
Arg3: fffff7000109c988
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_3452

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  bf3.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002f3d6f3 to fffff80002eced40

STACK_TEXT:  
fffff880`0c326ee8 fffff800`02f3d6f3 : 00000000`0000001a 00000000`00003452 00000000`0574e000 fffff700`0109c988 : nt!KeBugCheckEx
fffff880`0c326ef0 fffff800`02e9f942 : fffffa80`17f67b30 fffffa80`00000006 fffff880`00002687 fffff800`00000009 : nt! ?? ::FNODOBFM::`string'+0x356b3
fffff880`0c3277a0 fffff800`031a381a : fffff8a0`03538060 fffff880`0c327ae0 00000000`00000000 fffffa80`185dc060 : nt!MmCleanProcessAddressSpace+0x96
fffff880`0c3277f0 fffff800`03186cfd : 00000000`000000ff 00000000`00000001 00000000`e4bc4000 fffffa80`186c2b60 : nt!PspExitThread+0x56a
fffff880`0c3278f0 fffff800`02ec17da : 00000000`00000100 fffffa80`185dc120 00000000`00000001 fffff800`02ec48cd : nt!PsExitSpecialApc+0x1d
fffff880`0c327920 fffff800`02ec1b20 : 00000000`00000246 fffff880`0c3279a0 fffff800`03186c68 00000000`00000001 : nt!KiDeliverApc+0x2ca
fffff880`0c3279a0 fffff800`02ece077 : fffffa80`185dc060 00000000`0000040c 00000000`00000000 fffffa80`183c04f0 : nt!KiInitiateUserApc+0x70
fffff880`0c327ae0 00000000`73492e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`0603f0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73492e09


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+356b3
fffff800`02f3d6f3 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+356b3

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ec79dd2

FAILURE_BUCKET_ID:  X64_0x1a_3452_nt!_??_::FNODOBFM::_string_+356b3

BUCKET_ID:  X64_0x1a_3452_nt!_??_::FNODOBFM::_string_+356b3

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

Crash points to Memory problems... Drivers...

• If you are overclocking any hardware, please stop.
  
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  If you swap any memory components, follow these steps for ESD safety:
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
  Once these steps have been followed, it is safe to remove and replace components within your computer.
  
  
• An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
  
  a. Backup your system and user files
  b. Create a system restore point
  c. If you do not have a Windows 7 DVD, Create a system repair disc
  d. In Windows 7:

  • Click the Start Menu
  • Type verifier in Search programs and files (do not hit enter)
  • Right click verifier and click Run as administrator
  • Put a tick in Create custom settings (for code developers) and click next
  • Put a tick in Select individual settings from a full list and click next
  • Set up the individual settings as in the image and click next
    View attachment 205247
  • Put a tick in Select driver names from a list
  • Put a tick next to all non-Microsoft drivers.
  • Click Finish.
  • Restart your computer.

  
  If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using http://www.sevenforums.com/tutorials/700-system-restore.html OPTION TWO.
  
  Thanks to zigzag3143 for contributing to the Verifier steps.
  If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.​
  The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.

 

[Tank997]

i keep starting new threads because they are different BSOD errors

 

[writhziden]

Where did you see the tcpip.sys being blamed? My analysis shows this is similar to your previous crashes; see my previous post as it has been updated.

 

[Tank997]

Where did you see the tcpip.sys being blamed? My analysis shows this is similar to your previous crashes; see my previous post as it has been updated.

bluescreen viewer said the driver that caused it was tcpip.sys then it gave a driver address of tcpip.sys with numbers and letters next to it. But on my "Who crashed" program it says its ntknlmp.exe, so i dont know what happened there

 

[writhziden]

bluescreen viewer and who crashed often give erroneous information. WinDbg is a more reliable method to analyze blue screen crashes.