Ys VIII: Lacrimosa of Dana

Ys VIII: Lacrimosa of Dana

Ver estadísticas:
Acidburns 17 ABR 2018 a las 1:18
Crash, wont even launch, any idea ?
Hi,

I've read a lot of threads about crashes so far, but none of them seems to happen immediatly when the game is just launched. I click on Play, Steam displays "launched" next to the game's name, and then... nothing happens. "launched" just disapears.

Spec :
Windows 10 Pro
i7 8700k CoffeeLake
32Go DDR4
GeForce 1080
Asus Rog Strix Z370E Gaming

Thank you
< >
Mostrando 16-30 de 35 comentarios
Seattlehockeyfan84 19 ABR 2018 a las 12:33 
Publicado originalmente por Acidburns:
Publicado originalmente por gstommylee001:
it would be under application error not system.
it is actually under Application
Is there anything for the game being listed?
Acidburns 19 ABR 2018 a las 12:35 
Publicado originalmente por gstommylee001:
Publicado originalmente por Acidburns:
it is actually under Application
Is there anything for the game being listed?

nothing at all, when I launch the game and it closes immediatly, it seems not to log anything in the event log
Seattlehockeyfan84 19 ABR 2018 a las 12:41 
Publicado originalmente por Acidburns:
Publicado originalmente por gstommylee001:
Is there anything for the game being listed?

nothing at all, when I launch the game and it closes immediatly, it seems not to log anything in the event log

there should be. Its a applocation error and it should say ys8.exe in the details.
Acidburns 19 ABR 2018 a las 12:56 
Publicado originalmente por gstommylee001:
Publicado originalmente por Acidburns:

nothing at all, when I launch the game and it closes immediatly, it seems not to log anything in the event log

there should be. Its a applocation error and it should say ys8.exe in the details.

nothing related to that in the log :(
Seattlehockeyfan84 19 ABR 2018 a las 13:04 
Publicado originalmente por Acidburns:
Publicado originalmente por gstommylee001:

there should be. Its a applocation error and it should say ys8.exe in the details.

nothing related to that in the log :(

try loading the game, then under windows logs/application try to see anything that appears. Make sure its sorted by date with todays date being up top.
Última edición por Seattlehockeyfan84; 19 ABR 2018 a las 13:05
Seattlehockeyfan84 19 ABR 2018 a las 13:08 
my guess is its a 7b error that involves visual C++ Sean mention reinstalling it.

There are other files that could not be working right.

Try uninstalling all of the visual C++ stuff and redownloading them off the microsfot website you need both x86 and x64. There are multiple differen ones like 2010 2012 13 15 17 etc
Acidburns 19 ABR 2018 a las 13:13 
Nothing in the log. I'll try to reinstall Visual C++ again just in case
Acidburns 19 ABR 2018 a las 13:41 
Ok i installed all the visual c++ i could find, repaired 2010 and 2013 using the Microsoft's website ones, but still no changes. Idk what else I could try at this point.
Seattlehockeyfan84 19 ABR 2018 a las 14:52 
Publicado originalmente por Acidburns:
Ok i installed all the visual c++ i could find, repaired 2010 and 2013 using the Microsoft's website ones, but still no changes. Idk what else I could try at this point.

there is more than 2013 like 2015 2017
NISASean  [desarrollador] 19 ABR 2018 a las 14:54 
Publicado originalmente por Acidburns:
Ok i installed all the visual c++ i could find, repaired 2010 and 2013 using the Microsoft's website ones, but still no changes. Idk what else I could try at this point.

I'm not sure if this would help, but could you try the Preview branch that we've uploaded earlier today?

https://steamcommunity.com/app/579180/discussions/2/3288067088112098881/
Publicado originalmente por NISAAlex:
Here's how to access the preview branch:
1) From your Steam Library, right click on Ys VIII: Lacrimosa of DANA and select “Properties”
2) Go to the “BETAS” tab
3) Select the "preview" beta from the dropdown menu. This should start installing the beta version of Ys VIII (no password required)

We'll keep working together to find a solution for your launch issue.

Best,
Sean
Acidburns 19 ABR 2018 a las 23:24 
Thank you for your answers, i'm running the game using the preview branch, nothing changed.

I tried launching it directly with y8.exe (admin mode) located in the game root directory.
This time i get an error message : The application was unable to start correctly 0xc000007b.
I've replaced some .dll files in system32 and syswow64, nothing changed.

Also in the Windows event log/Application, the 2 ESENT errors always appear after i try to launch the game :

DllHost (14388,G,0) The beta feature EseDiskFlushConsistency is enabled in ESENT due to the beta site mode settings 0x800000
svchost (12504,G,0) The beta feature EseDiskFlushConsistency is enabled in ESENT due to the beta site mode settings 0x800000

Última edición por Acidburns; 19 ABR 2018 a las 23:25
Aemony 20 ABR 2018 a las 0:20 
Publicado originalmente por Acidburns:
Thank you for your answers, i'm running the game using the preview branch, nothing changed.

I tried launching it directly with y8.exe (admin mode) located in the game root directory.
This time i get an error message : The application was unable to start correctly 0xc000007b.
I've replaced some .dll files in system32 and syswow64, nothing changed.

That's a receipt for disaster. Run CMD in admin mode and execute a "sfc /scannow" right now, to ensure that you do not have any corruption or incorrect system files.

What logs do you actually get related to the game in Windows' Event Viewer? You should have an "Application Error" as well as an "Windows Error Reporting" right besides each others from when the game crashed. Both of these include some description about what caused the crash, in what module it occured, what the exception code was, etc.

The most commonly seems to be 0xc0000005, and simply means that /something/ in the process tried to access invalid memory. Either memory that did not exist, or memory that it did not have access to.


Publicado originalmente por Acidburns:
Also in the Windows event log/Application, the 2 ESENT errors always appear after i try to launch the game :

DllHost (14388,G,0) The beta feature EseDiskFlushConsistency is enabled in ESENT due to the beta site mode settings 0x800000
svchost (12504,G,0) The beta feature EseDiskFlushConsistency is enabled in ESENT due to the beta site mode settings 0x800000

This is not related to the game. It's something new in Windows 10 v1709 that Microsoft have enabled. That log comes on all systems every now and then.
Última edición por Aemony; 20 ABR 2018 a las 0:20
Acidburns 20 ABR 2018 a las 10:14 
Publicado originalmente por Aemony:
Publicado originalmente por Acidburns:
Thank you for your answers, i'm running the game using the preview branch, nothing changed.

I tried launching it directly with y8.exe (admin mode) located in the game root directory.
This time i get an error message : The application was unable to start correctly 0xc000007b.
I've replaced some .dll files in system32 and syswow64, nothing changed.

That's a receipt for disaster. Run CMD in admin mode and execute a "sfc /scannow" right now, to ensure that you do not have any corruption or incorrect system files.

What logs do you actually get related to the game in Windows' Event Viewer? You should have an "Application Error" as well as an "Windows Error Reporting" right besides each others from when the game crashed. Both of these include some description about what caused the crash, in what module it occured, what the exception code was, etc.

The most commonly seems to be 0xc0000005, and simply means that /something/ in the process tried to access invalid memory. Either memory that did not exist, or memory that it did not have access to.


Publicado originalmente por Acidburns:
Also in the Windows event log/Application, the 2 ESENT errors always appear after i try to launch the game :

DllHost (14388,G,0) The beta feature EseDiskFlushConsistency is enabled in ESENT due to the beta site mode settings 0x800000
svchost (12504,G,0) The beta feature EseDiskFlushConsistency is enabled in ESENT due to the beta site mode settings 0x800000

This is not related to the game. It's something new in Windows 10 v1709 that Microsoft have enabled. That log comes on all systems every now and then.


Thank you for your answers.
Unfortunatly, Windows logs absolutly nothing in the Event log. The only way to have an error message is to launch directly ys8.exe from the root directory, a popup appears telling me the "application couldn't start, error 0xc000007b, click ok to close" and that's it. After that, nothing else appears in the Windows event log, as if nothing crashed, except the Application popup line to notify me i just had a popup error, but without any more information.

I tried sfc /scannow, it found some error and said it repaired them. The game still won't launch tho :(
Aemony 20 ABR 2018 a las 12:09 
Okay, if you get 0xc000007b then that usually means one of the prerequisites for the game is not installed, or corrupt, or something similar. Could you rerun all the installers in the "_CommonRedist" subfolder of the game?
Última edición por Aemony; 20 ABR 2018 a las 12:09
Acidburns 20 ABR 2018 a las 12:54 
FINALLY WORKING
Thank you to everyone who took the time to answer, Aemony, gstommylee001, and many others.

In case this happens to anyone else, here is what i did :
- downloaded Depends22 tool, to know what ys8.exe needed to work. It showed some dll were actually installed, but showed in red. I guess it means they were corrupted. Even if i reinstalled VC++ 2010 and 2013 many times during my attempts the last few days, it didn't seem to delete the corrupted dlls. I removed them manually from system32 and syswow64, making myself the owner of some of them in order to delete them.

- uninstalled all the Visual C++ libraries (2005, 2008 2010 2012 2013 2015... all coming with "additionnal" or "minimum" addons, i think i had them all...)
- uninstalled .Net Framework and running the .Net cleanup tool (dotnetfx_cleanup_tool, easy to find)

- downloaded a Visual C++ Package, which contained 18 packages. It installs all of them at once.
- .Net framework came back clean (from windows update i guess)

I hope it helps^^
< >
Mostrando 16-30 de 35 comentarios
Por página: 1530 50