DA:Origins installed through Origins app keeps crashing

This game has stability issues on some CPUs. One suggested workaround that works for some people is to reduce your CPU affinity to one core. The downside is that it may affect performance.

Normally you'd have to do this every time you launch by going to the Task Manager in Windows. Here's a YouTube tutorial on how to set it permanently: https://www.youtube.com/watch?v=e565VSxdVhY

oo. I'll check that out. I saw about reducing it to one core, and I'd changed it, but I never checked to see if it stayed on one core. Will update when I have a chance to test

Busy weekend, but it appears to not be working. I set the shortcut (not launching through origin client) but when I check the task manager, it's still using all 8 cores.

I'll play around with it, but maybe if I manually set the process affinity every time I'll get better performance

Kind of obnoxious of me not to get back sooner. My apologies.

It... hasn't really changed. I have the game both through Origins and through Steam. Both behave the same way, even with new games. 

Not sure if there's anything else to do with it.

so, if anything, it's worse now. After

 there's immediately a transition, and it crashes every single time. I can't make any progress. Tried a few times yesterday. A few times today. Restarting computer, run without anything else running, earlier save points. No dice.

I wish I could remember exactly how I did it, but when I installed Origins through Steam a few weeks ago, I had to install a "LAA" (large address aware) or "4GB patch" to get the game not to crash all the time. I think Googling that will help you--I found a thread from 2014 in Steam's forums that detailed the steps needed. 

@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.

Thanks, I'll try that.