facebook rss twitter

Review: PowerColor Radeon X1300 HyperMemory 2

by Ryszard Sommefeldt on 7 April 2006, 09:29

Tags: PowerColor (6150.TWO)

Quick Link: HEXUS.net/qafav

Add to My Vault: x

System Setup and Notes

The PowerColor Radeon X1300 HyperMemory 2 was benchmarked on the same A8R-MVP (ATI RD480 + ULi M1575), AMD Athlon 64 4000+, 1GiB system as the X1300 PRO and X1600 XT were recently.

While it's not quite the system an X1300 HyperMemory board will find itself in, it helps us match it up to X1300 PRO and removes the system (as much as is possible at least) as a possible bottleneck.

Interestingly the board shipped with a 450MHz BIOS and a CD with flash tools to update the BIOS to the 600MHz shipping one. All retail examples will come with the very same BIOS, so there's no need to flash yourself the same way we did.

Hardware

  • PowerColor Radeon X1300 HyperMemory 2 Test Platform
Processor(s) AMD Athlon 64 4000+
2.4GHz, single-core, 1MiB L2, Clawhammer
Mainboard(s) ASUS A8R-MVP
ATI RD480 Crossfire
ULi M1575
Memory 2 x 512MiB G.Skill F1-3200DSU2-1GBLE
Memory Timings 2.5-4-4-8 @ 400MHz, 1T
BIOS Version 0402
Disk Drive 80GB Western Digital PATA
Graphics Card(s) PowerColor Radeon X1300 HyperMemory 2
ATI Radeon X1300 PRO
ATI Radeon X1600 XT
Graphics Driver CATALYST 6.2 BETA
Operating System Windows XP Professional, SP2, 32-bit
Core Logic Driver(s) ULi M1575 Chipset Driver V1.0.5.2a

Software

  • Game Software
  • Splinter Cell: Chaos Theory
  • F.E.A.R.
  • Far Cry
  • Chronicles of Riddick: EFBB

Notes

The format of the graphs is the same throughout this article. The line plots are the baseline scores without antialiasing or anisotropic texture filtering applied, the column plots the values with AA and AF applied.

Driver defaults were used throughout, and stock clocks were used for all cards. If in-game controls could be used for both antialiasing and anisotropic texture filtering, they were, otherwise the driver was used to force the required levels (if applicable and the game allowed it without rendering errors). Tested resolutions were 1024x768 and 1280x1024.

Game tests were run a minimum of three times at each setting, and the median value reported. In the case of manual 'run-through' testing with FRAPS, three consecutive runs that produced repeatable results, after further analysis, were used. If values weren't part of a repeatable set, they were discarded and obtained again.

If you have any questions about our testing methods, please feel free to ask at any time in the HEXUS.community.