NVIDIA Calls A Feature A 'Bug,' Strips Away Overclocking Option On Its Mobile Device Cards
from the you-can-buy-it-but-you-can't-have-it dept
In theory, the marketplace for goods works like this: a purchaser hands over $$$ and in return receives a product that they own and can use as they see fit. In reality, purchasers often hand over $$$ and find that the product they purchased is still in the grips of the company that took their money but seems loathe to honor its end of the deal.Case in point #38,909: guess what NVIDIA thinks is a "bug," not a "feature."
Starting with the Fermi drivers, though, a software overclock was possible in the drivers, which allowed you to adjust your laptop GPU's clockspeeds at will. Tools like AfterBurner from Micro-Star International Comp., Ltd. and Turbomaster by ASUSTek Computer Inc. allowed users to more easily and safely tweak their GPU's clockspeeds on select gaming laptops with cooling solutions designed to cope with the higher thermal load. Companies like the Clevo Comp., Sager, ASUS, MSI, and Dell's Alienware regularly sold models billing overclockability as a sales feature.NVIDIA pushed out new drivers last December that took away customers' ability to overclock their cards. These were targeted at cards for mobile and hybrid devices, where the chance of overheating (and causing serious damage) was more pronounced. Those who had overclocked their cards but now were unable to do so demanded answers from the manufacturer. And wouldn't you know it, the explanation for NVIDIA's removal of this option cites "safety" as the primary motivator.
What OEMs apparently didn't expect was that NVIDIA would rob customers of that feature. But that appears to be precisely what happened.
Unfortunately GeForce notebooks were not designed to support overclocking. Overclocking is by no means a trivial feature, and depends on thoughtful design of thermal, electrical, and other considerations. By overclocking a notebook, a user risks serious damage to the system that could result in non-functional systems, reduced notebook life, or many other effects."Safeguard systems from operating outside design limits" sounds an awful lot like "your purchased items are only as flexible as we allow them to be." Sure, warranty departments handling burnt up/out devices may have been making some noise about dealing with the aftereffects of careless overclocking, but if so, they're no less blameless than NVIDIA. Overclocking is generally one of those warranty-voiding activities, and if companies didn't want to be replacing torched devices, they should have handled it better at their end. (And, as Daily Tech points out, they should probably stop advertising overclocking as a "feature" if it's truly that much trouble in the warranty department.)
There was a bug introduced into our drivers which enabled some systems to overclock. This was fixed in a recent update. Our intent was not to remove features from GeForce notebooks, but rather to safeguard systems from operating outside design limits.
But NVIDIA's action takes the purchased product out of paying customers' hands. Most people who dabble in overclocking are technically adept and know the limits of their hardware (and the terms of their warranties). There will always be those who push too far or get in over their heads, and a few overclockers who disingenuously expect the device's manufacturer to bail them out when things go wrong, but these customers are in the minority.
When a company takes away a feature (especially one that has been advertised by the devices' manufacturers) and calls it a "bug," it's basically telling customers that they won't ever own what they purchased. In this case, NVIDIA is hurting some of its most loyal customers -- people who know their devices inside and out and will pay good money to stay ahead of the tech curve.
And NVIDIA's being a bit disingenuous itself. It calls overclocking a "bug" when explaining why it took this feature away. But if it truly was a bug, why didn't it issue a patch rather than eliminating the option? The obvious answer is that overclocking is no bug and NVIDIA knows it. But it has apparently chosen to placate its OEMs at the expense of some of its most reliable customers.
NVIDIA hasn't issued any further statements on its "bug fix," so it's safe to assume it doesn't really care whether it's angered a number of its customers. Its position in the graphics accelerator market is virtually unassailable, especially in the area (mobile/hybrid) where it has just guaranteed its customers will get less product than they paid for.
Thank you for reading this Techdirt post. With so many things competing for everyone’s attention these days, we really appreciate you giving us your time. We work hard every day to put quality content out there for our community.
Techdirt is one of the few remaining truly independent media outlets. We do not have a giant corporation behind us, and we rely heavily on our community to support us, in an age when advertisers are increasingly uninterested in sponsoring small, independent sites — especially a site like ours that is unwilling to pull punches in its reporting and analysis.
While other websites have resorted to paywalls, registration requirements, and increasingly annoying/intrusive advertising, we have always kept Techdirt open and available to anyone. But in order to continue doing so, we need your support. We offer a variety of ways for our readers to support us, from direct donations to special subscriptions and cool merchandise — and every little bit helps. Thank you.
–The Techdirt Team
Filed Under: bug, feature, overclocking, ownership, video chips
Companies: nvidia
Reader Comments
Subscribe: RSS
View by: Time | Thread
Reasoning
[ link to this | view in chronology ]
Re: Reasoning
Basically some lawyers likely said "some guy can OC his netbook, burn it up and file a warranty and there is nothing we can do. Fix this".
This is why we can't have nice things.
[ link to this | view in chronology ]
Re: Reasoning
[ link to this | view in chronology ]
Re: Re: Reasoning
[ link to this | view in chronology ]
It must be nice to have a "bug" open up an entire market for you.
[ link to this | view in chronology ]
[ link to this | view in chronology ]
Glad I use AMD
[ link to this | view in chronology ]
Re: Glad I use AMD
[ link to this | view in chronology ]
Re: Glad I use AMD
[ link to this | view in chronology ]
Re: Re: Glad I use AMD
[ link to this | view in chronology ]
If a hardcore user really wants to overclock then they can most likely still use nibitor to overwrite the default clock settings in the cards BIOS. Essentially, removing this bug / feature is just another hurdle.
[ link to this | view in chronology ]
Re:
[ link to this | view in chronology ]
yet another example of US courts allowing the various manufacturers to get with this double take! how the hell can any sound person think that when you've bought something, it still belongs to the manufacturer or seller? and even worse, this ridiculousness has spread, making even greater profits for the above!!
[ link to this | view in chronology ]
Important to note:
is really
NVIDIA pushed out new closed-source drivers...
This is but one of many reasons why closed-source software has to go. All of it.
[ link to this | view in chronology ]
If users want to keep overclocking available, they can simply use an older version of the driver. There's nothing really new a driver update can do for an existing card anyway. Updates are mostly about bug fixes and adding support for newer video cards. If you upgraded your driver and lost overclocking, stop whining and go download and install an older version. You'll have your overclocking back, and NVIDIA has protected itself from potential liabilities as well as future users from damaging their machines.
[ link to this | view in chronology ]
Re:
Obviously it's not a good idea to do it on a laptop, since you've so much less room to work with in terms of cooling, but if the hardware supports overclocking, allow it.
The problem with your line of thinking is that you don't follow it through. Software not vetted and signed by Microsoft could damage your machine, so, according to your logic, Microsoft shouldn't allow programs you write yourself to install in Windows.
[ link to this | view in chronology ]
Re:
Spouting off about your assumed expertise is irrelevant.
[ link to this | view in chronology ]
Re: Re:
I can very easily get malware on my machine, but no computer manufacturer to the home market would write-lock the hard drives in order to prevent this.
[ link to this | view in chronology ]
Re:
[ link to this | view in chronology ]
Re: Re:
Since when does a GTX980M have to be in a mobile platform or even than with bad cooling. IE: iMac's run crappy GTX700M series, and there's a bunch of ultra compact PCs coming out with similar setups.
[ link to this | view in chronology ]
Re:
But nobody's accused NVIDIA of setting fire to people's laptops, and they have no right to prevent the slim-to-zero chance of someone setting fire to their own laptop (it would burn out first).
[ link to this | view in chronology ]
Nvidia, where down is up and no means yes.
[ link to this | view in chronology ]
OTOH, the overall practice of pushing software updates with unknown and undocumented effects is a very rich vein to mine in terms of bad practice by companies. Consumers should very much be told in advance what their updates are doing.
[ link to this | view in chronology ]
Re:
This story is TECHDIRT pure and simple.
[ link to this | view in chronology ]
[ link to this | view in chronology ]
Re:
[ link to this | view in chronology ]
So it's not gonna affect too many people...
[ link to this | view in chronology ]
Re:
[ link to this | view in chronology ]
Re: Re:
[ link to this | view in chronology ]
Re:
Like rolling back the drivers to the previous version?
[ link to this | view in chronology ]
Asus copy:
"With ASUS TurboMaster technology, the G751 offers stable GPU overclocking along with an optimized dual-fan cooling system that keeps everything cool even in the heat of battle."
A lot of people bought them just for that reason. Now that capability is gone.
If this was a 'bug', the OEM vendors sure used it to drive sales. And funny how this 'bug' has existed for YEARS...
[ link to this | view in chronology ]
Re:
If ASUS markets overclocking capability, then takes it away IN THE DRIVERS THEY SUPPLY, then people can bitch.
[ link to this | view in chronology ]
Re:
Every time I see the phrase "gaming laptop" I flash back to the time I tried to install Angry Birds on a friend's Win7 laptop and was told that the game couldn't run due to some mode not being found. Like Angry Birds really pushes the envelope of gaming...
[ link to this | view in chronology ]
[ link to this | view in chronology ]
Be thankful...
Years ago I was pushed firmware updates for my pc. One of them bricked my NIC card! And since that was built onto the mainboard, guess what I wound up doing that weekend!
[ link to this | view in chronology ]
What I bought ...
6 months later I got into my car one morning and the red led panel didn't tell me the time and the outside temperature it said "bug fix installed"
Now when I pull away I find the car will do no more than 30mph. When I took it to the garage for a service they explained the original speed was a bug and was never safe this new mode is correct.
Anyone else gonna buy cars from Nvidia?
[ link to this | view in chronology ]
Re: What I bought ...
[ link to this | view in chronology ]
Re: Re: What I bought ...
[ link to this | view in chronology ]
Re: What I bought ...
[ link to this | view in chronology ]
Common Sense
Don't get me wrong, I have a corsair H50 water cooler slapped on my 3770k which has been running stable at 4.5ghz for over a year now. But the last time I overclocked my GPU was almost 10 years ago given the fact that long ago I discovered it's better to milk out better quality and performance by either using a tool like Nvidia Inspector and/or altering the video configuration files of a game among other things...
The only people I can see overclocking their mobile GPU are children and it would be a damn shame if they some how managed to blow their laptop up in their faces. I mean if the cmos battery or laptop battery are way too close to the gpu, I'm pretty positive they'll overheat and explode...
[ link to this | view in chronology ]
Re: Common Sense
There, any legal liability waived.
[ link to this | view in chronology ]
Re: Re: Common Sense
[ link to this | view in chronology ]
Re: Re: Re: Common Sense
[ link to this | view in chronology ]
Re: Re: Re: Re: Common Sense
Care to rephrase it in terms that reflect the point you're trying to make? lol
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Common Sense
Thing is, this is a fallacy. Gaming laptops and the people using them to overclock are generally not children. They're more than likely adults, who can make an informed decision to do something that is dangerous. So your comment that is basically saying "Think of the children!" is a non sequitur.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Common Sense
In my defense, I was 'thinking of my own childhood experiences' back in the late 90s in which I made many stupid decisions. Such as overclocking things to the point of catching on fire in computer class (which got me expelled) and I even got chemical burns once while attempting to resolder the connections of an overused PS2 port. Little did I know that the 'cmos battery' was ready to blow and was the reason why the cmos kept on flaking out all of the peripherals...
Have you ever seen a video of a battery exploding?
Regardless, overclocking should never be a mainstream consumer feature for more reasons than I can count.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Common Sense
/Same Logic
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Common Sense
Wake up...
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Common Sense
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Common Sense
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Common Sense
Disclaimer: the above is something that could have happened if I was that stupid, and I wrote it only to make a point.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Common Sense
[ link to this | view in chronology ]
Re: Re: Re: Common Sense
[ link to this | view in chronology ]
Re: Common Sense
[ link to this | view in chronology ]
Re: Re: Common Sense
[ link to this | view in chronology ]
Re: Re: Re: Common Sense
It's kind of like the red key and the black key for the Hellcat. You would be pretty upset if all of a sudden that red key didn't work anymore...
[ link to this | view in chronology ]
Re: Re: Re: Re: Common Sense
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Common Sense
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Common Sense
Now that I think about it, you have every legal right to ask for a refund according to consumer protection laws...
Personally, I think overclocking features on laptops should be hard wired through an old school dip switch (rather than through software) which can only be reached if you have the knowledge on how to rebuild them. That way, people with cheap laptops, who don't know any better, don't blow up their sh*t up and people who have laid down the cash can make their OC wet dreams come true...
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Common Sense
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Common Sense
I mean this is a pretty drastic move by Nvidia and I'm willing to lean towards the assumption that the situation is a lot worse than what is being reported...Otherwise, why would they do this to begin with?
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Common Sense
"I think the cost of implementing dip switches to enable overclocking greatly outweighs the cost of returns for those who completely destroyed their systems via the current methods."
Probably not. I'm guessing that only a very tiny percentage of customers overclock the card, and that it's a minority of those who that destroy their equipment in doing so.
"I mean this is a pretty drastic move by Nvidia and I'm willing to lean towards the assumption that the situation is a lot worse than what is being reported"
I don't think that Nvidia thought this was a drastic move.
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Common Sense
For low end systems, it's pretty obvious that they just want things to work minus all of the fluff.
"I don't think that Nvidia thought this was a drastic move."
Well they managed to piss off everyone that spent the money to exploit this feature so...I don't know what else to say?
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Common Sense
PS3 and Linux...
[ link to this | view in chronology ]
Re: Common Sense
I've always been an ATI guy tho so I don't really care what nvida does...
[ link to this | view in chronology ]
Perhaps the drivers should be modified to allow overclocking only after the user agrees to having the laptop's and GPU's serial numbers sent the manufacturers of both with a screen notice that overclocking voids the warranty. Now there would be a record that the end user knew the dangers and did it anyway and accepted the loss of warranty.
[ link to this | view in chronology ]
Re:
[ link to this | view in chronology ]
The REAL reason Nvidia has disabled overclocking on mobile GPUs
Back around 2008, Nvidia made changes to their mobile GPU manufacturing process—particularly to the solder "bumps" that both bonded and electrically connected the GPU chips to computer circuit boards. The cumulative result of these changes was an astonishingly high failure rate in notebook computers. The technology press predictably hung the label "bumpgate" on the whole mess.
It would be another year before Nvidia would officially acknowledge that the problem even existed and another year before they would settle the class-action lawsuit for $200 million. Add the inevitable direct suits from computer manufacturers and years of consumer distrust, and it's easy to understand why Nvidia's stock value took such a severe hit (from which it still hasn't fully recovered).
Given Nvidia's troubled past with thermal stress and GPU failures, their choice to disable overclocking for mobile GPUs is not terribly surprising, nor especially controversial.
[ link to this | view in chronology ]
Re: The REAL reason Nvidia has disabled overclocking on mobile GPUs
Perhaps not surprising, but this is obviously controversial. Understandably so, since this is yet another case of a company retroactively removing features from a product that people had already purchased.
That's not OK.
[ link to this | view in chronology ]