Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Did you move Magnolia?
And I mentioned in the post that I already looked at the mod slot causing the issue and it makes no sense because I haven't done anything with Magnolia, I disabled that mod and tried it again and it still crashed saying it was the same slot, but it was a different mod in that slot that time around.
The last time I seen that sort of behavior blaming a certain slot was a bad .dll in my NVidia driver, but it said the .dll not the fallout.exe.
Try reinstalling your drivers, rolling back your driver, or changing it from game to studio, etc.
For example, the crash might be caused by Mutant Menagerie, maybe there's a creature from the mod that's in Red Rocket right now and the game crashes everytime it tries to load in that creature.
So the callback in the crash log does actually refer to two DLLs, I just have no idea where they are on my PC or what programs they're tied to
[5] 0x7FF8FFE47034 KERNEL32.DLL+0017034
[6] 0x7FF900882651 ntdll.dll+0052651
those are windows DLLs budday. used to run the system and most likely aren't tied to your game problems?
here's what google says about those files
For anyone looking, this was how I fixed it: https://answers.microsoft.com/en-us/windows/forum/all/app-crash-with-ntdlldll/9aa59f80-99a1-4f3c-b2f0-7eb72df05b2a
but you put 4 of our heads together and BAM! we figure it out in a day. and it only took that long because we're not online at the same time and it takes time for messages to get read, lol.
a corrupted windows dll. who woulda thunk. i've been helping people fix problems with this game here in the forum for months. you honestly never know what's to blame with a PC lol. it could be anything i swear
When I had my .dll issue it was a nightmare. I reinstalled the game and all my mods like three times. This was because Buffout 4 kept pointing to whichever mod was in slot 07, remove one mod and it blamed another in the same slot.
The other obvious thing is when it blames a REALLY common mod like Workshop Framework, which is used by THOUSANDS of people so if there was an actual issue with the mod itself it would be really common topic.
I went through about a dozen different graphics drivers, some of different .dll from different drivers made it worse. At one point I could not even get through the title screen or load any save.
Overall I think I spent like 3-4 days trying to resolve my .dll issue. Took like about a week and a half because I gave up and took a breka for a day two between attempts. Most topics about the .dll was just people throwing wild crap guesses like weapon debris
Quite a bit comes from personal experience and helping people for years, you tend to see some of the issues and symptoms from different people. It also helps a lot when someone actually provides information rather than it just crashes or some bug rant.
So next time I see someone with these symptoms, but it aint pointing to the NVidia .dll I can point them towards the .dll you fixed.
I've been experiencing this issue for months, but I can't seem to solve it the way you are suggesting. I've also seen many posts addressing this impossibility. One was a Windows support person telling off another Windows support person for recommending this dll fix, because ntdll.dll cannot be registered nor unregistered with regsvr32.exe. The only way I have seen others recommend accomplishing this is by having someone send you their ntdll.dll from the same version of Windows as yourself.
Is there another way you managed? I'm not understanding how this was the solution.