Just been reading a few reviews on OCZ 4000EB's prior to ordering and came accross this little fly in the ointment 
.
Overclocking Results:
200MHz 2.0-3-2-5 1T 2.6v
225MHz 2.0-3-2-5 1T 2.6v
250MHz 2.5-3-2-6 1T 2.6v
255MHz 2.5-3-2-6 1T 2.7v
275MHz 3.0-3-2-8 1T 2.7v
Encountered Issues:
There are some issues that have been circling around the Platinum PC4000 EB 2GB for a while now regarding game stability. With the memory running at a maximum overclock of 275MHz-280MHz, games would artifact or become unstable even when Memtest is 100% error free and Super PI 32M passes without a hiccup. There is also another problem regarding the integrated memory controller of AMD Athlon 64 processors. Many enthusiasts are encountering different overclocking results with different processors. The worst seems to be the non-FX San Diego core. All the others overclock just fine, but it is just with these non-FX San Diego cores that overclocking becomes poor. With those problems in mind, I began another stage of stability testing. I found it quite weird that the game benchmarks, Far Cry and UT2K4, passed without a problem. I fired up CS:S and started to do some fragging, and within 10 minutes into the game, artifacts began to appear. It was not a video issue since my video card was not even overclocked. The CPU was more than capable of handling the HTT bus speed. It appeared to be a memory issue. If you can recall back in the days when I reviewed the Kingston HyperX PC4300 memory, similar incidents occurred and concluded to be a memory issue. I slowly dropped the memory frequency until I was able to game in CS:S without any big triangles. The final frequency turned out to be 265MHz with timings of 3-3-2-8. Now with that issue out of the way, I switched out my week 17 Venice for a San Diego I had lying around and proceeded with the testing. Just like what everyone else was encountering, the memory would only overclock to 260MHz. Unfortunately I did not have a San Diego core FX processor so I couldn't test to see if it would be ok in an FX San Diego.
.Overclocking Results:
200MHz 2.0-3-2-5 1T 2.6v
225MHz 2.0-3-2-5 1T 2.6v
250MHz 2.5-3-2-6 1T 2.6v
255MHz 2.5-3-2-6 1T 2.7v
275MHz 3.0-3-2-8 1T 2.7v
Encountered Issues:
There are some issues that have been circling around the Platinum PC4000 EB 2GB for a while now regarding game stability. With the memory running at a maximum overclock of 275MHz-280MHz, games would artifact or become unstable even when Memtest is 100% error free and Super PI 32M passes without a hiccup. There is also another problem regarding the integrated memory controller of AMD Athlon 64 processors. Many enthusiasts are encountering different overclocking results with different processors. The worst seems to be the non-FX San Diego core. All the others overclock just fine, but it is just with these non-FX San Diego cores that overclocking becomes poor. With those problems in mind, I began another stage of stability testing. I found it quite weird that the game benchmarks, Far Cry and UT2K4, passed without a problem. I fired up CS:S and started to do some fragging, and within 10 minutes into the game, artifacts began to appear. It was not a video issue since my video card was not even overclocked. The CPU was more than capable of handling the HTT bus speed. It appeared to be a memory issue. If you can recall back in the days when I reviewed the Kingston HyperX PC4300 memory, similar incidents occurred and concluded to be a memory issue. I slowly dropped the memory frequency until I was able to game in CS:S without any big triangles. The final frequency turned out to be 265MHz with timings of 3-3-2-8. Now with that issue out of the way, I switched out my week 17 Venice for a San Diego I had lying around and proceeded with the testing. Just like what everyone else was encountering, the memory would only overclock to 260MHz. Unfortunately I did not have a San Diego core FX processor so I couldn't test to see if it would be ok in an FX San Diego.
?
.