Jump to content

Eats7

Registered User
  • Posts

    73
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by Eats7

  1. 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.
  2. when you see C:\>... just type prr.exe then enter then type flash.bat and then enter
  3. 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.
  4. So you can confirm throttle is back with the 332 series?
  5. NO. These are BIOS files for m14x only. they are not just video bios's.
  6. i recommend IC diamond. its what i use and have been pretty happy with it.
  7. 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.
  8. Does anyone know if the 332 driver still disables throttle at 67 C?
  9. My cpu temps dont go past 75.. try a repaste. Also can anyone confirm the 332 driver still disables the throttle?
  10. 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.
  11. I know there is an option in there to overcclock the hd4000 (gt overclocking) not sure about memory allocation. it might be in there
  12. Im looking into it. I know they are doing something, but im not sure what.
  13. 331.82 still hasnt fixed the bug, so it's ok to update.
  14. 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
  15. 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.
  16. 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?
  17. 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.
  18. 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
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.