Ok, I talked to the original creator of the above thread and since he can't keep it up to date, I am going to bring in the results from there and include them here.

I will only be bringing across results that fit the requirements though. So that means wPrime 1.55, 2 or higher, and a screenshot with the wPrime score screen, and CPU-Z showing CPU and memory. Everything is up to date with the results from the other thread. Please let me know if you notice any mistakes.

RULES

- Please use wPrime version 1.55, here is a link to download 1.55. I will still record results from version 2+ but 1.55 gives better results so I urge you to use it.

- Set thread count to include all threads including hyperthreading. Example: 2600K should be set to 8 threads.

- One can be ranked more then once but not in the same cpu category i.e big joe has one score for Intel Core 2 (45nm) and one for Core i7. If a person posts 2 results in the same cpu category, only the best score will be kept.

- The submitted score must be written as follows:
First line: "wPrime 32m score example 5.853s"
Second line: "Cpu description and clocks i.e Q9550 @ 4ghz or 4000mhz"
Third line: "Memory description"
Fourth line: "Mobo description"
Those are the essential pieces of information but you can add more description as long as it follows the same guidelines as above.

- A valid screenshot is required and must be composed of: wPrime 32m test with the scores screen, cpu-z (cpu tab) and the cpu-z (memory tab).

- Keep the thread as clean as possible. Useless banter can be taken elsewhere. Questions relating to another users overclock or any related items are encouraged as the purpose of this thread is to compare overclocks and results.

- I might add stuff later, but i think we are all mature enough and that the rest is just common sense.

@Larkstar I am using offset + and during load it hits 1.5 on CPU-Z and 1.488 on AIDA64.

Ok this is the reason why I am switching to telling people to use wPrime 1.55 and not 2+. This run was done with the exact settings as my previous run but it came in about .9 seconds quicker on the 32M run and 29 seconds on 1024M.