lordalexander74 wrote:Quirinus wrote:lordalexander74 wrote:New issue: Recently loading the game via the launcher gives me the c0000005 error. Installed on day one onto D2 1.13c, played perfectly since then.
A day or so ago, I followed the above guide here to install MXL 2017 w/ D2SE and Plugy for single player, in case my internet connection craps out or I'm on vacation and can't bring my gaming rig. Copied my vanilla D2 files (I've a vanilla D2 install backed up) to another location, and followed that guide. Everything seemed to work fine.
Tried running the launcher today, and encountered that error. I can run MXL and log on to TSW fine with out using the launcher. Only when I started messing around trying to get single player w/ plugy up and running is when I encountered issues. Reinstalling D2 and MXL via launcher didn't help, still can't use the launcher to load D2.
Any idea what I can do to fix this?
c0000005 on hitting multiplayer can be fixed by adding game.exe and Diablo II.exe to the DEP excpetions list. you can find instructions in Menu>Multiplayer>Join (bottom of the page)
c0000005 can be caused by d2se/plugy not being set up properly
c0000005 can be related to video modes missing from registry. you can try running D2VidTst.exe
check that the launcher is using the correct D2 folder path (in launcher settings).
try to set game.exe and Diablo II.exe to run as admin.
Following a complete reinstall of D2 and MXL/launcher, and updating with the new patch, I tried running multiplayer before and after all those suggestions. Thankfully at the end, I could still access TSW through Diablo II.exe, though using the launcher for multiplayer still gives the c0000005 error. That's after checking compatibility, running the .exe files as admin and adding them to the DEP exception list. Still get that error after hitting multiplayer.
Someone suggested trying to add the launcher to the DEP list, but Windows won't let me do that. I can still access TSW, so not using the launcher isn't a big deal. Would like to fix this at some point.
Thanks for the help.
Yeah I'm having a similar issue, tried DEP, admin, vidtest, reinstalling and everything but I can't seem to get multiplayer to work with the launcher without it giving me the c0000005 error. I can play singleplayer just fine through the launcher though.
Also, multiplayer works fine if I just launch directly from Diablo II.exe.
My error.txt says:
"[2017-06-03 20:45:59 -06:00] Error: Command failed: C:\Games\Diablo II\Game.exe -w -3dfx
at ChildProcess.exithandler (child_process.js:223:12)
at emitTwo (events.js:106:13)
at ChildProcess.emit (events.js:191:7)
at maybeClose (internal/child_process.js:885:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)"