In Need of HELP!!

You know, I've been having an awful lot of problems with Diablo 2 myself. It's constantly crashing on me, and when I tried to use another video card, it freaked out my computer in the same way (even though until then it had been working just fine), so I had to remove the video card and go back to the crappy onboard video, which eventually worked after I reinstalled the drivers for that.

Diablo 2 is definately not my computer's best friend.

-Intelicide: The act of marketing overriding engineers to kill a product before it can be released.

No offense dhlucke, but I've gotten some very similar results after messing around with Diablo 2, and I know my computer isn't overheating. I think Diablo 2 just has some very nasty bugs in it or something. It's funny that it's the ONLY game on my system that won't run stable (I can even run Half Life, C&C2, and Quake 2 flawlessly ... well, except for some artifact problems due to my video card in HL that is a known bug of the video chipset), and yet I kick the pants off of the minimum requirements for Dialbo 2 as printed on the box.

I'd say it was my system if any of my other games crashed even once. But these problems ONLY occur while running Diablo 2.

So I'm inclined to believe that LinkDead is experiencing the same weird freakish things related to Diablo 2 that I am.

Of course, you could be right and it could be the heat sink in his case. But what about mine where I know it's not?

-Intelicide: The act of marketing overriding engineers to kill a product before it can be released.

No offense taken. So let me reword what I said.

If you are getting random errors, including SUWIN errors then you are "most likely" overheating. I've had experience with it. I'm guessing you had a hard enough time just installing windows than even getting into diablo. The only thing that is different in your situation is that you can somewhat run your computer. I couldn't even run anything let alone diablo. Mabye you're only overheating a little bit?! A bit of a stretch maybe, but I'd definitely check your temps...

Slvr, Did you get SUWIN errors?

Just my two cents with my experience.

<font color=red>Yeah, I took a crap on your lawn. Whatcha gonna do about it?</font color=red><P ID="edit"><FONT SIZE=-1><EM>Edited by dhlucke on 07/31/01 02:54 PM.</EM></FONT></P>

Dear slvr

I must side with dhlucke on this one. LinkDead says he formatted his HD which should take anything Diablo could have done out of the picture. I'm not saying Diablo didn't cause problems just that any of those problems should be gone after a format.

Since the software is a dead anyway I would try an fdisk mbr and really start from scrath. A widoze 98 or later recovery disk should have cd rom drivers for just about any cd rom.

The HSF is mounted correctly and has paste, the cpu runs at about 54 degrees Celcius , The main problem is then when the windows 98 install starts up it doesn't get past the first part it goes to 100% then freezes. I have no idea how to fix this.

What is the exact commands I should use, I'm not very good with using dos can you please tell me what exactly I should do in order to get my computer working again?

When it happened to me it was during a game of Diablo2. It just locked up (not even blue screened) and I had to hit the reset button because a three finger salute got me no response.

When it booted up thereafter, I got SUWIN errors every single boot. The only way Windows would even boot up was in safe mode and even then it kept complaining about something to do with a dual monitor setup. (Even though I've never run a dual-monitor setup in my life.) I was about to reformat my system because I got incredibly sick of being unable to use it for anything because even in safe mode it'd blue-screen just for the heck of it.

But I REALLY didn't want to reformat my system because I didn't have a backup for everything on it and really wasn't looking forward to losing all of the work I've done on writing two different books. I tried reinstalling Windows anyway though, knowing it was likely to reformat on me because I was just tired of putting up with it all.

Well, my computer made up my mind for me as it decided to crash just trying to run the Windows install. Heh heh. Luckily it hadn't been able to acomplish anything yet, otherwise I'd have really been pissed.

So, instead of reformatting and reinstalling Windows, I struggled through it. I removed every single piece of hardware that wasn't needed to run the system, and removed the drivers for them. I even went back to the onboard video and audio. Then I put my modem back in and doanloaded and updated every single driver that I could find.

Eventually I got the nearly bare-bones system to boot up without complaining about anything. Then I added everything back onto it one at a time, except for the video card, which hadn't really been worth it anyway as it was an old PCI PoS that didn't even have OpenGL support, so it just wasn't worth the effort to get it back in.

Since then my system has been running stable again. I even took the time to download the latest patch for Diablo2. (Which was a nightmare at a 26.4K connection speed.) However, Diablo2 still crashes like the dickens. While Diablo2 hasn't caused it to revert back to that nightmare, it still does frequently crash, lock up, and/or blue-screen on me. (It seems a random chance of any of the above happening, and if one happens, the others are never far behind.)

I even tried reinstalling Diablo2 onto a different hard drive, and even went so far as to copy and crack the darn thing so that I wasn't even using the CD. I still got the same results. So I just simply stopped playing Diablo2. It just wasn't a good enough game to be worth all of that.

I can however still play Half Life, Quake 1 and 2, and, Command and Conquer 1 and 2, and, well, any other game without these problems occuring. I even reinstalled Doom and Descent to test it. Even Diablo 1 doesn't cause these problems. My system is 100% stable and passes every systems check I can throw at it. Yet for Diablo 2 it is highly unstable and can crash anywhere between fifteen minutes to three hours.

My only possible conclusion is that either I've got a very rare hardware bug in something on my system that Diablo2 is the ONLY software that uses code which hits this bug, or Diablo2 is still an incredibly buggy game.

-Intelicide: The act of marketing overriding engineers to kill a product before it can be released.