vSam Posted July 4, 2015 Share Posted July 4, 2015 (edited) Ok, so, I'm unable to send in a crash report about this because the game doesn't actually crash. It just becomes unresponsive and will not become responsive no matter how long the wait. However, I do get a Windows error. Here's what it is: Description: A problem caused this program to stop interacting with Windows. Problem signature: Problem Event Name: AppHangB1 Application Name: Warframe.x64.exe Application Version: 2015.7.2.11 Application Timestamp: 559553d1 Hang Signature: 9ab9 Hang Type: 0 OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 1033 Additional Hang Signature 1: 9ab910cb53155d5a14b384487282a7b9 Additional Hang Signature 2: c1a8 Additional Hang Signature 3: c1a8b4c988616a2421d3dfd92c05279f Additional Hang Signature 4: 9ab9 Additional Hang Signature 5: 9ab910cb53155d5a14b384487282a7b9 Additional Hang Signature 6: c1a8 Additional Hang Signature 7: c1a8b4c988616a2421d3dfd92c05279f This specific "crash" happened during a mobile defense mission when I went to put the datamass into the console. I feel like this MIGHT be due to enabling the experimental physics optimizations listed in [DE]Glen's thread, I can't remember this specific issue happening before I turned the optimizations on. Here's some PC information: OS: Windows 7 GPU: AMD Radeon HD 7870 CPU: AMD FX-4100 (Overclocked to 4.1GHz) Edited July 6, 2015 by vSam Link to comment Share on other sites More sharing options...
vSam Posted July 6, 2015 Author Share Posted July 6, 2015 (edited) Well, here's another one. This seems to be happening most often in capture missions. Specifically, when the capture target comes into vision. Description: A problem caused this program to stop interacting with Windows. Problem signature: Problem Event Name: AppHangB1 Application Name: Warframe.x64.exe Application Version: 2015.7.2.11 Application Timestamp: 559553d1 Hang Signature: 9ab9 Hang Type: 0 OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 1033 Additional Hang Signature 1: 9ab910cb53155d5a14b384487282a7b9 Additional Hang Signature 2: c1a8 Additional Hang Signature 3: c1a8b4c988616a2421d3dfd92c05279f Additional Hang Signature 4: 9ab9 Additional Hang Signature 5: 9ab910cb53155d5a14b384487282a7b9 Additional Hang Signature 6: c1a8 Additional Hang Signature 7: c1a8b4c988616a2421d3dfd92c05279f Edited July 6, 2015 by vSam Link to comment Share on other sites More sharing options...
vSam Posted July 12, 2015 Author Share Posted July 12, 2015 Upon someone loading into my dojo. Description: A problem caused this program to stop interacting with Windows. Problem signature: Problem Event Name: AppHangB1 Application Name: Warframe.x64.exe Application Version: 2015.7.10.15 Application Timestamp: 55a01c8f Hang Signature: bf5c Hang Type: 0 OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 1033 Additional Hang Signature 1: bf5cf451b844d88f341ce7039f553440 Additional Hang Signature 2: ce30 Additional Hang Signature 3: ce30c7481252b0f3da91197cb20ee47b Additional Hang Signature 4: bf5c Additional Hang Signature 5: bf5cf451b844d88f341ce7039f553440 Additional Hang Signature 6: ce30 Additional Hang Signature 7: ce30c7481252b0f3da91197cb20ee47b Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now