Indeed, the Phenom-series CPUs are unaffected. My wife runs a 12 year old Phenom II X4, stock settings and hasn’t had any trouble with the update. Someone some pages back talked about the architecture of the FX series and how multiple cores share the same floating point modules causing cores to potentially be bottlenecked if the tasks (like spatial audio processing) relies too heavily on floating point math.

I’m assuming the Phenom II series doesn’t have that problem. Apparently a Phenom II can be put in an AM3+ socket, so I’m tempted to pick up a Phenom II X4 or X6 and “downgrade” my CPU to work around this.

Something FX 8XXX series people might try is using motherboard settings to turn off half the cores. I tried this with my FX 4100, and while it seemed to smooth out the sound a bit, I had nowhere near enough remaining CPU bandwidth to actually run the game above single digit FPS (in fact, sometimes the sound would stutter, but the cpu was maxed at 100% at 0 FPS, meaning that 2 cores isn’t enough for the sound alone). The idea is by taking half the cores offline, the remaining cores get exclusive access to the floating point modules so that the overall pipeline no longer gets backlogged trying to schedule floating point tasks with CPU cores that are idling due to the floating point modules being maxed out.

If spatial audio with such complex processing is the future of gaming, perhaps we need advances to offload these computations to the GPU, or perhaps make some sort of audio processing module that can handle these kinds of tasks (think beefed up sound card).