nonpaged kernel memory leak

Discussion in 'ESET NOD32 Antivirus' started by groovy88, Dec 13, 2012.

Thread Status:
Not open for further replies.
  1. groovy88

    groovy88 Registered Member

    Joined:
    Dec 13, 2012
    Posts:
    4
    When is this going to fixed? eamon.sys is allocating but not releasing nonpaged kernel memory. growing about 50 megs a day until BSOD.

    version 5.2.15.1

    on XP
     
  2. P_R_

    P_R_ Eset Staff Account

    Joined:
    Jul 25, 2012
    Posts:
    62
    Location:
    Slovakia
    Hello,

    could you please provide with full memory dump and SysInspector log?
    Please pack them and upload to safe location.
    You could send me PM with download details.

    Thank you.
     
  3. groovy88

    groovy88 Registered Member

    Joined:
    Dec 13, 2012
    Posts:
    4
    sure next time it locks up cause it uses ALL nonpaged memory I will.



    in the mean time I am running poolmon and driver verifier BOTH
    show eamon.sys never releasing memory.

    only been 48 hours since last restart and driver verifier is showing

    nonpaged bytes allocated 47607560
    nonpaged allocations 180486
    nonpaged peak bytes allocated 47607572
    nonpaged peak allocations 180488

    allocations are ALWAYS just 2 behind peak allocations
    never dropping.

    just in the time it took me to write the above it is now

    47650616
    180638
    47651808
    180640


    just grows and grows until all nonpaged is used up and system locks
     
  4. groovy88

    groovy88 Registered Member

    Joined:
    Dec 13, 2012
    Posts:
    4
    no fix came so went back to version 4. problem solved.

    Used driver verifier and i can see version 4 is releasing non paged memory
    where as version 5 and version 6 do not.
     
  5. agoretsky

    agoretsky Eset Staff Account

    Joined:
    Apr 4, 2006
    Posts:
    4,032
    Location:
    California
    Hello,

    Did you send in the full memory dump and SysInspector log that P_R_ requested?

    Regards,

    Aryeh Goretsky
     
  6. groovy88

    groovy88 Registered Member

    Joined:
    Dec 13, 2012
    Posts:
    4

    i tried but could not get a dump because this type of BSOD totally
    brings down the system to the point that no memory dump is created.

    system needs at least 16 megs nonpaged memory to make a dump file
    after BSOD but this problem uses all the nonpaged memory.

    been using version 4 for weeks and now nonpaged memory sits at 26 megs
    give or take and I can see version 4 releasing nonpaged memory unlike
    version 5 and 6, they never released.
     
  7. agoretsky

    agoretsky Eset Staff Account

    Joined:
    Apr 4, 2006
    Posts:
    4,032
    Location:
    California
    Hello,

    Have you tried manually triggering a dump when you noticed the problem occurring but before the system reached a critical level?

    Regards,

    Aryeh Goretsky
     
Thread Status:
Not open for further replies.