Game Crashes After Initial Opening Screen

I've recently changed my graphics card from a Sapphire 7970 to a R9 390x.  The game worked fine with the 7970, now it just gives me the opening screen, says initializing, and then crashes to desktop.  It does this for DX11 & DX12 both. 

I've updated to the latest Radeon Catalyst driver, and now have installed the beta version.  I've also tried uninstalling the game, and re-installing.  Same thing, just crashes.

Is there possibly something in the configuration for the game left over after the uninstall for the old card?  Do I possibly need to clear the config somehow?

Thanks

52,079 views 22 replies
Reply #2 Top

Have you checked your settings.ini file and made sure everything is as it should be (No settings are too high)? You could also delete it so the game creates a new one. I'm also wondering if you've performed a clean install of your video drivers.

Settings.ini locatioN:

C:\Users\YOUR_USERNAME\Documents\My Games\Ashes of the Singularity

Reply #3 Top

I just tried deleting everything from that directory.  I ran the game, same result, initial screen, then crash to desktop on both DX11 & DX12.

I've not tried deleting all my Radeon drivers, but I have updated it both with the current version, and the newer beta version just to make sure it forced an update.  Didn't help.  I can try uninstalling all of the Radeon stuff, and then re-installing.

Reply #4 Top

I've just used the AMD cleanup utility to remove all of my AMD related Radeon software, and re-installed with the current file from the web site.  Cleaned the directory given, and same result...still crashes. :(  Arrgghhh...I so want to play this game too...especially after spending $100 to become a founder.

Here's my settings.ini file, and runlog.txt file after running the game:

 Is there any way to run the game with a debug option to get a detailed crash report I can post?

User Directories Created
Graphics::EnumerateAdapters Complete
Device List Loaded: NumDevices = 1
Graphics::EnumerateAdapters Complete
InitTime: System::Init = 69
InitTime: Network::Init = 42
Crash Reporter Initialized
InitTime: Console&Resource::Init = 0
InitTime: LoadConfiguration = 0
InitTime: Audio::Startup = 42
InitTime: DoCreateWindow = 5
InitTime: InitGraphics = 466
InitTime: InitializeShaders = 13885
InitTime: UI Startup = 71
InitTime: AppSpecific Startup = 12
InitTime: UI Audio Load wait time = 443
InitTime: Movie Initialized wait time = 0
Show Window Complete
StateAppInit::Begin() at AppTime::Seconds = 15.136
 
 
 
 
 
[General]
IniVersion=10
 
[System]
FullScreen=0
Resolution=1920,1080
VSync=1
FreeSync=1
HotLoadEnabled=0
UIScale=1.0
BindCursor=FullScreen
AFRGPU=0
AsymetricGPU=0
SkipMovie=0
AutoSave=1
HealthBarsAlways=0
HideHotKeys=0
EmulateFullscreen=1
 
[Quality]
PointLights=High
Glare=High
ShadingSamples=16
TerrainShadingSamples=8
ShadowQuality=High
EnableMotionBlur=1
MaxMotionBlurFrameTime=12
MotionBlurInterframeTime=4
MSAASamples=1
MipsToRemove=1
RenderResolution=1920,1080
 
[Audio]
MuteAll=0
Volume_Master=100
Volume_Music=50
Volume_Environmental=50
Volume_Effect=50
Volume_UI=50
 
[Map]
DefaultMap=Deneb
Reply #5 Top

Sorry to hear you're experiencing this problem. Can you download and run the tool below:

http://sd.stardock.com/Support/supportToolTest/SDSupportTool.exe

Then attach the .zip that's created and send it in with a ticket to support:

https://esupport.stardock.com/index.php?/Tickets/Submit

Hopefully we can check your MSInfo logs to see if anything shows up that tips us off. Otherwise you'll need to wait until we have some more debugging to obtain. Crash reports are sent to the developers however already, so they receive the info.

Reply #6 Top

OK, I've run the support tool and uploaded the file that was generated.  Let me know if there's anything further I can do.

Thanks

Reply #7 Top

Finally got it past the initializing screen by deleting the settings.ini that The_Gear mentioned and also disabling SLI. If I enable SLI again and try and load through DX12 I get the usual drop back to Windows desktop, though before the last update I didn't need to do this.  

Well at least now I have the game running in DX12 again which I'm happy with.

Reply #8 Top

I had crashes with a 980 Ti, mostly in DX 12 after firing up a game.  I had to disable G-sync and V-sync in control panel and game options. No crashes, play for hours.

Reply #9 Top

Interesting that SLI had to be disabled.  I'm only running the single card, so doesn't apply to me, but made me think about any options in the Radeon control panel that could be adjusted that might be causing the crash to desktop.  Currently I just have the default options, as I re-loaded the graphics drivers.  But I did enable the graphics overclocking.  After the crash I turned it off again and tried it with it off as well, so probably not the issue, but maybe there's some other settings that need to be modified?

Reply #10 Top

OK, so for me the solution was to let Windows handle the size of the pagefile. I had limited it to 2GB, which apparently wasn't enough for this game...

Reply #11 Top

I'm having the same issue, new install of the game. GTX970.  Ticket WZG-615-31162.

I've attempted the various changes mentioned in this thread, disabling vsync/gsync, pagefile, deleting settings.ini.  Also tried tweaking the settings.ini to skip movie, force full screen.  Disabling emulatefullscreen allows the game to actually get to the menu but then when you try to start the game it crashes the display driver at the loading screen.

 

Faulting application name: tachyon.exe, version: 1.2.3.280, time stamp: 0x55def94b
Faulting module name: ntmarta.dll, version: 10.0.10240.16384, time stamp: 0x559f3c02
Exception code: 0xc0000005
Fault offset: 0x000066b0
Faulting process id: 0x3810
Faulting application start time: 0x01d0fce8485a2bb4
Faulting application path: C:\Games\Steam\steamapps\common\Ashes of the Singularity\tachyon.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntmarta.dll
Report Id: 8f3ac0cc-7f99-47d0-9b35-f67368e8be98
Faulting package full name:
Faulting package-relative application ID:

Reply #12 Top

Well my card (R9 390x) has 8 GB of RAM, so that would qualify.  Known issues with cards that have allot of memory?

Reply #13 Top

Quoting XavierMace, reply 11

I'm having the same issue, new install of the game. GTX970.  Ticket WZG-615-31162.

I've attempted the various changes mentioned in this thread, disabling vsync/gsync, pagefile, deleting settings.ini.  Also tried tweaking the settings.ini to skip movie, force full screen.  Disabling emulatefullscreen allows the game to actually get to the menu but then when you try to start the game it crashes the display driver at the loading screen.

 

Faulting application name: tachyon.exe, version: 1.2.3.280, time stamp: 0x55def94b
Faulting module name: ntmarta.dll, version: 10.0.10240.16384, time stamp: 0x559f3c02
Exception code: 0xc0000005
Fault offset: 0x000066b0
Faulting process id: 0x3810
Faulting application start time: 0x01d0fce8485a2bb4
Faulting application path: C:\Games\Steam\steamapps\common\Ashes of the Singularity\tachyon.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntmarta.dll
Report Id: 8f3ac0cc-7f99-47d0-9b35-f67368e8be98
Faulting package full name:
Faulting package-relative application ID:

I've replied to your ticket :)

Reply #14 Top

Ticket ID: HHT-613-11683 has been sent to Development Team for review and recommendations.  Thanks to all who gave suggestions to try and solve.

Reply #15 Top

Quoting XavierMace, reply 11

I'm having the same issue, new install of the game. GTX970.  Ticket WZG-615-31162.

I've attempted the various changes mentioned in this thread, disabling vsync/gsync, pagefile, deleting settings.ini.  Also tried tweaking the settings.ini to skip movie, force full screen.  Disabling emulatefullscreen allows the game to actually get to the menu but then when you try to start the game it crashes the display driver at the loading screen.

 

Faulting application name: tachyon.exe, version: 1.2.3.280, time stamp: 0x55def94b
Faulting module name: ntmarta.dll, version: 10.0.10240.16384, time stamp: 0x559f3c02
Exception code: 0xc0000005
Fault offset: 0x000066b0
Faulting process id: 0x3810
Faulting application start time: 0x01d0fce8485a2bb4
Faulting application path: C:\Games\Steam\steamapps\common\Ashes of the Singularity\tachyon.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntmarta.dll
Report Id: 8f3ac0cc-7f99-47d0-9b35-f67368e8be98
Faulting package full name:
Faulting package-relative application ID:

 

What this DX11 or DX12?

Reply #17 Top

Well I've finally got DX12 to start in SLI now without it switching back to the Windows desktop as before I had to disable SLI to get DX12 to work but now thanks to the tip sanoj52 said about the page file It now runs with SLI enabled. I had my page file disabled when I got my 16GB of ram not too long ago but when I set it back to system managed I could now run DX12 without having to disable SLI.

Reply #18 Top

After the last post, I thought I'd take a look at the page file.  I also had it disabled.  I don't have any SLI, but thought I'd give it a try.  Success!   :)  I am very surprised, but putting the page file to system managed fixed the issue.  My game works!  :)

Now, I know I didn't have any page file enabled before either with my old graphics card (Radeon 7970).  So apparently this is only an issue with some graphics cards, or else the game updated and this is something new.

In any case, anyone experiencing crashes to desktop at startup, I would recommend to set the page file to system managed.  It worked for me!

I will also send an email for the ticket letting them know what I've found.  Thanks everyone for the help!

+1 Loading…
Reply #19 Top

MSI R9 390X Gaming 8 GB owner here.

Just to throw this out there.  If the MSI Gaming App (Not MSI Afterburner) is running, Ashes of Singularity will not start.

If the game is running, and I open MSI Gaming App, the game will shut down.  No notice, nothing.  I was opening it to run the on-screen FPS and GPU stats and found it interesting.  A 2nd time I opened it I was switching my graphics card from Silent mode to Gaming mode.

I now know how to see GPU and FPS stats in game, and that's all find and dandy, but wanted to point out this compatibility thing with MSI Gaming App.  I'm confident it has to do with the Overlay, but not 100% sure.

Reply #20 Top

Changing the page file to system managed got the game to boot for me, but now it crashes during map loading. Time to go check another thread :)

Reply #21 Top

Excellent!