Crash on startup

[c37blader]

Hey AndrewT,

Instead of making my own thread, I am just piggybacking on here since Shiladie and I seem to be having very similar issues. I hope that is okay. I tried doing everything you said, and I cannot launch the game with "disable fullscreen optimizations" ticked. When I launch with that ticked, I get the error below. I can launch with all the other suggested settings (fullscreen, no vsync, 60 fps). I do not have a file called "exceptions.log", so cannot attach. I played a few years and got a month tick crash, so the error.log should be from that.

 

[AndrewT]

Hey AndrewT,

Instead of making my own thread, I am just piggybacking on here since Shiladie and I seem to be having very similar issues. I hope that is okay. I tried doing everything you said, and I cannot launch the game with "disable fullscreen optimizations" ticked. When I launch with that ticked, I get the error below. I can launch with all the other suggested settings (fullscreen, no vsync, 60 fps). I do not have a file called "exceptions.log", so cannot attach. I played a few years and got a month tick crash, so the error.log should be from that.

View attachment 1323883

We always prefer each problem in its own new thread, so I'll move you to your own.

 

[AndrewT]

I cannot launch the game with "disable fullscreen optimizations" ticked. When I launch with that ticked, I get the error below.

That is very unusual, unique perhaps, and may indicate something larger is wrong. You did UNtick everything else in that dialog, especially run as Admin?

Is the crash while playing confined to this one galaxy, or in any other or new one you might play?

DXDIAG is a program you run from the Windows search box on the task bar. After running it will open a window and start collecting info with a progress bar in the lower-left corner. When it completes click the 'save all information' button and save it to a file then attach that file here. IF dxdiag.txt fails to attach here, rename it to dxdiag.log , or zip it up.

 

[c37blader]

Yes, I made sure everything else was unticked (which was already the case).

Every game I have played since 4.0 has monthly tick crashes, and rarely non-monthly tick crashes. They get progressively worse further into the game.

I meant to attach the dxdiag, but I guess it didn't work properly. I tried changing the file extension this time.

 

[c37blader]

Here is another error.log, from a crash that actually gave me the error reporter instead of the usual unresponsive game freeze.

 

[Shiladie]

Every game I have played since 4.0 has monthly tick crashes, and rarely non-monthly tick crashes. They get progressively worse further into the game.

This sounds exactly like what I'm seeing, however I don't see issues with launching with that setting.

 

[c37blader]

Some interesting developments today. I noticed that the FPS cap that I am setting in the launcher settings is being completely ignored. Despite being set to 60, I get FPS between 200 and 300 quite often. Also, I had a game crash today that actually made my entire computer crash and restart, which was a first.

Also, the launcher setting of FPS cap keeps changing itself to 120, seemingly no matter what I do. Every time I open the game, when I check it has set itself to 120.

Another thing I noticed. I enabled VSYNC to see if it would fix crashing, and for some reason the game goes to 60 FPS when I enable VSYNC, despite my refresh rate being 120. When I alt tab out of the game and then back in, it is updating to 120 FPS.

 

[c37blader]

I enabled a framerate cap in RTSS since the game isn't properly framerate capping for whatever reason, and I have not crashed yet. Sample size isn't large enough yet, but I just went 10 years without a crash at 2345-2355 which is very unusual given my previous experiences. If I actually finish this game without crashing, I'll start another right away to try to test further.

 

[Shiladie]

I had a game crash today that actually made my entire computer crash and restart, which was a first.

I had that happen once soon after 4.0 but not in a couple updates, so I'd dismissed it as early instability
In my driver I just set the max framerate for the game to 60, as well as setting power to guarantee performance. Unfortunately I still crashed within a year of loading a save.

 

[AndrewT]

Some interesting developments today. I noticed that the FPS cap that I am setting in the launcher settings is being completely ignored. Despite being set to 60, I get FPS between 200 and 300 quite often.

You need to disable Vsync AND cap the refresh rate in the launcher-game settings menu. AND If GeForce Experience or the Nvidia app are running, exit them before starting the game.

 

[c37blader]

You need to disable Vsync AND cap the refresh rate in the launcher-game settings menu. AND If GeForce Experience or the Nvidia app are running, exit them before starting the game.

That is not the problem. I have an AMD card for one, so I do not have geforce experience running. When I launch the game with the FPS cap, it is not capped in game, confirmed by steam overlay, rtss, and AMD software. All 3 show the fps sky rocketing way past the value it is set to in the launcher settings.
I launch with these settings:

In game it goes up to 3-4 thousand FPS in main menu:

Top right FPS is from RTSS. I checked with AMD software and Steam overlay, all 3 tell me the same thing, which is that Stellaris is not being frame capped, despite me having it set. And every time I reopen Stellaris, the settings get changed back to 120 FPS:

 

[AndrewT]

I have an AMD card for one, so I do not have geforce experience running. When I launch the game with the FPS cap, it is not capped in game, confirmed by steam overlay, rtss, and AMD software. All 3 show the fps sky rocketing way past the value it is set to in the launcher settings.

I forget what AMD's equivalent of Experience is, Catalyst or something - that's not running? Any other such utilities like MSI?

If not, Then I guess we have a game bug there - that really should work!

 

[c37blader]

Well there is something called AMD Software: Adrenaline Edition, but I don't even think that I can turn that off. I don't see a way to close it, I can hide it from system tray but that doesn't close it. I think if I reinstall my driver I can do the minimal install to avoid that software. Should I try that?

 

[c37blader]

MSI Gaming Intelligence is also running.

 

[c37blader]

I went ahead and uninstalled MSI Gaming Intelligence, and reinstalled my driver with the "minimal" install to get rid of the AMD software. The exact issue I described above persists. The launcher settings keep getting reset to 120 every time I open the game, and the FPS in game is not being capped despite being set to 60 FPS.

 

[c37blader]

Going to sleep, but I got up to year 2400 with no crashes while playing with a framerate capped via RTSS. That is 55 years of late game Stellaris without a single crash. This save was crashing every 3 years or less before I enabled RTSS frame cap, so I am optimistic that the frame cap has fixed things for me. I have no idea why the games own frame cap settings don't work for me, but that seems to be the issue. Or at least, one of the issues, as the game obviously shouldn't be crashing when frame rate isn't capped...

I will continue playing, but won't have much time tomorrow so likely no updates until Wednesday or later.

 

[AndrewT]

Please make a new Windows user profile, log into Windows with that, and go into Startup apps and disable everything, and reboot.

Then run the launcher-game under that - do you get the same problem, with the game being unable to cap the refresh rate?