Ashes of the Singularity has crashed... Crash handler?

Well, was all excited to try this game from the start again (campaign), and when it just started to go into the action part, where the guys are requesting help, it crashed.

The (new?) crash handler has a few issues though, 1) there is no preview of what it is trying to send to Stardock, and 2) there is no privacy policy that I can find on that dialog.

The crash dump itself is:

Process Name: Ashes_DX11.exe : ... Process Architecture: x64 Exception Code: 0xC0000005 Exception Information: The thread tried to read from or write to a virtual address for which it does not have the appropriate access. Heap Information: Not Present

The RunLog.txt shows:

Executable Version: 1.20.20261
Executable Path: ... Ashes_DX11.exe
Graphics::EnumerateAdapters Complete
Device List Loaded: NumDevices = 1
Graphics::EnumerateAdapters Complete
InitTime: System::Init = 127
InitTime: Network::Init = 424
Crash Reporter Initialized
InitTime: Console&Resource::Init = 0
InitTime: LoadConfiguration = 0
InitTime: Audio::Startup Success = 86
InitTime: DoCreateWindow = 1382
InitTime: InitGraphics = 424
InitTime: InitializeShaders = 723
InitTime: UI Startup = 235
EnumerateMapDirectories at AppTime::Seconds = 4.888
Map Enumerate Time = 6196
InitTime: AppSpecific Startup = 7547
InitTime: Movie Initialized wait time = 0
Show Window Complete
InitTime: NetworkOverlay = 148
StateAppInit::Begin() at AppTime::Seconds = 11.304
StateAppInit - UI Menu Audio loaded at AppTime::Seconds = 15.540
StateAppInit - UI Game Audio loaded at AppTime::Seconds = 43.953
MasterContextLoadComplete() at AppTime::Seconds = 46.306
StateAppInit: EngineInit = 54757
InitTime: UI Audio Load wait time = 0
StateAppInit::End() at AppTime::Seconds = 70.521
StateFrontEnd::Begin() at AppTime::Seconds = 70.521
IntroMovie BeginPlay() at AppTime::Seconds = 70.521
UserNameAvailable at AppTime::Seconds = 70.521
StateFrontEnd::End() at AppTime::Seconds = 224.196
StateLoading::Begin() at AppTime::Seconds = 224.196
Map Path: Mission1
HeightMap Loaded at AppTime::Seconds = 224.494
ID Map Loaded at AppTime::Seconds = 224.582
Erosion Map Loaded at AppTime::Seconds = 224.744
Begin EngineCore::AsyncGameInit() at AppTime::Seconds = 225.713
End EngineCore::AsyncGameInit() at AppTime::Seconds = 226.248
StateLoading::End() at AppTime::Seconds = 226.283
StateGameView::Begin() at AppTime::Seconds = 226.283
StateGameView::StartupGame() Finished at AppTime::Seconds = 226.650
Crashed at AppTime::Seconds = 246.657
Crashed at AppTime::Seconds = 246.664

I can see it made SDCrash.zip which has a very small savegame in it, DXdiag output, the above runlog.txt, and the settings file.

The SDCrash.log file seems to be binary, no idea what is in it.

So, anyway, it really should be easier to parse what you are requesting people to send to your servers, and, a way to manually upload this stuff once a user looks over the data that is being sent.

 

 

2nd run no crash yet.. but  "typing ctrl" (in voice-over)?  Don't you mean "hitting ctrl key instead"?

Also, game was paused, and yet, as I was typing the thing about the control key, a voice just sighed, and said should have no problem outrunning it...

 

D'oh... it hung.

Description: A problem caused this program to stop interacting with Windows.

Problem signature: Problem Event Name: AppHangB1 Application Name: Ashes_DX11.exe Application Version: 1.2.0.0

Application Timestamp: 57596d50

Hang Signature: fecd

Hang Type: 134217728

OS Version: 6.3.9600.2.0.0.256.103

Locale ID: 1033

Additional Hang Signature 1: fecd7e7ac40dc62f21ce5d9f8a63e066

Additional Hang Signature 2: 26a8

Additional Hang Signature 3: 26a888264777436be5d8859ed4c4d9d6

Additional Hang Signature 4: fecd

Additional Hang Signature 5: fecd7e7ac40dc62f21ce5d9f8a63e066

Additional Hang Signature 6: 26a8

Additional Hang Signature 7: 26a888264777436be5d8859ed4c4d9d6

Waited a few mins to see if it responds again.... nope.

I will try DX12 version in a couple hours to see if it works better than the DX11 version.


35,280 views 7 replies
Reply #1 Top

Sorry to hear about that.  That's very odd.

The crash reports do automatically get sent to us so we can find out the issue. But thank you for posting!

Reply #2 Top

Sorry, I wasn't clear, I meant it had a dialog pop up asking for e-mail address and um... something else, and then a submit button.

That dialog.

 

I tried the first mission in DX12, all was fine there.

I went back to DX11, and I did get a freeze of around 5-6 mins before it resumed again.

 

Reply #3 Top

Quoting BadVoltage, reply 2

Sorry, I wasn't clear, I meant it had a dialog pop up asking for e-mail address and um... something else, and then a submit button.

That dialog.

 

I tried the first mission in DX12, all was fine there.

I went back to DX11, and I did get a freeze of around 5-6 mins before it resumed again.

 

 

That is odd indeed.  I don't suppose you have Visual Studio on your machine? :)

Reply #4 Top

Quoting Frogboy, reply 3


Quoting BadVoltage,

Sorry, I wasn't clear, I meant it had a dialog pop up asking for e-mail address and um... something else, and then a submit button.

That dialog.

 

I tried the first mission in DX12, all was fine there.

I went back to DX11, and I did get a freeze of around 5-6 mins before it resumed again.

 



 

That is odd indeed.  I don't suppose you have Visual Studio on your machine? :)

Actually I do.. 2013, 2014, and 2015 versions. :)

 

Reply #5 Top

thats awesome!

 

ok: next time you get a hang, open up visual studio, attach ashes as the process then break all. Post the stack info, even if it's just hex stuff. That will tell us a lot.

Reply #6 Top

>    Ashes_DX11.exe!00007ff7b21e0dc9()    Unknown
     Ashes_DX11.exe!00007ff7b21dec8d()    Unknown
     Ashes_DX11.exe!00007ff7b2218ec8()    Unknown
     Ashes_DX11.exe!00007ff7b2219187()    Unknown
     Ashes_DX11.exe!00007ff7b221929d()    Unknown
     [External Code]    

 

 

BTW, I noticed that if you happen to hit ESC when the (scripted) camera is moving to a location, it breaks the movement of the camera, so it is stuck where you pressed ESC, instead of continuing on to the location it is supposed to be.

 

 



Reply #7 Top

Here is that dialog.

For what it is worth, this appears to only show in offline mode.

Last Write Time:    6/13/2016 1:59:11 AM
Process Name:    Ashes_DX11.exe
Process Architecture:    x64
Exception Code:    0xC0000005
Exception Information:    The thread tried to read from or write to a virtual address for which it does not have the appropriate access.
Heap Information:    Not Present

No stack dump here...

I just started the very 1st campaign mission, where it froze before...