Was just playing hardcore and got the bluescreen from windows. Restart and my hc character is dead. Never had this happen in the original d2.
Your deeds of valor will be remembered.
6 Likes
If you got a Windows bluescreen, that is probably not something with the game itself, but rather your computer hardware and/or device drivers.
Did you record the error on the blue screen? Example: 0x0000000A
IRQL_NOT_LESS_OR_EQUAL
If you did not record the error, you can run “eventvwr”, look at Custom Views > Administrative Events, then look for a recent Source:“bugcheck” entry.
Never had this happen in classic d2? So you never got realm down or connection interrupted in classic? Yeah right…I lost plenty of characters in classic D2 due to random disconnects.
1 Like
I literally played the game for 5 minutes and dead. Windows is fine and I never get the blue screen playing d2r. Supremely outrageous that it doesnt log your character off.
Just like previous poster mention. Win bluescreen of death is not related to d2
d2 is played on the windows. so it related my friend.
If you say so.
/20 max characters
When any program crashes, the Windows kernel takes over and handles the crash to prevent the crashing program from taking down the whole system. This would result in a “crash to desktop”. To the user, the program would appear to suddenly close.
If anything, D2:R taxed your system to the point where the hardware and/or driver issue became present, resulting in the Windows crash.
WindowsKey + R to open the “Run” box. Type “eventvwr”, click OK. Look in Custom Views → Administrative Events, then look in the entry list under the “source” column for a recent “Bugcheck” entry.
1 Like
That sounds like you got beef with Windows and/or the various manufacturers of the components inside your machine. You should probably take it up with them in their forums rather than complaining about D2R.
A computer crash shouldnt lead to your character being clocked in and killed.
When your computer suddenly goes offline for whatever reason, be it a crash, power failure, ISP drop, etc… There is a short period of time required for the Blizzard servers to see that you have dropped, or “timed out”. Once the connection has timed out, your character will be removed from the game.
During that short time frame, if you were in the middle of a battle, your character would just stand there and take hits until they die. Your only hope would be if your character is tanky enough to handle the hits until the disconnect happens.
Hey, you’re playing hardcore. Deaths are inevitable. You accepted the agreement when creating the hardcore character. It’s not Blizzards fault that your computer crashed.
If you can’t handle that happening again, I suggest switching to softcore.
1 Like
This game crashing more than the original game so hardcore is not an option anymore. Just reporting what I experienced. So to those playing hardcore enjoy.
1 Like
First, I raise a glass to the dead
D2R appears to be taking longer to detect disconnects than the original D2. I’ve lost one (luckily low level) character to a disconnect and it would not have died in Original.
Most modern ARPGs actually don’t auto logout on disconnect now so you can’t abuse a system like you could in D2. In honesty… that is relatively normal now if you crash.
I do and so far in WAY too many hours… 1 character dead from game issues and 1 dead due to me opening a door =(
lvl 82 full vita with cta over 2000hp. dead to a simple blue screen. wont be playing hardcore anymore
died today from 2 or 3 revived corpses at the yard of pindle with 1,5k life and 40 block… game standing still 1 sec, then alt+F4 and it took hour for the game to close… wouldnt have happen in original… also now every day since some weeks at 3:45 i get disconnect (also in eso btw, but maybe connected), but rest of internet works fine… idk if that was also a problem on my side (i learned not to play higher chars at that time, only farm hots in norm) but the long time it takes the game to notice im out (crash or alt +F4) and other loading times makes it HC + (or HC ++ w/o ebug and strbug)