AMD's Phenom Processor @ lostcircuits.com

[KTE]

Jack,

I've been trying to replicate your runs but sorry, my Phenom is dead for 4 days now. No trick has worked and it is erroring at the memory initializing stage (C1). The LEDs on the Tracer start and then jam -- tried 3 working boards and 3 working PSU's. To say the least, my 9500 and both my last 9600 BE's did this if I cleared CMOS, randomly, but they would all restore to normal operation when left off for 8-9 hours or put under cold. This one doesn't. Multiple other users have had the same problem when settings are reset after flashing any BIOS. Achim had his 9500 die too and it was out of the blue. He gets the same errors. At the time of death mine was running stock (because I was testing old and new BIOSes). Prior to that, for the last two weeks it had been on low-ish volts. VCore 1.26-1.30V, HT 1.20V, NB 1.1V, IMC 1.038-1.10V, DIMM 2.0-2.2V. In particular, notice the delta between vIMM and vIMC. Throughout my experience, it would certainly appear to me that Phenom does indeed have major IMC problems, that's of the retail ones. Whether that's by running plus 2.0 VDIMM, or by increasing the deltaV between IMC and DIMM... I'm not sure, because we have no way to tell unless a Phenom susceptible to this is tested at low and high volts. I must admit, I am strongly leaning to it being dead because of running 2.2V DIMM @ sub 1.2V IMC. Achim's Phenom lasted around 2.5 months (?) and mine lasted roughly just short of 2 months.
Anyway, the grunt of the circumstance; the replacement Phenom won't arrive for long and when it does, I won't be testing it at all. It will go to the department it belongs at my uncles firm. Quite unfortunate since I had installed and setup benchmarks for 3dsMax 2008, Sony Vegas, SPECap, SPECopc, Maya 6.5, TrueSpace 7.5 and many major benchmarks to comparitively test with just this week. Honestly, I have no plans to play with Phenom anymore.

UT3: I have not been able to get it running on the Intel system. 3 systems all are giving me the same problems and they are different CD installs with and without the 1.1 and 1.2 patches. I get the same problem with UT 2003 and UT 2004. Looking at the documentation websites it seems to be a bug which only affected XP 64-bit before, that they knew (which they released hotfix in the patch).

Crysis: Been playing the game at these settings attached below, with High Physics and High Particles at 1028x768 and lower resolutions. Higher resolutions than this requires more video memory and will bottleneck only my GPU. I'm on a 3.7G Q6600/P35/PC2-8000/2600XT/Cat 8.2 (Cat. 8.3 has up to 15% DX10 performance improvement and much for DX9). Maximum CPU usage it ever gives is 34% while average is near the 30% mark (same power draw as FarCry). In 60 minutes playtime, av. FPS is hovering at 55-58 (pretty smooth). Highest seen is 101 FPS and lowest is 28 FPS. FRAPS doesn' work with it, it shows the FPS OK but keeps writing a massive list of 1 and 0 FPS with the benchmark option when there's plus 50 FPS for sure, although it does catch a few of higher FPS too. So I've been using the r_displayinfo = 1 command instead.

At those settings, the CPU Bench gives me av. FPS out of 4 loops as 48 while the GPU bench gives me av. FPS of 79.

Disabling one and then two cores gets the same play rate as four cores enabled.