Windows 7 Memory Leak?

[rupert88]

Has anyone noticed after their computer has been on for extended periods of time that they have no memory left. Initially after booting Windows 7 memory usage is at about 37% but after 10hours or so the memory usage is up to 93% (even with no visible user programs running) and im getting the error:insufficient resources when trying to open programs.

I have 4gb of RAM.

Anybody know of any fixes for this?

 

[Dinesh]

Hi Rupert and Welcome to the forum. Well, i guess that could be due to spyware or virus infection.Could you post a screenshot of the task manager (Processes tab) so that we can get some hint. When did you 1st notice this change? Which anti virus software are you using? Did you recently download or install anything?

 

[zigzag3143]

Has anyone noticed after their computer has been on for extended periods of time that they have no memory left. Initially after booting Windows 7 memory usage is at about 37% but after 10hours or so the memory usage is up to 93% (even with no visible user programs running) and im getting the error:insufficient resources when trying to open programs.

I have 4gb of RAM.

Anybody know of any fixes for this?

Could be indexing, open tabs in browser, a memory leak, etc. could you post a task manager pic of the situation when the problem is happening?

Ken

 

[denrock]

What build are you using? The RTM? When I start up windows 7 ultimate rtm I'm usually using 24-26% of my ram according to task manager which is about 1 gig since I have 4 gigs. Right Now I have ie, firefox and chrome all open with about 30 tabs open amongst them as well as windows 7 manager, mircrosoft security essentials, macdrive and a couple of other small little aps and I'm using 1.97GB (49%) of ram and my system has been up for about 36 hours. So there's definitely something going on with your set-up. There's something eating up all that ram and holding on to it that shouldn't be. Post those screen shots that the other posters asked for and I'm sure you'll get the help you need. Is your cpu usage up also or is that okay?


This thread might be of some help (but maybe not since your problem seems extreme)

 

[TGSoldier]

Nope. None of that here. And my PC does not come off :S

 

[DataMan47]

It would be helpful if you could identify what's using the memory.

Install Process Explorer (Google/Bing it). Turn on the "Private Bytes" and "WS Private" columns. Private bytes is the amount of non-shared memory that the process has committed, and the private working set is the subset of the total private bytes that are backed by actual physical memory (stuff that's not paged out).

 

[usasma]

Open up Task Manager (right click on the Task Bar)
Click on the Processes tab
Click on the "Show processes from all users" button in the lower left
Double click on the Memory column to sort it.
Let us know the image names of the processes that are using the most Memory (don't include System Idle Process - it's supposed to be high in normal circumstances).

 

[MadMax]

well count me in too,rtm x64,about 40% of 2gb at start,about 6 hours into my last restart and now its at 70%.weird

***edit***

okay that was baseless,as it isn't happening anymoar

 

[stormy13]

Only memory leak I have experienced is when playing poker on PokerStars, and it only affects the audiodg.exe process; have seen it grow to over 2 GB. A quick end task on that process and it is back to normal, or until I open PS again.

Other than that little anomaly, no other memory leaks seen.

 

[SoLoR]

Only memory leak I have experienced is when playing poker on PokerStars, and it only affects the audiodg.exe process; have seen it grow to over 2 GB. A quick end task on that process and it is back to normal, or until I open PS again.

Other than that little anomaly, no other memory leaks seen.

x-fi ? lots of us have this issue, there is workaround avilable, if you disable "sound blaster enchantments". Other then that, whine to creative...

 

[stormy13]

x-fi ? lots of us have this issue, there is workaround avilable, if you disable "sound blaster enchantments". Other then that, whine to creative...

Yep, and the stupid thing is it doesn't happen every time I play either.

 

[usasma]

The only documented memory leak that I've seen is when running CHKDSK /R on another volume (other than C. It'll quickly suck up all the memory that you have.

 

[logicearth]

The only documented memory leak that I've seen is when running CHKDSK /R on another volume (other than C. It'll quickly suck up all the memory that you have.

That is not a memory leak, that is by design. It will not hold on to that memory either.

 

[EarlZ]

That is not a memory leak, that is by design. It will not hold on to that memory either.

Eloborate why is it by design

 

[logicearth]

Eloborate why is it by design

Engineering Windows 7 : What we do with a bug report?

...the memory usage was by design and was a specific Windows 7 change for this scenario (the /r flag grabs an exclusive lock and repairs a disk and so our assumption is you’d really like the disk to be fixed before you do more stuff on the machine...

 

[rupert88]

Thanks for your replies. I too have an X-fi sound card but also seem to have discovered a new problem , now with my Antivirus (NOD32 ESET).Computer is extremely slow after startup until i disable it.

 

[andych]

Thanks for your replies. I too have an X-fi sound card but also seem to have discovered a new problem , now with my Antivirus (NOD32 ESET).Computer is extremely slow after startup until i disable it.

Try upgrading to the latest Eset....I am running Eset Security System 4 and my PC has been on without a reboot now since my RTM install, just over a week.
Ram usage on 64 bit is constant at 27% of 6gb. that is with FF open with 6 tabs, Office 2010 (64 bit) Outlook running, WHS Console on and a couple of Gadgets.
No signs of any memory leaks at all.

 

[mmarcu]

I had same problem ( 4 gigs ) booting the system used mem. was .992 to 1.25 gigs . Just exploring folders on HD`s used mem. built up to 2.4 gigs and even more w. out running any program . Some 1 to 1.5 gigs of mem. could not be identified not in Task Manager nor in Resource Monitor or in Procexe .

I am almost sure the problem was SOLVED after DEFRAG the System disk ( c: ) with Defragler from Piriform . !!! There were some 12% of fragmented files with more then 15,000 fragments , I suspect the fragments inflated the Kernel Memory .

Would Someone check that solution to be sure that`s the problem .

Now My System is working nice for the last few days the Used Memory is going up and back down as running or closing Programs .

 

[H2SO4]

I had same problem ( 4 gigs ) booting the system used mem. was .992 to 1.25 gigs . Just exploring folders on HD`s used mem. built up to 2.4 gigs and even more w. out running any program . Some 1 to 1.5 gigs of mem. could not be identified not in Task Manager nor in Resource Monitor or in Procexe .

I am almost sure the problem was SOLVED after DEFRAG the System disk ( c: ) with Defragler from Piriform . !!! There were some 12% of fragmented files with more then 15,000 fragments , I suspect the fragments inflated the Kernel Memory .

Would Someone check that solution to be sure that`s the problem .

Now My System is working nice for the last few days the Used Memory is going up and back down as running or closing Programs .

While I'm very glad that your issue is seemingly resolved, I'd like to assure you that no amount of fragmentation will by itself cause a "memory leak". The way that individual files and their fragments are stored on disk does not directly map to their in-memory layout. Also, a "leak" is a very specific type of software defect - a bug in other words - which can only be resolved by a code-level reworking.

There are literally squillions of different possible leak causes. Just because somebody else thinks they have a "memory leak" doesn't mean it's the same issue.

 

[mmarcu]

While I'm very glad that your issue is seemingly resolved, I'd like to assure you that no amount of fragmentation will by itself cause a "memory leak". The way that individual files and their fragments are stored on disk does not directly map to their in-memory layout. Also, a "leak" is a very specific type of software defect - a bug in other words - which can only be resolved by a code-level reworking.

There are literally squillions of different possible leak causes. Just because somebody else thinks they have a "memory leak" doesn't mean it's the same issue.

Hi H2SO4 , thanks for Your attention and be careful with the ACID !!!

I am in computers from the 70th`s fairly I can say I am an expert on Hardware , Software I manage well but isn`t "My strong side" .

I`ve installed the W7 x64 on a brand new machine Gigabyte P45-UD3 , E8400 , 4g. Kingston ( 2x2) , Gigabyte ATI 4850 ( 1g.) , Wd. Green 320 g. , Wd Green 1 t. , two others 160g. HD`s .

At the begining all worked fine the used mem. was .9 to 1.25 g. after boot going up to 2 - 2.6 g. and down with opened and closed programs usually going back to 1.25 - 1.35 g.

Working with hundreds of .rar on the C: I`ve noticed the used mem. build up to 2.5 g. and stay there for hours without going down then I`ve seen that just exploring folders used mem goes up over 2 g.

1 to 1.5 g. of memory could not be identified as used by programws or services not in Task Mngr. or Procexe nor on Resource Monitor .

After the defrag on C: , about 7 days ago the machine went back to normal operation there should be a good reason for sure isn`t a Hardware problem .