Hi EA_Barry,
Thanks for replying, and as someone who worked at Rockstar Games for 9 years, I understand how the industry works. Visceral is probably in crunch right now working on their Star Wars game, and since Dead Space 2 came out 5 years ago, their coders probably don't have the last DS2 build or assets on a workstation ready to test which means there would need to be resources pulled from the Star Wars game just to get things set up to build, test and validate a fix, and I'm guessing the producers running the team over there don't have a lot of interest in diverting their resources right now (their EA overlords probably feel the same).
On the flipside, keep in mind that AMD's Zen Summit Ridge is coming out in a couple of months, and that means more enthusiast CPUs (16-processor CPUs to be exact) that Dead Space 2 is just going to crash on launch on (this is in addition to the high end Intel CPUs it's already crashing on). Enthusiasts aren't going to like learning they have to gimp their performance and reboot their PCs to play Dead Space 2 (and ironically Dead Space 1 does not have this problem!) EA should put up an FAQ page about this issue, and ideally the EA Origin client team should leverage the fact that they can check the processor count in a system and issue a warning to anyone launching the game that they're going to experience a problem if they have more than 10 processors, and ideally communicate the work-around to the user (could just be a link to an EA FAQ page).
Meanwhile, I'll reach out to some of the developers of third party D3D interceptors/wrappers and see if there's a way to create a DLL that can alter how many processors a particular application 'sees', which I think could work around this issue without involving any gimping of system performance (right now this is just pure conjecture on my part that this is possible, but since at least one other commercial title has a similar problem - Ubisoft's Child of Light - and I have a few hundred other games I haven't tested yet, there may be some utility to creating a more generalized solution since I expect most publishers and developers to be largely apathetic to the situation due to the economics of the gaming marking).