By pstreef
Feb 27, 2011
Post New Reply
  1. Hi,

    I've been having trouble with a recurring BSOD, i was confident i fixed it after updating network card drivers when i didnt get a new bsod for 5 days but it just happened again.

    I'm copying my dumpfile here so i dont have to hassle with uploading it:

    I've only had the bsod's when i've got VMware virtual machine running (although i have it running almost all of the time i can't be sure it has anything to do with it)

    And as the most common cause for this error is zone alarm: No i don't use it.

    If there is anything else you need to know. Please ask!

    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    Use !analyze -v to get detailed debugging information.
    BugCheck D1, {0, 2, 0, fffff8800175de01}
    Probably caused by : tcpip.sys ( tcpip! ?? ::FNODOBFM::`string'+29161 )
    Followup: MachineOwner
    3: kd> !analyze -v
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    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.
    Arg1: 0000000000000000, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff8800175de01, address which referenced memory
    Debugging Details:
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb80e8
    tcpip! ?? ::FNODOBFM::`string'+29161
    fffff880`0175de01 8b08            mov     ecx,dword ptr [rax]
    PROCESS_NAME:  vmware-vmx.exe
    TRAP_FRAME:  fffff880009aee20 -- (.trap 0xfffff880009aee20)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=fffffa80087a7108
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8800175de01 rsp=fffff880009aefb0 rbp=0000000000000014
     r8=0000000000000000  r9=0000000000000000 r10=0000000000000011
    r11=0000000000000c04 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         ov up ei pl zr na po nc
    tcpip! ?? ::FNODOBFM::`string'+0x29161:
    fffff880`0175de01 8b08            mov     ecx,dword ptr [rax] ds:bb01:00000000`00000000=????????
    Resetting default scope
    LAST_CONTROL_TRANSFER:  from fffff80002c86be9 to fffff80002c87640
    fffff880`009aecd8 fffff800`02c86be9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff880`009aece0 fffff800`02c85860 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`08796010 : nt!KiBugCheckDispatch+0x69
    fffff880`009aee20 fffff880`0175de01 : 00000000`00000000 00000000`00000014 00000000`0000001c 00000000`00000001 : nt!KiPageFault+0x260
    fffff880`009aefb0 fffff880`016ad54c : 00000000`00000001 fffffa80`078dc140 00000000`00000000 00000000`00000000 : tcpip! ?? ::FNODOBFM::`string'+0x29161
    fffff880`009af390 fffff880`016adb75 : fffff880`08618122 fffffa80`07795820 fffffa80`078dc140 fffffa80`086594c0 : tcpip!InetInspectReceiveControlMessage+0x18c
    fffff880`009af440 fffff880`016ad39f : 00000000`00000000 00000000`00000000 00000000`00000002 fffff880`014a8df3 : tcpip!UdpReceiveControlMessages+0xd5
    fffff880`009af4d0 fffff880`016ad2ee : fffff880`018199a0 fffff880`016adc81 00000000`3053a84f ffffffff`ffffffff : tcpip!UdpNlClientReceiveControlMessage+0x1f
    fffff880`009af500 fffff880`016ada19 : fffff880`01813128 00000000`00000014 00000000`00000014 fffffa80`08659a10 : tcpip!IppDeliverControlToProtocol+0x5e
    fffff880`009af540 fffff880`016ade2e : fffff880`018199a0 fffffa80`083fd140 fffffa80`078dc000 fffff880`018199a0 : tcpip!Icmpv4pHandleError+0x1d9
    fffff880`009af6b0 fffff880`0170519e : fffffa80`08716800 00000000`00000000 fffff880`018199a0 fffff880`009af920 : tcpip!Icmpv4ReceiveDatagrams+0x15e
    fffff880`009af760 fffff880`01704caa : 00000000`00000000 fffff880`018199a0 fffff880`009af920 fffffa80`08658730 : tcpip!IppDeliverListToProtocol+0xfe
    fffff880`009af820 fffff880`017042a9 : fffff880`018199a0 fffffa80`08658800 fffff880`009af8a0 fffff880`009af910 : tcpip!IppProcessDeliverList+0x5a
    fffff880`009af8c0 fffff880`01701fff : fffffa80`0786bf50 fffffa80`078dc140 fffff880`018199a0 00000000`08716801 : tcpip!IppReceiveHeaderBatch+0x23a
    fffff880`009af9a0 fffff880`017015f2 : fffffa80`0878f930 00000000`00000000 fffffa80`08716801 fffff880`00000002 : tcpip!IpFlcReceivePackets+0x64f
    fffff880`009afba0 fffff880`01700a8a : fffffa80`08716800 fffff880`009afcd0 fffffa80`08716800 fffffa80`07280000 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x2b2
    fffff880`009afc80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xda
    tcpip! ?? ::FNODOBFM::`string'+29161
    fffff880`0175de01 8b08            mov     ecx,dword ptr [rax]
    SYMBOL_NAME:  tcpip! ?? ::FNODOBFM::`string'+29161
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: tcpip
    IMAGE_NAME:  tcpip.sys
    FAILURE_BUCKET_ID:  X64_0xD1_tcpip!_??_::FNODOBFM::_string_+29161
    BUCKET_ID:  X64_0xD1_tcpip!_??_::FNODOBFM::_string_+29161
    Followup: MachineOwner
  2. pstreef

    pstreef TS Rookie Topic Starter

    some older dumpfiles can be in my next post!
  3. Route44

    Route44 TechSpot Ambassador Posts: 11,966   +70

    tcpip.sys is a Windows OS driver that deals with networking/internet connection. We see this quite often when NIC/wireless drivers are in need of an update and those occasions when either security software is in conflict or the NIC card is bad.

    From where did you update the drivers?

    Please use our Manage Attachments button the next time you post and attach the five most recent minidumps in one Zip file.
  4. pstreef

    pstreef TS Rookie Topic Starter

    These 4 is all i have atm. I recently reinstalled to try to get rid of this bsod (and install a new SSD)

    I updated my onboard realtek pcie gbe family controller network card from the microsoft update tab.

    My mainboard is also pretty new (about 1,5 month) its a MSI 870a-g54

    and while i'm at it:

    cpu: amd phenom x4 965 3.4GHz
    memory: kingston hyper 4x 2gb ddr3 1600 cl9
    video: ati sapphire 4870 x2
    ssd: OCZ vertex something (had blue screens before buying this so should not matter)
    OS: windows 7 ultimate 64 bit

    if there is anything else you need let me know

    Attached Files:

  5. Route44

    Route44 TechSpot Ambassador Posts: 11,966   +70

    tcpip.sys in all four dumps. Since you have built this system update your NIC/wireless drivers directly from MSI.

    Go to MSI's website, find your exact motherboard and update from there and not Realtek.
  6. pstreef

    pstreef TS Rookie Topic Starter

    will try this when i'm home. I'll post again if i get another blue screen.

    thx for taking the time to look at this!

Similar Topics

Add New Comment

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...