JaceRae
-
Posts
7 -
Joined
-
Last visited
Posts posted by JaceRae
-
-
5 hours ago, JaceRae said:
Hopefully the only time I see freezing in Warframe ever again is when I play Frost.
Well, I am playing Frost now, but unfortunately I seem to have cultivated the very unique ability to freeze things even when not using my skills.
My game is now locking up as soon as I get within range of the excavator on the third mission (Mining for Eudico). The second mission, from Biz, ran without issue.
This time Windows was at least popping up the "Warframe has stopped responding" dialog.
After successfully making it past the last mission, I mistakenly restored all my graphics settings to the "High" preset and remained in Borderless Windowed mode.
I've now gone back to potato mode and replayed the first part of Eudico's mining mission and that seemed to work. I aborted back to Fortuna with 8 seconds left on the clock.
Now I'm turning on graphical features until something breaks, then reverting and trying again. So far I've established:
- Volumetric Lighting, High Dynamic Range, and Adaptive Exposure do not appear to cause the lock-ups. This is great news because HDR and Adaptive Exposure make the Star Chart look nice.
- High geometry detail, high shadow quality, high texture memory, 4x Anisotropic filtering, Trilinear filtering, and/or SMAA are causing a problem. I'll be trying to isolate which one next.
-
So, err... I accidentally completed the mission. Sorry DE!
After reading this post:
My husband realised he hadn't considered switching away from Fullscreen mode. We tried Borderless Windowed and the game didn't freeze!
To be clear: I don't have a high-DPI setup (as far as I'm aware). Just a bog-standard 1080p monitor.
Hopefully the only time I see freezing in Warframe ever again is when I play Frost.
-
So, err... We fixed it (I think).
Tried Borderless Windowed mode and no crash.
Could kick ourselves for not trying that sooner.
On 2019-08-11 at 9:59 PM, Papragu said:This is no new issue at all. If you google it, you will find posts going back to 2013. I used to have this issue too, solution was to downclock your GPU. Alot of manufacturers make cards that come slightly overclocked. For some reason Warframe doesn't like this. If you downclock your GPU by 30-40 Mhz, the issue should stop. I know this doesn't seem to make alot of sense, since the game worked fine with the same GPU but it solved the issue.
Thanks for the advice. I happen to have an OC-edition PNY GTX 1080. My husband tried underclocking the GPU using MSI Afterburner to the "normal" GTX 1080 clock speeds, as well as *far* below the default clock, and neither worked. The game still froze.
As above, switching to Borderless Windowed mode allowed me to finish the Vox Solaris mission.
-
Having the same problem. Logged a support ticket with logs generated by launcher attached, and posted a thread in the forum.
-
Join me, fellow travellers, on a journey of frustration and self-discovery as I try to play the Vox Solaris quest on my potato of a CPU, paired with a GTX 1080.
I've logged the bug with all the detail I'm going to give here, but I thought it might be helpful to a fellow Tenno out there who might've run into the same issue.
Here's the issue: Whenever I try to play the Vox Solaris quest, Warframe freezes at the "Defend the Spy Drone" phase.
My computer doesn't lock up and the game doesn't fully crash to the desktop, but it completely freezes. I can open the start menu and I can launch Task Manager... I just can't do anything with them because frozen Warframe sits on top of everything and eats my clicks. Eventually my husband figured out that he could open a command prompt and type `taskkill /f /im warframe*` to get back to the deskop rather than having to reboot every time. (See the screenshot.)
We eventually hooked up a secondary monitor so that he could look at temperature readings and other performance stats while the game was running.
As stated, the issue is 100% reproducible as follows:
- Go to Thursby in Fortuna and select "Eudico sent me."
- Enter the elevator
- Collect the three Corpus Caches
- Go to the drone site and bring down the drone
- Eudico speaks her voice lines, and the reinforcements start appearing
- The game freezes
My husband helped me test many different configurations of game settings, but the freeze always happens, though it does not necessarily happen immediately. On some occassions I was able to play to 15/30 reinforcements killed before the freeze.
Thusfar, this has only happened in the Orb Vallis while on the Vox Solaris quest. I have played many other missions on Earth, Venus, Mercury, and unlocked Mars without the game freezing like this.
I've told DE that given that I have an easy way to reproduce this bug (i.e. the Vox Solaris quest), I am happy to keep my Vox Solaris quest uncompleted and run it with whatever conditions they require to isolate the issue.
Anyway... I promised a potato CPU. Here are my computer specifications:
- AMD Athlon II X3 435 ("WHAT YEAR IS IT?")
- ASUS M4A89GTD Pro
- 8GB RAM
- GTX 1080 (OEM: PNY)
- Windows 10 Pro (64-bit)
Don't be too mean to my potato CPU... It is well within the minimum requirements.
After we Googled various combinations of "Warframe freeze", "AMD", "Fortuna", "Orb Vallis", and "Vox Solaris", we tried several things to fix the issue.
First up, we tried verifying and optimizing the game cache.
Thinking it might be a driver issue after the upgrade from an older Radeon card to the GTX 1080, we uninstalled whatever vestigial AMD drivers there might be as well as the current Nvidia drivers using DDU, then reinstalled the latest GeForce driver (without GeForce Experience this time) and my motherboard chipset drivers.
That didn't fix anything. Spoiler warning: nothing we did fixed the issue.
We then went through several combinations of game settings to see if maybe there was some new-fangled tech that might be conflicting with my CPU:
- High graphics preset, disabling Runtime Tesselation, Anti-Aliasing, HDR, Volumetric Lighting, Adaptive Lighting, Glare, Film Grain, etc.
- Audio reverb disabled
- Medium graphics preset, also disabling things one at a time.
- Low graphics preset --- all the bells and whistles disabled
- Full potato mode (DirectX 10, low graphics)
In-between all this we also checked the Event Viewer, which only confirmed that this wasn't a graphics driver crash issue like some people were getting, but I tried DirectX 10 mode anyway.
During one of the many crashed runs of the Vox Solaris quest we attempted, I noticed that my RAM usage went well over 2GB - much higher than most of the other areas of the game I've played.
This shouldn't be a problem considering that I've got 8GB RAM, but my husband thought that maybe there was a chance that my RAM was faulty, so he ran the built-in Windows 10 memory checker and it came back clean.
On the off chance it was a virtual memory issue, he also set the minimum swap space on one of my lesser-used drives to 16GB.
To monitor the temperature of the computer, we installed GPU-Z and Core Temp, which showed that the CPU was running quite hot by the time Warframe freezes. At the recommendation of a friend, we cracked open the case and I set about cleaning the many years of dust that had caked into the heatsink.
We tried again. The CPU temperature plummeted from between 70C and 77C, to under 50C while in the heat of the mission. This must be it! Warframe was causing the CPU to run at full tilt and the thermal throttle was causing the game to crash spectacularly!
Nope. Crushing disappointment once again. The game freezes and we're left testing two last things: a hard drive scan and DirectX 10 mode (which I already mentioned above).
The drive scan said there were errors on the drive with Warframe on it. We rebooted and repaired, but alas, once again the game froze at the exact same phase in the mission.
And that brings us to now, where I'm sharing my long and painful journey with you all, hoping it may be useful to someone in future. For now, it seems I am locked out of getting my K-Drive and all activities on the Orb Vallis, but that's fine if DE wants to use my account to isolate the bug. I'll happily play elsewhere for now... And if worst comes to worst and the issue can't be fixed and we can't upgrade my CPU and motherboard anytime soon, I can at least play through the quest on my husband's computer.
I'm just worried that what's happening in Vox Solaris might be indicative of a general issue on the Orb Vallis that would cause my game to randomly crash whenever I try to do any activities out there.
Adventures in troubleshooting - Freeze on Vox Solaris quest
in General
Posted
Well that was disappointing. After many more hours of testing, we thought we were making some real progress... building a list of graphics settings that were "safe" for my combination of hardware. Then we tested a "safe" configuration again and it bombed.
We thought we noticed that the crashes happen when we're being knocked around by shockwaves or when we're in the blast radius of the excavator when it comes down. So, we disabled Screen Shake and seem to be getting fewer "unexpected" crashes now.
It also appears as though some of the crashes and freezes only happen when the Orb Vallis is in its warm cycle. This still needs some more testing, though... we didn't properly document the effects of the warm cycle on the different settings we tested. We just tried to make sure that whatever was working also worked in the warm cycle.
Settings that appear to cause lock-ups
Settings that were not yet fully tested
Current working config
Everything else is set to its lowest setting, either Disabled or Low.
Of course, this isn't entirely scientific testing. We didn't restart the game between every test, so it is possible that there could be false positives and false negatives we haven't identified yet.
We also didn't test every possible combination. We went for the settings we thought would improve the look of the game most (e.g. HDR + Adaptive Exposure, Volumetric Lighting + Dynamic Lighting).
Here ends my testing for now. If I run into crashes based on this config or find more settings that reliably work, I'll post again.