Error Message

[noobintraining]

Error Message

Good evening forumites,

I was in town between NM Mephisto runs when suddenly the game crashed and I was met with a decidedly unfriendly error message:


Diablo II Error

Halt
Location:, line # 1646
Expression: Unrecoverable internal error 6fe2137c


Being the stubborn person I am, I immediately restarted and within a few seconds it happened again. I did a little searching both here and on the "Bug Reports and Suggestions" forum. I've read of similar errors, but they all seem to happen with Assassins...I am playing a Barbarian. I play 1.11b Vanilla, if that information is of any use.

I'll likely back up my characters and do a full re-install, but I am eager to hear your thoughts on the matter. Has anybody else encounted this problem? Can any of you provide any insight or suggestions?

Any help is much appreciated.

 

[TrubbaNot]

That very error made me crazy for half a year at least, and I never did solve it. The computer ended up dying a horrible death, and I don't get the error on my husband's computer.

I wish I had something helpful to offer, but all I can tell you is that in the months I was encountering it, neither Blizzard nor this forum was able to provide a solution. I hope you have better luck.

on edit: To me, it happened with all character classes. There was no pattern to it ... sometimes I could play for hours, sometimes for mere minutes.

 

[neumein]

That looks nasty. I haven't had that one before. I suggest the re-install. If that doesn't fix it, I'm sure some of the more experienced techies around here will help.

Hope it works out.

 

[sawm]

You might want to check out this thread, apparently there could be a portion of a .mpq file that's been corrupted somehow. Perhaps copying it from the CD might work...just a thought.

 

[TrubbaNot]

I really, really hope that works for you. I never posted in those threads that I even borrowed my friend's CDs (also store-bought) to reinstall the game and copy the MPQ files over, but it didn't solve it on that computer.

 

[RTB]

That's one of the problems of 1.11, errors don't tell what happened anymore.

 

[noobintraining]

You might want to check out this thread, apparently there could be a portion of a .mpq file that's been corrupted somehow. Perhaps copying it from the CD might work...just a thought.

Thank you very much! I missed that thread in my searches. I will certainly give it a try. I'm hoping for the best.

 

[BabyLink]

There are many facts that can explain this:

• you play 1.11b and it crash when the patch is mad at you
• some file is corrupted. Make a backup of your chars and reinstall
• A 1337 tyrael's might was about to drop, and the game wanted to keep it.

that's all i can think about. anyway. you better make a backup of your chars and reinstall the whole thing. If it still does it, it means that your char is corrupted. Does it happen with other characters, too?

 

[noobintraining]

There are many facts that can explain this:

• you play 1.11b and it crash when the patch is mad at you
• some file is corrupted. Make a backup of your chars and reinstall
• A 1337 tyrael's might was about to drop, and the game wanted to keep it.

that's all i can think about. anyway. you better make a backup of your chars and reinstall the whole thing. If it still does it, it means that your char is corrupted. Does it happen with other characters, too?

Thanks, I needed a laugh!

I just backed up my characters, but I'm going to try replacing the d2data.mpq file as suggested in other threads. Hopefully that'll work.

I'm not sure if I'll get the same error with my other characters, since this problem just started yesterday and I haven't played my other three characters in months.

 

[noobintraining]

UPDATE:

I deleted the file "d2data.mpq" and replaced it by manually copying the same file from the Diablo II installation disk.

I've played for about two hours since, and no more error message. I suppose this doesn't necessarily mean the problem is fixed, since the error message occurs somewhat sporadically. However, my hopes are high.

Special thanks to swam for directing me to another discussion about the error.

 

[TrubbaNot]

Excellent news!