Starcraft System Crash

[bdegner3210]

will the starcraft fix work for AoE?

I have almost the same problem for both starcraft and AoE II. The colors are screwed up when I launch and play the game, but anywhere from 5 minutes to 120 minutes in the screen turns lines of pink and yellow. Technically the game's still running but I can't see anything. When I try to exit the game the screen goes completely pink and then my monitor looses video connection entirely. I have to hard reset. I suspect the graphics card, but I'll try the starcraft.exe fix.

 

[KnowledgeWorker]

Solution is to be found here. (Deactivate all but one core.)

It's a bit messy, but I didn't find any other solution.

Will write to Blizzard for the rescue.

 

[KnowledgeWorker]

Ok, this surprisingly does not work for me either. *LOL* Tried core 0 and 1. Will investigate further.

 

[StevenBonnellII]

Me neither

Actually, if you read that thread all the way to the bottom, I posted like response 31 saying that it doesn't work for me, either.

 

[hax]

try updating to the latest (beta) video driver - nvidia forceware 191.03
and nforce - that seemed to at least improve things, as I haven't yet had a crash since I updated.

 

[KnowledgeWorker]

@hax: Interesting approach, yet I don't know what nforce is - or at least I thought it is only for Netbooks etc.? *edit* Installed nvidia forceware beta drivers - still crashes!

"Enable CPU throttling" doesn't help (which I first thought) too.

 

[KnowledgeWorker]

Um, I just read the one solution thread to its end and found:

... I noticed for every guy tagging along here, one thing we all have in common is the 8800GTS/GTX-series. ... You really shouldn't be running any driver past 178.xx on a G80 core like the 8800GTS/GTX sometimes it's been known to hurt the G80 and cause serious problems. Also you never notice that you're sc render in 639x479 which usually happens.

I do have + use a 8800GS with it seems to new drivers. What about you guys?!

 

[KnowledgeWorker]

Ok, I checked it out now at the laptop (should've done it before), where a mobile ATI card is at work and no problems at all! For me it looks like I've got bad luck with my "cheap graphics card" decision! -.-

 

[StevenBonnellII]

I'm using a 9600 GT.

 

[ambientmf]

Wow, lots of feedback on this thread.
Yeah, my lenovo thinkpad has a dedicated Quadro FX 570M GPU that uses the G84 core.
Since updating to the RTM version of Windows 7 however, I no longer have this issue it seems. I can't remember having the freezing issue for the last month or so of using RTM, instead of the RC.
Has anyone else had this

 

[KnowledgeWorker]

@ambienttmf: I don't think Windows 7 is the problem. But it's more of a question if the multicores are the problem (doesn't seem so, as my laptop works, also dualcore) or if it is the above mentioned NVIDIA series (which Steve Bonnell's config is up against) or whatever.

So @all: it seems, it is nothing of this, damn!

 

[zezasu]

Hey guys, first post to the seven forums and I hope I can help at least some people. I have noticed no ones posted this way.

**This will only work if you still have your serial key for starcraft/ warcraft/ keys that are not banned***

If you sign up for battle.net (yes sign up) and log in, there is a part for managing games and on there, you click add a game and you use your serial key and it will add it (at least for me) and then it will give you a digital key and a download link for windows or mac. You download and use the down loader to start running. It might take sometime but please wait. It took me 30mins. After your done downloading it to wherever you saved it, run the setup and use the digital key you got after using your cd key. I forgot where i found this and wish i could give credit, and this helped me a lot. It will screw your colors at the intro but after that it should work perfectly in all its glory of starcraft
I will try posting pictures if someone is really confused.

 

[hax]

Wow, lots of feedback on this thread.
Yeah, my lenovo thinkpad has a dedicated Quadro FX 570M GPU that uses the G84 core.
Since updating to the RTM version of Windows 7 however, I no longer have this issue it seems. I can't remember having the freezing issue for the last month or so of using RTM, instead of the RC.
Has anyone else had this

I use RTM too, still the same crashes as with the RC

however with the new nvidia drivers they have gotten fewer and I have stopped using methods like setting the affinity to one core, closing explorer etc. - since those did more harm than good.

 

[KnowledgeWorker]

Did anyone try it with the new v.191.07 drivers yet? I installed them but have other stuff to do currently.

 

[Levito]

I couldn't even get it to run properly on vista.

 

[KnowledgeWorker]

@Levito: That is because it is no OS issue, but one with either the CPU cores or the graphics card (not sure finally). What is your config (CPU, GPU)?

 

[hax]

Erm, it IS an OS / driver related issue, because I haven't had a single freeze in Vista yet? And in 7 I've had like 50 in about 3 months?

 

[KnowledgeWorker]

@hax: No, if you look at the other experiences (+ just the post before you), you see that it is a problem even in Vista / no problem even in Windows 7 ! Or how would you explain this?

 

[hax]

well, just because some people have problems in vista AND seven - where it obviously can be a hardware issue (like overheating GPU or something) doesn't mean that other people can't have an issue related directly to windows 7 - or do you think it's a coincidence that some people have the EXACT same issue just in windows 7 and NOT in vista - there are lots of blog postings and workarounds specifically for seven and not for vista, and it's exactly the same problem as there was in the RC of 7 - for some people it seems to have been resolved, for others not.

 

[donutsrgood]

it is not you

It is a Windows 7 graphics issue a friend who knows told me. There is a locking order bug in some palette animation code and Starcraft runs into it occasionally. (Remember palette animation from 10 plus years ago?). Because it is occasional it is likely a timing issue as to when you'd run into it. You could go for hours before running into it or it could happen after a few minutes. You just don't know. This is not to say there could also be driver issues for other crashes but there is definitely an OS reason too. There have been "fixes" proposed in the board but if they work, and I don't know that any work, the most they could do is to help to avoid the bug.