Leaderboard

It seems there is some confusion and outdated information. The first post-347 unlocked driver will be released this coming Monday or Tuesday. 345.20 is an old driver which is identical to 344.75 except for a couple patched files that have nothing to do with OC plus the 344.80 hotfix. That's why you have no problem overclocking on 345.20. NotebookCheck has confirmed with Nvidia that cards will stop shipping with the locked vBIOS once the aforementioned unlocked driver has been released.

Yeah, seen this so many times before. OEM blames manufacturer, manufacturer blames OEM, both only by implication and no definitive statement. We only find out post release exactly what is going on. Are all new 9xxm owners getting these canked Vbios? I bet they end up on the new AW's! Thanks for the correction on the driver, since it's still an old one I'll wait it out. They apparently released that one as part of the security fix for each driver branch. No surprise the unlock also crept in! Edit: OK researched it properly now and indeed all new cards are getting this Vbios. I can only shake my head, WHY? What is the huge benefit that they can ignore all the end-users in preference for some manufacturing/sales benefit??

Hi Mickyd1234! Two annotaions: First. nVidias latest issued driver 345.20 does support OCing again. NVIDIA DRIVERS GeForce Game Ready Driver WHQL Second. What nVidia states according to your information does not seem to match with what others (i.e. Prema) have experienced who got their chips directly from the green company. http://forum.techinferno.com/general-notebook-discussions/8998-nvidia-officially-states-they-cut-overclocking-mobile-gpus-17.html#post124860 And while it is true that he seemd to have success in circumventing the vBios lcok im am still not happy with this desicion. Best regards phila

It's hard to say - Windows was clearly recognizing that a second GPU was connected because the iGPU was disabled right at the Windows logo stage. It's just that I never got image back, either on the Macbook display or on the external monitor hooked up to the R9 290X, so I'm guessing it failed to initialize. I tried blindly typing in my password to see if it would log in but I didn't hear any sound from the speakers or see the keyboard backlight coming on so I assumed it crashed. On OS X, there was no issue booting it up so I think the issue is specific to Windows & Intel GPU drivers and how they behave by default on the Macbook Air. In fact, when I tried to use an Intel NUC, the R9 290X was initialized on boot but I still had picture from the iGPU and thus could log in and install Catalyst drivers as per usual. I tried hooking the R9 290X directly to the AKiTiO while powering the PCIe slot with a DC barrel adapter but it didn't seem to make a difference.

muse, psycho. new track!

Hardwell and tomorrowland