none
Driver in paged memory : WHCK driver memory test fail : non-paged pool which is larger than non-paged pool requirement 4096 KB RRS feed

  • Question

  • Make memory allocations
    from ExAllocatePoolWithTag(NonPagedPool) to ExAllocatePoolWithTag(PagedPool), but it is not working , not even less the number 62461.68kb.

    note: the non-page pool usagewas 16xxx KB if compile with VS2008+WDK7.0 . The KB number was increase after upgrade to VS2012+ WDK 8.0

    any idea about how to debug this issue???

    Thursday, July 25, 2013 2:37 AM

Answers

  • Hi,

    The following routines can be used to allocate pool memory. Please go through all of them to make sure you allocate paged pool memory with them.

    • ExpAllocateBigPool
    • ExAllocatePoolWithTag
    • ExAllocatePool
    • ExAllocatePoolWithTagPriority
    • ExAllocatePoolWithQuota
    • ExAllocatePoolWithQuotaTag

    Thanks,

    Liangqin

    • Marked as answer by Rebecca_Chang Tuesday, July 30, 2013 8:54 AM
    Tuesday, July 30, 2013 8:48 AM
  • I fixed the problem.

    the root cause is lame..

    Windows driver update is always change my test driver with online driver

    that is why the usage always fix at same number.

    is actually working.

    After that , the memory usage is easy with poolmon.

    the test only catch the usage while driver in casual (after initial, and not working)state.

    • Marked as answer by Rebecca_Chang Thursday, August 1, 2013 2:53 AM
    Thursday, August 1, 2013 2:53 AM

All replies

  • Hi,

    The following routines can be used to allocate pool memory. Please go through all of them to make sure you allocate paged pool memory with them.

    • ExpAllocateBigPool
    • ExAllocatePoolWithTag
    • ExAllocatePool
    • ExAllocatePoolWithTagPriority
    • ExAllocatePoolWithQuota
    • ExAllocatePoolWithQuotaTag

    Thanks,

    Liangqin

    • Marked as answer by Rebecca_Chang Tuesday, July 30, 2013 8:54 AM
    Tuesday, July 30, 2013 8:48 AM
  • I fixed the problem.

    the root cause is lame..

    Windows driver update is always change my test driver with online driver

    that is why the usage always fix at same number.

    is actually working.

    After that , the memory usage is easy with poolmon.

    the test only catch the usage while driver in casual (after initial, and not working)state.

    • Marked as answer by Rebecca_Chang Thursday, August 1, 2013 2:53 AM
    Thursday, August 1, 2013 2:53 AM