Bug Check 4e (PFN_LIST_CORRUPT)...

Discussion in 'Windows Vista Drivers' started by shravangk, Sep 28, 2006.

  1. shravangk

    shravangk Guest

    I have allocated a 10K buffer NonpagedPool. I allocate an MDL by
    sending this buffer pointer.
    Now I call MmBuildMdlForNonPagedPool on the above allocated MDl.

    I build the IRP with TdiBuildReceive call and submit it to TCP.

    I get this bug check 4e (PFN_LIST_CORRUPT).

    I have added the stack dump below.

    Please help me in resolving this problem.

    Thanks
    Soni.


    kd> !analyze -v
    *******************************************************************************
    *
    *
    * Bugcheck Analysis
    *
    *
    *
    *******************************************************************************
    PFN_LIST_CORRUPT (4e)

    Typically caused by drivers passing bad memory descriptor lists (ie:
    calling
    MmUnlockPages twice with the same list, etc). If a kernel debugger is
    available get the stack trace.

    Arguments:
    Arg1: 00000007, A driver has unlocked a page more times than it locked
    it
    Arg2: 00004d33, page frame number
    Arg3: 00000001, current share count
    Arg4: 00000000, 0

    Debugging Details:
    ------------------
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
    FAULTING_MODULE: 804d7000 nt
    DEBUG_FLR_IMAGE_TIMESTAMP: 3b264b35
    DEFAULT_BUCKET_ID: DRIVER_FAULT
    BUGCHECK_STR: 0x4E
    LAST_CONTROL_TRANSFER: from 805333be to 804e3b25

    STACK_TEXT:
    WARNING: Stack unwind information not available. Following frames may
    be wrong.
    8054fe70 805333be 00000003 00004d33 81073cc8
    nt!DbgBreakPointWithStatus+0x4
    80550250 805339ae 0000004e 00000007 00004d33
    nt!KeDeregisterBugCheckReasonCallback+0x6c7
    80550270 80525136 0000004e 00000007 00004d33 nt!KeBugCheckEx+0x1b
    805502bc 804f5bf8 ffa9e968 8055034c 81970ffc nt!PoSetSystemState+0xcb7b
    805502e4 8066a9c9 81970f68 8128b860 00000000 nt!MmUnlockPages+0x11e
    80550350 fa9fe81c 805503c0 ffaa25d8 805503c0
    nt!RtlCompressBuffer+0x2816
    80550368 faa15665 81970f68 00000000 0000000c tcpip!IPTransmit+0x1bd9
    80550388 fa9fe36a 805503c0 ffb87130 fab594ce
    tcpip!IPRegisterProtocol+0x2c3e
    80550404 fa9fbef9 81147498 4f02a8c0 6302a8c0 tcpip!IPTransmit+0x1727
    80550464 fa9fbb19 00000020 81217008 fa9fe076 tcpip!IPFreeBuff+0x638
    805504e0 fa9fb836 faa3b210 81217008 fab594ce tcpip!IPFreeBuff+0x258
    80550598 fa9fa922 81147498 fab594e2 0000001a tcpip+0x1836
    805505d8 fa9fa84d 00000000 811edcd8 fab594c0 tcpip+0x922
    80550614 baf95f45 ffb81260 00000000 bad9cb40 tcpip+0x84d
    80550668 bad9701d 0023f008 8124c9b0 00000001
    NDIS!FddiFilterDprIndicateReceive+0xd4d
    8055067c bad971b4 811af9f8 8124c9b0 00000001
    psched!RegisterPsComponent+0x6cef
    805506a0 bad975f9 811b9578 00000000 811af9f8
    psched!RegisterPsComponent+0x6e86
    805506b8 baf95d40 811b9570 812146b8 81214178
    psched!RegisterPsComponent+0x72cb
    80550708 bae0929f 0023f008 80550728 00000001
    NDIS!FddiFilterDprIndicateReceive+0xb48
    8055086c bae09461 00214178 00000000 ffbac130 e100b325+0x729f
    80550894 baf8bf09 81214178 80559580 80559320 e100b325+0x7461
    805508ac 804dc179 81214530 8121451c 00000000
    NDIS!NdisCompletePnPEvent+0x17b
    ffdff980 812f00a8 faf78000 00006667 00000001
    nt!KiDispatchInterrupt+0x376
    ffdff984 faf78000 00006667 00000001 805508c4 0x812f00a8
    ffdff988 00000000 00000001 805508c4 00000001 0xfaf78000

    STACK_COMMAND: kb

    FOLLOWUP_IP:
    e100b325+729f
    bae0929f 57 push edi
    FAULTING_SOURCE_CODE:
    SYMBOL_STACK_INDEX: 13
    FOLLOWUP_NAME: MachineOwner
    SYMBOL_NAME: e100b325+729f
    MODULE_NAME: e100b325
    IMAGE_NAME: e100b325.sys
    BUCKET_ID: WRONG_SYMBOLS
    Followup: MachineOwner
    ---------
     
    shravangk, Sep 28, 2006
    #1
    1. Advertisements

  2. shravangk

    Mark Roddy Guest

    On 28 Sep 2006 05:56:24 -0700, wrote:


    A wise man recently told you the following:

    "The problem appears to be a defective programmer - one who is unable
    to even set up the debugger properly. Did you notice the line:

    "***** Kernel symbols are WRONG. Please fix symbols to do analysis."

    Were you thinking that failing to heed the advice of the debugger and
    posting your message would bring you anything useful?

    Heck, I'm guessing you can find THIS response just by searching the
    archive - let's see... yup, try '"Kernel symbols are WRONG"
    site:eek:sronline.com' into Google and amazingly enough you will find a
    surprisingly large number of messages on this very topic.

    My suggestion would be to replace the defective programmer and see if
    that fixes the problem. :p"

    Did you think that perhaps this newsgroup and the ntdev email list are
    not read and monitored by the same people?

    Fix your symbols.


    =====================
    Mark Roddy DDK MVP
    Windows Vista/2003/XP/2000 Consulting
    Device and Filesystem Drivers
    Hollis Technology Solutions 603-321-1032
    www.hollistech.com
     
    Mark Roddy, Sep 28, 2006
    #2
    1. Advertisements

  3. shravangk

    shravangk Guest

    Mark, I have posted my question first in this group. Then I posted it
    in NTDEV.
     
    shravangk, Sep 29, 2006
    #3
  4. shravangk

    shravangk Guest

    Mark, I have posted my question first in this group. Then I posted it
    in NTDEV.
     
    shravangk, Sep 29, 2006
    #4
  5. shravangk

    shravangk Guest

    Mark, I have posted my question first in this group. Then I posted it
    in NTDEV.

    I have corrected the symbols and resolved the issue. Thanks.
     
    shravangk, Sep 29, 2006
    #5
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.