Yes, this is a know issue.
The support tool test is not meant to be comprehensive. It is possible it just doesn't recognize the turbo boost, or something, triggering the 'fail'.
Couple of questions...
Are you with Larian? I've seen your posts over on Steam as well... Also... How widespread is this issue, if you know that at this point? Is it effecting only i7 CPUs? Or laptop CPUs? Or a combination of both? And when can we expect a fix for this? As well, how much of a fix is possible?
My curiosity really is in how well this game engine can handle full multicore (all cores of a quad core) support. When the game was being designed, was it designed with 2 cores in mind? Or for a full quad core setup? I assume that because the recommended CPU is an i5 that full multicore support was intended. But I am curious why this game was not recommended to have an i7? What is the specific reasoning behind the i5? Is it because the i5s generally have a higher clock rate (from my experience anyways) and thus the game was meant to be run at fewer cores with higher clock rates? Or can optimization be done for CPUs with lower clock rates by utilizing all the threads? I guess the all inclusive question would be how capable this engine is when fully optimized? I suppose the folks over at Larian don't even know the answer to this, as this may be the first time they've put the engine through its full paces. I just want reassurance that a fix is possible and likely is all.
For example: Torchlight 2 was programmed from the ground up to be single core. Thus multicore support was impossible, short of rewriting the game engine. But with Original Sin, it seems that the multicore support was intended but not inclusive of the hardware on the market...
Maybe I'm just rambling at this point... Its late... Haha.
Thanks Raze for the response (assuming you are with Larian, if not... well... thanks anyway.)