locked
Windows 7 Pro x64 - possible memory leak with explorere.exe RRS feed

  • Question

  • I have been having a problem with one of my sytems that is running Windows 7 Pro x64. After the system has been on for a while I start noticing problems with explorer.exe, such as: not seeing all program that are open in the taskbar, not able to open program shortcuts on the taskbar, unable to open links on the desktop, etc. When I open task manager it shows that explorer.exe is using over 450 MB of RAM. I can usually click end task for explorer.exe and then run explorer.exe from a command prompt to get back running. The system is fully patched with the latest system updates and has ESET Nod32 Antivirus running. Any suggestions?

    I have also noticed that there are times that the small logos for desktop shortcuts display incorrectly and I have to restart to fix that. They will display with a smaller logo of Adobe, or Outlook, or IE, or other programs on top of the normal icon. Not sure if that is related to the same thing.

    Thanks,
    Mike

    Thursday, November 4, 2010 8:51 PM

Answers

  • Use VMMap to view which memory is growing over the time:

    http://technet.microsoft.com/en-us/sysinternals/dd535533.aspx


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    • Marked as answer by Arthur Xie Wednesday, November 24, 2010 9:34 AM
    Thursday, November 4, 2010 10:54 PM
  • Does the issue occur in Safe Mode? If not, boot in Clean Boot Mode to troubleshoot

    How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7

    If the issue occurs in Clean Boot Mode, you may use ShellExView

    Important Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

    Run ShellExView, in the pane sort the entries with manufacturers. Disable all non-Microsoft *.dll files, and check the result. If the issue does not occur, one of the files can be the culprit. We could narrow down it one by one.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
    • Marked as answer by Arthur Xie Wednesday, November 24, 2010 9:34 AM
    Monday, November 8, 2010 9:04 AM

All replies

  • Use VMMap to view which memory is growing over the time:

    http://technet.microsoft.com/en-us/sysinternals/dd535533.aspx


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    • Marked as answer by Arthur Xie Wednesday, November 24, 2010 9:34 AM
    Thursday, November 4, 2010 10:54 PM
  • Does the issue occur in Safe Mode? If not, boot in Clean Boot Mode to troubleshoot

    How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7

    If the issue occurs in Clean Boot Mode, you may use ShellExView

    Important Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

    Run ShellExView, in the pane sort the entries with manufacturers. Disable all non-Microsoft *.dll files, and check the result. If the issue does not occur, one of the files can be the culprit. We could narrow down it one by one.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
    • Marked as answer by Arthur Xie Wednesday, November 24, 2010 9:34 AM
    Monday, November 8, 2010 9:04 AM