Eats7

a13 unlocked works fine for me but watch dogs good fps only with 720p low details - is this max we gonna get on out m14x r2 gt650m 2gb?

depends on what you consider good fps..

I don't see a point in upgrading to A14. it brings nothing to the table in terms of improvements. I think it would be a wast of time for @svl7 to look into.

Restart the system and boot from your USB stick. Run prr.exe, then flash the bios by executing the flash.bat file. Wait until the tool completes the flash. If the verification is okay, reboot, else flash again..

Go to the bios, load the default settings and reboot. Done.

when you see C:\>...

just type prr.exe then enter

then type flash.bat and then enter

so this is an underclock?

no. the A10 was actually overclocked in the vbios by svl7. with a13, he just left it at stock clocks. you can still overclock a13 yourself.

Yeah i am getting rather annoyed with this damn 67c throttle, in fact i can't even be bothered to say anymore as it really does *bleep* me off.

So you can confirm throttle is back with the 332 series?

no downgrading allowed.

Ive used it, and have had no issues.

NO. These are BIOS files for m14x only. they are not just video bios's.

i recommend IC diamond. its what i use and have been pretty happy with it.

I see in the release notes they have re added boost back to the 650m. When it's on the boost powerstate, it will throttle. So I'm almost positive this driver throttles again. I will not be updating unless for some magical reason it no longer throttles on the boost powerstate and someone can post some proof.

I am tring to install an os x to my M14x, are there any ways to configure the graficcards in the hack BIOS?

No, sorry.

Has anyone noticed any issues with their hardware? Meaning hardware damage with overclocking their m14x r2?

Nope. At least not me.

Does anyone know if the 332 driver still disables throttle at 67 C?

the bios/vbios modded A13.

My cpu temps dont go past 75.. try a repaste.

Also can anyone confirm the 332 driver still disables the throttle?

what number does it say? Ive noticed in msi afterburner and evga precision, it reports the wrong clocks (405mhz) no matter what. however in hwinfo and nvidia inspector it reports the right core clock. i think it's a bug between the driver and msi/evga apps.

im using precision, i love havin in game osd:)

Is there an option to configure HD4000 internal memory allocation? Not so much into overclocking but want to know the memory size so I can OS X properly....;-)

I know there is an option in there to overcclock the hd4000 (gt overclocking) not sure about memory allocation. it might be in there

Im looking into it. I know they are doing something, but im not sure what.

331.82 still hasnt fixed the bug, so it's ok to update.

yes using it now

The more ive looked into it the more i think it may be something to do with nvidia inspector. my clocks keep getting stuck as well. but when i open nv inspecter they go back down to 135... weird. all other programs say the 405mhz/835mhz. When restoring defaults in nvinspector, it can sometimes make your clocks stuck, depending on what you fooled around with so im going to attempt to uninstall everything and try some stuff

yeah but thats a pain doing it everytime. and i dont think its at 405, i think thats a bug with nvidia inspector. its really pissing me off.

yeah i had that problem with msi afterburner showing 405 mhz only. its a bug i think, cuz when i restart afterburner, it shows 135 which it should. which version of afterburner are you using?

hmm i don't know about overclocking cpu, i have never had a need for it (its more than powerful for enough games)

as for the performance on battery, i'm not sure either, i have not noticed this.

see my post here http://forum.techinferno.com/alienware-m14x-aw-14/1787-%5Bm14x-r2%5D-vbios-mod-higher-boost-clocks-test-versions-only-36.html#post73746