No more overclocking on Nvidia mobile GPUs

lol, now thats....impractical

 

We should be proud of making Nvidia change their opinion about overclocking for mobile. Damn they have grown big

Q4 2013





Q4 2014

 

http://forum.techinferno.com/genera...t-overclocking-mobile-gpus-12.html#post124474

 

bahahahahahaha what the %"#¤¤#"! hell?!
There goes the tricks of surpassing the overclock blocking by using older drivers with the "bug". What purpose does overclocking enabled on drivers then?

There was a Clevo guy with one of the new machines with desktop chip and 980M (P77xZ or something) which asked for advice in the Alienware 18 forum because he couldnt get overclocking to work, even with pre 347.xx drivers. Guess thats why...

 

...Nvidia, you low-down dirty dog.

 

what the hell????
they playing with us????

 

Heh...

 

I knew they would try and screw us somehow. Time to give them hell again. This will be egg on their face again big time if websites pick this story up correctly.

Untrustworthy Dogs they are.

 

Let me just get this straight. After promising us drivers that will allow overclocking next month, they have begun to ship cards with a vBios that will not allow it, regardless of the driver that you use, and they only promised us these drivers in the first place to avoid us burning down their event on the 3rd.

And they thought that this would slip past us? How incredibly stupid can they get? Right when we started to wipe the sweat off of our brows too...

 

All that negative PR that was full blown in the air & we were thinking things would be set after our hardwork and then this things pops up, really Nvidia Corp. such a BS !!

Anyways after all this hassle & the Pascal refresh won't even ship with MXM though that Nvlink has + effects, I guess the Nv will not even allow flashing a vBIOS anymore. Maybe they are intented to kill OC with Maxwell if the AMD stays quiet as a sheep this plague will be spreaded to desktops too...

They are worthless liars, we cannot even compare to any species on the planet...

 

LOL well played nvidia, well played. before n=1 was saying how they could limit the vbios to +10 or something, and guess what? it's +0

 

Alright... This time, whomever is feeding media outlets the news about Nvidia's second scumbag move, please give them accurate, clear information - last time, every single news outlet reported that it was only 9XXM GPUs that couldn't overclock, when it was actually all Maxwell GPUs that couldn't (hence including GPUs in the 8XXM line as well, i.e. 840, 850 and 860M, if I remember correctly). How on earth did everyone get it wrong, I don't know.

This VBIOS trick may unfortunately be Nvidia's trump card. Most people I know who own gaming laptops don't have a Clevo. They always choose Alienware or ASUS, and don't bother with overclocking or flashing a modded BIOS.

Hence they may believe OC is gone for good, and just live with what they get.

@Prema , is it possible for Nvidia to disable OCing at such a level that even a modded VBIOS doesn't help get around? I'm worried they may resort to hardware blocks.

 

All NVFLASH versions that work with GTX9xxM cards are Windows only and already prevent any modified vBIOS to be flashed (unless the NVFLASH itself is modded, too). They could also simply prevent all modified vBIOS from working on driver level...

 

1: Wouldn't earlier VBIOS work for newer cards?

2: If we're going to be giving "accurate, clear information", do we understand any of the process in which this happened? Why did OCing slip through early on? What's the manufacturing cutoff date? Which VBIOS allow/block OCing?

 

We can still use modded VBIOS that the talented members of the community create to get around this though right?

 

HAH I knew it was too good to be true, and sadly I was right. Time to raise some more hell I guess.

There's a couple hacked versions of nvflash floating around. One bypasses certificate checks, and one bypasses any and all checks completely so that you can freely flash any vbios from any card to another. Both are on OCN, just search for a guy named "JoeDirt".

 

This is all getting worse and worse... I bet within a year they will disable desktop GPU overclocking as well.

 

As long as we can keep using VBIOS mods, it's not as bad as the driver-level block, right?

Very disappointing though.

Sent from my Nexus 5

 

Sigh...I should have known it was too good to be true. > : (

Scumbag Lenovo, Scumbag Nvidia, Scumbag corporations.

Thank goodness for the informative community here to uncover these disgusting practices in the first place. Kudos to you all!

I cringe to see how locked down the 1000m series or whatever the heck Nvidia will call their next GPUs.

 

@octiceps: time to update the OP and get ready for the next round of nvidia bashing....those damn little green trolls! unbelieveable! im gonna set up some emails to send to the major german tech sites here, this is NOT over, people!!!

Sent from my Nexus 5 using Tapatalk

 

That's scary. I didn't make a backup of my stock VBIOS before flashing :S

So they can just brick my GPU whenever they feel like it?

Sent from my Nexus 5

 

I'll update the petition too.

Unreal.

 

Dark times are ahead people.

Come on AMD, step up your game please!

 

They can't do that. At least, not to this generation of desktop GPUs. The next gen however...

 

They can never get away with this sort of thing on desktops. AMD is far too competitive on the desktop market. And the backlash would be greater than the 970 incident.

The reason they can get away with it with laptops is because the desktop community refuses to back our cause and defend us.

Sent from my Nexus 5

 

It takes time for a vBIOS to be written, tested and then work it's way down into sold units.

I wonder if this was always the plan, along with the clockblocking driver.

Now that the decision has been reversed maybe they will remove these vBIOS blocks and this one just slipped through the net due to the timing of recent events.

Time will tell I suppose.

EDIT: Also I see the OCN desktop trolls are out in force once again.

 

This was what I just thought.

Maybe they will reverse this now that their official policy regarding overclocking has changed?

Sent from my Nexus 5

 

I have bad new for everyone those laptops with the blobked Vbios have already shipped. the 2015 Alienware R2 models with the 970m are completely blocked off from overclocking at a bios level (you can check the AW 17r2 benchmarke thread for my detailed anlysis). I have tried to get a response from the AW reps in the AW AMA thread here but they just keep giving me the Run around/total BS answers. so yeah if you own an AW 17r2 with the 970m odds are you will never get to OC it at all.

 

in that case it would be VERY practical to make another statement regarding this in their official forums, especially in order to avoid another ****storm coming their way...

wow, alienwares without overclocking capabilities....brave new world

 

Alienware 13?

Also, incredibly offtopic, but is you P751ZM capable of running on iGPU alone, without dGPU at all?

 

I am primarily a desktop gamer and I got your back. Maybe I am in the minority, I have no idea, but I do support you all.

 

nope, iGPU is disabled on the ZM series

 

Wow, that's a real shame, the 970M overclocks really well - I wouldn't buy a laptop like that if I knew it wouldn't overclock, if I had one I'd send it back and get one from a manufacturer that didn't have overclocking blocked.

 

Nvidia clockblock part deux: vBIOS

 

There blocking overclocking per manufacturer. ?

 

We'll have to see which manufacturers will become affected. So far Clevo P751ZM 980M's are coming out blocked, and also the A17 R2 with 970M. Those are the two examples I've seen so far. The 980M's in the Clevo P751ZM used to be overclockable, but apparently they're now shipping with a locked down vBIOS that won't overclock.

 

Can OCed M295Xs outperform 970Ms?

 

both the P75xZM and the P77xZM are affected...

@DataShell: i highly doubt that. the M295X is still the same card as the 7970M. i had one of those and OCed the crap out of it, resulting in a performance that was between a 780M and an 880M (closer to the latter though). a 970M is faster than an 880M...

 

I think it's time for a broad class action against them. You have rebranding of cards. Then you have the 880m's broken out of the gate, never fixed, no offer to replace to those who purchased. The only thing they have done is cripple and throttle them to avoid complete hardware failure. This means advertised clocks are wrong, advertised benchmarks are wrong, and all advertised performance is wrong. They sold those products on lies.

Then you have the misadvertised 970 and it's not quite 4GB vram. Another product sold based on a lie. Now you have this overclocking fiasco. So they call an advertised feature a "bug" after 10 years, then the bug is going to be brought back due to pressure. Now, they are removing it again after trying to act like they are going to give customers what they shouldn't have had to ask for in the first place. More lies, misleading statements and products sold based on misleading information.

I'm telling you now, this company wouldn't stand a chance if a class action were to be brought against them. They deserve it, hell, they are almost begging for it.

 

I wonder is the vbios version number now different on the clevo p751zm from what is was before overclocking was blocked.?

 

Do you think Clevo even realised this latest vBIOS was locked.

Who actually manufactures the MXM cards - Nvidia?

 

But the modded VBIOS can still be installed, right?

 

Agreed, they need a swift kick in the butt, and how!

 

Clevo manufactures them, but they likely just use whatever reference code they're given for the GPU. I've tried numerous drivers and it's locked out. One of them the vRAM could be adjusted but GPU not at all.

 

Will now, a very interesting turn of events, while it seems it won't affect any of us whom already own, anyone planning on buying a Maxwell card is screwed. Time to put the hurt on nvidia. First they try to software block us. Now this? The nvidia doesn't have a future in my household anymore. As long as they don't disable software overclock again, i'll keep what I got, but as soon as it dies I really think AMD will have my support from now on. Makes me ashamed to owned 2 laptops with nvidia now. But after spending over $2k on my GT72 recently and not having any other source of income, I'm stuck with what I have now, otherwise I'd say screw it and take a performance hit and go AMD. Just to screw nvidia. They keep this **** up they won't have a marketshare.

 

Nvidia made the 970m and 980m good enough to rebrand at least three more times. And if they don't block overclocking everyone who bought the 970m and 980m won't need to buy a new card for the next 3 gpu upgrades. It's just driving nvidia crazy knowing all the loss in gpu upgrades they are going loose out on and they are willing to go to the extent to stab us in the back to keep it from happening.

 

Affected notebooks so far? AW 17/15/13 and Clevo P77xZM/P75xZM?

 

The good thing is they can't force a vBIOS update on anyone who has already bought a machine. If they even think they can try I WILL sue for pushing something on my laptop I DIDN'T WANT, NEED or otherwise have ANY PART OF! Try it nvidia, just try it.

I hope for nvidia's sake it is what you state, they may have been looking at shipping both the new driver and new vBIOS at the same time and due to testing of the vBIOS it took a little longer for that one to leak out, but regardless, nvidia is in for a world of hurt.

 

The problem is that AMD has not been taking their mobile sector seriously. And while it might hurt Nvidia, rewarding AMD by buying their mediocre products is not going to help mobile gaming as a whole. The best thing to do right now would be to hold out on purchasing anything until Q2, because Team Red can only improve on their M295x. And for all of our sakes, let's hope they do.