• We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.

AlltheG

Recruit
Oct 26, 2024
4
0
My game has suddenly started crashing after a couple of minutes of loading for the last few days. It does not appear to be at a specific date or with a specific country or a specific save game, as I have tried all different. I've completely uninstalled and reinstalled (following a few other posts I found on the topic) but nothing has helped.

No mods but a PC in need of an upgrade, but, no problems in other games. I've added a few of the exception files (not all of them, as they all appear to show the same thing?).

Thanks for any help.


Edit - Actually, this is only happening in new games. I loaded an older save game and it was fine.
 

Attachments

  • exception.txt
    1,9 KB · Views: 0
  • exception.txt
    1,9 KB · Views: 0
  • exception.txt
    1,9 KB · Views: 0
  • exception.txt
    1,9 KB · Views: 0
  • exception.txt
    1,9 KB · Views: 0
Last edited:
Right click on eu4.exe , properties, compatibility. Tick "disable fullScreen optimisations" untick every other box in that dialog, Apply and exit.

Edit settings.txt to say:

refreshRate=60
fullScreen=yes
borderless=no

vsync=no

Then in the launcher Game Settings menu, select fullScreen display mode.

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.

Please attach here your Documents/Paradox Interactive/Europa Universalis IV/settings.txt and pdx_settings.txt .
From your Documents/Paradox Interactive/Europa Universalis IV/logs/ folder, attach here system.log , error.log .
 
Thank you but that didn't help. Attached exceptions again.

I have run a few other tests and I can say that:

1) My game is Oirat, I've run a few different saves (restarted at least 6 different times) and it always crashes between 1448-1452 (ish) - it lets me play the first 4 years without an issue but then crashes, no specific date, event, menu etc but that time frame. The only thing in common is that I am at war with Ming and captured Beijing.
2) It doesn't crash when I leave the game paused (I left it for 20 minutes and nothing, then as soon as I unpause it always crashes within a minute).
3) My current save is June 1452 and it doesn't make it to August 1452
4) I have tried a test Ottomans & Castille game and the same, it lets me get to (slightly later) - 1454 (ish) and it crashes around this time.
5) I loaded an older save from late 1500's (as Oirat) and there are no problems.
6) Edit - I've also started a game as Oirat in 1453 and it played fine until 1470, no crashes at all.

Therefore, I assume that is date specific and not settings?
 

Attachments

  • exception.txt
    1,9 KB · Views: 0
Last edited:
I had a look at your save. It is one of the common crashes in the current version. It happens when a country gets annexed which has a subject who has its independence supported. In your case the Ottomans are about to annex Byzantium which has Athens as a Pronoia vassal who has its independence supported by Karaman and Naples:
1730038480225.png

For reference, here is the stacktrace when letting your save crash on Linux:
Code:
  ./eu4                          ( CSupportIndependence::OnDisable()         + 0x24  )  [0x1698e22]
  ./eu4                          ( CDependency::OnDisable(bool, bool)        + 0xb2  )  [0x169b368]
  ./eu4                          ( CDependency::Transfer(CCountryTag, CCountryTag)  + 0x21  )  [0x169b22d]
  ./eu4                          ( CCountry::ClearRelations(CCountryTag)     + 0x934 )  [0x103c766]
  ./eu4                          ( CCountry::NotifyLostLastProvince(CCountryTag)  + 0x7f0 )  [0x103d830]
  ./eu4                          ( CProvince::SetOwner(CProvince::SSetOwnerParameters const&)  + 0xf8e )  [0x1646c84]
  ./eu4                          ( CProvince::Conquer(CCountryTag, CEU3Date const&, char const*, bool, SConquerParams const&)  + 0x270 )  [0x165223e]
  ./eu4                          ( CCountry::Annex(CCountryTag, bool, bool, bool, bool, bool, bool)  + 0xad8 )  [0xfced22]
  ./eu4                          ( CPeaceOffer::Execute_Annex(CArray<std::pair<CCountryTag, CCountryTag> >&)  + 0x45a )  [0x15b6bb0]
  ./eu4                          ( CPeaceOffer::Execute()                    + 0x167b)  [0x15b2497]
  ./eu4                          ( CRequestPeaceAction::ExecuteDerived() const  + 0xb06 )  [0x1256c6e]
  ./eu4                          ( CDiplomaticAction::Execute() const        + 0x99  )  [0x11ad4ef]
  ./eu4                          ( CDiplomaticActionCommand::Execute() const  + 0x4cc )  [0x11afda8]
There are a bunch of bugreports about this crash. It seems to be much more frequent on macOS than on windows, but I have seen a few cases on windows as well. The only workaround which I know which does not involve console commands would be to revert back to version 1.37.2. But there is a small chance that this could cause other issues.
 
Strange that it keeps happening on virtually every game that I play though!
It might be that the crash is more likely on some systems. It is a segfault, so eu4 is trying to access a part of the memory which is not assigned to eu4. Maybe it is using a pointer which points to memory which eu4 released shortly before, but on systems with little free RAM it is likely that eu4 got assigned that address again, so it doesn't crash on those systems. Or maybe it is reading beyond the memory which is assigned to it, but on systems with a lot of free RAM it is likely that the memory afterwards is also assigned to eu4(because the OS tries to keep the memory which is assigned to a program close together) so it doesn't crash on those systems.

But it could also be that you were just the one unlucky person who got the crash most often on windows. In that case it is unlikely that it happens again in your next campaign