Crash / hard lock

Hello! My crashed Logfiles:

I have an ASUS Z390-E Gaming motherboard, 64GB of Corsair RAM, and an i9-K processor; the board's AI has stably overclocked it to 4700 MHz. According to Intel, the processor can easily withstand temperatures up to 90°C; Intel throttles it immediately if it gets too hot. I’m using a Zotac 4090, and Resizable BAR (Re-Size BAR) is enabled, which reduces the load on the processor. The issue isn't related to the use of multiple threads, as modern games do. I’ve played plenty of other titles for hours without any problems. I build my own systems, so I know when something isn't working right.

The performance spikes mentioned occur initially at the processor level when the game or a save file is loading, but they drop back down shortly after. The i9-K is designed to handle that sort of thing with ease. So, my question is: what exactly is wrong with the programming, or is the game having trouble with a 240Hz 27-inch Asus monitor? Also, the graphics card settings don't cover the full range of possibilities that Zotac's software would allow if given the chance.

I always have TechPowerUp GPU-Z running alongside the game on a second 27-inch monitor. It displays everything—CPU, memory, power spikes, usage levels, and so on. I’ve played games that are far more demanding than Captain of Industry. So, what exactly is the problem? What triggers all these crashes once the game reaches a certain stage of advancement?

braindead8349 [discord] wrote:

The performance spikes mentioned occur initially at the processor level when the game or a save file is loading, but they drop back down shortly...

The spikes I saw did happen during gameplay. Yes, could be autosave, as the game itself and unity are active in parallel 🤔. And ... I was just in middle game when I got the spikes. Could not nail them to a specific behaviour back then (e.g. pathfinding). I just found it odd, that most cores are near idle (esp. with my 2-die 5900X) and the CPU exceeded TDP long enough to overheat.
Usually the even viewers of the OS or even on bios level should help indicating HW related crash issues.

Hi there! So, I have 8 physical cores and 8 virtual ones; the processor usually isn't fully utilized. There was another game, X2—with the new patch, a lot of physics are calculated in real-time, along with everything involving ray tracing and so on. However, thanks to the latest BIOS update from ASUS for my Z390-E Gaming motherboard—specifically by enabling ReBAR—things have sped up quite a bit. Micro-stuttering is significantly reduced when there’s a heavy calculation load. For the system to work properly, though, you need a really good CPU cooler (I use an Alpenföhn for my i9) and a good case that directs cooling air to the right spots and quickly exhausts the hot air. You can use the monitoring program GPU-Z to see everything in real-time: how much power each component is drawing, component temperatures, load spikes, and so on. If a crash occurs, the log lets you see exactly when and where the problem happened and what caused it (e.g., something getting too hot). Yesterday, after my post, I played Captain of Industry for another hour and 10 minutes before it crashed again. I kept playing after that, too, right up until I went to bed in the early morning. It is running more stably thanks to the changes in the latest patch, but there must still be an underlying issue causing even a high-end system like mine to crash. As I said, there are other games that put a heavier load on my current system, yet they run stably for hours without crashing.

Hi! Now i played 20 Minutes than was the Game completly crashed! How are we supposed to keep playing the game for any length of time without ending up totally frustrated? Please look into why the game keeps crashing for so many people—not just me! Thanks a lot!

check ur ram, check if it uses the max voltage its rated for, also u can run prime95 or memtest86. that was the case for me

It's hard to say really. Some crashes do come from the game - for example the mining/forestry tower overlay crash which is now fixed. Others come from incompatible software (discord overlay seems to be problematic). Others come from something hardware related, whether it be bad components, overclocking, insufficient cooling, or an underpowered PSU).

If there's a specific thing that you're doing when it crashes then we can take a look at that (eg. multiple people reported issues with the new mining/forestry overlay, which we managed to track down to a bug, and we're making sure no bugs of the same form exist). Obviously we want to fix anything we can find but, because they're so often they're caused by things completely outside of our control, without a way to reproduce them (activity X often results in crashes) there's often little we can do.

trollge10 [discord] wrote:

check ur ram, check if it uses the max voltage its rated for, also u can run prime95 or memtest86. that was the case for me

i have Corsair Ram 64 Gigabyte 3200 Mhz DDR4 <-- i have this full checked with testprograms! its not my Hardwareproblem its a Problem from the Game Captain of Industry!!!

Captain Jeremy wrote:

It's hard to say really. Some crashes do come from the game - for example the mining/forestry tower overlay crash which is now fixed. Others come from...

Hello! You’ve built a tool into the game that automatically sends error reports to you whenever the game crashes, for whatever reason. Surely you just need to look at that data to narrow down the problem or fix it via a patch—right? I always keep that feature enabled so the error report is sent immediately if the game crashes. As I said, I know exactly how my system works—I build it myself, handle the cooling, and so on. Of course, there are people who really shouldn't be messing with that sort of thing. And while companies selling overclocked PCs can get it right, that isn't always the case; it’s often problematic, especially for laypeople. I’ve been playing PC games since the early 90s—back when most people didn't even know this hobby existed. We’ve managed to get far more complex systems running stably. I hope you find a solution within the game's code—thanks a lot!