Ty Dino. Unfortunately as I have explained before, this behavior (especially on nvidia) has no link to the wrapper. This was the case with the original wrapper, the original v2, and the new rewritten version. As you might have noticed, the wrapper uses as much resources as having a mspaint window opened during the benchmark. There is no watchdog (a la XTU) that might interfere with the benchmark, its sole purpose is to make sure you start the benchmark with the default settings & files and that you don't alter the screenshot.
If you have any suggestions as to what might trigger this behavior I'm more than happy to listen and fix/implement the changes.
What am I supposed to see there? That he ranked twice with same card? Don't blame the software for a website bug. That he has two cards detected in wrapper, out of which one is not properly installed?