

This led me to try something that revealed the second quirk. The I/O LED indicator still goes on as normal during the freezes, indicating the background services are still working. Then there's little quirks I've noticed that happen with this freezing issue that can potentially be exploited in order to gather more data. Likewise, increasing the CPU fan to cool the entire system makes it less likely to crash. I tested this by manually lowering the CPU fan speed to essentially heat up the whole system, and since my GPU holds hotter than my CPU, the GPU becomes the clear point of failure. Second, I've noticed similar freezes while just sitting on the desktop or doing some non-DXVX stuff in the background such as streaming video or whatever. Furthermore, it doesn't seem to be a DXVK issue, but rather, a driver issue that's related to increased GPU temperatures.įor one, it becomes more likely to happen again if I start up Warframe immediately after restarting the system. The short version is that this issue seems to be more prevalent with higher GPU temperatures. Okay, so this is gonna be a long comment since there's a lot of information to go through.

Maybe we could get a d3d11.fakeStreamOutUnsupported setting to DISable stream output and/or more logging facilities related to it to debug this further?ĮDIT: please excuse my lack of an apitrace, but it's simply not possible to reliably run the game without dxvk due to a memory management issue in the microsoft dlls in combination with linux allowing larger memory chunks to be allocated than win does.

Referencing, it seems the versions including/supporting stream output reliably freeze Warframe (leaving behind an unresponsive window, the background music still playing and 3 threads at 150% cpu to be killed before restarting the game) on average every 5-15minutes.ĭowngrading to 0.81 has fixed the issue for some people (including me), so while not 100% sure stream output is the culprit it seems to be pointed to by that. Either enable or disable vsync in game (esc->options->display) because "auto" breaks.
