Game Crash

[47a]

My game has been crashing at seemingly random and I receive these 2 crash messages, help is appreciated

http://prnt.sc/f7l939
http://prnt.sc/f7l95q

Moderator's edit (Calahan) - For convenience, I've attached the output and error logs that are located in a download link later in the post to the OP.

[attachment deleted by admin due to age]

[Neotic]

My game has been crashing at seemingly random and I receive these 2 crash messages, help is appreciated

http://prnt.sc/f7l939
http://prnt.sc/f7l95q

Can you please link the log file and the "crash report" so they can find out what the problem is. Also do you know how many gb of ram you have?

[47a]

8gb of ram, and i'm not sure how to link the log files

[Neotic]

8gb of ram, and i'm not sure how to link the log files

Use a website like dropbox and create a download link for it.
If you cant find the log file follow the instructions for your OS
https://ludeon.com/forums/index.php?topic=513.0

[47a]

https://files.fm/u/9ccxu8m9 Got it, I think

[ReZpawner]

Firstly, the error message says that the log file is located in the Rimworld directory, next to the exe file. If you're using Steam, that will be %steam\steamapps\common\RimWorld , where % is just the drive letter, depending on where you installed Steam.

As for the other error message, it's commonly found when a Unity program runs out of RAM. This does not however mean that you don't have enough - particularly since Rimworld is a 32-bit program, which means that it cannot utilise more than 4GB of it anyway. Garbage collection problems in Unity, a large amount of mods, (less likely) buggy code, or any of a hundred other reasons can all cause the error you're seeing, so without the log-file, we're left with narrowing it down almost by pure guesswork.

If you're using a lot of mods though, do try to disable them and see if that helps.

...and also, specify if you're using the unstable testing version(A17) or A16.

[47a]

above should be a link to the log files, and i'm using A16

http://prntscr.com/f7lslb
mods used

[ReZpawner]

Without having any other error messages to compare with, I would probably suggest updating the graphic-card drivers on your computer, to see if that works first. If nothing else, it seems to have helped a lot of other people with that error message in Unity. That said, it looks like it could be related to the garbage collector (mono). That's pure speculation though, as I'm not too familiar with errors in Unity.

Edit: The graphic card part is not just a complete random guess btw. The error message pretty much mentions two things, "Skipped rendering frame because GfxDevice is in invalid state (device lost)" and a bunch of Mono stuff. I've seen a couple of more error messages that don't mention the D3D part at all, which suggests that it is the cause of the crash. I'm sure some of the mods here have gone through quite a few more of those logs than I have, and may be able to give you more specific advice about it, but new drivers isn't a bad place to start regardless.

[47a]

I think my drivers are up to date already http://prntscr.com/f7m012

[Neotic]

above should be a link to the log files, and i'm using A16

http://prntscr.com/f7lslb
mods used

If you're using mods then this should be in the mod bugs section

[Calahan]

@ 47a - I've moved this to support because, based on those log errors, this seems more likely to be a problem with your computer (such as your graphic driver) rather than a bug in the base game or the mods you use. And to avoid causing concern, your computer is likely fine, and that an update to the Unity engine might be at fault as well, as sometime an update causes loss of compatibility with older graphic cards, which yours appears to be. (the "Intel(R) Q45/Q43 Express Chipset" was released in 2008 according to Wiki)

It would help if you could please answer the following questions:-

1 - What version of Windows are you using?
2 - What version of your graphics driver are you currently using? (the screenshot you posted says that Windows says it is up to date, but that doesn't tell us what driver version it is). 
3 - You say in the OP that the "game has been crashing at seemingly random". Is this random crashing recent? Or has it always been like this when playing A16?
3a - If it is recent then when did it start? Did your computer perform any sort of update around the time it started? (you might need to check the Windows update log for this info, but how to do that depends on what version of Windows you use)
3b - If it's not recent, and this has always been a problem when playing A16, then have you played any of the earlier versions of RimWorld? If so did you ever have this problem playing those?
4 - Have you tried playing a vanilla game to see if the same crashing occurs? If you haven't tired this yet then can you please try it.
5 - If the crashing is constant across A16, then can you please try playing A15 to see if that crashes or not. (according to the log file you are using the Steam version. If so then there is an option in Steam, under the Beta tab, to roll the game back to A15).
6 - Have you ever had this type of crash playing any other game? Especially any of Unity engine games (do you know if own any other Unity engine games? If so have you tried playing one of those recently?)

[47a]

1 - Windows 7 professional 32 bit
2 - http://prntscr.com/f7mltq
3 - i haven't started up rimworld in a while but don't recall this happening previously, so far in the past day its crashed 3 times, so always been like this in A16
4 - Not yet, ill give it a try, would this indicate issue with a mod(s) im using?
6 - I don't recall having this type of crash before and im unsure if any of my other games use Unity engine

[Calahan]

Thank you for the answers.

https://downloadcenter.intel.com/product/81511/Graphics-Drivers-for-Intel-Q45-Express-Chipset
According to the above Intel page, and filtering for Windows 32bit, your current graphics driver, 8.15.10.2869, is the most recent one. And there hasn't been any updates for several years, so I think we can rule out this being an issue caused by a recent graphics driver update.

A search through the forum for past instances of "HandleD3DDeviceLost" log errors turned up the following two informative posts by (the always excellent support guru) nccvoyager.
https://ludeon.com/forums/index.php?topic=26517.msg268946#msg268946
https://ludeon.com/forums/index.php?topic=30118.msg306532#msg306532

So based on the above, another set of questions:-

1 - Are you using a laptop?
1a - If yes, please trying setting all your power options to high performance or maximum etc.
2 - Do you ever alt-tab while playing? If yes, then can you please try playing the game for as long as possible without alt-tabbing, and take note of whether the game crashes or not.
3 - Are you using a multiple-monitor setup?
4 - Are your DirectX drivers up-to-date? (and which DirectX version are you using?)

For testing the game you can also try the following two troubleshooting variables:-

- Playing in Windowed mode (assuming you were playing in fullscreen before).
- Enable the "run in background" option in the options menu.

For testing can you please just play vanilla RimWorld. Do not use any mods as that makes it harder to isolate the problem (as it's still not entirely ruled out this is a mod issue, but it just seems less likely at the moment). Try playing A16 first and if that is still crashing, even with the variables (and "maximum power" power management settings), then try the same with A15 (again don't use mods, not least as most mods are likely out of date having been updated to A16).

You said you haven't "started up RimWorld in a while", and that the crashing has always been present in A16, and that things were fine in earlier versions (such as A15?). In which case the crashing in A16 might be caused by a Unity engine update that occurred between A15 and A16, and this update is causing an issue for your (older) graphics card. In which case I'm not sure what can be done to be honest, and it's up to Unity to fix the issue. But we're not at that point yet and still lots to rule out first.

[47a]

1 - No, desktop
2 - I use the windows key to go out of my tab while playing fairly frequently
3 - single monitor
4 - how can i check if DirectX drivers are up to date? and DirectX 11

[Calahan]

Thanks again for the answer.

According to nccvoyager (in one of those threads I linked):-

So, doing some research, this error (HandleD3DDeviceLost) is an error thrown by Unity in regards to several different issues.
Most of those issues seem to deal with graphics idle states, including alt-tabbing from games causing the game to "lose focus" and throw an error.
(This is, apparently, one reason that fullscreen Unity games tend to crash when not the focused window for a while.)

So if you are using the Windows key regularly while playing then that might well be the cause of the problem. As that would both match the error generated in the log file...

HandleD3DDeviceLost
  HandleD3DDeviceLost: still lost
Skipped rendering frame because GfxDevice is in invalid state (device lost)

... and, according to nccvoyager's research, it would match one of the main reasons for the Unity engine producing this error.

So the most logical next diagnostic step is for you to completely avoid using the Windows key (alt-tabbing) while playing. As if you test that, and the game doesn't crash, then you almost certainly have your answer regarding what's causing the crash.

You can get all the info about your DirectX drivers (and more) by typing "dxdiag" into the Windows run command box. I haven't used Windows 7 in many years so can't remember if the run box is on the Start menu or not. But you can probably open it by pressing WindowsKey+r. If you click the "Save All Info" button and then post the resulting text file as an attachment. Although this DirectX info likely isn't needed if the above test confirms the cause is the game losing focus due to using the Windows key while playing, which seems likely at this point.