Kuffs

My bad, should be fixed now.

Thanks for the quick update. I guess the P5 and P8 states could have been unlocked before, but P0 couldn't. Now +/- 524 MHz is available. Have to try it in the 3d Mark 11 now and I'll report back.

314.22 drivers

Stock: 600/700: P3892, max temp 79 (but run after OC run; didn't keep track during the first run)

OC: 900/1000: P5473 (40% increase), max temp 77 C

OC: 1000/1000: P5903 (50% increase), max temp 79 C

Didn't try to go higher, don't plan to; this is just what I needed to improve the performance in DCS World and try to get by till those 780M prices go down to some reasonable levels (read: much much less than the current 700 EUR ).

Thanks a lot!

BTW, I've been to Switzerland and man the beer is expensive there.. Hope my small token of appreciation can get you one!

3GB Clevo 670mx added and Dell K4000m added. Check the second post.

Thanks for the Dell K4000M update. I've flashed it, but the nvidia inspector and e.g. EVGA Precision are still limited to 135 MHz. This is with the 314.22 drivers, I've tried upgrading to 320.18, but those give me a black screen (and 100+ pages of feedback on them on Nvidia forum are not very encouraging ).

Kuffs: "Really doubt"? Er, basically every PCB is custom in a mobile system. It more or less has to be since you're trying to cram it into such tight confines. Not only is the motherboard unique and unswappable between different cases (even by the same manufacturer), but the GPU is customized as well to a smaller degree.

We're only discussing GPUs here and MXM 3.0b compatible ones.

Rather than having a configuration file, it's cheaper and increases performance (Slightly, but it's there) to have everything hard-coded. It's safer too; if something goes wrong and data gets corrupted, the GPU won't boot since it's very likely the code explaining how to boot got corrupted with it. If it continued to boot and then read bad numbers, it might ask for some obscenely large amount of power or something and potentially ruin other parts of the laptop.

I have no idea what are you talking about here. It's just a lot of generalizations and assumptions.

Generally what happens is there's a base image given to them by nVidia, and then they have a program that lets them tweak it to suit their needs. (How else do you think NiBitor used to work?) -- These days though, companies generally have their leaks covered. That's why we got people like svl7!

Yes, this is what I was talking about. I'd presume most OEMs don't customize the Nvidia BIOS structure, but maybe tweak some options or parts at most and why would they (unless they make changes to the Nvidia PCB design or specs of the used components like memory and such)?

This is why I could take the 680M from e.g. a Clevo laptop and put it in my Dell Precision M6600 or M6700 and it would work although the card is not officially supported by the motherboard BIOS.

Kuffs: No, almost every vbios is different, even between different manufacturers. That's why he has ones for the 680m for both Clevo and Dell cards and such. He does actually need one in his possession (or a willing test subject, if you feel like volunteering) to see if stuff works.

Not so sure that's so often the case. Usually, just the OEM ID is different between different manufacturers. Yes, they can have a custom BIOS, but usually they don't bother as having a dedicated development team for that costs money and what are the gains really? Unless you have a custom PCB or smth which I doubt they do in mobile.

See this post and the one after it. If you want to speed the process up, you can buy svl7 a K4000M.

But I thought that the Nvidia BIOS'es are similar so he can change it without actually owning one (e.g. there's already a modifed K3000M and K5000M (hence why I posted my vBIOS here https://anonfiles.com/file/28887b9dbe84d945d616f1e194e02509).

Yes, it's called a "hex editor"

Of course I know it's done with a HEX editor and I presume that the address location for the clock values Nvidia uses for their vBIOS is probably in the same spot so it can be found easily by someone who knows what to look for. Hence why you have programs like vBIOS patcher which then edit these values which the ones you want. All I asked was if this patcher application supports K4000M or not.

I just hope he can find time to mod the K4000M. Is there some sofware for this? Does that vBIOS patcher support Nvidia Quadro cards? OK, I could probably use the 675MX one, but I'd rather have one which my laptop BIOS supports officially.

For me the topic is interesting, i owned M17x R3 for a year (with 580M GTX) and it was getting ridicilously hot even at stock clocks. It was throttling all the time and GPU reached 80c. I have seen m6700 and m17x cooling systems and they are pretty similar setup, but where comes that big difference?

But 580M is a Fermi core in 40nm. You can't really directly compare its temperature to the Kepler core (28nm) one.

@svl7: Can you please unlock the K4000M BIOS?

This is the one saved with GPU-Z off my Dell..

https://anonfiles.com/file/28887b9dbe84d945d616f1e194e02509