GeForce GTX 460M SLI: Mobile Gaming Value From AVADirect?

Test Systems Configuration And Driver Issues

A drop from the previous six-core to four-core processor meant we couldn’t use the performance data from our last X7200-based review, and were instead forced to try to find the fastest previously-tested four-core models in today’s comparison. That’s unfortunate, since its Core i7-950 desktop processor has a higher non-Turbo Boost clock than the Core i7-940XM mobile processor used in Eurocom’s X8100. Of course, any performance gained by using a desktop processor will turn into energy lost in our efficiency comparison.

Two GeForce GTX 460M modules cost less than a single GTX 480M, so that’s the most logical Nvidia GPU match-up. Alienware’s super-performing M17x takes up arms for AMD’s Radeon series, its dual Mobility Radeon HD 5870 modules in CrossFire mode.

Also notice that the X7200 was tested twice, using the as-delivered 259.51 graphics drivers and specially-patched 260.99 “Verde” versions. The 259.51 driver often crashed when the cards dropped out of 3D mode at the end of a game test, and we found that the 260.99 drivers fixed it. The only problem for notebook buyers is, the public 260.99 drivers would not install without a little prep work.

Because Nvidia has not yet validated Clevo’s cards, the public driver INFs don’t list the card’s ID. We found three methods to enable “Verde” driver installations on AVADirect’s Clevo notebook.

The easiest method is to patch the public driver’s NVAM.INF file, finding the lines that refer to the GTX 460M device ID “0DD1” and replacing the ID of one card with that of another. We found six instances of this code, representing three cards on two different driver models. Replacing both instances of the first card listed (20401043) with the ID of our card (72001558) allowed the drivers to install without a hitch, including the Nvidia HDMI audio drivers. Because the installer removes all HD audio codec drivers before updating Nvidia’s audio drivers, the Realtek driver must also be reinstalled.

Nvidia used a different method in its own 260.99 preview driver for Asus’ G73Jw notebook, adding the lines %NVIDIA_DEV.0DD1.02% = Section017, PCI\VEN_10DE&DEV_0DD1&SUBSYS_71001558 and %NVIDIA_DEV.0DD1.02% = Section018, PCI\VEN_10DE&DEV_0DD1&SUBSYS_71001558 to the appropriate places in NVCV.INF. We tried changing Asus’ customized driver to match our card (72001558), and the graphics drivers installed without updating the Nvidia audio drivers.

Users who know a little bit more about INF structure can do to the public driver what Nvidia did to the Asus driver, adding %NVIDIA_DEV.0DD1.02% = Section017, PCI\VEN_10DE&DEV_0DD1&SUBSYS_72001558 and %NVIDIA_DEV.0DD1.02% = Section018, PCI\VEN_10DE&DEV_0DD1&SUBSYS_72001558 to the appropriate places in NVCV.INF. The results are identical to using the modified Asus driver, and we tested all three methods to make sure they worked.

In all three cases, the 260.99 driver fixed the stability problem previously found in the 259.51 driver. Nvidia tells us to expect an official update in early December that will make manual driver hacks unnecessary for its unified software package.