Diablo2 crash in Windows 2000 for you?

|mpeg|

Banned
Jan 9, 2000
737
0
0
Hi, I frequently find if I run Diablo2 then close it and then start it back up again it will freeze my computer totally. I have to do a hard reboot by shutting off the computer then turning it back on. Does this happen to anyone else in win2k? Thanks.

P3 800, 384mb RAM, viper770 tnt2 ultra, plextor cd-rom, toshiba dvd-rom, sb live!, SMC 10mbit NIC
 

odog

Diamond Member
Oct 9, 1999
4,059
0
0
yeah.... i get the lockup with music still playing.....and have to do the good ole reset button... three finger doesn't work and caps lock won't change.... so it's a pretty hard lockup:(
 

Mister T

Diamond Member
Feb 25, 2000
3,439
0
0
a friend of mine has this problem.
He blames his cd-rom.
Is your cd-rom working ok?
 

|mpeg|

Banned
Jan 9, 2000
737
0
0
Yes, it works perfectly in everything else. But I've only used my plextor, I'll try it with my toshiba later. BTW, Anyone have the win2k compatibility webpage with the forums?
 
Oct 9, 1999
15,216
3
81
I can run it in W2K but not 3D mode for they havent yet released a patch for the ATI Rage Fury PRO cards..
So far 2D is great.. but I would love 3D.
 

Ben_Tech

Member
Jan 12, 2000
114
0
0
I had the exact same problem in Win98. It seems DII is very sensitive to overclocked systems because clocking my cpu and bus down took care of it, even though all other apps run 100% stable. I don't know if you are running over spec like me, but if you are, it's worth a try. Good luck!!
 

Gatsby

Golden Member
Nov 6, 1999
1,588
0
0
Here's how I fixed the problem.

1) Change your video settings fom direct 3d to direct draw.. yah yah the graphics suck but it works.

or

2) upgrade to the 5.3 NOT 5.32 or so I've read and you can use direct 3d.. I know the 5.3s work cause I;ve used them for the last 4 days without a single crash. This is in battle.net and local games for well over 30 hours

Gatsby
 

Zoe

Senior member
Jan 28, 2000
217
0
0
Same problem here; it locked up after running nonstop for a long time. It could've been a small memory leak, since that's one of the bugfixes mentioned in the latest 1.02 patch.