Member
Hi,
I have a new MSI 1080 ti. All settings on this game are set to the max, however textures settings are only able to be set to next setting down, High. As soon as I change this setting to Ultra, the game crashes! This card has 11 GB VRAM so is plenty to accommodate the max settings (everything maxed uses less than 5 GB VRAM), and when it crashes, the GPU temp is only 67 degrees so I don't think the GPU is crashing.
My CPU is the i7 7820x * (8 core hyperthread CPU) so is powerful enough.
Any ideas why the game keeps crashing when I turn on the textures to Ultra?
Thanks, any advice appreciated.
Ubisoft Support Staff
Hey Johnson9191. Can you see if basic PC troubleshooting helps at all? Please let me know how it goes!
Member
I noticed, in your other thread, that you have/had a crashing issue with an Unknown file version d3dCompiler_47.dll error notice. I was sorta hanging back waiting for you to post again, before sticking my nose in it. One of two things is true: either the incidents are related, or the incidents are not related. Bear with me, there is a point...Originally Posted by Johnson9191 Go to original post
I have been going round and round with tech support via a ticket--filed over a month ago, concerning unexplained "silent" crashes, (no error popups)--often, however, associated with the 'unknown file version: d3dCompiler_47.dll. error popup, (Event ID 26) immediately prior (by 1 (one) second to the silent crash to the desktop. The silent crash is NOT ALWAYS preceded by the unknown file version notice, however the crash is ALWAYS immediately preceded by Event ID 2004, and another Event ID 26, in the Windows System Log (Computer Management > Event Viewer > Windows Logs > System.) This is the only location these events are logged (not in error reporting) other than an "abnormal" shutdown in the uPlay launcher logs,
A light explanation of the events: (Times are arbitrary, but taken from my System Log)
9:26:02 AM Event ID: 6 ...EasyAntiCheatSys... loaded: (game started)
1:00:17 PM Event ID: 2004 Low virtual memory diagnosis (GRW.exe consuming the most virtual memory)
1:07:41 PM Event ID: 2004 Low virtual memory diagnosis (GRW.exe consuming the most virtual memory)
1:07:54 PM Event ID: 26 Windows - Out of Virtual Memory
1:08:03 PM Event ID: 26 GRW.exe: Unknown file version ../d3dCompiler_47.dll
1:08:04 PM Event ID: 1 EasyAntiCheatSys unloaded (the game has crashed to the desktop
In one of these sequences, the desktop windows manager (dwm.exe) crashed because it could not allocate additional memory.
In doing my homework, after your other post--and the very weak answer you received from support... well long story short, d3dComplier_47,dll is a windows operating system file, part of DirectX, as was mentioned, however there are two such files on a system with GRW installed: one in the GRW folder, and the other (installed with DirectX) in the Windows/System32 folder. If one file is missing, or corrupt, the game will use the other. If both are damaged or missing, the game will not run at all. So I deleted the file in the GRW folder, forcing the game to use the file in the system32 folder... when the game crashed again (same sequence as above,) the unknown file version was .../nvvolumetriclighting.win64.dll rather than d3dCompiler_47.dll. I strongly suspect that the file is NOT unknown, missing, nor corrupt--rather a memory allocation issue. Guilt by association...
I run a fairly strong system:
CPU - i7 7700K not overclocked (liquid cooled)
GPU - nVidia GTX 1080 (x2) in SLI (frame rates ~ 70FPS @ 4K output Ultra High settings) not overclocked; stock cooling with custom curve; average temp around 60C. ~50C on cooler days....
Mobo - Asus ROG Maximus IX Hero
RAM - 32GB Corsair Vengence 3200 running standard speed 2133MHz.
OS: Windows 10 Education 64bit
On my system:
The only way the game will not crash, (either silently or with the unknown file version popup) in time, is to run an unlimited size pagefile. So this game is not only using VRAM, (and monitoring the usage shows it is using about what the settings tell you it should) it is also relying heavily on virtual memory (Physical RAM + Pagefile) in order to continue running. It eats up 32GB of physical ram, in around 4 hours and crashes, with no pagefile; and with a pagefile--the usage continues to grow. My pagefile has seen 40GB + while running GRW, plus the 6GB or so of physical RAM. If run for extended periods of time, the physical ram usage continues to climb (have seen it at 16GB, while task manager reports only 6GB or so being used by GRW--but nothing else is running except the baseline stuff (around 3GB give or take.)
That is my idea on why your game keeps crashing, presented with the evidence. I could very well be wrong, admittedly... but guilt by association, and a history of the game crashing with low virtual memory, going back to March, 2017. Turn on ultra, and virtual memory use goes through the roof. GRW is a wonderful game, but it pushes the systems hard... Only way to know if there is a relationship, is for you to be willing to peruse your Windows System Log for the above events....it won't show up anywhere else, unless you actually do have a faulting stick of RAM, for instance. A torturous act at the very best..
I did all the suggested troubleshooting, including a 6 hour memory test, jumped through hoops, and howled at the moon... and then it was suggested I start all over.... not a thing wrong with this system... Support Staff, and Tech Support tickets can only do so much... we have to do the work too...
