Forum Discussion
@EA_Atic No mods. Only the DLC available in the Origin application. I currently have the console enabled, but this started before I did that. I also have the command line to run using only one core like discussed above. So, tags to the exe, but no mods.
I just had a play session that lasted about an hour, with a few game saves/loads along the way, and a few times I switched windows. I felt like these actions are often potential destabilizers to some applications. They did not seem to matter much, though. The crash happened shortly after an area transition as a plot-important dialog started.
Most of the earlier crashes, if not all, have happened at area transitions, and this is the first I remember that wasn't strictly an area change. (I don't know how it's programmed, but I reckon there are some similar processes at work for the beginnings of these conversations and for loading an area.
I forgot to include the event viewer data.
There are three relevant entries. Two are Info logs saying "The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start." and then the reverse (auto to demand) five minutes later. These are about 15 minutes after the crash.
At time of the crash, an error shows up:
Faulting application name: daorigins.exe, version: 1.5.13263.0, time stamp: 0x52164c37
Faulting module name: daorigins.exe, version: 1.5.13263.0, time stamp: 0x52164c37
Exception code: 0xc0000005
Fault offset: 0x0006e69c
Faulting process id: 0x2ef8
Faulting application start time: 0x01d83ef88e7eff9a
Faulting application path: C:\Program Files (x86)\Origin Games\Dragon Age\bin_ship\daorigins.exe
Faulting module path: C:\Program Files (x86)\Origin Games\Dragon Age\bin_ship\daorigins.exe
Report Id: 9e33d844-c5bf-4f81-952f-efce616e2c7b
Faulting package full name:
Faulting package-relative application ID:
Do you want me to provide the details? And if so, do you want the XML or a copypasta of the friendly view?