[1.1.2654 rev672] Crash at world generation.

[CrossBread]

Just purchased yesterday.  At first the game was crashing with a StackOverflow log in the early morning of the 3rd day of my tutorial world.  I reported that via email (from the Steam support page) and went to start a new world.  That didn't even make it into the level before crashing to desktop.  So, there is no save file.  Not sure how to reproduce.  I also noticed that the game kept minimizing itself when running in full screen mode, so I switched it to windowed.  No idea if it's related, but seemed like buggy behavior.

Win 10
GTX 1060

Here is the entirety of the Player.log after the crash:

Code Select Expand

Mono path[0] = 'F:/Program Files (x86)/SteamLibrary/steamapps/common/RimWorld/RimWorldWin64_Data/Managed'
Mono config path = 'F:/Program Files (x86)/SteamLibrary/steamapps/common/RimWorld/MonoBleedingEdge/etc'
Initialize engine version: 2019.2.17f1 (8e603399ca02)
[XR] Discovering subsystems at path F:/Program Files (x86)/SteamLibrary/steamapps/common/RimWorld/RimWorldWin64_Data/UnitySubsystems
GfxDevice: creating device client; threaded=1
Direct3D:
    Version:  Direct3D 11.0 [level 11.1]
    Renderer: NVIDIA GeForce GTX 1060 (ID=0x1c20)
    Vendor:   
    VRAM:     6052 MB
    Driver:   24.21.13.9901
Begin MonoManager ReloadAssembly
- Completed reload, in  0.313 seconds
<RI> Initializing input.

<RI> Input initialized.

<RI> Initialized touch support.

UnloadTime: 0.585400 ms
RimWorld 1.1.2654 rev672

[CrossBread]

Tried again with the same result.  Crash happens on the Generating World screen.

[CrossBread]

Noticed a Windows Error Report process pop up in the Task Manager as it was crashing, so checked the Windows Event Viewer and it had several of these, one for each time it crashed:

Code Select Expand

Faulting application name: RimWorldWin64.exe, version: 2019.2.17.24627, time stamp: 0x5df1e6e4
Faulting module name: mono-2.0-bdwgc.dll, version: 0.0.0.0, time stamp: 0x5dc03abb
Exception code: 0xc0000005
Fault offset: 0x000000000009ad45
Faulting process id: 0x4c34
Faulting application start time: 0x01d64c30fe65972a
Faulting application path: F:\Program Files (x86)\SteamLibrary\steamapps\common\RimWorld\RimWorldWin64.exe
Faulting module path: F:\Program Files (x86)\SteamLibrary\steamapps\common\RimWorld\MonoBleedingEdge\EmbedRuntime\mono-2.0-bdwgc.dll
Report Id: 52e95595-ca29-47b4-85d8-921221c8fa1b
Faulting package full name:
Faulting package-relative application ID:

[Canute]

Hi,
did you try to update the video driver lately ?
Driver:   24.21.13.9901, seems to bit old for GTX 1060

[CrossBread]

I think I figured it out.  Rimworld was installed to the Steam Library on my F:\ drive, a portable drive.  Other games have worked fine, but when I went to reinstall, I got an error about write permissions to the drive.  I switched it to D:\ (an internal data drive) and it's been working fine since.

[ison]

Sorry for the inconvenience. It looks like you figured it out!