Jump to content

elpamyelhsa

Members
  • Posts

    3
  • Joined

  • Last visited

Posts posted by elpamyelhsa

  1. 13 hours ago, Peter Randziak said:

    Hello guys,

    can you please share the output from the Poolmon utility for us to check? 

    Regards, P.R.

    Here is a full dump during this issue.

    https://elpamsoft-my.sharepoint.com/personal/ashley_elpamsoft_com/_layouts/15/guestaccess.aspx?docid=066895d4cc1d045d1af77d429b4c78a75&authkey=AfKbO9rYKljUhOGhmx8Nu7M

    I will wait for the next PC to come in with this error to provide Poolmon info.

  2. 12 hours ago, Marcos said:

    In safe mode or with Self-defense disabled, import the attached reg file to enable heap tracing for ekrn. Then restart the computer. Make sure that Full dumps are enabled in the advanced setup -> Tools -> Diagnostics.

    When you notice a high memory use by ekrn, generate a dump via advanced setup -> Tools -> Diagnostics -> Create (dump).
    When done, collect logs with ELC, upload the zip file to a safe location and pm me a download link. Finally you can disable heap tracing by importing the appropriate reg file.

    ekrn_heap_tracing.rar

    I have had a 3rd PC do this now and captured a memory dump as previously requested. Unfortunately it is 8GB in size but i can share it still if you like. Removing v10, Installing v9 and upgrading to v10 seems to resolve the issue. Previously on another faulting machine, removing v10 and reinstalling v10 would not fix the issue.

    To do the 'dump' you have requested here i will have to wait for the next machine exhibiting this bug. Working in IT this shouldn't be an issue.

  3. Had this on two PCs this week

    NonPaged Pool data is maxing out RAM until Windows becomes unstable

    No process is claiming the RAM in Microsoft Process Explorer

    Microsoft Tool RAMMan shows NonPaged Pool 90% of RAM usage (2.9GB on both machines with 4GB RAM)

    Microsoft tool Poolmem.exe shows the driver issue

    ESET 10.1.219.0 on Windows 7 Pro one machine 32bit and one x64

    On 8/2/2017 at 2:35 AM, itman said:

    This should resolve who "is the culprit" in regards to in regards to memory usage. Download Process Explorer from here: https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer . It's a portable app and will run from anywhere. Run it as Admin.. Click on "View." Then click on "Select Columns." Click on the "Process Memory" tab. Select the following:

    • Private Bytes
    • Peak Private Bytes
    • Working Set Size
    • Peak Working Set Size

    You can keep Process Explorer running or open it up periodically to examine the above "Peak" columns. This should point you to whom the offending processes is. For example on my PC for ekrn.exe, peak private bytes is 244 MB and peak working set size is 352 MB with current private bytes of 45 MB and working set size of 146 MB.

     

×
×
  • Create New...