Server returned HTTP error code 500
I try to finish benchmark test for x86 experimental CPU - 1Ghz,
256MB RAM, Windows XP.
After test finish sadly i can't upload results as i getting
following error message:
Geekbench encountered the following problem when trying to upload
your results to the Geekbench Result Browser: server returned HTTP
error code 500.
Is there any chance to even get offline benchmark scores or log files what exactly happened wrong ?
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
Support Staff 1 Posted by John on 25 Jul, 2012 11:32 PM
Tomasz -
Could you download an older version of Geekbench (e.g., Geekbench 2.2.7) and see if it encounters the same error? If it does, could you save the results and send them to me?
Thanks,
John
2 Posted by Tomasz.Malewski on 26 Jul, 2012 09:40 AM
... Sharpen Image
Blur Image
Memory
Read Sequential
Write Sequential
Stdlib Allocate
Stdlib Write
Stdlib Copy
Stream
Stream Copy
Stream Scale
Stream Add
Stream Triad
Benchmark Summary
Integer Score 188 Floating Point Score 100 Memory Score 141 Stream Score 75
Geekbench Score 136
Upload results to the Geekbench Result Browser? [Y/n]y
Uploading results to the Geekbench Result Browser. This could take a minute
or two depending on the speed of your internet connection.
server returned HTTP error code 500
C:\Program Files\Geekbench 2.2>
Support Staff 3 Posted by John on 26 Jul, 2012 03:57 PM
Tomasz -
Could you run Geekbench with the following command-line switches:
and send me the output.gb2 file? Note that you may have to adjust the path for output.gb2 since you're running Geekbench directly from the Program Files directory.
Thanks,
John
4 Posted by Tomasz.Malewski on 26 Jul, 2012 06:02 PM
Dear John,
In attachment YOu will find output file
Support Staff 5 Posted by John on 20 Feb, 2013 01:28 AM
Tomasz,
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?
Thanks,
John