Originally Posted by infrared
hmm, does your computer have onboard graphics?
Heh, I'm betting you're thinking it's using it, like an "AGP Graphics Aperture Window" set in the BIOS (what normal graphics cards can access from ordinary System RAM)...
Wouldn't surprise me one bit if this is the case, especially w/ an onboard mobo integrated graphics "card" setup.
You guys are pursuing it hardware-side, I'll help him on the software-side!
Ok, here we go:
Software-side, want to take a peek @ a few things with us? Open up Taskmgr.exe (right-click on your timeclock in the lower right hand side of your screen & select it from the menu choices to activate it, or use the Start Button-> Run command & type in Taskmgr.exe & click OK)...
Once it is open? Do yourself a favor (and us for this exercise), and use its VIEW menu, & select columns option (might as well check them ALL off & use them for analysis).
You want to pay particular attention to these columns:
Tell us which processes you run are consuming the MOST memory... Particularly, the MemUsage and PeakMemUsage ones.
If it is some svchost.exe or services.exe one?
We can dig even farther into it, albeit using another tool that is a BIT more detailed called ProcessExplorer from SysInternals (freeware too, & good tool (even though its author & I have had some "minor differences" over the years, I have to admit, it IS his best piece of work & excellent))!
(That is only if we have to & it turns up being some service (those are brokered by svchost.exe/services.exe! Taskmgr.exe won't break those into their "constituent parts", like for instance/example, it will when a 16-bit app runs under NTVDM.EXE (which is the 16-bit process broker))).
However, Process Explorer, WILL.
* That all said - Get back to us with that info!
(As we may be able to ferret out exactly WHICH process is eating up all of your RAM memory this way via a software-side analysis).
There are a couple of hacks you COULD try, but imo, not worth it on AlwaysUnloadDLL though, &/or altering your diskcaching schema (from DiskCache favoring (LargeSystemCache) to favoring Programs instead) is possible here, and worth looking @ later...
Still, we have to see what is what here, first though & see what is eating up your RAM on you, first.
P.S.=> It may just be your diskcache, because "TECHNICALLY", you want much of your RAM consumed believe it or not, especially after LONG TERM USE of your system! This is the typical school of thought...
(Technically though, your RAM should be nearly ALL used for caching up to some point, depending on HOW you set your system up for use (server, vs. workstation & my 2nd-to-last paragraph's statement above about LargeSystemCache being set = 1 (server) vs. 0 (iirc, workstation caching method)))
BUT, that cache should "shrink/grow" as needed though - sometimes this is NOT the case though... apk