e_gfxErrorOutofMemory?!

Technical Support
Prev 1 3 4 5 6 Next
So after much troubleshooting, the only thing that worked for me was, disabling the whole comodo internet security suite, hope it helps. Have not crashed after playing the game for about 6+ hours.
FKastr0, I still crashed after a complete reformat of my computer, so nothing was installed except the Windows Vista 32-bit and Starcraft II. I think I can rule out interfering programs.

Should my next step be to buy a different video card? Should I try Nvidia instead of ATI and see if it makes a difference? I was trying not to spend any more on upgrading my system, as I think it should be able to run this game with no issues.

Yet, it doesn't. I'm still crashing and it has been almost a month since release. The odd thing is I never had this happen in the beta. For me, the beta felt like a more stable game.
I am too getting this same problem, really sad to see nobody from blue has responded to your problem as well as many of us here experiencing the same issue. I cannot begin to express the frustration this problem sends out. I have noticed alot of users here are running high performance computers and yet the game will either freeze, crash or slowly begin to slow down during gameplay..

This is a serious problem that needs to be addressed asap!

Specs:
Windows Vista Ultimate (32-Bit)
Intel Core 2 6600 @ 2.40 GHz
2302 MB Ram (Technically 4 gigs but Vista is retarded)
Dual GeForce 9600 GT SLI 512 MB DDR3

So I am running well above the requirements and I have also tried running lower settings, it actually made things worse..
Sadly, I wouldn't recommend using the words 'memory leak' people around these parts seem to take serious offense to those 2 words even though there is a good sized thread about the paged pool memory error which I am also a victim of, seems they think Blizzard is infallible of any kind of error in any way, which is a damn shame.

The ones that make me laugh the most are the ones saying it's windows' fault, REALLY? I can play crysis and xpac for hours at maxed graphics and never run out of memory or have issues, hell I can play other much more graphically and memory intensive games then SC2 for longer periods and not get crashes or sent to my desktop, yet, apparently SC2 is the needle in the haystack I guess?

I have an ATI card and my semi work around to keep the error from coming up so fast for me was to turn my ccc ai from advanced back to basic, seems to have helped a little bit but, ya not a fix of course.
Bump.
Sadly, I wouldn't recommend using the words 'memory leak' people around these parts seem to take serious offense to those 2 words even though there is a good sized thread about the paged pool memory error which I am also a victim of, seems they think Blizzard is infallible of any kind of error in any way, which is a damn shame.

The ones that make me laugh the most are the ones saying it's windows' fault, REALLY? I can play crysis and xpac for hours at maxed graphics and never run out of memory or have issues, hell I can play other much more graphically and memory intensive games then SC2 for longer periods and not get crashes or sent to my desktop, yet, apparently SC2 is the needle in the haystack I guess?

I have an ATI card and my semi work around to keep the error from coming up so fast for me was to turn my ccc ai from advanced back to basic, seems to have helped a little bit but, ya not a fix of course.


Exactly what I'm saying, any other game I play which takes a whole lot more graphics then this game, plays perfectly fine and smooth, so what gives?

I rather hear a representative come out with the truth and tell us "We have a error in our system and we are currently try to fix it" rather than all these other posts I keep seeing trying to "cover" up the problem.
Sadly, I wouldn't recommend using the words 'memory leak' people around these parts seem to take serious offense to those 2 words even though there is a good sized thread about the paged pool memory error which I am also a victim of, seems they think Blizzard is infallible of any kind of error in any way, which is a damn shame.


It's not that we think Blizz is infallible. This game has lots of bugs. The issue is what you call a memory leak and the fact that you think YOUR computer is infallible. Most of you hear a buzzword and start repeating it without knowing what it is. You ASSUME that because you are running out of virtual memory that it is a memory leak. Not one of you have ever actually monitored memory usage while playing to confirm it. you just ASSUME memory leak. You want to learn what a memory leak really is? Go read this article.


http://support.microsoft.com/kb/318263



The ones that make me laugh the most are the ones saying it's windows' fault, REALLY?


never said it was windows fault. Said it was the way some XP systems are CONFIGURED. This point has proven out more than once when people here who are smart enough to check their own systems figured out that it was their virtual memory settings. They changed the settings and no more problems

The problem lies in how paged memory is configured on your computer. It could be that you limited it too much because you heard that it would help performance, or even disabled it completely as I have seen some do. It could be that the default settings in windows are not enough for this game with the amount of memory in the system. It could be that the drive the pagefile is on is running out of room. Lots of things can be the cause, and are more likely the cause than a 'memory leak'.


I can play crysis and xpac for hours at maxed graphics and never run out of memory or have issues, hell I can play other much more graphically and memory intensive games then SC2 for longer periods and not get crashes or sent to my desktop, yet, apparently SC2 is the needle in the haystack I guess?


this statement shows that you really don't have a clue what you are talking about. What does Crysis have to do with anything? That game uses a mere 800MB of ram to control a dozen units. SC 2 uses 2GB of ram to control hundreds to over a thousand units at once. Which game is more memory intensive? SC 2 by a long shot. And your assertion that you play lots of games that are more memory intensive is hogwash. You have never played a game that is more memory intensive than SC 2 because there has never been a game yet that uses anywhere near the amount of ram this game uses.



Go read this if you want to learn about paged memory and how to help your computer perform better, and possibly fix your problem so you can play.


http://support.microsoft.com/kb/314482/en-us


It's not that we think Blizz is infallible. This game has lots of bugs. The issue is what you call a memory leak and the fact that you think YOUR computer is infallible. Most of you hear a buzzword and start repeating it without knowing what it is. You ASSUME that because you are running out of virtual memory that it is a memory leak. Not one of you have ever actually monitored memory usage while playing to confirm it. you just ASSUME memory leak. You want to learn what a memory leak really is? Go read this article.


http://support.microsoft.com/kb/318263


Memory Usage Startup Error Current

CRT malloc
Bytes 0 0 0
Peak 0 0 0

MemAlloc
Allocated 0 4 820
Overhead 0 0 0
Header+Footer 0 0 0
# Blocks 0 0 0
Committed 0 4,194,304 4,194,304
Reserved 0 4,194,304 4,194,304

Thread Stacks
Comitted 557,056 19,341,312 19,341,312
Reserved 9,338,880 29,941,760 29,941,760

Loaded Modules
Comitted + Reserved 87,932,928 114,418,652 114,418,652

Sound
Allocated 0 86,689,793 86,689,793

Resource Estimation
invalid 0 0 0
texture 0 461,316,791 461,316,791
shader pair 0 25,850,732 25,850,732
specialized shader 0 7,359,892 7,359,892
model 0 88,770,458 88,770,458
sound 0 32,754,375 32,754,375
movie 0 2,097,152 2,097,152
Total 0 618,149,400 618,149,400

Process Memory
Pagefile Usage 45,514,752 1,411,629,056 1,410,707,456
Pagefile Usage Peak 45,580,288 1,419,784,192 1,419,784,192

Working Set 16,965,632 1,372,155,904 1,375,662,080
Working Set Peak 17,014,784 1,382,457,344 1,382,457,344
Working Set Min 204,800 204,800 204,800
Working Set Max 1,413,120 1,413,120 1,413,120

Paged Pool 197,380 299,164 299,164
Paged Pool Peak 203,228 299,188 299,188

Nonpaged Pool 7,720 279,504 279,544
Nonpaged Pool Peak 7,864 279,880 279,880
Global Paged Pool 57,597,952 189,370,368 189,366,272
Global Nonpaged Pool 15,134,720 17,580,032 17,580,032

XP Paged Pool
Used 57,597,952 189,370,368 189,366,272
Free 319,889,408 188,116,992 188,121,088

VirtualQuery Pages
Committed 103,477,248 1,508,884,480 1,507,962,880
Reserved 17,997,824 537,554,944 538,480,640
Free 2,025,943,040 100,978,688 100,974,592

Max Contigous Free 760,307,712 2,818,048 2,818,048

Committed-Private 10,326,016 1,373,978,624 1,373,057,024
Committed-Mapped 5,218,304 20,484,096 20,484,096
Committed-Image 87,932,928 114,421,760 114,421,760

Reserved-Private 13,303,808 532,860,928 533,786,624
Reserved-Mapped 4,694,016 4,694,016 4,694,016
Reserved-Image 0 0 0

Main Stack Size
Peak 532,480 1,904,640 1,904,640
Limit 8,388,608 8,388,608 8,388,608

System Memory
Physical Mem Used 434,929,664 2,186,010,624 2,189,352,960
Physical Mem Free 3,053,072,384 1,301,991,424 1,298,649,088
Physical Mem Total 3,488,002,048 3,488,002,048 3,488,002,048

Page File Used 296,693,760 1,841,709,056 1,840,828,416
Page File Free 5,167,087,616 3,622,072,320 3,622,952,960
Page File Limit 5,463,781,376 5,463,781,376 5,463,781,376

Process VM Used 121,389,056 2,025,713,664 2,025,717,760
Process VM Free 2,025,963,520 121,638,912 121,634,816
Process VM Limit 2,147,352,576 2,147,352,576 2,147,352,576
bump for thursday
For anyone who wants to say that those of us with virtual memory problems probably don't know what we're doing, I called Blizzard tech support a week after this game came out. Reported my problems.

The guy said, based on specs of the PC (and all drivers being current) that I should have NO problems, even at Ultra. I patiently did everything he told me (almost all of which I had already done a few times just to be sure it wasn't my end).

It is NOT on the user end, at least not without major reconfiguration of various settings. No other programs have this problem. This is just a problem with SC2. Defend the company all you want, but the fact that numerous customers have had this problem with this specific game would indicate to me that the problem is not with any specific PC setup. If it were, how are such different rigs having the same issues?

And to those folks who make the smug little posts about how we need to learn what virtual memory is so that we don't call Blizzard out on it, perhaps you should email Blizzard those links. Their own tech support apparently couldn't fix the virtual memory issue by fiddling with virtual memory settings on my own PC.

I guess by the same standard, they are idiots as well, eh?
Wow everyone in here is pointing fingers... "It's Blizzard's fault", "it's your pc's fault"... does all of this really matter. The fact of the matter is plenty of people including myself have well above the recommended specs for this game and are experiencing this issue. Meanwhile, blizzard hasn't done a damn thing to address it. I've searched high and low on this matter and only have found a few things on private forums.

Blizzard needs to get thier heads out of their asses and atleast admit the issue is there and look into it. There is literally NOTHING adressing this issue >:(
I just got that error a little while ago today. I've been gaming for several hours, so I can see thats why it happened. But, I was on like all day sometimes and never got this error before. My memory usages on the computer and everything was all low, low temps on cpu and gcard.

AMD Athlon X3 3.1Ghz
4Gb Ram
Ati 4850 Gddr5 512mb
Windows Xp Home Sp3

I had just finished a game, everything was still fine. Then joined a new game, and when the map started it just exited out immediately. I coulda sworn I saw a blue reply to this issue before so I was looking through the forum. But apparently I was wrong, and this is what I see. Lots of people getting the short end while blizzards blues sit on their thumbs and ignore their jobs.

Why would we be directed to check the tech support forum when we get the error if, I don't know, NO ONE was actually going to respond. Instead they spend their time creating dumb polls and feeding troll bait.
Bump,
Same damn problem. Except I uninstalled Nortan and it cleared up for a bit. I can play one game and then the next game is a bit worse, by the third game (the one i just played now) I made 3 barracks as terran, got !@*#ty framerate then after a couple of minutes of frozen screen, I lost.
Ok, I actually contacted Blizzard Technical Support after receiving this same error. I'll get to that in a second. First of all, I'm running...

Windows 7 32bit
ASUS M4A89GTD-PRO/USB3
3.4MHz AMD Phenom II 965 Deneb
4GB Corsair DDR3 1333MHz
XFX ATI Radeon HD 5770 JuniperXT 1GB

...I get these same errors randomly whenever I'm playing SC2. Like I said, I've submitted error reports to Blizz and after giving them log files and actually explaining the troubleshooting steps which I've already gone through...their response was as follows:

"In that case, you may be better at describing the situation with your computer directly with our technicians over the forums. The preferred method for reporting bugs for StarCraft II is to post on the Bug Report Forum here: http://us.battle.net/sc2/en/forum/13440/. I appreciate that we have good tech guys like you whom have the knowledge to help our guys single out bugs, I honestly am not that educated when it comes down to REALLY technical things."

That was copy/paste from the email (with the exception of the underline/bold/italic...that is just for emphasis).

I mean...really? The part that amazed me the most was how a guy who is "not that educated when it comes down to REALLY technical things" can get a job as tech support when I, a CST major, can't find a job for the life of me.

I never had these crashes when the game first came out. I took a break for a few months and it seems like after downloading all the new patches, suddenly it just randomly crashes at the end of roughly 25% of the matches I play. It ONLY does it when it's loading to the score screen at the end of a match, or when the countdown timer reaches "0" before the match starts.

I've heard some people say that this is actually really common with ATI cards, as somehow the game tries to draw the score screen extremely fast and can momentarily overheat the gpu...but I've checked my temps and my gpu max never goes above 78C, which is well-below it's rated maximum temp. All of my cores stay well below 50C, so that's not the issue either. It just seems odd that I NEVER have an issue with any other game but I ALWAYS have an issue with SC2. I've tried limiting the framerate in the SC2 config, reinstalling the game, updating drivers, re-flashing BIOS, and have even tried completely re-formatting my drive.

The gameplay is perfectly fine, but the menu/loading to the menu is where these memory errors always occur. Any suggestions? The only reason I posted this here is because BLIZZARD TECHNICAL SUPPORT basically said they had no clue.
Anyone?
Also, I find it completely astonishing that this thread has been active for over 6 months and has still never gotten an actual response from a Blizzard rep.
Bump.
Just played 2 matches. After the seconds match had ended the "victory" dialog came up. I clicked "score screen" and sure enough, crash.

I think it's quite ironic that, being a tech support forum, there are threads such as this that remain unanswered by an actual Blizzard employee 6 months from the start date...yet in the past 24 hours there are 4 separate blue posts here...

http://us.battle.net/sc2/en/forum/topic/2089110470

...welcoming a new SC2 MVP on the forums. Can you say "priorities"?

While I admire someone being rewarded for doing something like helping others out in the forums, there are waaaaay more important topics at hand which remain (as stated before) unanswered and ignored. This thread has been here since RELEASE. The problem still obviously exists. It would be extremely appreciated if someone from Blizzard would at least acknowledge that this problem (which seems to be affecting a decent percentage of users and has done so for quite a while) is indeed being looked into. I'll even offer to help them test solutions to it! Seriously!
Bump for the third day in a row.
Are you still experiencing this problem?

Join the Conversation

Return to Forum