John on 20 Feb, 2013 01:28 AM
Sorry for the delay in getting back to you. This problem was due
to a bug in the processor identification code which I think was
fixed in Geekbench 2.4.0. Could you let me know whether you're
still experiencing this issue in Geekbench 2.4.0?