Random Crashes

Started by Kionairis, July 03, 2020, 10:23:31 AM

Previous topic - Next topic

Kionairis



Hi,

Recently I've been getting into Rimworld and so far am really enjoying it. However Somewhere between every 10 minutes to an hour I have a crash to dekstop. The game screen goes black and a "loading"-bar box pops up with the Ludeon logo, and eventually it all dissapears to the desktop.

I am running Windows 10 - 1909, the latest version. I also am running the latest Nvidia drivers and AMD processor chipset. I am running the latest non-beta version of the game on steam (the default one).

In terms of hardware I have a Nvidia 2080 and a Ryzen 3900x, as well as 16GB Ram.

I have tried verifying the game files, as well as reinstalling it on another harddrive. I've also tried windows memory diagnostic and found no issues, chkdsk also reports no issues. I have no problems with any other games. During play the cpu heats up to around 45 celcius. I've also tried reinstalling the latest Nvidia graphics driver.

In the player log I get the following:


Trying to get default parms for null incident category. (Filename: C:\buildslave\unity\build\Runtime/Export/Debug/Debug.bindings.h Line: 35)
System.NullReferenceException: Object reference not set to an instance of an object
at RimWorld.StorytellerUtility.DefaultParmsNow (RimWorld.IncidentCategoryDef incCat, RimWorld.IIncidentTarget target) [0x0001b] in
<0ee2c524c4be441e9b7f8bfcb20aca6f>:0   at
RimWorld.StorytellerComp.GenerateParms (RimWorld.IncidentCategoryDef incCat, RimWorld.IIncidentTarget target) [0x00000] in
<0ee2c524c4be441e9b7f8bfcb20aca6f>:0   at
RimWorld.StorytellerComp_OnOffCycle.GenerateIncident (RimWorld.IIncidentTarget target) [0x0000c] in
<0ee2c524c4be441e9b7f8bfcb20aca6f>:0   at
RimWorld.StorytellerComp_OnOffCycle+<MakeIntervalIncidents>d__2.MoveNext () [0x00119] in
<0ee2c524c4be441e9b7f8bfcb20aca6f>:0   
at RimWorld.Storyteller+<MakeIncidentsForInterval>d__19.MoveNext () [0x00171] in
<0ee2c524c4be441e9b7f8bfcb20aca6f>:0   at
RimWorld.Storyteller+<MakeIncidentsForInterval>d__18.MoveNext () [0x000a1] in
<0ee2c524c4be441e9b7f8bfcb20aca6f>:0   at
RimWorld.Storyteller.StorytellerTick () [0x00042] in
<0ee2c524c4be441e9b7f8bfcb20aca6f>:0   at
Verse.TickManager.DoSingleTick () [0x00109] in
<0ee2c524c4be441e9b7f8bfcb20aca6f>:0

And in the crash log I get:


RimWorld by Ludeon Studios by Ludeon Studios [version: Unity 2019.2.17f1_8e603399ca02]
UnityPlayer.dll caused an Access Violation (0xc0000005)
in module UnityPlayer.dll at 0033:d5093930.
Error occurred at 2020-06-30_135314.
C:\Program Files (x86)\Steam\steamapps\common\RimWorld\RimWorldWin64.exe, run by NAME.
32% physical memory in use.
16328 MB physical memory [11086 MB free].
1159 MB process peak paging file [1159 MB used].
826 MB process peak working set [798 MB used].
System Commit Total/Limit/Peak: 8942MB/25032MB/13766MB
System Physical Total/Available: 16328MB/11086MB
System Process Count: 191
System Thread Count: 3245
System Handle Count: 89382
Disk space data for 'C:\Users\NAME\AppData\Local\Temp\Ludeon Studios\RimWorld by Ludeon Studios\Crashes\Crash_2020-06-30_125252755\': 201269878784 bytes free of 255382777856 total.
Read from location 0000000000000000 caused an access violation.
Context:
RDI:    0x0000000000000000  RSI: 0x000001f534177540  RAX:   0x000001f532a3e2bc
RBX:    0x000000518bace790  RCX: 0x0000000000000000  RDX:   0x000000518bace738
RIP:    0x00007ffdd5093930  RBP: 0x000000518bace7b0  SegCs: 0x0000005100000033
EFlags: 0x0000000000010246  RSP: 0x000000518bace6b0  SegSs: 0x000000510000002b
R8:     0x00007ffdd5f9e168  R9:  0x000001a3a6f6fbc4  R10:   0x0000000000000000
R11:    0x000000518bace6a8  R12: 0x000001f5330880e0  R13:   0x000001f533088000
R14:    0x0000000000000001  R15: 0x000001f533088000

I'm not sure which causes the other or how to go about fixing this or identifying the issue.

Any help is much appreciated!

Canute

Hi,
if you didn't update your video card driver recently you should try this at first.

If that didn't help it is one of these unity error's which are hard to identify.
Some got problems with anti-virus other with shaders.
But you better should search self for
"UnityPlayer.dll caused an Access Violation (0xc0000005)"
and read throw a few topics. But posting then older then 2019 you should ignore.