I struggled with this error every time I exited my Diablo 2 game since the early versions of Median XL. Today I finally had enough and decided to search the internet for every remedy I could find. I finally found a working solution. I hope it works for you.
My computer specs: OS: Windows 10 Professional 64-bit [10.0, Build 19045] CPU: AMD Ryzen 7 5750GE CPU RAM: 64GB Ram DDR4-3200 / PC4-25600 SSD: 2TB NVMe Samsung 980 Pro SSD GPU: AMD Radeon Vega [Cezanne] 512 MBytes DDR4 SDRAM
Game Video Mode: 3DFX Glide
Solution: 1. Add the Diablo2 "Game.exe" to DEP exception. //i.imgur.com/cz8BdGr.pngexception Requires a Restart
2. Set the Sigma Launcher shortcut to Compatibility Mode for "Windows 7"
3. Set the Sigma Launcher and Diablo2 "Game.exe" to "Run as Administrator" in the Compatibility Mode settings.
That's it!
Common Love Badge
Earned over 20 cookies
For completeness sake, the reason why this happens: Installing Median-XL actually downgrades the Diablo II Game.exe to some 1.13 version that is not fully compatible with Windows 7, 8 and 10. So whilst the symptom might be gone after these 'fixes' it is unclear what happens beneath the surface.
Most Mod creators don't want to deal with 1.14 patches and Median-XL actually went for a downgrade to a compatible version.
Great Popularity Badge
Has a thread with over 50.000 views
Common Love Badge
Earned over 20 cookies
Common Supporter Badge
Donated 1 time
Sadly for me this didn't work. Reset and everything.
Great Supporter Badge
Donated 5 times
Just set Game.exe to Compatibility - Windows XP SP3 and check "Run this program as administrator" and enjoy !
Great Popularity Badge
Has a thread with over 50.000 views
Common Love Badge
Earned over 20 cookies
Common Supporter Badge
Donated 1 time
xpucoo wrote:Just set Game.exe to Compatibility - Windows XP SP3 and check "Run this program as administrator" and enjoy !
When I do that and launch the game it tells me that D2DX has discovered an issue and has auto-corrected these settings for me, turning compatibility settings off again...
I'm with my barb [in SP] in SS on Normal. I go in and get surounded by the invisibles. I start doing War Cry [doing 2k damage] and the death animations for the boogers start. I kill about 9 of them this the screen freezes. I wait and wait. Finaly, Desktop comes up and this error is up:
UNHANDLED EXCEPTION: ACCESS_VIOLATION [c0000005]
From the Known Bugs Section, it says:
Added: July 14/03 Error message or bug: 06:38:19.180 ***** UNHANDLED EXCEPTION: ACCESS_VIOLATION [c0000005] 06:38:19.180 Fault address: 6F815793 01:00004793 E:\GAMES\DIABLO II\D2GLIDE.DLL 06:38:19.180 eax:00000000 ebx:0000008c ecx:00000000 edx:051bb9fc esi:0068eac4 06:38:19.180 edi:000000dc ebp:00000001 esp:0068ea80 eip:6f815793 flg:00010293 06:38:19.230 cs:015f ds:0167 es:0167 ss:0167 fs:120f gs:0000 Cause: This error message is quite common. The [c00000005] error code can be caused by a number of different error conditions to do with the Client and possibly the operating system. Specifically, I encountered this error in Act 3 - Swamp Pit Level 2 in which Wraith Knights were encountered. In an earlier version [2.4c], the Blood Knights were supposed to be removed entirely from Act 3. Obviously, I missed one instance and now it is back to haunt me and any other players who go to this one map level - nowhere else in Act 3. Solution: Fortunately, this map level is not a quest-critical map and can be avoided. The Knights will be removed from this map in version 3.1.
I think I forgot how many Zero's there where in the error message [I was very
Kato
by Kato » Fri Jul 18, 2003 1:14 am
Myhrginoc
Hand-picked
by Myhrginoc » Fri Jul 18, 2003 2:31 am
You have to keep in mind the difference between an Assertion Failure and an Unhandled Exception. An assertion error is one that Blizzard expected might happen, and included error handling code to deal with it [usually posting a popup, logging in the debug file and exiting]. An unhandled exception is one they don't know about [it's unhandled, no?], and there are no helpful messages to point out possible problems. So unhandled exceptions are harder to debug because there are fewer clues. The c0000005 error you see is a generic Windows error [not a D2 error!] that means the program tried to access memory Windows doesn't think it should access [that is why "Access Violation"]. One very common reason for this is a register got zero for a value [how is the devil in the details] and was then used as a pointer. [C/C++ programmers will recognize the infamous null pointer bug right away.]
Since this is a generic Windows error [there are thousands upon thousands of possible access violations], you do need to be more specific about what you were doing, what was on-screen and where you were. That is why Kato asks so much information from a bug report.
Do the right thing. It will gratify some people and astonish the rest. ~ Mark Twain Run Diablo II in any version for mods: tutorial The Terms of Service!! Know them, abide by them, and enjoy the forums at peace. The Beginner's Guide v1.4: [MS Word | PDF] || Mod Running Scripts || TFW: Awakening
MRZigzz
by MRZigzz » Fri Jul 18, 2003 3:30 am
Well, I'm not exactly sure what the type of error it was [I was still somewhat wasted from the night before]. I really need to have a notepad somewhere around me to record this stuff.
Basicly, I did what the site said and gave the last 100 lines of D2030717:
19:46:08.160 Closing Direct3D window....19:46:09.210 ... Direct3D window closed. 19:46:09.210 Opening Direct3D window at 800x600... 19:46:09.370 Texture Memory Total= 104.688 MB, Free= 103.770 MB 19:46:09.370 Local Total= 56.688 MB, Free= 55.770 MB 19:46:09.370 AGP Total= 48.000 MB, Free= 48.000 MB 19:46:09.370 Ignoring AGP Memory 19:46:14.150 Opening Direct3D window succeeded. 19:46:14.260 Closing Direct3D window.... 19:46:14.540 ... Direct3D window closed. 19:46:14.540 Opening Direct3D window at 640x480 at 32 bit for cutscenes... 19:46:14.700 Opening Direct3D window for cutscenes succeeded. 19:46:14.700 In Direct3DPlayCutscene 19:46:14.700 About to play bink file 19:46:18.490 In Direct3DPlayCutscene 19:46:18.490 About to play bink file 19:46:19.100 Closing Direct3D window.... 19:46:19.150 ... Direct3D window closed. 19:46:19.150 Opening Direct3D window at 800x600... 19:46:19.310 Texture Memory Total= 104.688 MB, Free= 103.770 MB 19:46:19.310 Local Total= 56.688 MB, Free= 55.770 MB 19:46:19.310 AGP Total= 48.000 MB, Free= 48.000 MB 19:46:19.310 Ignoring AGP Memory 19:46:24.150 Opening Direct3D window succeeded. 19:46:32.610 ENG is locale
19:46:43.920 [D2CLIENT] Start entering at 27730174
19:46:44.030 Closing Direct3D window.... 19:46:44.250 ... Direct3D window closed. 19:46:44.250 Opening Direct3D window at 800x600... 19:46:44.250 Texture Memory Total= 104.688 MB, Free= 103.770 MB 19:46:44.250 Local Total= 56.688 MB, Free= 55.770 MB 19:46:44.250 AGP Total= 48.000 MB, Free= 48.000 MB 19:46:44.250 Ignoring AGP Memory 19:46:56.720 Opening Direct3D window succeeded. 19:46:56.940 [D2CLIENT] Finish entering at 27743194. Elapsed: 13020
19:46:57.380 Seed: 2091704116 19:47:35.880 Seed: 2091704116 19:54:09.480 Closing Direct3D window.... 19:54:10.470 ... Direct3D window closed. 19:54:14.530 Opening Direct3D window at 800x600... 19:54:14.530 Texture Memory Total= 104.688 MB, Free= 103.770 MB 19:54:14.530 Local Total= 56.688 MB, Free= 55.770 MB 19:54:14.530 AGP Total= 48.000 MB, Free= 48.000 MB 19:54:14.530 Ignoring AGP Memory 19:54:27.050 Opening Direct3D window succeeded. 20:28:50.050 Seed: 2091704116 20:30:55.830 [D2CLIENT] Start closing at 30382494.
20:30:56.050 game close start 30382719
20:30:56.110 game close end 30382749
20:30:57.100 [D2CLIENT] Finish closing at 30383744. Elapsed: 1250
20:30:57.920 Closing Direct3D window.... 20:30:58.030 ... Direct3D window closed. 20:30:58.030 Opening Direct3D window at 800x600... 20:30:58.030 Texture Memory Total= 104.688 MB, Free= 103.770 MB 20:30:58.030 Local Total= 56.688 MB, Free= 55.770 MB 20:30:58.030 AGP Total= 48.000 MB, Free= 48.000 MB 20:30:58.030 Ignoring AGP Memory 20:31:02.750 Opening Direct3D window succeeded. 20:31:04.510 Closing Direct3D window.... 20:31:04.840 ... Direct3D window closed. 20:31:05.170 Shutting down Direct3D...
1. lvl 168 Brab doing Suicide Sanctum with the Whirlwind, War Cry, Bash, and Battle Orders. 2. Invisible Boogers [nothing else that was on screen] 3. Suicidal Sanctum 4. Normal 5. Single-Player
There, see what you can find, I havn't read/modded enough to find the error here.
Tycho Posts: 3 Joined: Mon Jun 23, 2003 1:04 pm
by Tycho » Fri Jul 18, 2003 11:39 am
me and some friends were doing insane on sinister realm yesterday, suddenly all exept 2 ppl dropped... diablo quited and we got the UNHANDLED EXCEPTION: ACCESS_VIOLATION [c0000005] error,, we rejoined , but when we joined party and went trough the tp it happened again... ive never encountered this error before and havent encountered it after either
SoulForge
by SoulForge » Fri Jul 18, 2003 4:31 pm
Me and a friend have been playing this mod for a little while now. [granted we are only lvl 61] But its alot of fun. But this error has been really killing our progress
I'll post an error report next time it happens.
Drachenritter
by Drachenritter » Fri Jul 18, 2003 5:23 pm
hm if NOT all are dropping from a game at the same time , the error can't be "in the game" ... seemes logical ,cause IF some weird action from a monster would crash the game , all connected players in these area would crash too ... at least the host.
So in my opinion it seemes to be an operationg system error [ maybe some problems with grafic or direct x or windows-version ]
Maybe some new grafics in zy-el are causing trouble with "new technology" like xp or direct x 9 ...
Thats the reason why kato never encounterd bugs like booger or shaman ... but others are getting these bugs.
That reminds me for my old win 98 / directX 8 - combo ... if "sound-acceleration" was set at the highest value [ inside the dxdiag-panels ] , i had crashes all the time ... even in lod . Setting the acceleration from fast to normal helped ... no crashes .
Fear the Power of Light !
Malifrax
by Malifrax » Fri Jul 18, 2003 9:30 pm
SoulForge, those access fault addresses in your log file are exactly the same as the ones I get when random buggy unique shamans crash my game in singleplayer or tcp/ip. There are a couple of threads about this which can be found here and here. Kato thinks he may have fixed it in 3.1 of Zy-El, but he has no way of knowing for sure since he can't seem to get the crashes.
You talk to the arena master. "Ye have won more fights than anybody else." "Nobody is betting against ye any longer and we believe, that ye art invincible." "Sorry, no more fights."
Kato
by Kato » Sat Jul 19, 2003 3:42 pm
[quote=SoulForge";p="115526"]Well i went looking for a crash and got one
I umm didn't know what to include in here so here's a link
//www.gamersline.net/downloads/accessviolation.txt
I hope someone can dig something out of that and tell me what's wrong =[[/quote]
00:24:23.708 Symbols Loaded for 'game_crk.exe'
streetracinkid84 Posts: 81 Joined: Fri Apr 18, 2003 11:31 pm Location: england Contact:
by streetracinkid84 » Sat Jul 19, 2003 4:04 pm
I am a little bit of loneliness a little bit of disregard Handful of complaints but I can’t help the fact that everybody can see these scars I am what I want you to want what I want you to feel But it's like no matter what I do, I can't convince you, to just believe this is real
Kato
by Kato » Sat Jul 19, 2003 4:07 pm
MRZigzz";p="115395" wrote:Well, I'm not exactly sure what the type of error it was [I was still somewhat wasted from the night before]. I really need to have a notepad somewhere around me to record this stuff.Basicly, I did what the site said and gave the last 100 lines of D2030717:
19:46:08.160 Closing Direct3D window....19:46:09.210 ... Direct3D window closed. 19:46:09.210 Opening Direct3D window at 800x600... 19:46:09.370 Texture Memory Total= 104.688 MB, Free= 103.770 MB 19:46:09.370 Local Total= 56.688 MB, Free= 55.770 MB 19:46:09.370 AGP Total= 48.000 MB, Free= 48.000 MB 19:46:09.370 Ignoring AGP Memory 19:46:14.150 Opening Direct3D window succeeded. 19:46:14.260 Closing Direct3D window.... 19:46:14.540 ... Direct3D window closed. 19:46:14.540 Opening Direct3D window at 640x480 at 32 bit for cutscenes... 19:46:14.700 Opening Direct3D window for cutscenes succeeded. 19:46:14.700 In Direct3DPlayCutscene 19:46:14.700 About to play bink file 19:46:18.490 In Direct3DPlayCutscene 19:46:18.490 About to play bink file 19:46:19.100 Closing Direct3D window.... 19:46:19.150 ... Direct3D window closed. 19:46:19.150 Opening Direct3D window at 800x600... 19:46:19.310 Texture Memory Total= 104.688 MB, Free= 103.770 MB 19:46:19.310 Local Total= 56.688 MB, Free= 55.770 MB 19:46:19.310 AGP Total= 48.000 MB, Free= 48.000 MB 19:46:19.310 Ignoring AGP Memory 19:46:24.150 Opening Direct3D window succeeded. 19:46:32.610 ENG is locale
19:46:43.920 [D2CLIENT] Start entering at 27730174
19:46:44.030 Closing Direct3D window.... 19:46:44.250 ... Direct3D window closed. 19:46:44.250 Opening Direct3D window at 800x600... 19:46:44.250 Texture Memory Total= 104.688 MB, Free= 103.770 MB 19:46:44.250 Local Total= 56.688 MB, Free= 55.770 MB 19:46:44.250 AGP Total= 48.000 MB, Free= 48.000 MB 19:46:44.250 Ignoring AGP Memory 19:46:56.720 Opening Direct3D window succeeded. 19:46:56.940 [D2CLIENT] Finish entering at 27743194. Elapsed: 13020
19:46:57.380 Seed: 2091704116 19:47:35.880 Seed: 2091704116 19:54:09.480 Closing Direct3D window.... 19:54:10.470 ... Direct3D window closed. 19:54:14.530 Opening Direct3D window at 800x600... 19:54:14.530 Texture Memory Total= 104.688 MB, Free= 103.770 MB 19:54:14.530 Local Total= 56.688 MB, Free= 55.770 MB 19:54:14.530 AGP Total= 48.000 MB, Free= 48.000 MB 19:54:14.530 Ignoring AGP Memory 19:54:27.050 Opening Direct3D window succeeded. 20:28:50.050 Seed: 2091704116 20:30:55.830 [D2CLIENT] Start closing at 30382494.
20:30:56.050 game close start 30382719
20:30:56.110 game close end 30382749
20:30:57.100 [D2CLIENT] Finish closing at 30383744. Elapsed: 1250
20:30:57.920 Closing Direct3D window.... 20:30:58.030 ... Direct3D window closed. 20:30:58.030 Opening Direct3D window at 800x600... 20:30:58.030 Texture Memory Total= 104.688 MB, Free= 103.770 MB 20:30:58.030 Local Total= 56.688 MB, Free= 55.770 MB 20:30:58.030 AGP Total= 48.000 MB, Free= 48.000 MB 20:30:58.030 Ignoring AGP Memory 20:31:02.750 Opening Direct3D window succeeded. 20:31:04.510 Closing Direct3D window.... 20:31:04.840 ... Direct3D window closed. 20:31:05.170 Shutting down Direct3D...1. lvl 168 Brab doing Suicide Sanctum with the Whirlwind, War Cry, Bash, and Battle Orders. 2. Invisible Boogers [nothing else that was on screen] 3. Suicidal Sanctum 4. Normal 5. Single-Player
There, see what you can find, I havn't read/modded enough to find the error here.
Kato
by Kato » Mon Jul 21, 2003 6:13 pm
Myhrginoc
Hand-picked
by Myhrginoc » Tue Jul 22, 2003 4:17 am
Yep, that's ordinary game behavior. You don't look for the last 100 lines in those files, you search for either phrase "Assertion Failure" or "Unhandled Exception". You take that line and the next thirty or so lines to be the usable part of the error log. Also the module enumeration, since that shows if you are running the notorious player-activated auxiliary software we always yowl about.
As Kato says, this mod [and any legit mod] doesn't support or guarantee compatibility with those player-activated auxiliaries.
Do the right thing. It will gratify some people and astonish the rest. ~ Mark Twain Run Diablo II in any version for mods: tutorial The Terms of Service!! Know them, abide by them, and enjoy the forums at peace. The Beginner's Guide v1.4: [MS Word | PDF] || Mod Running Scripts || TFW: Awakening
MRZigzz
by MRZigzz » Tue Jul 22, 2003 4:19 am
So far, I have gone in and done SS about 6 times doing the same thing [war cry] a few times and no interuptions. It's happened twice in a row [in one day] and hasn't done it again since. I just brought it up in case it had anything to do with the bug in the known bug section therefore having to remove the invicible boogers from SS. I just remember the bug with boogers [I can't remember if it had to do with the moving animation or the death animation] but I just don't want it to happen again in SS with a skill I like to use.
spagy Posts: 3 Joined: Wed Dec 11, 2002 8:16 pm
by spagy » Tue Jul 22, 2003 1:44 pm
I get the EXACT same problem, D2 quitting only to give me a small popup with the very same message. The weird thing is it only happends when im about to open chests, hidden caches, corpses and so on. So I guess its some perticular item that causes the crasch, thts about to pop out from whatever i tried to open.