Running as Background Process. Please, help. Please.

[HeavyArmour13]

Welp....I have good news and bad news. The good news is I've got the game running again. The bad news is that I figured out that one of my mods corrupted a line of code causing my problem. The only way to fix it was to move all of my mod files/folders leftover in the steam/Fallout 4 folder to my desktop so when I reinstalled the game it was a clean slate. Now I'm having to go through the tedious process of reinstalling my mods 1 by 1 (all 280+ of them) to get my game back the way it was. I'm pretty sure I know which mod caused the issue, so I'll keep that one off. Getting all my outfits to fit correctly again with no clipping is going to drive me nuts, but I guess it's worth it in the end. I still have a lot I want to do in this game and aren't ready to give it up just yet. I appreciate you guys trying to help.

[Crescent42]

Look at UCO if you don't already have it. It won't fix the clipping fix just the way you want, because I know how you feel about getting it just right lol, but there is an option to make parts of armor or entire clothing sets invisible. Wouldn't have to worry about clipping then.

[Maicol0815]

Same exact problem, hitting it with all 4 at the same time didn't work.
I have tried multiple times to remove the .exe files and it worked once, like 2-4 days ago, but then I haven't been able to repeat it, it won't work anymore.
I have tried removing .ini files multiple times, as well.
Only thing I haven't tried is uninstalling and reinstalling mods, but that's because I did it like 7-9 days ago and I fixed everything ,made a proper load order and have a clean save just to fix some script errors I was having, and I'm not keen on doing it all over again. There are no new mods compared to before I did the clean save, and re-installation of mods, and it worked before then. It actually worked fine after I did that, for a few days, then this happens.
There was one "fix" that I managed to replicate several times, but not in any particular pattern or consistency to make it liable, and now even that doesn't work.
It seems like it's just random if it fixes itself or not, just completely random. But the thing is, I don't think mods are the cause of it. I thought it might be memory, but I have ENB loading 10GB, which isn't even my actual max, so it's not colliding with other programs on my PC.

I'm at my wits end. I recently got back into FO4, from my initial dislike of the game, and I was REALLY excited to get to play it in constant 60 FPS on my new rig.

Tbh, I think it's something wrong with FO4 itself, that only affects some systems, and this problem presented itself after a recent update. That's what I believe.

I took a look in the event viewer as well, but that is incomprehensible to me.

Edited November 2, 2016 by Maicol0815

[HeavyArmour13]

In case it helps anyone else, I think I found out what caused my issue. For some reason (maybe an update because it didn't used to matter) but my SweetFX ReShader was what was causing my game to run in the background. One of the files needs to be changed to work with Windows 10. If you are using a Reshader, one of your files in the Reshade folder is named dxgi.dll. You'll need to change that from dxgi.dll to d3d11.dll

Once I did that, the game loaded again.

[Maicol0815]

In case it helps anyone else, I think I found out what caused my issue. For some reason (maybe an update because it didn't used to matter) but my SweetFX ReShader was what was causing my game to run in the background. One of the files needs to be changed to work with Windows 10. If you are using a Reshader, one of your files in the Reshade folder is named dxgi.dll. You'll need to change that from dxgi.dll to d3d11.dll

Once I did that, the game loaded again.

 

Trying it right now!

 

EDIT: Actually, firstly, my dxgi.dll is in my Fallout 4 folder, not in the ReShade folder, secondly I already have a d3d11.dll file in my Fallout 4 folder.

Removing the other d3d11.dll and renaming dxgi.dll to d3d11.dll didn't work.

 

EDIT 2: As that didn't work I wanted to try removing the ReShade mod all together, but my computer isn't letting me remove the folder...

This is just pissing me off more and more.

Edited November 5, 2016 by Maicol0815

[Crescent42]

Wow, that just sounds like you called FO4 the wrong name during happy time, Maicol. I've been looking around and a lot of the cases that are similar to this one resolve when using F4SE as the main launch option in NMM.

 

I agree, I never had any problems with fo4, NEVER, not even one freeze or stutter or ctd. Nothing! But after the latest update to the vanilla game from steam it went crazy. If you've hit the problem with all 4 possible fixes like you mentioned, and tried the other things that I tried, and have your arguments set right....not sure what else there is to do.

 

There's an option in NMM to uninstall all mods at once. Try that. I know it sucks but really if that's the only option left.....

 

If you Have a bunch of mods that are mixed between being loaded or not save your current mod list as a profile name of your choice, then create a new profile. That will make it so the mods you have installed currently are saved, swap to a clean profile with no mods, and try loading up. If that doesn't do anything you can go back and load your previous profile and all the mods you had before will still be active.

 

 

I've found that alternate start mods cause a fair few issues. Such as currently I can't start a new game. i have to load from an old save and then visit the surgeon to alter my face and such. Maybe an alternate start mod is messing you up. No idea why or why that bad but they are usually the usual suspects in my experience.

 

I know how you feel. I was pretty let down with fo4 on release too and I let it sit for a long time until the right mods came out for it and I could make it the game I wanted. Keep plugging away at it.

[Maicol0815]

Yeah. it managed to start now, but I think that's just because I restarted the PC.
And apparently, I was getting 2 short high pitch beeps now and again, and that has something to do with the motherboard warnign that there's a problem with the memory. So I took them out and put them back, blowing into their sockets for good measure (even-though the mobo is completely new), so I hope that fixed the memory problem, but I wonder if that was the fix I needed. We'll see. I'll come back if it doesn't work, and hope for an angel or God himself to appear and fix this for me.

[Maicol0815]

Forgot to come back, but it didn't work. The double beeps aren't fix and seem to be unrelated.
But Fallout 4 has been running kinda well, only sad part is that the mods that caused me to do a complete reinstallation the first time has stopped working again...
Does Fallout 4 have some sort of problem loading scripts? Or is there some guide to how scripts should be treated, like the corresponding .esp:s should be last in the load order?

[Crescent42]

Guess who's back? ME!

 

I could cuss this game to an early grave.

 

I downloaded Nuka-World today (its on sale btw). Go to start up Fo4 and it runs the f4se for half a second and then it shuts down. It's acting like a crash but it won't even run from steam. At all.

 

Also, today my computer forced a windows 10 update on me. i didn't think that was possible because I thought I had cut any kind of control microsoft had on forcing updates. I don't know what's causing the issues now and I can't seem to get any normal fix to work.

 

EDIT: I forgot to mention I got the second contraptions dlc and vault-tec dlc before the windows update and nothing was affected at all.

 

EDIT: FIXED: It took a total re-install of all files to fix the issue. I tried using old saves and old ini files but no combination of those worked. Everything brand-new and a re-install of all the mods I had.

Edited December 2, 2016 by Crescent42