Submission Details
boblemagnifique`s wPrime - 32m score - Elite League
1min 13sec 750ms with AMD Athlon MP 1600+ (Palomino) at 2204MHz
Ranking position
n/a
Global 1x CPU rank:
1st
Athlon MP 1600+ (Palomino) rank:
1st out of 16
Points earned for overclocker league
-
Global Points
Not boblemagnifique's best submission
-
Hardware Points
1st using Athlon MP 1600+ (Palomino)
15.0 Points
Points earned for team league
-
Global Team Power Points (GTPP) Not French Legion's best submission
0.0 Points
-
Hardware Team Power Points (HTPP) 1st in team using Athlon MP 1600+ (Palomino)
7.6 Points
Hardware details
CPU details
- Model: AMD Athlon MP 1600+ (Palomino) 'Palomino'
- Cooling: Cascade Phase Change
- Cores: 2,204MHz(+57.43%)
Memory details
VGA details
- Speed: MHz / MHz (Stock)
Mainboard details
- Manufacturer: Abit
- Model: NF7 V2.0
- Cooling: Air (Custom)
- Chipset: nForce2 Ultra 400
-
Recent Comments
Sweet says:
Hi, boblemagnifique, please your CPU is Athlon XP 1600+ or Athlon MP 1600+ ?
You upload like XP, but Cpu-z show MP
Thanks for your help in this.
Sw
boblemagnifique says:
Hi Sweet , it's a true XP 1600+ (AX1600DMT3C) but the last CPUz bug with my NF7 rev 2.0 my all cpus (for exemple : L2 Cache = 64Ko)
Turrican says:
i have this problem with the l2 cache on palomino cpus as well , but only if i apply high vcore (2.1V+). with stock vcore i have the full 256kb l2-cache.
i think the l2-cache "problem" isn't cpu-z related, but cpu?
you can tell by the performance of the benchmarks the used l2-cache is really only 64kb then. so i don't think it's a read error by cpu-z
boblemagnifique says:
yes maybe , i have test my XP 2200+ and no problem for the cache L2 (256Ko).
The core is crumbled but it's alive for the moment ^^
Turrican says:
this seem only apply to "palomino" cpus and not "thoroughbred" or "barton", so no wonder the 2200+ is fine.
boblemagnifique says:
I have the same problem with my Barton 2500+ => http://hwbot.org/signature.img?iid=541423&thumb=false&iehack=.jpg
I can try soon on my other mb abit NF7 rev 1.2.
Please log in or register to comment.