Killerspartan Posted December 20, 2019 Share Posted December 20, 2019 (edited) Hey folks,I recently moved Skyrim and all my nexus mods (as well as install folder and all that jazz) from my hard disk drive (D:) to my SSD (C:). I reinstalled all my mods, reinstalled Skyrim to my C: drive, sorted the load order with LOOT and did all of that stuff. I'm decently well versed with installing mods, and I don't think they are causing the problems here.Nearly any time I try to load a save, the game CTDs. In my SKSE crash dumps, I'm getting the exception, "0xC0000005, The thread tried to read from or write to a virtual address for which it does not have the appropriate access". Ok, I know loading old save games with mods on them after an uninstall is bad news, but I also made new games with the Alternate Start mod on, and upon using the bed to be teleported to the overworld, the game crashes with the same exception in the dumps. I was also actually able to load pre-uninstall save games, and they crash upon attempting to change cells (using a door, using a "coc" command in the console).I have reinstalled my graphics drivers, I have uninstalled all Microsofft C++ Redist programs from my computer and reinstalled just the latest ones, I have used Dependency Walker to try and figure out if I'm missing any .dll files (but the program is nearly useless because it can't really deal with Win 10 architecture and gives a million false positives). I have done all of that and then made a clean reinstall of Skyrim, but nothing has worked.Does anyone have literally any ideas about what the hell is wrong? This only happens with Skyrim, otherwise my computer runs perfectly fine and I have never had a dependency issue with any other programs. Perhaps this stems from moving Skyrim from my D: to C: folder? Back on D: I would still get occasional crashes where the SKSE crashdump would list 0xC0000005 as the exception error, but the game was still playable. I switched it to my C: thinking that this would help problems, but it has only made the game inoperable. I haven't yet tried putting everything back on the D: drive cause it's kind of a pain in the ♥♥♥ and there's no reason it shouldn't also be able to run on my C: drive.Thank you to all who read or lend a helping hand. Edited December 20, 2019 by Killerspartan Link to comment Share on other sites More sharing options...
HeyYou Posted December 20, 2019 Share Posted December 20, 2019 Delete, or rename, you skyrim.ini files in your My Documents\My games\Skyrim folder. Try the game again. That error is really generic.... it supposedly points to a hardware issue, but, if the game ran fine before moving it, it's likely windows 'best guess' as to what happened. Link to comment Share on other sites More sharing options...
Killerspartan Posted December 21, 2019 Author Share Posted December 21, 2019 Delete, or rename, you skyrim.ini files in your My Documents\My games\Skyrim folder. Try the game again. That error is really generic.... it supposedly points to a hardware issue, but, if the game ran fine before moving it, it's likely windows 'best guess' as to what happened.Hey, thanks for taking the time to give me some advice, Unfortunately deleting the Skyrim.ini had no affect on the crashing :( Link to comment Share on other sites More sharing options...
HeyYou Posted December 21, 2019 Share Posted December 21, 2019 I was hoping it would be easy, but, no such luck..... Disable your mods that require the script extender, fire up the game without it, start a new game, and see if it behaves any different. Link to comment Share on other sites More sharing options...
Killerspartan Posted July 8, 2020 Author Share Posted July 8, 2020 Hey folks, The root of the problem was d3d9.dll in Skyrim's directory. This is the file used by ENBseries in order to run. I'm not exactly sure why d3d9.dll causes the game to crash, but I'm investigating it. Link to comment Share on other sites More sharing options...
Killerspartan Posted July 8, 2020 Author Share Posted July 8, 2020 Back again folks, The problem is solved. I created a new rule in Windows Defender for enbhost.exe, specifically allowing it to bypass the firewall. Now everything works fine. Supposedly, this issue can also happen due to running RIVA, MSI Afterburner, and other overlays/performance enhancers/capture programs. Link to comment Share on other sites More sharing options...
Recommended Posts