Please see this article for common trouble shooting tips.
You can post your crash logs on pastebin, or using spoiler tags. Please do not post the full, unformatted contents of your crash log without either of these options.
Here is how to write spoiler tags: [spoiler] It just works. [/spoiler]
This appears to be an F4SE log which is different from the crash logs that Buffout 4 creates. I did notice, however that you are using v0.7.2 of F4SE which is for v1.10.984 of the game and Buffout 4 is not compatible with said version of the game.
Have you used the Cathedral Assets Optimizer to pack your mods into BA2 files? If you have, follow the instructions here. If you haven't, open this article and scroll down to "Part 5 | Additional Steps To Take When Crash Logs Are Unhelpful Or Unavailable".
See the "Script Crash" via the Buffout 4 Dictionary and try the solutions listed.
Also, because you have LooksMenu installed, do know that action should be taken when it is used alongside Buffout 4. Head to "(Fallout 4) > Data > F4SE > Plugins > Buffout4 > config.toml" and set the F4EE patch to true, which will fix some LooksMenu bugs. Do note however that this should only be enabled if you are running v1.6.20 of LooksMenu as that is the only version the patch will work with.
Hi, First things, I am not good at this sort of stuff, but, I can follow directions, mostly. A few questions, I have a recurring CTD which occurs at or in connection with fast travel, I get Crash Logs and they appear where they are meant to be, I run Crash Analyser and it runs, and runs, and runs, and there never appears to be any result so I can't even begin to learn what's happening. Any clues as how long it takes to analyse a Crash Log in the Analyser and where the output should end up would be appreciated as a first step. I have tried searching for AUTOSCAN output but nothing. Anyway thanks very much in advance.
CLASSIC should scan a log almost instantly. If it doesn't, something isn't working right. When CLASSIC does successfully scan a log, the autoscan result will be an .md file placed in the same folder as the crash log itself. It would be worth making sure that the crash log is in the default location as that is where the scanner is looking for it (in your Documents > My Games > Fallout4 > F4SE). Otherwise, in CLASSIC you will have to click "Browse Folder" where it says "Custom Scan Folder" and select the folder where the crash log is stored.
If it still won't work, post the full crash log here using spoiler tags (instructions at the top) or Pastebin and I can take a look at it.
Thanks for getting back so quickly. I've done a quick check on directory pointers and it seems to be correct, but no *.MD file, anywhere. I'm starting to suspect this might be a NG issue as everything worked fine prior to me (foolishly) upgrading, should've taken the time to read more about the downsides. I have the BuffoutNG version but am not sure it's loading correctly so I will do some work to see if that's a likely culprit before I upload any files. Thanks again. Speak soon.
OK, so I have thrown up my hands in defeat, nothing I have tried will create a Autoscan.md file, so I now post, fingers crossed, a Crash Log in Pastebin, user KayyGee, title FO4 Crash Log. https://pastebin.com/PpgHB6eF.
I tried to use Pastebin, but their "SMART" filter blocked it, even though it's just a plaintext log (rolls eyes).
Anyway, at the top where it says "SUSPECT FOUND!" next to various types of crashes such as the "Mesh (NIF) Crash" are what you want to pay attention to. Each crash type it lists there (6 in total) are possible problems leading to this crash you are having. Solutions to those crash types can be found on the Buffout 4 Dictionary.
If you scroll down to where it says "Scanning The Log For Specific Suspects..." it lists Outcasts and Remnants as well because the scanner found that in the log, which sometimes indicates that mod in particular caused the crash so I would recommend doing something with it such as uninstalling it and trying to run the game again. If you do uninstall a mod, just make sure to backup your saves first.
16820 comments
Here is how to write spoiler tags:
[spoiler]
It just works.
[/spoiler]
Will format as:
My game CTD after leaving the vanilla Basment in Sanctuary Hills.
Any ideas?
https://pastebin.com/e06EJ2PG
It seems i dont get any classic crash file created?!
Thank you!
https://pastebin.com/F02m2Nkb
crash-2025-07-22-04-05-19.log - Pastebin.com
https://pastebin.com/4qm46wuX
https://pastebin.com/jdxtM6tD
Also, because you have LooksMenu installed, do know that action should be taken when it is used alongside Buffout 4. Head to "(Fallout 4) > Data > F4SE > Plugins > Buffout4 > config.toml" and set the F4EE patch to true, which will fix some LooksMenu bugs. Do note however that this should only be enabled if you are running v1.6.20 of LooksMenu as that is the only version the patch will work with.
KG
If it still won't work, post the full crash log here using spoiler tags (instructions at the top) or Pastebin and I can take a look at it.
Thanks for getting back so quickly. I've done a quick check on directory pointers and it seems to be correct, but no *.MD file, anywhere. I'm starting to suspect this might be a NG issue as everything worked fine prior to me (foolishly) upgrading, should've taken the time to read more about the downsides. I have the BuffoutNG version but am not sure it's loading correctly so I will do some work to see if that's a likely culprit before I upload any files. Thanks again. Speak soon.
KG
PrivateBin Paste
I tried to use Pastebin, but their "SMART" filter blocked it, even though it's just a plaintext log (rolls eyes).
Anyway, at the top where it says "SUSPECT FOUND!" next to various types of crashes such as the "Mesh (NIF) Crash" are what you want to pay attention to. Each crash type it lists there (6 in total) are possible problems leading to this crash you are having. Solutions to those crash types can be found on the Buffout 4 Dictionary.
If you scroll down to where it says "Scanning The Log For Specific Suspects..." it lists Outcasts and Remnants as well because the scanner found that in the log, which sometimes indicates that mod in particular caused the crash so I would recommend doing something with it such as uninstalling it and trying to run the game again. If you do uninstall a mod, just make sure to backup your saves first.