So I've managed to play through the introductory bit, in the infirmary when trying to leave the game crashed with a DirectX error popup saying the following:
See a few others have ran into this, any ideas on what to try? Reinstall the latest Nvidia driver?
Yeah I've gotten that 3 times in 4 hours of playing.
I get the same message I made sure my drivers are updated
Curious to know if rolling back the drivers would fix it. **bleep** shame as I managed to play a couple hours and was having a blast.
this
I'm also running into this same error and I've tried everything in the link above, does anyone know of any other fixes?
SOLUTION THAT HELPED ME.
So I had the exact same issue everyone is reporting here, spent most of the day doing everything reinstalling, re-install drivers, reinstall DX, nothing worked, until I did a deeper dive into event viewer and searching the specific issue causing the crashes, in my case this is what was the issue:
Windows Paging size was to little,
Do the following and let me know if it helps you:
(Keep in mind the higher the paging size, the more storage is occupied from your C-drive)
To be clear:
Initial size - 24000
Maximum size - 24100.
Hope this helps at least some of you, I been able to play without interruptions, and before I struggled to even pass the character creation.
About how much storage is left available on your C drive for this to work for you. I really dont want to delete Bg3 lol
I have over 600GB open on my drive, but I also only had the one crash so far
Does this need to be the drive the game is on or the C drive? I'm running off an external SSD. Not seeing an option to change anything?
Tick of "Automatically manage paging file size for all drives" at the top, than you should be able to change it. The changes needs to be for the C-drive.
I tried this it didn't work for me. Is there anything we can do to fix this?
Sorry to hear man, its **bleep** when nothing works, trust me before I found this fix for me, I did everything, defragged, reinstalled, downgraded windows update, repaired the game, Reinstalled DX, reslotted GPU, cleared CMOS, reset bios, the list goes on, nothing worked aside from what I shared here.
In my case I looked in event viewer and thats where I spotted the Virtual Memory running low, cause I have 16GB Ram, the game runs about 98% of that memory, increasing your VM made sure there was backup memory if it reached 100%.
Community ManagerHey Everyone,
If you are still running into the DirectX Error 'GetDeviceRemovedreason", let us know the following information if you have not already.
We can use this information, to help make the team aware of the issue and to further investigate.
Cheers!
I've answered a lot of this in my replies above, but compiling it here with extra files:
EA ID: JennyCross34
Which client are you on? EA App (PC)
EA app Error ID Number: a2ad0915-5e0e-4969-a6c2-016f233783a7
Does this happen at a specific point while playing, or after a certain time playing? A bit of both.
The error first occurred in Character Creation, whenever I went to the Inquisitor section. I was able to get past this by disabling strand hair. (I'm also one of the people with an RX 7900 XTX affected by graphical artifacting.) By disabling this, I was able to enter the game and play, though I experienced several crashes, and this time there was no common factor.
I only tracked the most recent 21 crashes, over the course of 13ish hours of play and troubleshooting on Saturday and Sunday:
• 7 were in cutscenes
• 1 was in combat
• 1 was in a vendor window
• 1 was while reading a codex
• 1 was during the shader business before the game properly loaded
• 10 were running around in the world (1 Ossuary, 1 Crossroads, 1 Arlathan, 2 Treviso, and *5 Dock Town)
Six of these crashes also crashed the EA App with the game. One was violent enough it locked up Windows for a bit.
*The final five "running around the world" crashes were in a very specific area of Dock Town. Attaching images for reference. (I also got this weird black rain/smoke/eyes stuff, which happened 2-3 times before. Reloading usually fixes it, but this time it didn't--so I'm attaching the pic just in case it's somehow related.) I've been stuck at this point, unable to progress, ever since. When the patch dropped today, I tried again--but I can't even load into the game before it crashes now. It crashes on the black loading screen. Loading any of the auto-saves results in the same.
Hope some of this helps.
Update: November 13, 2024
I updated Windows last night and saw Veilguard Patch 2 happened this morning. I know the patch notes were small and specific, and did not include this issue, but I tried anyway for science. No change.
Update: November 22, 2024
A little late due to internet outage, but I have applied Patch 3, made sure everything else was up-to-date, etc. No change.
Hope you are able to fix it!
EA ID: Erenyin
Which client are you on? Steam (PC)
Does this happen at a specific point while playing, or after a certain time playing? Various. Some fixes have worked for a while and then stopped helping. Behaviour that has been fine one day has changed in the next. Turning off strand hair has fixed instances of specific crashes detailed below, but I haven't run the game for long enough with it off to confirm if it fixes the random instances too.
Some specific instances always seem to trigger a crash, of those I remember:
- entering the eluvian room in the Lighthouse
- the start of the cutscene waking up in the infirmary after the introductory sequence
- the start of every dream/meditation cutscene with Solas in the Fade that I've had
- the start of the cutscene with Bellara repairing the eluvian
- using the mirror of transformation for a second time (the first time seems to work, at least if it's quick)
However, there have also been seemingly random instances unrelated to specific events or played time:
- while the game was paused and I was out of the room (ESC pause menu, not skills/party/etc)
- while viewing the companion menu and switching between characters
- others that I'm not remembering
I've applied the patch and re-tested those that I can with available save files, with no improvement from the pre-patch version.
DxDiag is attached.
Any updates on this? Still an issue here even after Patch 3. I don't remember this being an issue until at least after the first patch. Was fine at launch.
Done all the suggested ideas, reinstalled the latest Nvidia Drivers and even the game, still crashed as of yesterday after maybe 2 hours. Never seen this error before this game in all my years playing on PC.
After the new patch and the new Nvidia driver and re-compiling shaders, I still have this error pop up.
Please Advise!! I have been getting this error for hours after the install took from 11 to 4:30 CST. All drivers up to date, running directx 12, amd ryzen 3 3250, did BIOS update before game launched, even un-installed then reinstalled amd drivers because updating gave me a black screen. I've gone to the tech issues page and done all the steps but a clean boot even clearing cache in EA app and I'm re-downloading the game now. Please help I paid for this on pre order 2 months ago and I really want to enjoy it!!
I would just refund the game at this point if you are able to.
3 patches in and they have not fixed the crashing and seem to have no idea of what is happening. I'm pretty convinced at this point there is a flaw with Frostbite Engine that is so fundamentally broken that they cannot fix it, considering many people have referenced that the only other games they have had similar issues with were other Frostbite Engine games, such as NHL, and those were never fixed.
Just had this again today, this crash has happened twice now. Really impacting my ability to enjoy the game unfortunately
Nearly 150 comments in this thread and no response from EA?
I read somewhere that it seems like the crash is due to the hair strand shaders writing to a UAV, then reading it back in the same workgroup, but missing the device's memory barrier in places, which causes the GPU hang. Surely you could patch in some kind of workaround to this to prevent it in cases caused by strand hair? I really don't want to have to turn it off permanently as I think the hair looks awful with it turned off.
