i have 8gb of ram in a windows vista ultimate system (i realize overkill but it's so cheap right now and i run alot of audio programs simultaneously so i figured why not). Regardless often times my memory says it's running at over 50% which seems strange because my laptop runs the same programs on a 32bit vista system and is only using about 35% and it only has 2gb of ram. Regardless yesterday i got a message that said i couldn't load a program because i was out of memory on the 64bit system and i wasn't running anything other than normal. All 8gb are showing up on the pc info page. Can anyone help me figure out what's going on.

It is a intel quad core 2.4ghz system. oh also my memory rating on that new windows experience index page is 5.5 which is my lowest score which i would think would probably be my highest score. anyway just thought i'd add that info.

please help me... i need this thing to crush or it puts a severe damper on my livelihood.

thanks

Dani AI

Generated

A compact troubleshooting checklist and targeted steps to chase down persistent memory/“out of memory” symptoms on a Windows system. The usual root causes to test for are: exhaustion of the commit limit (RAM + pagefile), a leaking driver that eats kernel (nonpaged) pool, an application with a runaway private working set, or failing RAM. The steps below focus on measurable checks you can run immediately and how to follow up.

Start by measuring, not guessing. Use resmon.exe or Process Explorer to see per-process Private Bytes, Working Set and overall Commit (System Information in Process Explorer). Capture a short PerfMon log with these counters: Memory\Committed Bytes, Memory\Commit Limit, Memory\Pool Nonpaged Bytes, Memory\Pool Paged Bytes and Process(*)\Private Bytes to watch trends over 5–10 minutes. If Commit approaches Commit Limit, add pagefile or let Windows manage it; if nonpaged pool steadily grows, you likely have a driver leak.

Tools and targeted actions:

  • Use Process Explorer (download) to sort by Private Bytes and inspect handles/threads for suspect processes. (Process Explorer)
  • If kernel pool is growing, run PoolMon to find the leaking tag and then correlate to drivers; update or remove the offending driver. ()
  • Check startup with Autoruns and run an up-to-date malware scan if anything looks unknown. (Autoruns)
  • Run a memory test (MemTest86 or the Windows Memory Diagnostic) to rule out bad DIMMs and update BIOS/chipset/audio drivers (audio drivers often interact heavily with audio apps).

Short-term relief: increase or move the pagefile to a fast drive, or set a fixed initial+maximum size to avoid fragmentation. Long-term: identify the leaking process/driver from the PerfMon log or PoolMon output, collect a process dump if an app crashes (ProcDump), and provide those logs if asking for more help. As suggested, checking running processes and startup items is a good first step—use the tools above to make that check definitive.

hello dear i think you have some serious problem ragarding memory, first of all i would like to suggest clean ur pc later is ur system detect 8 gb ram or less?
if it detects then i think u have problems with overcloacking. have u done this?
if yes restore the system.
and if not then check out the proccesses in taskmanager, how much memory the all proccess ate up?
i think there u find some unuseful(virus) proccess named as ex:- svghost.exe(ewhich is 11 in number) or csrss.exe(which is 2 in number) etc..
you should also check out Ur FSB which should transfer data at fast rate.
if this all fails just format ur pc; and if u don't like to format just messege me i will see you later.
sorry for late thanks.....

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.