Rimworld World Map goes All White - No Crash

[Dramier]

Issue:  Steam or non-steam versions, Rimworld has a graphical error when the world (globe) map is opened.   Happens when picking a new colony and when doing caravans.   Sometimes does not happen, would say the ratio is about 80% of the time.   The error seems to involve a graphics card driver reset.   When the world map is opened, it displays as normal and everything runs normally.   When the error happens, the monitor 'resets' and the world map goes completely white.   Nothing can be seen, not the UI, not the icons, nothing.  The application window is there, and the minimize, maximize, close, and title bar are all present and visible.   The rest of the window is literally solid white.   However the game itself does not seem to crash, and sound can be heard in the background and it seems to continue working.   I then have to close the window and restart to get it back.   There is no crash log generated, and no apparent errors in the player.log.

The computer specifications are as follows:
Mobo: Asus P8Z77-VLK - All bios drivers updated/current.
CPU: Intel I5-3350P @ 3.1ghz.   No overclocking, watercooled.
RAM: G.Skill 16GB DDR3 RAM @ 799.9mhz. (4x4GB)
Storage: Samsung SSD 860 EVO 500GB
Graphics: Nvidia 970 GTX 4GB (1164mhz core/3505mhz ram) Factory settings.
OS: Windows 10 Pro licensed, activated and fully updated.
Other: Razer Mamba TE mouse.
Dual monitors setup.  Default desktop resolutions: 1920x1080.

Nvidia driver: 451.67 (installed along with GeForce Experience)
Rimworld Version: 1.1.2654 rev672

All drivers are up to date, Windows is fully updated, Steam is fully updated, bios and all hardware devices fully updated.

Rimworld is 100% vanilla.   No mods, no dlc.   Doesn't matter if it's Steam version or non-steam version.   

Here are the steps based on the support stickied post, and searching the net for related issues that I have performed:

Complete re-install of Rimworld to include manually deleting all folders and running the registery cleaning entry.   
Complete re-install of Nvidia drivers with safe boot wipes and restarts.
Testing running Rimworld with GeForce experience disabled.
Testing running Rimworld in windowed mode.
Testing running Rimworld in full-screen mode.
Testing running Rimworld non-steam version.
Testing running Rimworld with graphics card DE-clocked down to 92%.  (More on this to follow.)
Verified no subscribed mods in Steam.
Performed Steam file verification.
Tested with forced opengl launch option.
Tested with forced directx launch option.
Installed on secondary drive.
Verified no hamachi installed.
Restarted the PC with both restart and shutdown options.
All possible combinations of the above list as well.

Multiple benchmark and testing applications performed on the CPU, GPU and RAM - no errors/problems found.
Disabled antivirus/Windows defender applications.
'Clean' boot with ALL other applications suspended or removed.
Disconnected internet and tested.
Switched to single monitor setup.
Tested switching from HDMI to DVI and also VGA.
Monitored GPU/CPU temps and eliminated overheating of any type.
Monitored voltage readings and eliminated PSU failures.


Notes:  My girlfriend has an identically built machine, with a different model of Asus mobo and twice as much RAM, and it runs without issue on her system.   Same windows version, same nivida drivers, etc.

I can play the game normally without any issues, I just cannot reliably open the world view to handle quests or form caravans.   I have experienced a nearly identical error on only one other game
and that was Vermintide 2, which would crash seconds into a match.   The fix there was to declock the 970GTX and it solved the issue.   That unfortunately did not work for Rimworld.  It should also be
noted that no other games on this system have any issues.   I can open and play well over a few hundred different games without problems both older and newer, Unity based or not.   In fact I develop in Unity on this same system building 3D games without issues.

This system is not built for overclocking, and is never overclocked.  It's a watercooled system that I built to play 1080P games at max FPS several years ago with full stability.  The 970GTX installed comes factory overclocked. 

Honestly, I'm not 100% sure this is an issue with Rimworld.   With the information I've provided here, there is basically little to nothing for you to suggest because there are no error messages, no logs to dig into, nothing to see.   The fact it runs flawlessly on a nearly identical machine makes me think it's a hardware failure/pending failure issue.   However, the fact that it only seems to occur when the world map is opened makes me think it's a Unity/coding error.   I feel like if that were the case though, you would have already heard about it and have a stickied solution. 

Regardless, I'm open to suggestions, would be nice to play the game the way it was intended.   If I get a crash log at any point I will update this and any suggestions you have I will be happy to try.   I've tried everything I can think of, and please understand I'm not angry or anything.   As I said, I am a game dev myself, so I get it.   Sometimes weird things happen.   Anyway, love the game, and hopefully we'll get lucky and maybe there's something I missed or somebody has a suggestion.

UPDATE:  I ran it in fullscreen mode and it actually crashed.   Crash log is below:

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

<RI> Input initialized.

<RI> Initialized touch support.

UnloadTime: 0.543000 ms
RimWorld 1.1.2654 rev672
Unloading 5 Unused Serialized files (Serialized files now loaded: 0)
UnloadTime: 0.433400 ms

Unloading 52 unused Assets to reduce memory usage. Loaded Objects now: 10107.
Total: 65.473500 ms (FindLiveObjects: 0.513400 ms CreateObjectMapping: 0.328100 ms MarkObjects: 64.566500 ms  DeleteObjects: 0.065100 ms)

Loading game from file ShenTest19 - active rescue quest with mods:
  - Ludeon.RimWorld
Unloading 0 Unused Serialized files (Serialized files now loaded: 0)

Unloading 0 unused Assets to reduce memory usage. Loaded Objects now: 16331.
Total: 141.061300 ms (FindLiveObjects: 0.791500 ms CreateObjectMapping: 0.950300 ms MarkObjects: 139.280900 ms  DeleteObjects: 0.038300 ms)

D3D11: Failed to create RenderTexture (1920 x 1080 fmt 27 aa 1), error 0x887a0005

(Filename: C:\buildslave\unity\build\Runtime/GfxDevice/d3d11/RenderTextureD3D11.cpp Line: 207)

D3D11: Failed to create RenderTexture (1920 x 1080 fmt 19 aa 1), error 0x887a0005

(Filename: C:\buildslave\unity\build\Runtime/GfxDevice/d3d11/RenderTextureD3D11.cpp Line: 207)

Crash!!!
SymInit: Symbol-SearchPath: '.;C:\Program Files (x86)\Steam\steamapps\common\RimWorld;C:\Program Files (x86)\Steam\steamapps\common\RimWorld;C:\WINDOWS;C:\WINDOWS\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols;';, symOptions: 534, UserName: 'drami'
OS-Version: 10.0.0
C:\Program Files (x86)\Steam\steamapps\common\RimWorld\RimWorldWin64.exe:RimWorldWin64.exe (00007FF7203D0000), size: 667648 (result: 0), SymType: '-deferred-', PDB: '', fileVersion: 2019.2.17.24627
C:\WINDOWS\SYSTEM32\ntdll.dll:ntdll.dll (00007FF980C60000), size: 2031616 (result: 0), SymType: '-deferred-', PDB: '', fileVersion: 10.0.18362.815

-truncated due to maximum message length, if you need to see the DLL listings I can post those up-

========== OUTPUTTING STACK TRACE ==================

0x00007FF923E93930 (UnityPlayer) PAL_Thread_SupportsThreads
0x00007FF923EA6CAA (UnityPlayer) PAL_Thread_SupportsThreads
0x00007FF923E95F9B (UnityPlayer) PAL_Thread_SupportsThreads
0x00007FF923F24E45 (UnityPlayer) PAL_Thread_SupportsThreads
0x00007FF923F2A1CB (UnityPlayer) PAL_Thread_SupportsThreads
0x00007FF923F2A2A8 (UnityPlayer) PAL_Thread_SupportsThreads
0x00007FF92422D5C8 (UnityPlayer) UnityMain
0x00007FF9809D7BD4 (KERNEL32) BaseThreadInitThunk
0x00007FF980CCCE51 (ntdll) RtlUserThreadStart

========== END OF STACKTRACE ===========

A crash has been intercepted by the crash handler. For call stack and other details, see the latest crash report generated in:
* C:/Users/drami/AppData/Local/Temp/Ludeon Studios/RimWorld by Ludeon Studios/Crashes

[Canute]

Hi,
it is definitiv an issue with the videocard and/or the drivers or settings. Special since it run's at your GF mashine without problems.

Since the error/crash is about
D3D11: Failed to create RenderTexture (1920 x 1080 fmt 19 aa 1), error 0x887a0005
i search a bit and found something that someone used
-force-d3d9
I think you need it to add it at the target line at your desktop shortcut.

[Dramier]

Actually I suspect something else entirely.   I strongly am thinking that is is due to the factory OC settings.   I'm going to tear into the two machines here in a minute, but I believe if I recall correctly that her 970GTX is a slightly different one than mine, with mine being a higher OC factory one than hers.    The driver versions are identical, that was literally the first thing I checked.

My current theory is that since this 970GTX is at least three or four years old, and I use my machine far far more than she does, it is starting to degrade when running at the factory OC settings.   For whatever reason this is manifesting in Rimworld, (and probably other games as well but since I don't game that much....) and this just happens to be where it is showing up.

I will give the d3d line a shot again, I've used it once already with no changes.   What I am going to do next is verify the difference between her 970 and mine, and then declock my 970gtx down to the baseline 970 settings and see what happens.  I have a save game file now that has an active caravan mission so I can reliably reproduce the crash.   I will run through and see what I get and update if I figure anything out.

[Canute]

Check the logfile if Rimworld use DX11 or DX9.
Maybe you can force it with the use of the Geforce software instead of the commandline.

[Cranu]

I have been having the same problems... have played Rimworld for over 100 hours on this PC and now it crashes to a blank white screen constantly... half the time it even crashes on the load screen and I never even get into the game.

I have no problems with any other games just this one crashing even on startup now.

[Canute]

Cranu,
then you should post the crash log that rimworld create when it is crash.
When you just switched vom 1.0 rimworld to 1.1, then it is prolly about old video driver and you should update them.

[Dramier]

Following up with the solution for my situation:

I de-clocked the Nvidia 970 GTX by 145mhz on the core clock and 45mhz on the memory clock and have had no further issues.

I don't know why this is necessary, but I suspect it's just the video card aging.   I tried a few other heavier 3D games, like PubG, X4:Foundations, and had no issues without the declock.   Just to be clear, the video card wasn't even at 60 degrees Celsius when the reset happens, and there are no other mitigating factors.   RAM, VRAM, harddrives, everything checked out 100% with no failures.   

I used MSi Afterburner to set the declock.    Hopefully this will help somebody else who comes across this and has tried everything else.   

[Cranu]

There is no crash log. It just goes white.

I did however look to have fixed my problems by installing the 2020-07 Cumulative update preview for windows 10.  KB4568831. After installing that update it seems my Rimworld stopped hanging with a all white screen.

[Dramier]

Check the logfile if Rimworld use DX11 or DX9.
Maybe you can force it with the use of the Geforce software instead of the commandline.

I forgot to address this...

The force d3d line had no effect.   It still used DX11 according to the logs.   OpenGL also had no effect.    Tested using both the steam launch options and doing a command line batch file.