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

palmus

Colonel
87 Badges
May 7, 2004
870
83
  • Hearts of Iron 4: Arms Against Tyranny
  • Hearts of Iron IV Sign-up
  • 500k Club
  • Hearts of Iron IV: Together for Victory
  • Victoria 2
  • Victoria 2: Heart of Darkness
  • Victoria: Revolutions
  • Victoria 2: A House Divided
  • Crusader Kings II: Holy Knight (pre-order)
  • Hearts of Iron IV: Expansion Pass
  • Europa Universalis 4: Emperor
  • Europa Universalis III Complete
  • Hearts of Iron Anthology
  • Cities: Skylines - Parklife
  • Europa Universalis IV: Rule Britannia
  • Crusader Kings II: Sword of Islam
  • Hearts of Iron III
  • Divine Wind
  • Heir to the Throne
  • Crusader Kings II: Sons of Abraham
  • Crusader Kings II: The Republic
  • Crusader Kings II: Rajas of India
  • Crusader Kings II: The Old Gods
  • Crusader Kings II: Legacy of Rome
  • Cities in Motion
  • Crusader Kings II: Way of Life
  • Europa Universalis IV: Pre-order
  • Europa Universalis IV: El Dorado
I have the same problem with CK as Vicky. I/we get CTDs all the time for the clients or the hosts computer restarts.
Got exactly the same problem with all my paradox games and getting really sick about it. I thought that maybe my computer is the problem.
I have a 2400+ with 512mb RAM and a Geforce 2 with 32mb and I got the latest drivers for all my hardware and we shut down everything but CK/vicky/hoi/eu2, and we use no kind of firewall.
If we start a new game, it CTD about every 15minutes and then it gets a random CTD about evrey 2 hours. What shall I/we do? getting really desperat :(
 
One player CTD:ing once in two hours is very good rate. Also, use Slow speed when starting the game, as AI is Ultra-active at the start of Scenario (puts ministers in place, declares wars, takes claims etc etc...).
 
Byakhiam said:
One player CTD:ing once in two hours is very good rate. Also, use Slow speed when starting the game, as AI is Ultra-active at the start of Scenario (puts ministers in place, declares wars, takes claims etc etc...).

well, we are running in below normal mode.
I think that it should run as good in very slow mode as in extremly fast, because it's very unnecessary to have all those speed modes then?

edit: not just one player ctds, both clients ctds or just the host. sometimes the hosts computer restarts and we've tried different hosts.
 
Last edited:
Turn off all processes, except the bare minimum needed to run Windows. Turn off for example:
-all instant message software
-anti-virus software
-firewall software
-Microsoft autoupdater
-other autoupdater
-all office programs that "lurk"
-directcd
-rename the AVI folder AVI_BACK (to keep AVI from turning on)

and then launch CK or Victoria or whatever. Should improve stability a lot.
 
Jarkko Suvinen said:
Turn off all processes, except the bare minimum needed to run Windows. Turn off for example:
-all instant message software
-anti-virus software
-firewall software
-Microsoft autoupdater
-other autoupdater
-all office programs that "lurk"
-directcd
-rename the AVI folder AVI_BACK (to keep AVI from turning on)

and then launch CK or Victoria or whatever. Should improve stability a lot.

actually, I've turned all those thing off and the stability didn't improve that much.
If you have to do all this stuff, they should put it on the box :p
 
Are you playing a new 1.03A 1066 scenario? If so, you're likely falling victim to a small error in the scenario file. Open your latest save game file and search for the text "dyn = 0 ". You will probably find one (or possibly more) characters with this incorrect dynasty. Replace all instances with "dyn = 708 " (which is the dynasty that is intended for this character) and then save. Most likely this will resolve your issue until an official fix is posted.
 
palmus said:
If you have to do all this stuff, they should put it on the box :p
You *don't* have to do it, especially if you have a state-of-the-art computer :) But in multi-play one wants to minimize the causes of a ctd because if one generally have a crash in 12 hours, with a few of players that means somebody is crashing every two hours.
 
MrT said:
Are you playing a new 1.03A 1066 scenario? If so, you're likely falling victim to a small error in the scenario file. Open your latest save game file and search for the text "dyn = 0 ". You will probably find one (or possibly more) characters with this incorrect dynasty. Replace all instances with "dyn = 708 " (which is the dynasty that is intended for this character) and then save. Most likely this will resolve your issue until an official fix is posted.

no we were playing 1.02.
 
Jarkko Suvinen said:
You *don't* have to do it, especially if you have a state-of-the-art computer :) But in multi-play one wants to minimize the causes of a ctd because if one generally have a crash in 12 hours, with a few of players that means somebody is crashing every two hours.

why can't it just... work?

edit: a crash in every 12 hours would be really good.
a crash in every 2 hours is unacceptable.
:confused:
 
Last weekend, me and a friend wanted to play CK at LAN.. we attempted many times, but it crashed every 2 hours.. worst part was that the game got destroyed when trying to load, autosave, normal save games, or playerdrop save games.. so we gave up after playing typically 4 hours on a game, then having to restart because we were unable to load :/

We didnt find the reason why it crashed sadly. We used version 1.03a over LAN with new computers with nothing else running.
 
Goose said:
Last weekend, me and a friend wanted to play CK at LAN.. we attempted many times, but it crashed every 2 hours.. worst part was that the game got destroyed when trying to load, autosave, normal save games, or playerdrop save games.. so we gave up after playing typically 4 hours on a game, then having to restart because we were unable to load :/

We didnt find the reason why it crashed sadly. We used version 1.03a over LAN with new computers with nothing else running.


I know, I have a far better computer then are required by the minimum requirements so it should run properly, but it won't.
We have to beg to Johan or something :p
 
Until now I have played with my son and nephew some 11 hours CK MP over LAN.

Host machine: 1.8 GHz, 512MB memory, XP Home
Client machine: 800 MHz, 512MB memory, XP Home

About 6 hours on 1.02, and 5 hours on 1.03a. *No* crashes so far (altough as precaution me and my nephew edited today the "0 dynasty" -thingy in 1085 to avoid crashes).

On Internet I have seen on 1.03a one over 2 hour 2-player session with no crashes, and one 3 hour 5-player session with one crash.

If people are having problems around about 1090 (playing 1066 campaign in SP or MP) with 1.03, they should take a lok at the sticky thread in General forum. They actually do stick the important threads for some reason...
 
Jarkko Suvinen said:
Until now I have played with my son and nephew some 11 hours CK MP over LAN.

Host machine: 1.8 GHz, 512MB memory, XP Home
Client machine: 800 MHz, 512MB memory, XP Home

About 6 hours on 1.02, and 5 hours on 1.03a. *No* crashes so far (altough as precaution me and my nephew edited today the "0 dynasty" -thingy in 1085 to avoid crashes).

On Internet I have seen on 1.03a one over 2 hour 2-player session with no crashes, and one 3 hour 5-player session with one crash.

If people are having problems around about 1090 (playing 1066 campaign in SP or MP) with 1.03, they should take a lok at the sticky thread in General forum. They actually do stick the important threads for some reason...

must be some weird network settings or something.
It crashes every 30minutes for me.
 
1.03b is even more stable. Today we played 3 hours in one go without crashes, altough after that we had three crahses in two hours. First with 5 people, then with 4. 2 players from Europe (Finland actually), 3 from USA.
 
Jarkko Suvinen said:
1.03b is even more stable. Today we played 3 hours in one go without crashes, altough after that we had three crahses in two hours. First with 5 people, then with 4. 2 players from Europe (Finland actually), 3 from USA.

yeah okay.
anyway, I think it's really bad that it won't work properly.