You'll probably need to add a rule for both D2 and LoD. Its a long shot, but might as well give it a bash.
Oh and one sly little issue with Windows is the Data Execution Prevention list (DEP) and can cause some funky problems. gtasa.exe doesn't use DEP at all, ao if you set DEP for all applications but gtasa.exe (like you do by adding it to this list), you are not solving SA error, but instead you. Whatever this issue is, it's NOT caused by DEP. If you have multiple graphics cards, start by disabling the multi-gpu stuff. data execution prevention 'turn on DEP for all programs and services except those i select' add gtasa.exe 10. DON'T ADD SA TO THIS LIST, LEAVE IT AT DEFAULT SETTING ( 'for essential Windows applications only'). Modern GPU's can make life more awkward, but a huge issue is SLI and Crossfire. This would be the way to ensure that it isn't modern drivers, OpenGL/DirectX incompatibility or whatever of your graphics card.
Install the game in there, and it should run. Going for a long shot here, but one method that should get the game running will be to download and install a virtual machine (with like a 8GB virtual disk tops probably) and install Windows XP onto that. Also, as far as I'm aware, the digital download editions have been updated as to not require compatibility mode, so if you instantly set the compatibility, remove it and try again. Unhandled Exceptions can be caused by unresponsive instances stopping the game from reinitializing itself.Ħ4bit could be an issue, but from memory, I believe I last played the game on 64bit Windows 7 without any notable hiccups. Befreo attempting to relaunch, do CTRL+ALT+DEL and go to the task manager, under both processes and applications confirm that there is nothing to do with Blizzard/D2/LoD hiding somewhere. Could be something to do with the memory addressing.