• 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.
Dec 13, 2024
8
1
Good day everyone,

Since 1.8.6 my game has been crashing randomly, and its quite frustrating. I don't have any mods installed, and have verified, uninstalled and even deleted the Victoria file from my documents but the game still crashes. Ive attached the most recent report.

If anyone can point me in the right direction that would be greatly appreciated.

Thank you.
 

Attachments

  • error.log
    32,6 KB · Views: 0
  • debug.log
    302 KB · Views: 0
  • system.log
    955 bytes · Views: 0
  • game.log
    82,5 KB · Views: 0
  • 1Like
Reactions:
When looking at the error log this shows up

[jomini_script_system.cpp:270]: Script system error! Error: Event target link 'owner' returned an invalid object Script location: file: common/political_movements/00_ideological_movements.txt line: 1444
 
Hi! Could you please attach the crash folder that includes minidump from "Documents/Paradox Interactive/Victoria 3/crashes"?
Error logs usually don't contain any data that is relevant to the crash.
 
Hi! Here it is
 

Attachments

  • minidump.dmp
    38,2 MB · Views: 0
  • exception.txt
    1,9 KB · Views: 0
  • meta.yml
    1.004 bytes · Views: 0
  • pdx_settings.json
    1,9 KB · Views: 0
  • debug.log
    863,7 KB · Views: 0
  • error.log
    25,9 KB · Views: 0
  • game.log
    150,5 KB · Views: 0
Hi! Could you please attach the crash folder that includes minidump from "Documents/Paradox Interactive/Victoria 3/crashes"?
Error logs usually don't contain any data that is relevant to the crash.
Hello, heres another crash that just happened 30 seconds after I opened the game
 

Attachments

  • exception.txt
    2,6 KB · Views: 0
  • meta.yml
    723 bytes · Views: 0
  • minidump.dmp
    87,7 MB · Views: 0
  • pdx_settings.json
    789 bytes · Views: 0
  • debug.log
    302 KB · Views: 0
  • error.log
    32,6 KB · Views: 0
  • game.log
    82,5 KB · Views: 0
  • system.log
    955 bytes · Views: 0
1 victoria3.exe ODDLParser::OpenDDLExport::writeValueType (+ 2417597)
@PDX_Sosanna we've seen a few exceptions logs with this first line recently. Can you say what that ODDL or OpenDDL process it, what aspect of the game or Windows it relates to please?
 
@PDX_Sosanna we've seen a few exceptions logs with this first line recently. Can you say what that ODDL or OpenDDL process it, what aspect of the game or Windows it relates to please?
Here's a third
 

Attachments

  • exception.txt
    2,6 KB · Views: 0
  • meta.yml
    723 bytes · Views: 0
  • minidump.dmp
    87,7 MB · Views: 0
  • pdx_settings.json
    789 bytes · Views: 0
  • debug.log
    302 KB · Views: 0
  • error.log
    32,6 KB · Views: 0
  • game.log
    82,5 KB · Views: 0
  • system.log
    955 bytes · Views: 0
Crash number 4:
 

Attachments

  • exception.txt
    2,6 KB · Views: 0
  • meta.yml
    723 bytes · Views: 0
  • minidump.dmp
    87,7 MB · Views: 0
  • pdx_settings.json
    789 bytes · Views: 0
  • debug.log
    302 KB · Views: 0
  • game.log
    82,5 KB · Views: 0
  • error.log
    32,6 KB · Views: 0
  • system.log
    955 bytes · Views: 0
@AndrewT These 2 users have 2 completely distinct crash issues. Exception files on Windows and Linux are mangled and usually won't give much useful data.

@FrostbiteKelvin Your CTD is known, sadly it couldn't be fixed in time for 1.8.6 release. It is likely going to get fixed in the next patch after the holidays.

@DrinkMoeWater1337 Has the game worked smoothly before 1.8.6 patch? It's a bit odd as I can't find anything similar in our databases. I have reached out to our programmers and will add the issue to our bug tracker if it doesn't turn out to be a setup issue.
 
@AndrewT These 2 users have 2 completely distinct crash issues. Exception files on Windows and Linux are mangled and usually won't give much useful data.

@FrostbiteKelvin Your CTD is known, sadly it couldn't be fixed in time for 1.8.6 release. It is likely going to get fixed in the next patch after the holidays.

@DrinkMoeWater1337 Has the game worked smoothly before 1.8.6 patch? It's a bit odd as I can't find anything similar in our databases. I have reached out to our programmers and will add the issue to our bug tracker if it doesn't turn out to be a setup issue.
To be honest, I don't remember it crashing at all before 1.8.6 although my hours were limited. Should I try rolling back?
 
@AndrewT These 2 users have 2 completely distinct crash issues. Exception files on Windows and Linux are mangled and usually won't give much useful data.

@FrostbiteKelvin Your CTD is known, sadly it couldn't be fixed in time for 1.8.6 release. It is likely going to get fixed in the next patch after the holidays.

@DrinkMoeWater1337 Has the game worked smoothly before 1.8.6 patch? It's a bit odd as I can't find anything similar in our databases. I have reached out to our programmers and will add the issue to our bug tracker if it doesn't turn out to be a setup issue.
TYVM... I have 2 games waiting to be finished
 
Hello! Not sure if this matches but I have been having similar crashes in the beginning of the game. Playing 100% vanilla with a fresh install
 

Attachments

  • debug.log
    241,2 KB · Views: 0
  • error.log
    1.000 bytes · Views: 0
  • game.log
    52,5 KB · Views: 0
  • system.log
    939 bytes · Views: 0
  • exception.txt
    2,1 KB · Views: 0
  • meta.yml
    1.004 bytes · Views: 0
  • minidump.dmp
    48,3 MB · Views: 0
  • pdx_settings.json
    1,9 KB · Views: 0
The only issue I see in your files is the CPU is one of the models that is affected by the well-known Intel hardware faults. Have you updated your bios in, sya, the last month or so? If not please try that and see if it helps.

If that doesn't help or apply here, 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.