Cory Parker Staton

Does anyone know of any issues with reverting to the stock 223 bios? If not, do I simply use the flash tool provided to restore the stock? I seem to have deleted my back up a few weeks ago thinking it was something else... =/

Has anyone had issues with updating to the latest Nvidia drivers after flashing the custom Bios? I'm trying to rule out this mod for a problem I'm encountering. Driver software seems to think I have no compatible hardware (which we all know is BS)

R01f

Done. Try. This is the first modified version of the BIOS for your GTX660M graphics card. The whole procedure of the flashing BIOS firmware is the same as in the first post of this topic. In any case, put directly on drive C stock bios G75VWAS.223, first renaming it to G75VW.bin

Omfg. I don't know what you did, but I finally have the overclock working. I'm assuming it had something to do with the UEFI section as I'm 100% certain my SSD with Windows 8 is running off that. I've verified that an EFI partition exists.

Anyways, thanks a million man!! Beautiful job!!

While I am not "Happy" that you are in the same boat as me, I guess at least someone else is having this "problem".

Perhaps as our numbers increase there will be some attention paid to our apparent exclusion and perhaps some effort made to get it working for us.

As Cory stated in his followup, we most certainly have the 660m card. I would have thought that would be obvious from my nvidia inspector screenshots, but I guess those pictures weren't worth a thousand words after all.

Bottom line: Some of us with newer machines, with 660m, have a bios that flashes in multiple chunks. Again, as memory serves, the numbers did not add up to the size of the flash. We have the new bios menu options, but no overclock.

Thanks for any investigations. I would be happy to help in any way that I can.

Rolf

As for the size of the flash adding up, I'm not sure. I presume it would have had to for the BIOS to work properly. I wish I'd taken a screenshot to post showing that everything flashed in stages, chunks, whatever. Simply put, we're still capped at the +135 MHz overclocking limit regardless of the program, and I can't seem to flash back with a stock 223 as EZflash states it's an outdated build.

Klem

My card is the GTX 660M, which is why I'm a bit confused as to why it's not worked.

Any thoughts at all on why my card won't overclock beyond the stock with this OC vbios?

I should mention:

This was a 'new gen' windows 8 machine, best buy variant. I bought it in January.

When the flashing was taking place, it was not all one 8 MB chunk. It flashed several smaller chunks. I would have to do it again, but it seems like it was something along the lines of a 1.6 MB chunk, and some other chunks of smaller sizes. As I recall (and I really should have made a screenshot -- I guess I could do it again) the sizes of the 3-4+ chunks did not add up to the size of the bios. I noticed in the screenshot of 'what it was supposed to look like' that that persons flash was written in one chunk.

I wonder if my vbios is in a separate area. Maybe it was never overwritten, giving me the same effect as using the non-OC unlocked bios. If I make no changes, my card boots up with stock 835 mHz clock after flashing this OC vbios.

Sticker on the bottom says:

MB ver G75VW check number 4427

CANOAS218496416

G75VW-BHI7NO7

2012-10

I'm now in the same boat as R01f. I've got access to the new menus and stuff in the bios, but clock speeds are unchanged. I have the exact same system as him as well, purchased 2-6-2013. I also noticed that my bios was written in several chunks like R01f described, though I'm not terribly concerned about this. Any ideas on working out this issue? Should the default clock speed have been raised by the OC bios, or do I need to OC manually?

Ok, so I did everything, all went well. Went to the Bios to check things annnnddd none of the new menu options were there. I don't know if I somehow managed to flash the backup or something, but I tried reflashing (several times) and nothing has changed. I swear this should be so simple, I can't figure out why I keep messing it up. =/

@Klem, thanks for the response. I did as you said in an elevated command prompt, but as I try to execute the batch file, it simply states it's not recognized as an operable program or batch file. Is this a common issue? Has anyone else run into this?

Edit: nvm, I figured it out, made an error typing in the command. Thanks for leading me to use the command prompt. I thought I could just execute it from the folder. =)

Sigh. Yes, I understand and executed the instructions to the tee. You can see all the files are in the same folder through the translucent window in the screenshot. I'm not sure you're understanding my issue. I'm not seeing where, or if at all, the backup file is being made.

Hi!

You use Win32, but Fptw64 for Win64.

Good luck!

Since my system is 64-bit, shouldn't I be using Win64? Also, I don't see Win32 on the initial post. I'm assuming I'd have to search Google for it.

When trying to create the backup, I'm not receiving a backup file anywhere. I squeezed off a screenshot of running the batch file under admin.

Any suggestions on how to correct this?

I'm currently struggling with this right now. I had a dual-boot Win8 Ubuntu setup on my G74 before it bricked, so I assumed I could just transplant the two HDs and things would be just fine. Not the case. I've had to delete my old Ubuntu partition, and still can't boot from a live usb to install again. Have SecureBoot enabled? I get binary whitelisted. Not enabled? Black screen. Have spent at least 3 hours today researching how to get it to work, about to try modifying the code in GRUB.

Once you buy the new drive, do you just pop the plastic cover off the stock drive and place it on the new one? I'm a stickler for making sure any upgrade matches the rest of the system.

I'm surprised a few of you guys are talking about trying to replace the gpu on a $1400 laptop. Would a modded bios or 680 make that much difference in gaming or is this more about "doing it because you can?"

I know for me, the simple fact of being able to is satisfying enough. The engineer in me loves these kinds of challenges. However, I have read the thread in it's entirety that guido7142 has mentioned. Hundreds of pages later, I've come to the conclusion that it is possible physically with extreme case modification. But the software side? As far as I know, none of us are capable of rewriting the vbios. Unless anyone has worked at Asus or could maybe get a friend who works there to help develop a vbios for a standard MXM, I don't think it will happen. =(

Yes, if you have the matching ASUS BIOS Version before completing the installation of this custom BIOS you should experience no difficulties unless there is a pre-existing HW fault.

So what you're saying is if you already flashed to 223 bios and THEN flash the mod, there should be no issues unless it's a hardware fault that predates the modded flash?

Ezflash won't let you flash unsigned firmware.

Huh. I assume there's no way to make it appear signed either. I've always been sketchy of using windows flash applications.

I was wondering if the bios was the same for the g75vx there just isnt much information on this new asus laptop. ty for reading this.

No, pretty sure the 223 bios won't work. Double checked the support page ASUS - G75VX The specs are close to the same, but the GPU is different. Also in the download section is has a revision number at 204 for bios, so I presume the 223 isn't compatible. =/

---

So why do we use a winflash tool to flash this instead of Ezflash built into the MB?