for now it doesn't seem like an issue. I booted up Elden Ring and did the same thing; no error occurred on shutdown. went back to Dark Souls 3 and did it again; error occurred on shutdown
Windows strikes again
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
hi, I have noticed a bit of a strange error in Event Viewer while going back through to search for a different event, which is this Bad_Module_Info error
this has worried me that my Ram is potentially dying or something along those lines, and I began searching other Errors. this Bad Module Info error has only occurred on the 14th and 15th of June this year; there is no record of an earlier instance or later one. here are there Windows Error Reporting information events that happen right after:
not too long after, it happened again, except there were 3 Windows Error Reporting messages after the initial Error, and one of them was this;
on the 15th of June, this Bad_Info_Module error and the 3 Windows Reporting messages occurred again, around the time I was playing Dark Souls 3. occasionally, when closing Dark Souls 3, Windows seems to treat it like an error and creates its own error messages which look like this:
the thing is, I'm not sure if it's connected to Dark Souls 3 or not. the Bad_Info_Module happened again a few minutes after these 3 messages came up for DS3, which I believe should have been me closing the game. the Bad Info Module errors on the 14th of June happened at least 30-40 minutes before I got off Dark Souls, and I do not recall being on the game for that entire time
I have an RTX 3070 with Driver Version 531.29, which was reinstalled with DDU a few days later. my Bios is Version 2806 for the Asus B550-F and Chipsets are completely up to date. I've only had this entire PC setup since February 2023
the weird thing is that I read Bad_Info_Module typically causes crashes or noticeable issues, and can be caused by a low amount of resources in the PC. my Dark Souls 3 definitely did not crash at any point; the error messages pertaining to "DarkSoulsIII.exe" have happened inconsistently in the past when closing the game, Nioh 2 also does it, without any trace of a Bad_Info_Module error. not only did I never crash, or suffer a performance hit, my resources were nowhere near being 'low'; my CPU and GPU usage were not close to 100%, my Memory usage was only around 30%, and I have over 1tb of storage left on my SSD. I also had no idea this error even existed until today when scrolling back through Event Viewer
I have tested multiple times with HCI Memtest over a couple of hours and found 0 errors with my Ram/Memory; I did run sfc /scannow in CMD earlier today, and I think before and after using DDU, which fixed corrupt files. but this is really confusing me; I tried replicating this Bad_Module_Info error just before but no luck
-I alt f4'd Dark Souls 3 on the title screen, and while in-game
-I shut down MSI Afterburner while Dark Souls 3 was still active
-I started logging in MSI Afterburner and then alt f4'd Dark Souls 3 to see if that might have confused the program and caused the error
but nope, none of this has re-caused the error message. fullscreen optimizations are also already disabled, which I know can cause all kinds of issues, and the game has been run both with and without Administrator permissions. I'm really confused and kind of concerned that something is going faulty, even if I didn't actually crash, especially because it happened 4 times in total (twice on the 14th, at 5:58pm and 6:16pm, and twice on the 15th, at 12:16pm and 12:19pm)
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
for now it doesn't seem like an issue. I booted up Elden Ring and did the same thing; no error occurred on shutdown. went back to Dark Souls 3 and did it again; error occurred on shutdown
Windows strikes again
If you havent problem you can ignored.
I've continued to get on Dark Souls 3 and get off via AltF4 and Quit Game
it feels more and more like the "DarkSoulsIII.exe ntdll.dll" and "Bad_Module_Info" errors are basically the same and interchangeable. I replicated the Bad Module errors twice more through Alt F4, although the DarkSoulsIII.exe error occurred more often through quitting the process
it might be something to do with how Dark Souls 3 unloads itself, which triggers a module error/the exe error in EventViewer
I get that; I generally follow that rule. it's just, I've never seen the Bad_Module_Info error in Event Viewer before or after these 2 days, where they happened in close proximity to each other. maybe running sfc /scannow 'fixed' it, who knows
I got panicked because the words "Bad Module Info" just sounds like a Memory /Ram-related issue. everything I've tried to research about it though always shows images of an error showing up on screen, and/or crashing the game entirely
neither of those things happened to me. I did a quick google search of the Exception Code: 0x c0000374, which appears on both the Bad_Module_Info errors, and the "DarkSoulsIII.exe ntdll.dll" errors, but I didn't have much luck. just that they might be related to Status Heap Corruption, which can be fixed by SFC
I ran SFC both today and when I used DDU, like I said, although that never actually has an affect of the "DarkSoulsIII.exe" errors; those ones are just a weird natural occurrence. the Module Info errors are not as commonplace