Blue Screen of Death ( BSOD) from tcpip.sys
Hey everyone. I have this horrible problem that keeps killing my server. I get the blue screen stating tcpip.sys failed. I used the Windows Debugging tool (Windbg) and confirmed that it is indeed tcpip.sys. I tried updating (upgrading?) the drivers for many things, including my Network Card, but I have no luck. I have a Dell Poweredge 2900 server. Anyone have any suggestions? Here's the Debug file: 0: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ******************************************************************************** BAD_POOL_CALLER (c2)The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.Arguments:Arg1: 00000007, Attempt to free pool which was already freedArg2: 0000110b, (reserved)Arg3: 000f0005, Memory contents of the pool blockArg4: 8837a3e0, Address of the block of pool being deallocated Debugging Details:------------------ GetPointerFromAddress: unable to read from 8194b868Unable to read MiSystemVaType memory at 8192b420 POOL_ADDRESS: GetPointerFromAddress: unable to read from 8194b868Unable to read MiSystemVaType memory at 8192b4208837a3e0 BUGCHECK_STR: 0xc2_7 CUSTOMER_CRASH_COUNT: 6 DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP PROCESS_NAME: System CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from 81901184 to 818e09ed STACK_TEXT: 81909a04 81901184 000000c2 00000007 0000110b nt!KeBugCheckEx+0x1e81909a78 8c97c70e 8837a3e0 666d5049 00000000 nt!ExFreePoolWithTag+0x17f81909a90 8c97cde5 85ccc728 8837a3e0 81909ab0 tcpip!IppCleanupMfe+0x6281909aa0 8c97ce3e 8837a3e0 85cb4b28 81909b2c tcpip!IppDereferenceMfe+0x1c81909ab0 8c9317ad 8837a3e0 85ccc740 85ccc728 tcpip!IppRemoveMfeUnderLock+0x4d81909b2c 8c931700 85ccc728 8c99eca0 81909b94 tcpip!IppMfeSetTimeOut+0x7381909b50 8c931260 8c99eca0 8c9af760 81909c88 tcpip!IppCompartmentSetTimeout+0x9681909b60 8c931421 8c99eca0 81818a62 8c9af7a0 tcpip!IppProtocolTimeout+0xf81909b68 81818a62 8c9af7a0 00000000 d70212ac tcpip!IppTimeout+0x3c81909c88 818a095d 81909cd0 00000002 81909cd8 nt!KiTimerListExpire+0x36481909ce8 818a04a9 00000000 00000000 00041cae nt!KiTimerExpiration+0x2a081909d50 818a02cd 00000000 0000000e 00000000 nt!KiRetireDpcList+0xba81909d54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x49 STACK_COMMAND: kb FOLLOWUP_IP: tcpip!IppCleanupMfe+628c97c70e 8b4508 mov eax,dword ptr [ebp+8] SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: tcpip!IppCleanupMfe+62 FOLLOWUP_NAME: MachineOwner MODULE_NAME: tcpip IMAGE_NAME: tcpip.sys DEBUG_FLR_IMAGE_TIMESTAMP: 474531f3 FAILURE_BUCKET_ID: 0xc2_7_tcpip!IppCleanupMfe+62 BUCKET_ID: 0xc2_7_tcpip!IppCleanupMfe+62 Followup: MachineOwner--------- 0: kd> lmvm tcpipstart end module name8c8d9000 8c9c0000 tcpip (pdb symbols) DownstreamStore\tcpip.pdb\728AFC7E208A4FD68DC4583C752004EB2\tcpip.pdb Loaded symbol image file: tcpip.sys Mapped memory image file: DownstreamStore\tcpip.sys\474531F3e7000\tcpip.sys Image path: \SystemRoot\System32\drivers\tcpip.sys Image name: tcpip.sys Timestamp: Thu Nov 22 00:38:27 2007 (474531F3) CheckSum: 000DD20F ImageSize: 000E7000 File version: 6.0.6001.17051 Product version: 6.0.6001.17051 File flags: 0 (Mask 3F) File OS: 40004 NT Win32 File type: 3.6 Driver File date: 00000000.00000000 Translations: 0409.04b0 CompanyName: Microsoft Corporation ProductName: Microsoft Windows Operating System InternalName: tcpip.sys OriginalFilename: tcpip.sys ProductVersion: 6.0.6001.17051 FileVersion: 6.0.6001.17051 (longhorn_rc1.071121-2029) FileDescription: TCP/IP Driver LegalCopyright: Microsoft Corporation. All rights reserved
February 12th, 2008 3:33am

Hi, Please note for the solid troubleshooting this kind ofkenal crash issue, we need to analyze the crashed dump file. Unfortunately, debugging is beyond what we can do in the forum. Therefore, please contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request. To obtain the phone numbers for specific technology request please take a look at the web site listed below:;EN-US;OfferProPhone#faq607 I would like to suggest trying the following: 1) Last Known Good Configuration 1. Restart the computer. 2. Keep pressing F8 key until the Windows Startup menu appears. 3. Choose the Last known good configuration, and press Enter. 2) Perform a following test to check if the issue persists or not: 1. Click Start | Run and type "msconfig" (no quotes) and press enter. 2. Click services from the tab, check the check box of "Hide All Microsoft Service", and then click "Disable all" 3. Click Startup from the tab, then click "Disable all" 4. Click "OK" and follow the instructions to Restart Computer, after rebooting if you get a prompt dialog of System Configuration, please check the check box in the dialog and click "OK". If this issue still persists, please contact the hardware provider for driver update. And also, any members or MVPs in this topic who have the similar experience may be happy to share their knowledge regarding it. I hope this helps. Best wishes --------------Morgan Che Microsoft Online Community Support
Free Windows Admin Tool Kit Click here and download it now
February 18th, 2008 1:23pm

Hi, I've had the same problem since RTM. I've just left the machine running (rebooting every couple of hours).It all started after installing RRAS, however - it seems to have calmed down since unchecking IPv6 for both the Lan and Wan adapters...Hope this helps, seems to be working for me.
March 9th, 2008 4:52am

I'm having this as well, and the only thing that is working for me so far is to unplug the network adapter (its a FritzLAN WLAN USB stick) I really really need help with this, I am currently unable to access the internet via my Vista box.nm, I see this is a Windows Server forum - anyone can give me info about this error on Vista would be greatly appreciated, or at least point me the right direction. Have contacted MS support over a hotfix for this error, but I have gotten no answer. (likely weekend I guess). If I could download it I would.
Free Windows Admin Tool Kit Click here and download it now
April 6th, 2008 1:39am

My W2K8 x64 server just died because of a similar crash. Windows Error reporting says nothing. Here is the dump analysis: ******************************************************************************** ** Bugcheck Analysis ** ******************************************************************************** DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)An attempt was made to access a pageable (or completely invalid) address at aninterrupt request level (IRQL) that is too high. This is usuallycaused by drivers using improper addresses.If kernel debugger is available get stack backtrace.Arguments:Arg1: 0000000000000008, memory referencedArg2: 0000000000000002, IRQLArg3: 0000000000000001, value 0 = read operation, 1 = write operationArg4: fffffa6000e9a765, address which referenced memory Debugging Details:------------------ WRITE_ADDRESS: 0000000000000008 CURRENT_IRQL: 2 FAULTING_IP: tcpip!IppRemoveMfeUnderLock+35fffffa60`00e9a765 48894108 mov qword ptr [rcx+8],rax DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: System TRAP_FRAME: fffff80003e806f0 -- (.trap 0xfffff80003e806f0)NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=fffffa8005b825f0 rbx=fffffa8005d498a0 rcx=0000000000000000rdx=fffff80003e808f0 rsi=fffff80003e80890 rdi=fffff80003e80890rip=fffffa6000e9a765 rsp=fffff80003e80880 rbp=fffffa80042cc010r8=fffff80003e808f0 r9=fffffa80042cf010 r10=0000000000000001r11=0000000000000020 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0 nv up ei pl nz na pe cytcpip!IppRemoveMfeUnderLock+0x35:fffffa60`00e9a765 48894108 mov qword ptr [rcx+8],rax ds:00000000`00000008=????????????????Resetting default scope LAST_CONTROL_TRANSFER: from fffff8000186912e to fffff80001869390 STACK_TEXT: fffff800`03e805a8 fffff800`0186912e : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000001 : nt!KeBugCheckExfffff800`03e805b0 fffff800`0186800b : 00000000`00000001 00000000`00000000 00000000`00000600 fffffa80`05b825f0 : nt!KiBugCheckDispatch+0x6efffff800`03e806f0 fffffa60`00e9a765 : fffff800`03e80880 fffff800`03e80880 fffff800`03e80890 fffff800`03e80890 : nt!KiPageFault+0x20bfffff800`03e80880 fffffa60`00eff719 : fffffa80`042ca890 fffff800`03e80928 fffffa80`042ca890 fffff800`03e808c0 : tcpip!IppRemoveMfeUnderLock+0x35fffff800`03e808b0 fffffa60`00eff5da : fffff800`03e80ad8 00000000`00000000 fffffa80`042cc028 fffff800`03e80ad8 : tcpip!IppMfeSetTimeOut+0xc9fffff800`03e809d0 fffffa60`00eff8aa : fffffa80`04268600 fffff800`03e80ad8 00000000`00000000 fffff800`03e80cd0 : tcpip!IppCompartmentSetTimeout+0x9afffff800`03e80a40 fffff800`018718b3 : fffff800`00000001 fffff800`01988fa0 fffff800`01988cf0 00000000`00000002 : tcpip!IppTimeout+0x5afffff800`03e80a70 fffff800`018722f5 : fffff800`03e80cd0 fffffa80`0462aa02 fffff800`03e80cc8 fffffa60`00000020 : nt!KiTimerListExpire+0x333fffff800`03e80ca0 fffff800`01872a9f : 00094ad8`ec4c3e3f 00000000`00000000 00000000`00000020 fffff800`0198ba80 : nt!KiTimerExpiration+0x295fffff800`03e80d10 fffff800`01873b72 : fffff800`01988680 fffff800`01988680 00000000`00000000 fffff800`0198db80 : nt!KiRetireDpcList+0x1dffffff800`03e80d80 fffff800`01a415c0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x62fffff800`03e80db0 00000000`fffff800 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!zzz_AsmCodeRange_End+0x4fffff800`03e7a0b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00680000`00000000 : 0xfffff800fffff800`03e7a0b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00680000`00000000 00000000`00000000 : 0x0
May 21st, 2008 2:47am

Sorry to hear that. I never found a fix. I just installed the retail release of the 64 bit Version today. I'll have to see how that goes...Good luck.
Free Windows Admin Tool Kit Click here and download it now
May 21st, 2008 9:54am

My SBS 2008 SP1 (64 bit) system is suffering from similar tcpip (d1) crashes. Any progress to report? Fulco
June 29th, 2010 6:57pm

I have a 2008 R2 system and I'm expericing the same issue. Server Blue Screens with DRIVER_IRQL_NOT_LESS_OR_EQUAL, STOP ERROR 0x000000d1 TCPIP.SYS I contact IBM hardware service and we've installed the latest drivers last week. This error seems to be happening every Sunday. Only thing this server is running is Exchange 2007 SP1 and AD, nothing else.
Free Windows Admin Tool Kit Click here and download it now
October 4th, 2010 2:21pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics