none
BSOD TcpSegmentTcbSend in tcpip.sys

    Question

  • I got a BSOD while sending large data using Transmit Packet MSDN API. Any idea what could be the issue?

    16.0: kd:x86> !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: 0000000000000000, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff88008ad85bb, address which referenced memory

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


    READ_ADDRESS:  0000000000000000 

    CURRENT_IRQL:  2

    FAULTING_IP: 
    tcpip!TcpSegmentTcbSend+17b
    fffff880`08ad85bb 49              dec     ecx

    DEFAULT_BUCKET_ID:  VISTA_RC

    BUGCHECK_STR:  0xD1

    LAST_CONTROL_TRANSFER:  from 0000000000000000 to 0000000000000000

    STACK_TEXT:  
    00000000 00000000 00000000 00000000 00000000 0x0


    STACK_COMMAND:  .bugcheck ; kb

    FOLLOWUP_IP: 
    tcpip!TcpSegmentTcbSend+17b
    fffff880`08ad85bb 49              dec     ecx

    FOLLOWUP_NAME:  MachineOwner

    IMAGE_NAME:  Unknown_Image

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

    SYMBOL_NAME:  tcpip!TcpSegmentTcbSend+17b

    BUCKET_ID:  INVALID_KERNEL_CONTEXT

    MODULE_NAME: Unknown_Module

    Followup: MachineOwner

    Friday, July 19, 2013 5:48 PM

All replies

  • Your !analyze does not contain enough call stack data, and no OS version. maybe you do not have correct symbols. Try to send your dump here and post the decode *in a suitable forum*. This is not a right forum for your issue.

    --pa

    Sunday, July 21, 2013 11:33 AM