Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I started looking around for any additional cache files I could delete, and eventually found some at %localappdata%\BioWare\Dragon Age The Veilguard\cache
After deleting all the files in that folder (yesterday afternoon), I haven't had a single crash! Just to be sure, I clear the folder out every time prior to starting the game.
Just posting so that I can find this post again if someone else posts with the same problems.
Or if it starts happening to me.
There is definitly something wrong with that game. It cooks CPUs. I got 12700k and 4080 and I never had any issues with any game. I changed my CPU fan settings and limited frames to 100 on my 120hz LG Oled, this solved it.
Capping my frames to 60 didn't fix it. I had switched my cpu fan from standard to turbo in my bios menu, but that didn't really improve it much (all these were adjusted on Nov 1), so wondering if I need to crank the cpu fans to 100 and mess with my case fan in/out flows.
I have 12700k and 4060 running on a 144hz LG Ultrawide
Wanted to update everyone in case anyone else has this problem- after 8 trips to microcenter, we discovered my new CPU was defected. They got me a new one, and I’m playing the game again! Thank you to everyone who offered advice!
How is this still a thing? Worked for me, thank you.
Yes, I necro'd this thread because this answer solved my problems and is still relevant, regardless to the OP's original issue. Glad he got that sorted!