War3 Critical Error

[XsexecutionerX]

Has anyone else been getting critical errors while playing Warcraft. So far I've gotten about 4 of them all when play DOTA 5.67.

 

[IceDevil9]

Nope, but I've heard of them.

-Frank

 

[GodHatesYou1701]

Critical Errors have been occuring since Warcraft 3 came out...No one has found a way to stop them...

 

[XsexecutionerX]

I started getting them once I switched to Xp SP2, before that I just had win 2000 and never got any.

 

[ChrisH36]

Has anyone else been getting critical errors while playing Warcraft. So far I've gotten about 4 of them all when play DOTA 5.67.

what that error that causes the game to freeze, screen to go black, then causes a STOP 0x8E thing! Well, I guess THAT is caused by a trigger that doesn't work properly or something. Aren't a majority of the models in DOTA palette swapped?

 

[Ntrik_]

what that error that causes the game to freeze, screen to go black, then causes a STOP 0x8E thing! Well, I guess THAT is caused by a trigger that doesn't work properly or something. Aren't a majority of the models in DOTA palette swapped?

That happened to me when I got new GFX card, so Ill assume its all about your gfx card and mother board and cpu and w/e

 

[TweaK]

Yea, probably hardware. Try updating all your drivers, and directx.

 

[ChrisH36]

That happened to me when I got new GFX card, so Ill assume its all about your gfx card and mother board and cpu and w/e

Yep, if software doesnt work, assume its a hardware problem.

 

[OMGLOLWTFPWN]

It has happened to me before but not often.

 

[XsexecutionerX]

I found out that it was a problem with an item in DOTA that caused the game to crash, since then it had been fixed though.

 

[ChrisH36]

I guess it was trigger or model related then, DOTA uses lots of imported and altered models anyways. Like that Shaman that was all black and a red stripe across his face.

 

[vicious-bebop]

ive never got an error nor have i played a lot of dota and all i have been seeing is the huge amount of sever splits.

 

[ChrisH36]

The error was fixed after v5.73 was released.