Warframe not Launching Consistently for Weeks

[camtonoooo]

I've been having an issue where I click to play Warframe within Steam and the Warframe launcher will not open. I'm in the midst of a prolonged tech support ticket with DE Support about this, and have tried numerous things, from reinstalling Steam/Warframe, checking integrity of windows install, disabling all non-vital start services, and much more. Every other application and game on my PC works just fine; only Warframe is giving me problems. 

The weird thing is that sometimes, randomly, the launcher does work. It didn't work for almost a week, for the past few days it's been working just fine, and now it isn't working again. It's like every time I want to play Warframe, it's a game of Russian roulette to determine whether I can or not.

I saw in the most recent patch notes that there was a server-side deployment for an issue where the launcher would not work on new installs, though this issue I'm experiencing makes me think it's more pervasive than just new installs, and that the issue is still there. Is anyone else having a similar problem?

[Hobie-wan]

When it doesn't open, go to search on the start button (or Cortana, ew) and look for event viewer. Pull it up and on the left go to Windows Logs and then Applications. There's a date and time column, so if you look at stuff that happened just now when the game failed to open, you might get a clue.

[camtonoooo]

@Hobie-wan Thanks for the suggestion! Here are the logs I get when trying to launch:

 

Faulting application name: Launcher.exe_unknown, version: 2020.11.25.12, time stamp: 0x5fbe96fe
Faulting module name: ntdll.dll, version: 10.0.19041.610, time stamp: 0xe5d7ed5c
Exception code: 0xc0000374
Fault offset: 0x00000000000fed29
Faulting process id: 0x640
Faulting application start time: 0x01d6c6b2421a75f5
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\Warframe\Tools\Launcher.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 74aa0b41-53d5-4c5b-8412-e68a0c72c1c6
Faulting package full name: 
Faulting package-relative application ID: 

 

Fault bucket 1930431122950377858, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: Launcher.exe_unknown
P2: 2020.11.25.12
P3: 5fbe96fe
P4: StackHash_c9d4
P5: 10.0.19041.610
P6: e5d7ed5c
P7: c0000374
P8: PCH_BE_FROM_ntdll+0x000000000009C8F4
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6C11.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6C7F.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6C90.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6C9D.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6CAE.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Launcher.exe_unk_9f43ce650ae3f0f3dd5e9ddcb8a4b957dba3a_4265e2d9_181b31db-9b2d-467b-a760-6aadfaf1ab17

Analysis symbol: 
Rechecking for solution: 0
Report Id: 74aa0b41-53d5-4c5b-8412-e68a0c72c1c6
Report Status: 268435456
Hashed bucket: c25abf34b38edb5d0aca44e0e2d0d182
Cab Guid: 0

 

 

Any idea what this means?

[Hobie-wan]

The Exception code 0xc0000374 is probably the most useful bit. Googling around pointed to suggestions like these:

https://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_perf-insiderplat_pc/explorerexe-crashes-exception-code-0xc0000374/71f6e9f0-89c0-4c73-9fb4-0c75648f5136

Methods 1 and 3 are the easier ones to try at that link in the answer post.

From another link, some stuff in your windows user could be corrupted. You could create a new user and see if WF will launch ok from that new one. Though moving stuff to a new user can be a big pain in the butt, it still could be useful to test if the other stuff doesn't help. Perhaps you need to scan your hard drive for errors if there's some corruption that's only sometimes affecting WF. Maybe there's some temp user stuff that's wonky just some of the time that only WF is using.

Good luck.

[NoSpax]

Check your RAM for errors, because that error code is a heap corruption.

https://www.howtogeek.com/260813/how-to-test-your-computers-ram-for-problems/

[camtonoooo]

@NoSpax Tested the RAM as you suggested and upon completion was told "The Windows Memory Diagnostic tested the computer's memory and detected no errors".

[NoSpax]

That's odd. Since everyone should have the same files, the problem must be on your end.

Did you had a Windows update (one of those super long ones) recently?

[camtonoooo]

@NoSpax No, I don't believe I had any sort of major windows update recently, though it may have happened automatically while my PC was on and I was away from it. Why would only Warframe be giving me issues, though? All my other games, whether graphically intensive or not, with their own launcher or without, within and not within Steam, etc. and they all work perfectly. It's only Warframe giving me problems.

[ChaosShard]

Same problem here. But in my case, The problem occurred right after windows forced me update to 2H12 or somewhat version. Hope there is a solution to this. Can’t roll back my system.