Random mid-game crash, suspecting mods but all turned off

[Sneakk]

Hi, game crashes at completely random points when unpaused. updated drivers, reinstalled the game, verified the files, tried bug hunting, looking up solutions, and even tried running the game with all mods turned off, and still crashed.

I looked in the error logs and they still seem to mention specifics that seem to be from mods, so I have no idea what's going on there.

 

[Sneakk]

I watched another similar crash report mention having a tiny screen of the game on the top left, which mine had as well, so I applied the fix from that thread to my game as well, still crashed, but without the tiny screen and I seem to have a different error log now, so I'll post that as well now:

 

[AndrewT]

Disabling mods does not remove effects they have already had on a saved galaxy. Do you also get this in a galaxy that's never had any mods used in it?

If so, Right-click on stellaris.exe, properties, compatibility. Tick "disable fullscreen optimizations" untick every other box in that dialog, Apply, and exit.
Then in the launcher Game Settings menu, select the fullScreen display mode, Vsync off, refresh rate 60.


If that doesn't help:
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. Thanks.

Please attach here your Documents/Paradox Interactive/Stellaris/settings.txt and pdx_settings.txt .
From your Documents/Paradox Interactive/Stellaris/logs/ folder, attach here system.log , error.log , exceptions.log

 

[Sneakk]

Disabling mods does not remove effects they have already had on a saved galaxy. Do you also get this in a galaxy that's never had any mods used in it?

If so, Right-click on stellaris.exe, properties, compatibility. Tick "disable fullscreen optimizations" untick every other box in that dialog, Apply, and exit.
Then in the launcher Game Settings menu, select the fullScreen display mode, Vsync off, refresh rate 60.


If that doesn't help:
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. Thanks.

Please attach here your Documents/Paradox Interactive/Stellaris/settings.txt and pdx_settings.txt .
From your Documents/Paradox Interactive/Stellaris/logs/ folder, attach here system.log , error.log , exceptions.log

Hello Mr. Andrew, it seems fate can't keep us separated from one another. I have tested this on a new, modless galaxy ofcourse, but I have also done it on a modded save as well, just to see the effects. the crash logs I have sent are only from the modless start.

the second crash log I've sent you is with the vsync off, 60 refresh rate and the other bobs and bits. I believe I've already posted the dxdiag upfront, but I guess I'll post a new one again.

 

[AndrewT]

System Manufacturer: Gigabyte Technology Co., Ltd.
System Model: Z690 GAMING X DDR4
BIOS: F22 (type: UEFI)
Processor: 13th Gen Intel(R) Core(TM) i9-13900K (32 CPUs), ~3.0GHz

You very likely have the CPU/bios hardware issue discussed here:

Victoria 3 | 12th/13th/14th Generation Intel Processors

Hello all! An update, 12th and 13th Generation Intel Processors are related to a Crash to Desktop (CTD) happening frequently, this is related to architecture changes by Intel and specifically E-cores. We are working with Intel to address these...

forum.paradoxplaza.com

FIRST please check for an updated bios. Then please implement the “Intel Default” option in it, if present.

Good luck!

 

[Sneakk]

You very likely have the CPU/bios hardware issue discussed here:

Victoria 3 | 12th/13th/14th Generation Intel Processors

Hello all! An update, 12th and 13th Generation Intel Processors are related to a Crash to Desktop (CTD) happening frequently, this is related to architecture changes by Intel and specifically E-cores. We are working with Intel to address these...

forum.paradoxplaza.com

FIRST please check for an updated bios. Then please implement the “Intel Default” option in it, if present.

Good luck!

Thanks, this seems a bit over my head but I'll try attempting it on my own before (eventually) running here for help again. just on a limb while I have a hold of you, could you at least help me figure out how to check my bios version and then how to update it? Here's a picture and stats of my motherboard just in case

EDIT: I figured it out! I used chatGPT to help me out and it actually did! I updated it to the latest verison, now to figure out the other bits...

 

[Sneakk]

Thanks, this seems a bit over my head but I'll try attempting it on my own before (eventually) running here for help again. just on a limb while I have a hold of you, could you at least help me figure out how to check my bios version and then how to update it? Here's a picture and stats of my motherboard just in case

View attachment 1210194


EDIT: I figured it out! I used chatGPT to help me out and it actually did! I updated it to the latest verison, now to figure out the other bits...

aaaand I hit a brick wall, I'm in the BIOS, but I'm not exactly sure what to do once I'm there. I've installed XTU as well, but also have no idea what to do once I open it up.

 

[AndrewT]

I am sorry but I cannot help you with the precise steps to update your particular bios, I've never done it myself and I don't have a Gigabyte system in any case.

Please contact Gigabyte support.

 

[Sneakk]

I am sorry but I cannot help you with the precise steps to update your particular bios, I've never done it myself and I don't have a Gigabyte system in any case.

Please contact Gigabyte support.

That's fine, I could probably get someone smarter than me to look at my BIOS issue, any idea with the XTU though?

 

[Sneakk]

With a mix of ChatGPT and calling someone who's smarter than me, I not only seem to have fixed the problem, but actually made all the pdx games run faster! I'll post what I've done here for any future folk who find themselves in my unfortunate position:

1. I updated my BIOS by looking up what version it is through downloading speccy, then finding the manufacturer's website and downloading the proper BIOS update for my specific motherboard, putting it on a USB drive and then updating it in BIOS

2. After a restart, I entered BIOS again and under the Tweaker tab, looked for something along the lines of CPU Vcore or Core Voltage Control, and set it to 1.4V (I could have put it at 1.47, but I wanted to play it extra safe), saved and exited the BIOS.

3. After download the XTU (make sure you restart after installing it, in my case it didn't let me enter the program until I did that), I opened advanced view, and under "advanced tuning", I looked for something called AVX2 Ratio Offset and set it to 10 or 10x or something like that.

And that was pretty much it! preliminary tests show no crashing so far, when in a typical timeframe it would have crashed about 5 times already, and in my particular case, it increased the game's overall speed!