Diablo II Problem...
I don't know if you guys can answer this, I tried a D2 forum, but they don't know a thing. Sometimes I am running Diablo II and get an error, whatever, it doesn't matter what error really, so it crashes Diablo II, when I try to log back in and use B.
I don't know if you guys can answer this, I tried a D2 forum, but they don't know a thing.
Sometimes I am running Diablo II and get an error, whatever, it doesn't matter what error really, so it crashes Diablo II, when I try to log back in and use B.net, it says "CD-key already in use by <name here>" <---which is obviously me, but i'm not on there!
I do CTRL/ALT/DEL only to find the D2 process that was suppose to have been killed when it crashed still running!!
Anyone know how I can prevent this from happening?
Sometimes I am running Diablo II and get an error, whatever, it doesn't matter what error really, so it crashes Diablo II, when I try to log back in and use B.net, it says "CD-key already in use by <name here>" <---which is obviously me, but i'm not on there!
I do CTRL/ALT/DEL only to find the D2 process that was suppose to have been killed when it crashed still running!!
Anyone know how I can prevent this from happening?
Participate on our website and join the conversation
This topic is archived. New comments cannot be posted and votes cannot be cast.
Responses to this topic
Sounds like a bug that would need to be patched by the Author, Blizzard, if I remember correctly. Have you applied any/all patches?
Wouldn't you think the interaction between the OS and Diablo II is a symptom of some kind of bug in the software? Could be an issue of timing between all devices that need to be interacted with, i.e., Graphics Card, Sound Card, Mouse, etc...
Just saying it's not a bug with D2 doesn't really help. I play this game quite a bit, but only single player or a TCP/IP game with friends and/or relatives and not thru B.net servers.
I also seem to recall this very thing being discussed about on the open tech support forums of b.net some time back, can't recall the exact date however, sorry.
The fact that the D2 process is still running could point to the cause but the only way I can recommend that you get bye this is to run Task Manger and kill the game.exe process then reload D2 and reconnect to b.net.
Have you also sent an email to Blizzards tech support detailing this same info? Basically if using Task Manager to kill the process and relaunching the game works then let them know this as well.
Obviously this is not an ideal option, but it may be the only one available to you.
Just saying it's not a bug with D2 doesn't really help. I play this game quite a bit, but only single player or a TCP/IP game with friends and/or relatives and not thru B.net servers.
I also seem to recall this very thing being discussed about on the open tech support forums of b.net some time back, can't recall the exact date however, sorry.
The fact that the D2 process is still running could point to the cause but the only way I can recommend that you get bye this is to run Task Manger and kill the game.exe process then reload D2 and reconnect to b.net.
Have you also sent an email to Blizzards tech support detailing this same info? Basically if using Task Manager to kill the process and relaunching the game works then let them know this as well.
Obviously this is not an ideal option, but it may be the only one available to you.
