Many crashes since the last two updates

[Kunnlan]

Hello,

Since the last two updates my game crashes regularly in the middle of the game. I don't know why, I play without any mod, I installed and uninstalled my game completely several times + deleted what remained manually, I never had this problem before. I have all the DLC, and the game is in French.
My graphics card drivers are up to date, and I play under Windows.

 

[Kunnlan]

It's still an error "Unhandled exception C0000005"

 

[Kunnlan]

New bug report today, if that helps:

 

[AndrewT]

Not really sure what could be causing that log, where there is no source found for the exception at the start.

Is there any particularaction or event that seems to trigger the crash?

Once it happens can you reload the game and save and carry on? Or does it crash at that point again?


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 it fails to attach here, rename it to dxdiag.log

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

 

[Kunnlan]

Hello,

first of all thank you very much for your interest in my problem.

There is no event or date that seems to cause the crashes, it's purely random.

Yes, I can reload my save, replay and save again, it won't crash at the same time.

I am sending you the requested documents as an attachment.

Sorry, despite several attempts and even renaming the file it is impossible for me to send you Dxdiag.
I can perhaps give you some information if it is to have my configuration:


Processor: AMD Ryzen 7 1700X Eight-Core Processor (16 CPUs), ~3.4GHz
Memory: 16384MB RAM
NVIDIA GeForce RTX 2070
Windows 10 Famille 64-bit

 

[AndrewT]

despite several attempts and even renaming the file it is impossible for me to send you Dxdiag.

dxdiag.log out to work, but you could try zipping it up instead.


From the files attached, 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.

Does that help at all?

 

[Kunnlan]

So I followed all your instructions, but unfortunately it didn't work. I had 2 crashes. However, I noticed that my game goes much faster, deactivating Vsync is really a good idea.



I'm in the process of relaunching a new game, you never know it might work, I'll keep you informed.

 

[Kunnlan]

My new game also crashed, after 18 years in the game. I give you in compressed format the complete report in the Stellaris spit file.

EDIT : Since I'm the only one having this problem, I decided to completely format my computer. I hope this is enough, I'll keep you posted.

 

[DrFranknfurter]

I just wanted to say you aren't the only one suddenly experiencing crashes.

I just had my first crash in 3 years (from the date on the other two crash reports), the crash reporter crashed trying to send the report but I have the same exception:
C0000005

 

[AndrewT]

I just wanted to say you aren't the only one suddenly experiencing crashes.

I just had my first crash in 3 years (from the date on the other two crash reports), the crash reporter crashed trying to send the report but I have the same exception:
C0000005

Your exceptions log is different to the OP's so you probably have a different crash cause.

I think your Nvidia driver is old, so please update it to June 2024 https://www.nvidia.com/Download/index.aspx?lang=en-us


THEN 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.

 

[DrFranknfurter]

Your exceptions log is different to the OP's so you probably have a different crash cause.

I think your Nvidia driver is old, so please update it to June 2024 https://www.nvidia.com/Download/index.aspx?lang=en-us


THEN 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.

Thank you for the reply, I will try that and post if I have more crashes.

 

[Kunnlan]

Hello,

So I did a complete format of my computer, and the problem is still not resolved.

I had a first crash in 2235, an Unhandled exception C000001D error. I didn't have disable fullscreen optimization, so I did that then restarted my game. I was able to play it for a few years and crashed again, this time an Unhandled exception C0000005.

So I'm going to repost everything for you like last time, but with a complete format + a clean reinstallation with updated drivers the problem most likely comes from the game.

 

[Kunnlan]

I may have an idea to submit to you. I think the problem is with the Nanite interdictor warship, for 2 reasons:

-it comes regularly in the error report
-in the French version of the game, when viewing the ships of a fleet in the fleet designer, the Nanite Interdictor is bugged. It seems that the localization is not working, it appears under the name Nanite_Interdictor, and in description I have SHIP_GRAPHICS_NANITE_INTERDICTOR_DESC .

I've never had a crash problem with this game even though I play it a lot, but with the latest The Machine Age update I'm crashing.
And it just so happens that this update touches on the Nanite Interdictor.

I'm even going to go further in my theory: an AI Empire must have an event that allows you to obtain a Nanite Interdictor. This being bugged, the game becomes unstable and crashes. But I'm not sure, because I believe that the nanite interdictor event takes at least 40 years after the discovery of the anomaly.

I'll give you my last save if it helps, I have all the DLC

 

[AndrewT]

I had a first crash in 2235, an Unhandled exception C000001D error. I didn't have disable fullscreen optimization, so I did that then restarted my game. I was able to play it for a few years and crashed again, this time an Unhandled exception C0000005.

Those two codes are completely unrelated, and can only really come from two separate causes if in code; however a hardware fault such as bad memory or CPU could account for them. @jpd can comment more knowledgeably on that matter.

The first one means Illegal Instruction, that is that somehow a line of code in the game contains a command not valid for this CPU. It is pretty close to impossible that this can happen! It would have to get through the compiler process somehow. The second one is normal for a code error. But in neither case is a crash entry made in dxdiag, which tends to point to something outside the game.

Look in your Windows Event Viewer at the time if these crashes; are there any ERROR or WARNING entries there at those times?

 

[jpd]

Both exceptions happen while the code is processing functions calls inside the physfs library package (https://icculus.org/physfs/docs-devel/html/). This library is part of the game engine and is responsible for processing the main data file and merge them with files in mods that are enabled.

It's highly unusual to have crashes inside that library package, especially an illegal instruction crash.

The crash points for both crashes are actually very close together. According to the stack trace, the preceding call to the final crash point is PHYSFS_swapSLE64 (+ 18804911) for both. The first one then has PHYSFS_swapSLE64 (+ 18804758) as final call before the crash, while the other has PHYSFS_swapSLE64 (+ 18804882). These two points are only some 125 memory locations apart.

Do you have a virus scanner active, that might be interfering with this library (as the function of this library *is* to process files on disk).

 

[Kunnlan]

Those two codes are completely unrelated, and can only really come from two separate causes if in code; however a hardware fault such as bad memory or CPU could account for them. @jpd can comment more knowledgeably on that matter.

The first one means Illegal Instruction, that is that somehow a line of code in the game contains a command not valid for this CPU. It is pretty close to impossible that this can happen! It would have to get through the compiler process somehow. The second one is normal for a code error. But in neither case is a crash entry made in dxdiag, which tends to point to something outside the game.

Look in your Windows Event Viewer at the time if these crashes; are there any ERROR or WARNING entries there at those times?

So for Windows Event Viewer yes there is a report. To start today at 00:25 I had a new crash and it appears in the error section, I also give you the exception file at the same time :

Nom du journal :Application
Source : Application Error
Date : 10/07/2024 00:25:49
ID de l’événement :1000
Catégorie de la tâche 100)
Niveau : Erreur
Mots clés : Classique
Utilisateur : N/A
Ordinateur : DESKTOP-8K14CQV
Description :
Nom de l’application défaillante stellaris.exe, version : 1.0.0.0, horodatage : 0x666b18ca
Nom du module défaillant : unknown, version : 0.0.0.0, horodatage : 0x00000000
Code d’exception : 0xc0000005
Décalage d’erreur : 0x0000000000000003
ID du processus défaillant : 0x219c
Heure de début de l’application défaillante : 0x01dad24db94333cc
Chemin d’accès de l’application défaillante : C:\Program Files (x86)\Steam\steamapps\common\Stellaris\stellaris.exe
Chemin d’accès du module défaillant: unknown
ID de rapport : 1856f442-e541-4f36-bd7d-a3de6761d948
Nom complet du package défaillant :
ID de l’application relative au package défaillant :
XML de l’événement :
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>100</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2024-07-09T22:25:49.0115632Z" />
<EventRecordID>679</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>DESKTOP-8K14CQV</Computer>
<Security />
</System>
<EventData>
<Data>stellaris.exe</Data>
<Data>1.0.0.0</Data>
<Data>666b18ca</Data>
<Data>unknown</Data>
<Data>0.0.0.0</Data>
<Data>00000000</Data>
<Data>c0000005</Data>
<Data>0000000000000003</Data>
<Data>219c</Data>
<Data>01dad24db94333cc</Data>
<Data>C:\Program Files (x86)\Steam\steamapps\common\Stellaris\stellaris.exe</Data>
<Data>unknown</Data>
<Data>1856f442-e541-4f36-bd7d-a3de6761d948</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

And that's all I found. I have meticulously inspected each log entry in the error and warning categories and this is all I have, I hope it can still help you.

Both exceptions happen while the code is processing functions calls inside the physfs library package (https://icculus.org/physfs/docs-devel/html/). This library is part of the game engine and is responsible for processing the main data file and merge them with files in mods that are enabled.

It's highly unusual to have crashes inside that library package, especially an illegal instruction crash.

The crash points for both crashes are actually very close together. According to the stack trace, the preceding call to the final crash point is PHYSFS_swapSLE64 (+ 18804911) for both. The first one then has PHYSFS_swapSLE64 (+ 18804758) as final call before the crash, while the other has PHYSFS_swapSLE64 (+ 18804882). These two points are only some 125 memory locations apart.

Do you have a virus scanner active, that might be interfering with this library (as the function of this library *is* to process files on disk).

My only active antivirus is the basic one built into Windows 10, nothing else.

I would like to add a clarification that might be useful. When The Machine Age expansion came out, I was able to play several games without any problems, going far with over 200 years in the game.

My crashes started when update 3.12.4 was released i think.

 

[AndrewT]

From what @jpd says I am probably wrong, it may well be a game problem - or something interfering with it.

As you have Windows Defender, go into ransomware and add stellaris.exeto the Apps Allowed Through list in Controlled Folder Access there.

 

[Kunnlan]

Hello,

I just checked my ransomware protection was not activated, so the problem can't come from there either unfortunately.

I wanted to check a theory, I was playing a new game in version 3.12.3, which I was able to install thanks to the beta option available through Steam. I have the same starting parameters as for my old game, with the same custom faction

I'm in 2258, and I haven't had a single crash!
I'm going to continue my game, but this seems to confirm my theory: the problem comes from a patch, either 3.12.4 or the current patch, 3.12.5.

 

[Wibblebeak]

I've have also had quite a few crashes since the last couple of patches (and minimizing and freezing issue as well).

 

[Kunnlan]

Hello,

I continued my game a bit in 3.12.3 to see if there were still any crashes, and I was able to play 113 years without any problems. So this is most likely a game bug.

So I know it's July-August, in most countries it's the holidays and I wish the whole Paradox team to make the most of it.
But once the working time returns, please correct this bug in the next updates so that the loyal player that I am can continue my adventure with this superb game.