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

myrt

Major
17 Badges
Jan 2, 2015
570
138
  • Crusader Kings II: Legacy of Rome
  • Crusader Kings II: The Old Gods
  • Crusader Kings II: The Republic
  • Crusader Kings II: Sons of Abraham
  • Crusader Kings II: Sword of Islam
  • Crusader Kings II
  • Imperator: Rome - Magna Graecia
  • Imperator: Rome
  • Hearts of Iron IV: Expansion Pass
  • Hearts of Iron IV: Death or Dishonor
  • Hearts of Iron IV: Cadet
  • Europa Universalis IV: Common Sense
  • Mount & Blade: Warband
  • Victoria 2
  • Magicka
  • Europa Universalis IV: Art of War
  • Europa Universalis IV
I've been trying to record some timelapses (17 to be exact), but every attempt except the first one, where I accidentally didn't click the record-button, has ended in the game crashing within 1-2 hours, because that's just how lucky I am. After the first few times, I tried letting it run without the screen-recorder, thinking it could be the cause of the crash. I also tried turning down the game speed from 5 to 4 and 5 to 3, but it didn't help, and it went fine the first time, so I don't see why that's the reason.

Any logs or something that could help me out?

vids.png
 
What recording software are you using? Did you try the game with it completely unloaded, rather than just not recording?

After one of these crashes can you start the game right up again and play? Or do you need to reboot, or wait a while before it will start okay?


Please report the temperatures of your CPU and video (GPU)
1/ before starting the game up and
2/ after say 30 minutes' play.
If your PC's vendor has given you no way of reading temperatures, install
SPEEDFAN http://www.almico.com/sfdownload.php
 
I can start the game right away. I use OBS studio. Yes, I closed the process with task manager. I did a reboot a couple of times before trying again, but that didn't change anything as far as I know.

CPU and GPU were both at 32 C before starting the game. After playing for 30 minutes, the T is now 45 for CPU and 42 for GPU (see pic for more info)
I was working while I did this test, so I had like 40 tabs in Chrome up at the moment. The load on the processors was probably a little less the last times I tried
speccy.png
 
Last edited:
The symptoms of crashing only after playing for a period is typical of overheating issues ... but those temperatures are fine, the problem is elsewhere.

Quite where I cannot see, to be honest. I'm still not 100% clear - does it happen the same when OBS Studio is unloaded, or not?

To answer your original question game logs are in documents/paradox/ck2/logs/ . But I'll guess the crash comes from outside the game so they are unlikely to record anything about it.

How about at the end of a dxdiag.txt , anything mentioned about the crashes there? Windows Event Viewer?
 
The symptoms of crashing only after playing for a period is typical of overheating issues ... but those temperatures are fine, the problem is elsewhere.

Quite where I cannot see, to be honest. I'm still not 100% clear - does it happen the same when OBS Studio is unloaded, or not?

To answer your original question game logs are in documents/paradox/ck2/logs/ . But I'll guess the crash comes from outside the game so they are unlikely to record anything about it.

How about at the end of a dxdiag.txt , anything mentioned about the crashes there? Windows Event Viewer?
Windows event viewer gave me this around the time at the crash:
upload_2019-2-22_9-38-46.png


Didn't see any other errors around then
 
I'm still not 100% clear - does it happen the same when OBS Studio is unloaded, or not?

You should try renaming that CEFProcess.exe to something like CEFProcess.NOT to stop it running - see if that helps.