Flyview

Alright so I decompressed my BIOS with PhoenixTool from MyDigitalLife forum. Now what, how can I tell which of these files is the vBIOS? Thanks for the guidance!

The voltage options are locked on this Ivy Bridge laptop. I was hoping to unlock them through modifying the BIOS?

Hey guys, So about a year ago I tried this and even though I was able to extract the bios ME region and modify it, it didn't unlock anything on my UX32VD with Intel HM76 board. Is there anything I can modify in the bios image to allow some undervolting? The CPU just gets way too hot when also running the dedicated GPU on this laptop. Attached is the ME region I extracted a year ago. ME Region.zip

Thanks. I'll work on extracting the vbios for now. I know I decompressed the entire bios before trying to unlock the CPU. So has no one has been able to edit a vbios for a Fermi mobile card? That's not good news!

Hey I know I'm digging this up from 2 years ago, but I'm looking for a modded nVidia 620m vbios. I'm hoping to undervolt it as this card just gets too damn hot in my Asus UX32VD. Did you ever have a custom vbios for it? The only "trick" I've managed so far is to disable nVidia PowerMizer with PowerMizer Manager app, set it in to low performance mode, and then up the clocks in that mode back to stock clocks. This allow me to run at 0.925v instead of 0.975v but it's STILL really hot. It'll reach 85c+ under load at 24c ambient. This is in combination with an i7 3517U with eliminated TDP for turbo power boost with Intel XTU. The problem is they share a heat pipe and heat eac hother up. Would anyone be so kind as to build me a modded vbios or point me to some documentation on doing this myself? I can post the original. Thanks!

So should I try this on my ASUS UX32VD with HM76 chipset? Could it cause something bad?

Thanks! Yea then I'm not even interested in changing BCLK, I know in the past when I've tried increasing FSB on other computers with PCI-E SATA harddrives, it would lock up very very fast. If I could unlock the multipliers, that'd be great. Were you able to do that?

Interesting, I opened up the ME region only .bin I posted earlier and you are correct, the changed bits aren't there (I guess the "Int" folder is no good). However, they are if I open up the full image, which I flashed. I also re-dumped the current FW and opened the image in fitc and the bits are changed. Here is my newly dumped .bin after the changes: http://s000.tinyupload.com/?file_id=61252391357967251527 I'm really just doing this to see if it's possible, not so much out of need, this is an Ultrabook after all. I would love to unlock the multipliers. The BCLK would also overclock other components right?

Well I built and flashed the entire FW (8mB). I figured it wasn't necessary to change the number of flash devices if I did that? I did indeed do the flashing in Windows.

Seriously!? The modified one I pulled from the "Int" (Intermediate) build folder. It creates these when building the full .bin image which I flashed.

Yea I guess so. Here's my original and modified ME regions (in .zip). I just realized the modified one is much larger. I took these from the files FITC first created for the original, and from the Int folder for the new one. ME Region - modified.zip ME Region.zip

So I flashed my modified firmware (just built and flashed the full thing), nothing additional unlocked in XTU or ThrottleStop that I can tell. In fact, I could have sworn that in XTU, I previously could see "Reference clock - 100Mhz" greyed out but now I can't see it at all. I tried attaching my original and modified ME regions here but it says invalid file. Tried both .bin and .rar.

You are correct. I tried drivers 347.88 just to check and the same thing happens. I can choose the clocks to apply, but they don't actually apply. What else should I check? This is on a Asus UX32VD running Windows 8.1 Pro.

It always shows 625MHz in Afterburner when memory has also ramped up to 900MHz under load, no matter what I set it to. Memory changes on the other hand do take effect. Sent from my Nexus 5

I just did that. Completely wiped with DDU, re-installed drivers 350.12, core clock selection still doesn't have an effect. Tried both with MSI Afterburner and Nvidia Inspector. I.e. I can set the clock, but when checking the actual clocks in Nvidia control panel "system information", the GPU clock is at 625. The memory clock overclocks fine and is reported as such. I initially realized there's a problem when I noticed 3DMark11 was reporting my GPU core clock as stock, and the memory clock as overclocked.