Strange...

[Billton]

So I was playing D2 today, just teleporting around act 3 with my pally, and I got some "Unrecoverable Error" or something... Now whenever I join a game, my connection gets interrupted about 20 seconds later. This ever happen to anyone else? Any idea what the problem is?

[Orphan]

That's happened once or twice for me too. I find that restarting the computer to clear the memory helps resolve it though.

[BlueOctoberFan]

I've had that happen as well, but I never saw any error message. I simply coudln't stay in a game without it getting interrupted after less than a minute. I think I did the same thing with restarting, that or it went away after I was signed off for a while.

[Ihmhi]

You guys could have a bad stick of RAM.

Hypothetical situation: a friend is reading some text to you, and you are writing it down. Now, let us say bad ram is equivalent to your friend having a lisp. It is kinda hard to understand him. Eventually you are going to get up and slap him.

Anyway, friend with a lisp aside, bad ram means that a piece of data in the RAM will not be read correctly. Let us say you try to shoot a fireball and the fireball graphic loads into the RAM, but in the bad portion... the fireball is not rendered properly, the computer does not know what to do, and then... crash.

I have found Firefox (the webbrowser) is a good indicator for detecting crashes. If Firefox crashes during normal use it is usually indicative of bad RAM (at least it was for me).

Anyway, if you continue to have this problem, remove all but one stick of RAM and play for a while. If you have the same issues, that could be the problem stick. If you can play fine for a while, change up your sticks.

If you have problems on multiple sticks of RAM (or all of them) using the swapping method, then that means one of three things:


1) It is not a RAM-related problem.

2) You have multiple bad sticks of RAM.

3) Something else.


See, the bad thing about computers is that since there is no one great diagnostic tool in existance you either have to have specialized software or specialized knowledge to fix a problem like this quickly. If not, then you just have to do things like this one by one. If it is not #1 or #2 on the list, then it is #3, which means you have to start thinking about other possibilities as to what is wrong.

[buddahsbigtoe]

ive had that happen on occasion. it was because even though the game crashed, it was still in memory. i was even able to bring the game up and return to the same game i was in, but when i got to the same area, it would crash again. the only thing i could do to fix it was either reboot or kill it as an active process.

[BlueOctoberFan]

You guys could have a bad stick of RAM.

Funny you should say that... This weekend I was playing with a couple of copies running, when I got a pop-up warning bubble from the task bar saying that virtual memory was running low. Then, after about 1 min, I got a blue screen saying that Windows encountered an error and was shutting down (the screen was actually full of text, but that's what I could read before it shut down entirely). Trying to turn on the computer resulted in getting the first loading screen (brand name, press F10 to enter setup, etc.) and locking. I popped out the RAM that I had added (1G), and it runs again. Now I just need new RAM (going from 1.2G down to 256MB is a little too much of a slow down for me).