Flagman

Ofc its retail GT70 Anyway, after flashing svl7 vBIOS it looks like everything works as intended. Now it boots with proper 666 clock, and overclocking works like a charm. Didn't do a lot of testing, but no problems so far.

Turbo button is just a relic from older MSI notebooks where it actually did something. In my GT70(Win7 + S-Bar) Turbo button acts as P1 button, so I can set other program to turn on after I press it, but it does nothing else. It lights up for a sec and that's it, doesn't matter if MSI VGA OC is running, with it running with admin privileges, with it set to run in P1, without it etc. As I said, there is no pattern AFAIK as to why sometimes it starts with 666 and most of the time(always with new OS) with 653.The only difference I see is in VDDC. GPUZ reports it while playing like this: 1.0375 with old OS that started with 666Mhz, stays the same after OCing to +135. 1.0250 with new OS that has started with 653Mhz. 0.9750 with new OS after I set Afterburner to +135( it stays at 653). The more I OC in new OS the more it drops from 1.0250 to 0.9750. If I downclock few Mhz VDDC jumps to 1.0375.

Crucial MX100 256GB version. One of the best budget SSDs out there atm.

My GT70 came with this GTX 675MX, so yea its officially supported. I have seen few treads online from GT70 with GTX 675MX owners that have the same 653 problem, but there were either no solution or it did nothing in my case. Here's my vBIOS 675MX.zip

Hey, I have MSI GT70 with GTX 675MX and there is a problem with its core clock. My problem is kind of similar to one in this thread http://forum.techinferno.com/msi/3792-675mx-clock-stuck-stock-msi-afterburner-enabled.html is but there is more stuff that's unexplainable. I have stock 10U BIOS, vBIOS is also stock http://gpuz.techpowerup.com/14/06/25/bkw.png As most of you know MSI GTX 675MX standart core clock is 666 Mhz. The problem is that pc boots with 675MX clock as 653 for no apparent reason or explanation. I now have 2 OSes in my pc, and while with my old OS in old HDD the chance to boot with 666 was about 20%, with my new OS in new SSD that chance is absoliutely gone, and it never boots into 666. If it boots with core clock as 653, there is no way to overclock it. MSI afterburner doesn't work, Nvidia Inspector doesn't work, targeting different pstates doesn't work above 653, while down-clocking works as it should. I can turn my pc with new OS, see 675MX clock as 653, restart with old OS, core clock magically is 666, overclocking works to vBIOS limited +135 without problems, then I restart pc to new OS and its back to 653 which doesn't let me OC VGA in any way I tried. I had most drivers from OEM 306 to 340 but none of them had any effect on this behavior. I wonder what are the chances that modified vBIOS would fix this problem, and/or is there anything else that might change these anomalies.

That's very possible. One thing is cooling CPU that's is idling, while its completely difference picture when CPU is 100% loaded, especially because fan speed cant keep up with load in those first seconds. The way Intel builds their CPU doesn't help either.

Medium settings should be about playable.