PDA

View Full Version : Diablo2 Crash


TJ9
11-06-01, 12:20 PM
When I install diablo 2 with the Lord of Destruction Expansion it says that it has currupted file(mpqs?). When installing onto another computer with the same discs it installs alright.
I am useing an:
Geforce 3
1 gig t-bird(unlocked but not overclocked)
AK75 EC motherboard
a 32 speed CDR

when I copy the program from one computer to mine over the network it will run but has random crashes.

WyrmMaster
11-06-01, 05:29 PM
Try a different CD drive.

Krome
04-18-02, 07:11 PM
I just got smashed by Andariel [sp?], and I exited the game in frustration, now when I try to start a new game I get a error during the "loading" screen. something about "d2 line 1070" or something to that extent. Anybody had a similar prob b4?

Krome
04-23-02, 03:17 AM
I have the actual error here....


*Diablo II Error*
Assertion Failure
D2COMMON\UNITS\Units.cpp, Line #1710
Expression:hUnit

I know others have had the same problem, nobody has had a fix yet. It has something to do with the 1.09D patch and "Andariel", that's what we all have in common?

Lord_Zoltan
05-03-02, 08:13 PM
Krome that error is usually depending on wat your playing in.
are you playing in Single player, Open Bnet, or Closed.
I can help you if you answer one of those..
COOL !

or just send me a mail Holydrunkmonk@hotmail.com

Oni
05-03-02, 08:58 PM
TJ9, it sounds as if your HD is suspect. If you're overclocked, I'd drop back to stock and see if it'll install. If not, try swapping out your HD. If it works on the other HD, I'd format your current HD and try again. If it still doesn't work, its RMA time.

Kid Payne
05-10-02, 01:56 PM
how about installing D2, then patching it. Then install LoD then patch it. Just a suggestion. Don't really know what the problem could be.

Krome
05-12-02, 03:35 AM
Originally posted by Lord_Zoltan
Krome that error is usually depending on wat your playing in.
are you playing in Single player, Open Bnet, or Closed.
I can help you if you answer one of those..
COOL !

You got mail... I will be sure to post the fix, if it comes around. :beer: