Game Freezes with buzzing sound from speakers

Over the past few days, there have been a number of occasions where the game freezes, and a buzzing sound comes from the speakers. This has happened a few times, but I have also had a number of hours of gameplay inbetween with no issues. I do play with one mod. I have attached my my most recent logfile, and the game save. The last occurrence was at around 15:18, interestingly, there was nothing much in the log at that time.

On all occasions, the game will finally respond, and I have been able to save and exit the game without any loss.

Cheers,
Chris.

You are entirely correct: there are no logged events around 15:18.

• The last autosave before the issue was at 15:04:23.
• The very next log entry doesn't appear until 15:19:24, when the game captured a paused autosave (15-19-autosave-paused.save).
• The fact that the game remained completely silent during the freeze from 15:18 to 15:19 strictly proves that the freeze happened at the Windows or GPU/Audio driver level. The Unity engine was completely locked up and could not execute any code to register or log an error.

During initialization, the log reveals that you actually have four active mods installed, along with 2 official DLCs:

• MultiLangLib
• TruckParking
• TruckTrek
• UndergroundTransportMod

Notably, the UndergroundTransportMod throws an initialization error right at startup:
Value of int is -1, expected not negative... at UndergroundTransportMod.UTResearch.RegisterData.
This indicates that a research node within the mod is broken or incompatible with your current game version (v0.8.7d).

Throughout the gameplay session, the log is spammed with hundreds of warnings from the trains DLC:
Adding destroyed entity Track #0 ... in AddEntityOnSync, ignoring.
The game is constantly trying to sync and render train tracks that have already been deleted. While the game successfully ignores these to prevent a hard crash, this constant loop places a massive background strain on your CPU and RAM, which can lead to transient performance stalls.

1. Clean Up Your Mods: You mentioned playing with only one mod, but the folder AppData\Roaming\Captain of Industry\Mods contains 4 active entries. Completely remove or disable the outdated mods—especially UndergroundTransportMod which is actively failing.
2. Optimize Your Train Tracks: The destroyed entity Track warnings indicate corrupted or improperly deleted rail segments. Try to locate these areas in your save or redesign sections of your rail network to stop the engine from throwing errors.
3. Cap Your Framerate: The log notes you are running the game at a heavy 3840 x 2160 (4K) resolution. Captain of Industry becomes incredibly demanding on late-game factories. If your GPU or Power Supply is straining to push 4K, it can trigger the exact type of driver hang and audio buzz you experienced. Cap your FPS to 60 or enable V-Sync in the graphics settings to alleviate this pressure.

Given that you are playing in 4K resolution, the demand on your hardware is immense. Could you share your GPU model and CPU model?

Hi poltime,

thanks for your detailed response. It is appreciated.

I am playing with a 2560x1600 window on a 4k screen. I do have the FPS set to VSync (and have a 60Hz monitor) and it correctly displays a 60fps setting.

I cannot disable the underground transport mod, as I'm using it extensively in the game.

With regards the destroyed entity track warnings, I have no idea how I could have incorrectly deleted tracks. Is it possible they are being thrown by track sections that are on the map in design mode? I do have quite a few of those laying around as I plan out extensions.

My specs are

CPU: AMD Ryzen 9 9950X3D
GPU: GeForce RTX 5080
RAM: 64GB
VRAM: 16GB
SSD: Kingston M.2 NVMe SSD 4TB

My CPU Total load barely registers, with the Core Max load hovering around 25-30%. GPU Load is around 20%, but I do notice that the GPU Memory is around 80%.

The number of instances of this happening has decreased dramatically recently. Not quite sure what has changed, but happy that it appears, for now, to have been resolved.

Cheers,
Chris.