Running a mixed RAM configuration (two completely different brands, different sub-timings, and different native speeds) is the most likely reason your game is crashing during map generation. Even though Windows boots and works fine at a downclocked 2400 MT/s, Unity's map generator heavily stresses the memory controller with massive, multi-threaded data blocks. Because the Kingston and Crucial modules have different internal latencies, they desynchronize under load, causing the CPU to miscalculate data, which in turn causes the GPU driver to crash (DXGI_ERROR_DEVICE_REMOVED). To fix this and get the game running, apply these memory troubleshooting steps: 1. The Ultimate Test: Pull out two sticks To prove this is the issue, physically isolate one matched pair: Turn off your PC and unplug the power cable. Remove the Kingston HyperX sticks entirely. Leave only the two Crucial Ballistix sticks installed in slots A2 and B2 (usually the 2nd and 4th slots from the CPU—check your ASRock B460 Pro4 manual). Boot the PC and try generating a map in Captain of Industry. If it works, your mixed RAM config is 100% unstable. 2. Lock a Safe, Uniform Speed and Voltage manually. If you want to keep all 32 GB installed, you cannot rely on "Auto" BIOS settings because your motherboard is getting confused trying to read two different SPD profiles. You must force safe settings manually: Restart your PC and press Delete or F2 to enter the BIOS. Go to the OC Tweaker tab -> DRAM Configuration. Ensure XMP is strictly Disabled. Manually set DRAM Frequency to 2400 MHz (or even 2133 MHz just for testing). Scroll down to DRAM Voltage and manually change it from Auto to 1.35V. 3. Change RAM Slot Ordering. Channel A (Slots 1 & 2): Put one Kingston and one Crucial stick here. Channel B (Slots 3 & 4): Put the other Kingston and Crucial stick here.
