1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Windows Vista Need help on diagnosing this bsod dump

Discussion in 'Legacy Windows' started by GSS12, 2008/12/21.

  1. 2008/12/21
    GSS12

    GSS12 Inactive Thread Starter

    Joined:
    2008/12/21
    Messages:
    7
    Likes Received:
    0
    Hi,

    I have been getting random BSODs recently. I know this because I saw it as I returned to my PC one day but before I could read the error message, the BSOD went away and the PC did its rebooting thing.

    I have MS Debugging Tools as I am a .NET developer, so I analysed the dump:

    Probably caused by: ntkrpamp.exe ( nt!IoGetAttachedDevice+c)

    Module name: NT

    DEFAULT_BUCKET_ID: Vista Driver Fault

    Is there a way for me to copy the entire analysis from Debugging Tools?

    Anyway, any ideas what the cause is?

    Thanks
     
  2. 2008/12/22
    mattman

    mattman Inactive Alumni

    Joined:
    2002/06/10
    Messages:
    8,198
    Likes Received:
    63
    In the dump readout, highlight the text and press Ctrl + C, you should then be able to open Notepad and paste it there, or into your reply here.
     

  3. to hide this advert.

  4. 2008/12/22
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    Follow these instructions to post a Dump Data Log.


    Please note:
     
    Arie,
    #3
  5. 2008/12/22
    GSS12

    GSS12 Inactive Thread Starter

    Joined:
    2008/12/21
    Messages:
    7
    Likes Received:
    0
    Hi,

    Here is the dump:

    READ_ADDRESS: GetPointerFromAddress: unable to read from 825315ac
    Unable to read MiSystemVaType memory at 825117e0
    00000000

    CURRENT_IRQL: 2

    FAULTING_IP:
    tcpip!IppGetInterfaceScopeZone+1f
    9518c534 8b00 mov eax,dword ptr [eax]

    CUSTOMER_CRASH_COUNT: 2

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0xD1

    PROCESS_NAME: vsmon.exe

    TRAP_FRAME: a3662830 -- (.trap 0xffffffffa3662830)
    ErrCode = 00000000
    eax=00000000 ebx=87fdd9c0 ecx=000000f0 edx=000000c0 esi=85fe3300 edi=00000000
    eip=9518c534 esp=a36628a4 ebp=a36628a4 iopl=0 nv up ei pl zr na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
    tcpip!IppGetInterfaceScopeZone+0x1f:
    9518c534 8b00 mov eax,dword ptr [eax] ds:0023:00000000=????????
    Resetting default scope

    LAST_CONTROL_TRANSFER: from 9518c534 to 8248fdc4

    STACK_TEXT:
    a3662830 9518c534 badb0d00 000000c0 951e29c8 nt!KiTrap0E+0x2ac
    a36628a4 9517dc93 85fe3300 0000000e 85fe3348 tcpip!IppGetInterfaceScopeZone+0x1f
    a36628c0 9517e02a 87fdd9c0 a3662a24 e0000001 tcpip!IppRouteToDestination+0x56
    a3662908 95197000 951e29c8 85fe3300 951e29c8 tcpip!IppJoinPath+0x9c
    a3662a64 951c032f 00000000 00000007 951e29c8 tcpip!IppSendDatagramsCommon+0x26c
    a3662afc 94a11e9d 00000000 00000007 88b7b620 tcpip!IppInspectInjectTlSend+0xd7
    a3662b58 953ccb78 88844798 00000000 0000088c fwpkclnt!FwpsInjectTransportSendAsync0+0x220
    WARNING: Stack unwind information not available. Following frames may be wrong.
    a3662ba8 953c9ba6 8823a678 8571d980 8571d984 vsdatant+0x29b78
    a3662bbc 953cffa0 04bfed10 00000001 8571d980 vsdatant+0x26ba6
    a3662be0 953d036a 887b7c98 00000001 04bfed10 vsdatant+0x2cfa0
    a3662c18 953cf235 88139948 8571d968 88139948 vsdatant+0x2d36a
    a3662c2c 82427f9b 88139948 8571d968 8571d968 vsdatant+0x2c235
    a3662c44 82588f55 887b7c98 8571d968 8571d9d8 nt!IofCallDriver+0x63
    a3662c64 82589f15 88139948 887b7c98 04bfed00 nt!IopSynchronousServiceTail+0x1e0
    a3662d00 8258ee7d 88139948 8571d968 00000000 nt!IopXxxControlFile+0x6b7
    a3662d34 8248caea 000003c0 00000000 00000000 nt!NtDeviceIoControlFile+0x2a
    a3662d34 773a0f34 000003c0 00000000 00000000 nt!KiFastCallEntry+0x12a
    04bfeca4 00000000 00000000 00000000 00000000 0x773a0f34


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    fwpkclnt!FwpsInjectTransportSendAsync0+220
    94a11e9d ff75f4 push dword ptr [ebp-0Ch]

    SYMBOL_STACK_INDEX: 6

    SYMBOL_NAME: fwpkclnt!FwpsInjectTransportSendAsync0+220

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: fwpkclnt

    IMAGE_NAME: fwpkclnt.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 4549b2f6

    FAILURE_BUCKET_ID: 0xD1_fwpkclnt!FwpsInjectTransportSendAsync0+220

    BUCKET_ID: 0xD1_fwpkclnt!FwpsInjectTransportSendAsync0+220

    Followup: MachineOwner
     
  6. 2008/12/23
    mattman

    mattman Inactive Alumni

    Joined:
    2002/06/10
    Messages:
    8,198
    Likes Received:
    63
    There is no mention of ntkrpamp.exe being involved in that last dump. Check it's date or is it a new one?

    Vsmon is a ZoneAlarm file. fwpkclnt.sys appears to be an internet "driver" and may be related to encrtypting information across the internet.

    That's a little information for you. You will need to check the dumps for if they are new or old and if those same (or related) files keep appearing.

    This appears to be that same dump/BSOD at the ZA forum:
    http://forums.zonelabs.com/zonelabs/board/message?board.id=gen&message.id=48384

    Matt
     

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.