|
Artosis
United States2135 Posts
I get paged pool memory error all the time. constantly. its completely unplayable, i can't stream well with it, its destroying my practice time on SC2 as well as my records and overall practice.
About my comp: its really good. 4 gigs of memory. its not overheating, i checked into that. I put all the settings on lowest, except textures is on ultra i think. not sure why lol.
Things I've tried:
R1CH's fix. I upped my paged pool to the middle size he put in that. It wouldn't take the big one. No help.
this thing: Megabytes Hexadecimal Decimal 192Mb 0c000000 201326592 256Mb 10000000 268435456 384Mb 18000000 402653184
didn't help. tried it alone, with r1ch's fix, and r1ch's fix without it. no help at all.
putting "pagedPoolLimitEnforced=1" into the Variables.txt file in the beta folder. no help at all.
The only other possibility i came across is this, found on a blizzard board:
"Originally posted by Ragnasaur [Blizzard Poster] Your machine sounds like it should be able to handle Ultra settings, however it might be possible you're using too much memory. We have a way to limit the amount of memory consumed by SC2's assets, and I'd be curious to see if lowering this value would result in better performance for you. To enable this workaround, please create or edit your variables.txt file located in My Documents/Starcraft II Beta directory, and add the line:
texspace=512
Setting this value too low will make things far worse as we will end up paging out assets artificially."
I'm scared to try this. I want my SC2 running perfectly.
PLEASE SOMEONE HELP ME.
|
Can you post your system specs / OS as well as any extra hardware which requires drivers, and a list of any security / firewall / antivirus / etc style software you have running. Also what is your paged pool usage at before running SC2?
|
|
Artosis
United States2135 Posts
how do i find out all that stuff?
|
Is this a newer machine? It's possible that a stick of your RAM has gone bad. You might want to try and run memtest and see if it complains about something. Are you running a lot of background programs while playing? You could also potentially have a virus or trojan that's sucking up RAM, causing you to crash.
|
Artosis
United States2135 Posts
i've reinstalled, its a pretty new comp, i just bought new memory and had it tested. i dont run anything in the background and it still happens
|
On May 19 2010 12:38 Artosis wrote: how do i find out all that stuff?
You could just copy/paste the blizzard diagnostic when you opt in for the beta, shows the crucial hardware.
Alternatively, start -> run -> dxdiag, or device manager for specifics and drivers
|
I'm not sure what your problem is, but I do know where you can get an answer:
http://superuser.com/
It may feel odd to have to go somewhere else for the answer, but I can guarantee if anyone can answer it these guys can.
You can even sign up for an account with a google/yahoo/openid to make life easy or post anonymously.
Try to be as clear as possible when you explain your problem and what you've tried to do to solve it.
|
|
Hi, this happened to me, I tried reinstalling SC and that didn't work, then I upgraded to Windows7 and installed the game again from scratch, haven't had the problem since.
What version of windows are you running? you might want to try upgrading to 7 if you're running XP or vista.
|
Artosis, try removing one ram out of the computer and see if it gets fixed. It has helped other people that has experienced the same problem as you. And don't ask why it works I have no clue, it just does.
|
to me it also sounds like broken ram.
Trywhat the poster above said, or at least run the diagnostic tool "memtest.exe" i havent had that problem, but similar problems what were also caused by bad ram
|
I'm addressing this because it doesn't seem that any solution was actually reached, but I found a solution.
What I've found is that XP, Vista, and 7 each comes with different default settings for paged pool memory, so changing operating systems is a solution, but isn't the only solution.
I found that my XPsp3 had a restriction put on paged pool limit in the registry by default. I was able to set it to unrestricted by changing the value listed for "paged pool limit" in the registry from "0x10000000" to "0xffffffff". I know it may seem odd to replace numbers with letters, but my understanding (which is still incomplete) is that "ffffffff" is hexidecimal speak for "unrestricted".
At any rate, it worked. My paged pool limit (which is viewable with Process Explorer) jumped from 160MB (rendering SC2 basically unplayable) to 358MB. At 358MB, It runs smoothly at medium settings on my dual core Turion/2GB ram laptop.
|
I would also try removing one stick at a time. If that doesn't work and you feel like you've exhausted all obvious posibilities like upgrading your drivers, bios and so on, I'd format the hole thing at put Windows 7 on it
|
0xffffffff is the largest unsigned 32 bit integer. Windows has a maximum percentage of ram that it will reserve for pool mem and you set the setting higher than the max, so it used the other value instead.
Note that the amount of pool memory needed is different depending on your hardware and drivers. I've never seen more than about 140MB allocated from the paged pool. (Win7, 4gb ram)
|
|
|
|