Would you mind installing MSI Afterburner and using the screen overlay to check CPU usage?
Piledriver is a weird ass architecture and we need some more data on it.Edit:
Did some one-on-one chatting with this pretty boy.
Took the liberty of mirroring his log file: http://broscar.nl/files/EyesOnlyfx6300.hml
(there's no personal information in it at all).
Can be opened with any text editor, but if you have MSI Afterburner installed it can be displayed as nice visual graph.
GPU usage might be a faulty registration, so we'll have to ignore that, but his framerate drops well before CPU usage starts to skyrocket and even when it does, it never goes 100%.
This might be a multithreading issue, but I think it has something to do with the architecture of his CPU
The floating point performance of that processor is completely gimped and I have no idea what it's doing with it's cache.
Even so, 3 'cores' that can do floating point computing should be enough to not drop the game to 12 fps, unless AMD f*cked something up big time.
I can't really do anything about this. I might as well be wrong, but I'll just forward this sh*t to Rob and have him facepalm over this.