UNHANDLED EXCEPTION: ACCESS_VIOLATION (c0000005)

[badboyroy]

UNHANDLED EXCEPTION:
ACCESS_VIOLATION (c0000005)


The above noted error has got me really pissed. I have been tryin this and that fix....I have tried everythin except voodoo. I have gone to the official blizz site and followed their "official" advice and nothin helps. I have even run the windows ram tester as suggested as well and even though it did find errors.

Here is a list of things I have tried:

Re-re-re-reinstalling.
Defrag-defrag-defraging.
Reformat-format-formating.
Updat-updat-updating.


I have tweaked my system to no end. NOTHIN is workin.

Any suggestions?

[badboyroy]

I noticed it happens mostly when I am loggin into baal runs...for some damn reason.

I do what anyone else would do...I use ctrl A and then ctrl C to make gettin into the next game faster...and then boom it happens after about three times or so in doin it. Then when I relaunch D2 I am unable to join games for a few minutes.

What the hell.


I followed the instructions on the Blizz support site that specifically dealt with this issue and nothin has changed.

[Shadow_247]

So you reformatted your entire computer, and still got the error after reinstalling? Usually a complete manual uninstall and reinstall will solve the problem, but a reformat would take care of any files left by the uninstaller.

Run scandisk if you have win9x (accessories->system tools->)
or error checking in winXP (My computer->right click D2 drive->tools tab->check now)

Short of that working, i'll recommend you to upgrade your video and sound card drivers to the lastest version.

Also, if you haven't already, try changing your video mode to DirectDraw (Run VidTest.exe in /d2 folder->run test->select directdraw).

On that note, make sure you have the lastest directx drivers (i think we're at 9.0c).

Try playing in windowed mode for a while (add -w to the end of your shortcut command line)

Try the above, get back to me if it still doesn't work.

[RTB]

D2 uses that error when it doesn't know what just happened. Since you've tried everything, perhaps switching videomodes as shadow_247 said can fix the error.

[Ikeren]

Interestingly enough, I saw that error, but not in D2. When I was playing the Eastern Sun Mod on the Chaos Empire Server by mistake that happened when a certain spell showed up (One with a different image due to the Eastern Sun Mod, and a normal image on the Chaos Empire Server).

Thus, I can say the "When Diablo2 doesn't know what's going on" part is completely justified...but what exactly is it that you are doing? Perhaps Diablo2 doesn't reconigize a command, and after a while tries to do something it shouldn't?

In reality, the program should always know what is happening...which means what could be happening is a piece of data is loading improperly, and it dosen't know what that piece of data is...problem is, a Re-install should take care of it...unless it's faulty on the CD...does your CD have many scratches? Or one very prounounced one?

[tactik]

I had these errors, so I tried updating my videocard drivers, updating directx, running scandisk & defragmenting my drive. Then I re-installed D2 hoping this would at least make those errors less common.
After all this I stopped getting the "Access violation" error, now my D2 either just stops responding or crashes my computer. :(
I also tried running it in window mode, it caused my computer to show me that wonderfull blue screen I haven't seen since win98!

What to do next? The only thing I can think of is buying a new hard drive so I can install WinXP on my computer and hope it runs better than Win2K (thou I doubt it since it's also from Microsoft). Any other ideas?

EDIT: What really is frustrating about this is that I've got D2 running perfectly (except on low fps rate) on a 300 mhz computer, but my 2400 mhz computer crashes. Now my 2400 mhz comp isn't even to be trusted for muling! :(

[Soepgroente]

Switching from "3D" to "2D" fixed it for me.

[Crimh]

I never had these problems until patch 1.10. Now, I get this error and more every now and then. Oh and I have tried all the above suggestions. Even mailed Blizzard about it and they came up with some crappy solution which of course didn't work at all.

Ah yeah, once I updated to 1.10, I couldn't start the game either from the cd, so now I have to use a nocd patch to run it. Of course, Blizzard couldn't help me there either.

[xlodtraderx]

Make sure your an administrator and not a user...when your a user you have limited acess to certain programs...only the administrator can designate wheather you can or cannot use a program...so make sure your set as the administrator (this is windows im assuming?)

[Rex]

I had the same problem untill I mounted the rom as an image on a virtual drive, and started using a GlideFX wrapper. Don't know what really was the cure, but I haven't seen the problem since.

[stzein]

I had this error too in the past, though not too often. I've never seen it again since I switched to Linux. :clap:

[erratta]

I do what anyone else would do...I use ctrl A and then ctrl C to make gettin into the next game faster...and then boom it happens after about three times or so in doin it. Then when I relaunch D2 I am unable to join games for a few minutes.



happens with Ctls-A / Ctrl-C.... what helps: Ctrl-A lets say "baal-001"
Ctrl-C .... then Backspace, Backspace (needs to be twice as I found)... type 02 (as it's a new game you are after)

re tweaking your system: don't, especially if you are tweaking from sites like blackviper.

re unable to join games after - what *might* help - create or join a game with different character from the same account, then go back to character you had problems with.

[erratta]

just a slight correction (I thought something's not right here) I was talking about Ctrl-C / Ctrl-V aka copy-paste, not select all / copy to clipboard, I use Shift-End to select. So... it looks to me at this point that it might also be that if you do it very quickly - you will have game crash.

[Mr SpArKLe]

:uhhuh: happens 2 everyone...

[Fiblah]

Are you guys using Windows SP2?

After I upgraded to SP2, I would get this error every other game I would join. It was annoying me so bad. I uninstalled D2 a few times, but that didnt work. Finally, I uninstalled SP2, and I havent gotten the error since. :drool:

If you are running SP2, try uninstalling it. See if that works for you like it did for me. :)

PS: First post, hello all. :flip:

[Psyrus]

I'm sure everybody has experienced the infamous c0000005 error at least once, but hopefully nobody will ever have to go through this...


Over here, D2X would run just fine for at least 4 to 5 months. Then one day during Direct 3D's usual checksum stuff that occurs once starting D2X, I get a wonderful BSoD. Ever since then, the game has been continually interrupted by numerous c0000005's, sprite decompression errors, corrupted data file errors, and about two other types of errors. Reinstalling wouldn't help any either. I would get an error that read "bad data file detected" after installing the expansion, and the in-game errors persisted.

I emailed tech support regarding this once, but on the same day I received a reply, the computer it was formerly installed on decided it wasn't going to work anymore:

"winlogon.exe" not found
"lsass.exe" not found

I don't know if it was related to the "corrupted data file" problem, but the entire computer is now being replaced because a ram stick that was installed was apparently faulty and screwed everything up. So now, what I was instructed to send to tech support is forever lost.


All I can say is don't let this happen to you. :stoned:

[Dreamsmith]

I had this error too in the past, though not too often. I've never seen it again since I switched to Linux. :clap:

I do see this error every once in a while running up to date Gentoo Linux and the latest stable WINE ebuild. I see it a lot if I do too much copy/pasting, but even abstaining from that entirely I still see it maybe once a month on average.

[Unscene]

I did notice it occuring more frequently when I hopped into baal runs too. Just a theory, but could it be tied to MH, or duped crap? Perhaps there's an overload of it and it infects your character file from being around so much of it? Does this error happens only on the realms? Does it originate as a server issue? A Thrid party software issue? Hardware defects? Who knows, maybe a higher force is just telling us to stop playing the damn game once in a while... :uhhuh:

[Zavior]

Switching from "3D" to "2D" fixed it for me.
Same here. Was getting really mad about it.