Crashes, No Mods, Good CPU Specs

[zacharyhough096]

The game stability, is non-existent. I can't run a single game for FIVE Minutes! No mods, lots of ram, ect. Lowered res., maps size, & ect. Windows 10, nvida 2 gbs of vram, 8 or 12 gbs of ram, maybe there is a compatibility patch, or community mod for bug fixes and crashes? I'm just livid that I can't play this very awesome game I just purchased from steam

[Canute]

We need at last an error log after a crash, to see the reason for the crash
Take a look at point 6. from
https://ludeon.com/forums/index.php?topic=513.0

Btw. how many RAM you got is for a 32 bit program irrelavant, it never can address more then 3,2 GB, and Rimworld is still 32 bit.

[zacharyhough096]

Initialize engine version: 5.6.3p1 (9c92e827232b)
GfxDevice: creating device client; threaded=1
Direct3D:
    Version:  Direct3D 9.0c [nvldumd.dll 23.21.13.8816]
    Renderer: NVIDIA GeForce GTX 1050
    Vendor:   NVIDIA
    VRAM:     1987 MB (via DXGI)
    Caps:     Shader=30 DepthRT=1 NativeDepth=1 NativeShadow=1 DF16=0 INTZ=1 NULL=1 RESZ=0 SlowINTZ=0 ATOC=1 BC4=1 BC5=1
Begin MonoManager ReloadAssembly
Platform assembly: C:\Program Files (x86)\Steam\steamapps\common\RimWorld\RimWorldWin_Data\Managed\UnityEngine.dll (this message is harmless)
Loading C:\Program Files (x86)\Steam\steamapps\common\RimWorld\RimWorldWin_Data\Managed\UnityEngine.dll into Unity Child Domain
Platform assembly: C:\Program Files (x86)\Steam\steamapps\common\RimWorld\RimWorldWin_Data\Managed\Assembly-CSharp-firstpass.dll (this message is harmless)
Loading C:\Program Files (x86)\Steam\steamapps\common\RimWorld\RimWorldWin_Data\Managed\Assembly-CSharp-firstpass.dll into Unity Child Domain
Platform assembly: C:\Program Files (x86)\Steam\steamapps\common\RimWorld\RimWorldWin_Data\Managed\Assembly-CSharp.dll (this message is harmless)
Loading C:\Program Files (x86)\Steam\steamapps\common\RimWorld\RimWorldWin_Data\Managed\Assembly-CSharp.dll into Unity Child Domain
Platform assembly: C:\Program Files (x86)\Steam\steamapps\common\RimWorld\RimWorldWin_Data\Managed\UnityEngine.UI.dll (this message is harmless)
Loading C:\Program Files (x86)\Steam\steamapps\common\RimWorld\RimWorldWin_Data\Managed\UnityEngine.UI.dll into Unity Child Domain
Platform assembly: C:\Program Files (x86)\Steam\steamapps\common\RimWorld\RimWorldWin_Data\Managed\UnityEngine.Networking.dll (this message is harmless)
Loading C:\Program Files (x86)\Steam\steamapps\common\RimWorld\RimWorldWin_Data\Managed\UnityEngine.Networking.dll into Unity Child Domain
Platform assembly: C:\Program Files (x86)\Steam\steamapps\common\RimWorld\RimWorldWin_Data\Managed\NAudio.dll (this message is harmless)
Loading C:\Program Files (x86)\Steam\steamapps\common\RimWorld\RimWorldWin_Data\Managed\NAudio.dll into Unity Child Domain
Platform assembly: C:\Program Files (x86)\Steam\steamapps\common\RimWorld\RimWorldWin_Data\Managed\NVorbis.dll (this message is harmless)
Loading C:\Program Files (x86)\Steam\steamapps\common\RimWorld\RimWorldWin_Data\Managed\NVorbis.dll into Unity Child Domain
Platform assembly: C:\Program Files (x86)\Steam\steamapps\common\RimWorld\RimWorldWin_Data\Managed\TextMeshPro-1.0.55.56.0b11.dll (this message is harmless)
Loading C:\Program Files (x86)\Steam\steamapps\common\RimWorld\RimWorldWin_Data\Managed\TextMeshPro-1.0.55.56.0b11.dll into Unity Child Domain
- Completed reload, in  0.039 seconds
Platform assembly: C:\Program Files (x86)\Steam\steamapps\common\RimWorld\RimWorldWin_Data\Managed\System.Core.dll (this message is harmless)
Platform assembly: C:\Program Files (x86)\Steam\steamapps\common\RimWorld\RimWorldWin_Data\Managed\System.dll (this message is harmless)
Platform assembly: C:\Program Files (x86)\Steam\steamapps\common\RimWorld\RimWorldWin_Data\Managed\System.Xml.dll (this message is harmless)
WARNING: Shader Unsupported: 'Hidden/VR/BlitCopyFromTexArray' - Pass '' has no vertex shader
WARNING: Shader Unsupported: 'Hidden/VR/BlitCopyFromTexArray' - Setting to default shader.
<RI> Initializing input.

<RI> Input initialized.

desktop: 3840x2160 60Hz; virtual: 3840x2160 at 0,0
<RI> Initialized touch support.

UnloadTime: 1.436266 ms
RimWorld 0.18.1722 rev1198

(Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/DebugBindings.gen.cpp Line: 51)

Platform assembly: C:\Program Files (x86)\Steam\steamapps\common\RimWorld\RimWorldWin_Data\Managed\System.Xml.Linq.dll (this message is harmless)
Unloading 5 Unused Serialized files (Serialized files now loaded: 0)
UnloadTime: 1.140684 ms

Unloading 39 unused Assets to reduce memory usage. Loaded Objects now: 7799.
Total: 33.141014 ms (FindLiveObjects: 0.703281 ms CreateObjectMapping: 0.558839 ms MarkObjects: 31.790949 ms  DeleteObjects: 0.086199 ms)

Loading game from file Tutorial with mods Core

(Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/DebugBindings.gen.cpp Line: 51)

Unloading 0 Unused Serialized files (Serialized files now loaded: 0)

Unloading 0 unused Assets to reduce memory usage. Loaded Objects now: 14194.
Total: 152.705276 ms (FindLiveObjects: 1.459272 ms CreateObjectMapping: 0.986632 ms MarkObjects: 150.201431 ms  DeleteObjects: 0.057077 ms)

Crash!!!

.....

I'd add save game files, but I don't usually make it far enough into the game to save

[Canute]

Wau, the log show (at last me) nothing about a crash reason.

desktop: 3840x2160 60Hz; virtual: 3840x2160 at 0,0

Do you downsample ?
This is maybe a reason i could imagine that rimworld or unity couldn't handle.
Could you try to use your native monitor resolution of 1920x1080 for the desktop instead ?

[Calahan]

Can you please:

1 - Play the game again, and when/I it crashes please check for the other files that should be generated when a crash occurs. There should be crash.dmp and error.log files alongside the output_log.txt file (they should be in the steamapps\common\RimWorld\RimWorldWin_Data folder). And please post them as an attachment and not copy and paste their contents into a post (as that both elongates the thread for no reason making it more difficult to read, plus it also risks omitting information due to human error).

The log file is (mysteriously) giving no indication as to the cause of the crash. So hopefully the other files will (assuming they were generated). If they don't, or if they weren't generated, then it could be very difficult to troubleshoot this issue because clues are needed in order to troubleshoot problems, and without such clues it becomes a lot more difficult (and usually comes down to just guessing and hoping a guess is correct).

2 - Provide more information about your computer. CPU, RAM (you said 8 or 12Gb which is it?), desktop or laptop computer. The log file has provided your GPU information.

2a - Confirm that Windows 10 and your GPU drivers are fully up to date.

3 - As Canute mentions above (which you didn't respond to before creating a duplicate thread), please can you try running the game in a lower resolution, such as 1920x1080p. I do not know if that is the reason for the crash but it is a possibility worth eliminating.

3a - Please also try running the game in windowed mode (which can be done via the options menu).

4 - Try starting a new vanilla game with any storyteller and scenario, and using the default world and map sizes. Your log file indicates that you are attempting to load the tutorial, so starting a new game will help determine if the tutorial is the cause of the crash.

5 - Confirm that you have no other programs running that are using your sound device or GPU. This includes recording software, voice chat software, video/music players, basically anything that could be using your sound device or GPU. There's no indication (as yet) that this is the cause of your crash, but they have caused crashes in the past for other users (although in such cases the log file usually indicates this as the problem).

6 - Please can you check whether or not you have the Nvidia Share option enabled (IIRC the feature is toggled via the GeForce Control Panel). And if so please disable it (this feature has caused technical issues for numerous RimWorld users in the past).


Finally, please don't create duplicate threads for the same issue (I have deleted the thread you posted in bugs, plus this is not a bug in the game so it does not belong in bugs). Please keep in mind that people have real lives and as such are not always able to rapidly respond to requests for technical assistance due to those real lives, and the responsibility and time constraints that come with them (and especially so on weekends). So just because nobody answered your request (as rapidly as you would like) is not a reason to create duplicate threads for it. So please refrain from doing that again in future.