Forum Discussion
16 Replies
The game progressed a couple seconds further but ultimately crashed before the prologue ended
The missing of a dedicated graphic card in your system might be a problem here, Intel graphic drivers are sometimes a problem, especially in older games.
Repair the game again.
(Origin: Game Library > Right-click the game cover > Repair)
(EA app: My Collection > Click on the three dots on the game cover > Repair)
(Steam: Game Library > Right-click the game > Properties > Local Files > Verify integrity of game files.)Then:
- Follow this manual to the letter to cleanly uninstall all Intel driver components.
(Use the latest driver from the HP website of our laptop.) - Install the graphics driver > Go online.
- Test.
- Follow this manual to the letter to cleanly uninstall all Intel driver components.
So now the game won't launch in steam (Failure:app running)...
Restart your laptop. (A real restart, not just shut down and start again.)
Then repair the game again.
(Steam: Game Library > Right-click the game > Properties > Local Files > Verify integrity of game files.)
Thank you. That got the app to launch but the game still crashes at the same place
- Go to your "...\Documents\Bioware\" folder.
- Move the "Dragon Age" folder to your Desktop.
- Test the game.
When I launch the game, the config page comes up, loads, and then the application closes.
This happens every time you launch from Steam as well?
- Press the Windows key and "R" at the same time.
- In the new Window, type or copy and paste "%LOCALAPPDATA%\CrashDumps" (Without the quotation marks) > Press ENTER
- Look if there are any "DAOrigins.exe.Xxxx.dmp" files in the "..Local\CrashDumps" folder.
- Zip 2 - 3 "DAOrigins.exe.Xxxx.dmp" files together and upload them at a free file hosting service like Dropbox or Onedrive.
- Post the link here.
If there aren't any dump files of ME:
- Press the Windows key > Write: Command Prompt > Right click on "Command Prompt" in the search results > Run as administrator.
- Copy and paste reg add "HKLM\Software\Microsoft\Windows\Windows Error Reporting\LocalDumps\devenv.exe" /v DumpType /d 2 /t REG_DWORD into the prompt Window > Press ENTER.
- Play the game until it crashes.
- After the game crashes, let all Windows crash dialogues finish.
- Press the Windows key and "R" at the same time. > Type "%LOCALAPPDATA%\CrashDumps" (Without the quotation marks) into the new window > Press ENTER.
- Zip 2 - 3 "DAOrigins.exe" files together and upload them at file hosting service like Dropbox or you can use the Onedrive "public" folder.
- Post the link here.
If you want to undo the automatic dump creation, use the command below in a elevated command prompt (As in point 1) reg delete "HKLM\Software\Microsoft\Windows\Windows Error Reporting\LocalDumps" /f
Yes, it happens when I try to launch it via steam, desktop, or files.
Is this the file you meant?
It looks like a DirectXShaderCompiler DLL (dxilconv.dll) leads to a access violation and a stop error.
This might very well be a driver problem as mentioned before.
Please preform a clean boot and test the Game in clean boot mode.
(Make sure the "EABackgroundService" remains enabled under point 3 in the guide.)Make sure your virus scanner and other security software and also Afterburner and similar software is disabled.
I performed a clean boot several times over the past couple of days. The config screen pops up, shows a loading bar as it is collecting game information, and then the program shuts itself down.
Run DDU again, but this time use the newest intel driver for your APU, you can find it on this Intel page.
(Use the stable version from 7/31/2023, not the beta.)I successfully installed the 7/31 version and rebooted the PC after running DDU. I verified game files and launched the game, but the same screen appeared and then closed the application.
Wait, nevermind. My video settings got reset so I had to go back in and lower them.
The game launches now. It's playing a couple seconds past the point where it usually crashes in the prologue, but ultimately crashes before the scene ends.
I am afraid we are running out of options here.
I suspect it's a driver problem, but I can't be 100%.Update:
I spoke with intel support and after some back and forth they informed me that the issue does not lie on their end. I have been directed back to EA.
Not a great update.