Jump to content

omega939

Registered User
  • Posts

    276
  • Joined

  • Last visited

  • Days Won

    3

Posts posted by omega939

  1. This vBIOS is great! Stock clocks are now the boost ones and they run at 0.95V..

    Stock 3D Mark 11: Intel Core i7 3940XM @4.2GHz and stock 970M(running on full boost): NVIDIA GeForce GTX 970M video card benchmark result - Intel Core i7-3940XM,Alienware M17xR4

    For Firestrike: Stock 970M (full boost ) + 3940XM @ 4.2GHz: NVIDIA GeForce GTX 970M video card benchmark result - Intel Core i7-3940XM,Alienware M17xR4

    Anyways, max stable OC I've done on 344.75 is +300 core and +600 memory (+300 on boost memory clock) with power target on 130% and 1.056V..

    NVIDIA GeForce GTX 970M video card benchmark result - Intel Core i7-3940XM,Alienware M17xR4

    Will be doing more benching later today.. Need to ramp the voltage up a bit..

    Hmm.. I think i really need to upgrade my CPU to an extreme then :D .. btw.. You using nvidia inspector right?

  2. Monitor actual clocks & GPU usage during gaming using something like GPUz to determine where the difference lies. (Ensure that game is actually being run on NVidia dedicated GPU and not on the Intel GPU).

    The game is definitely running with 970m at ultra settings. if it where to run on intel gpu then the game is not playable at ultra settings and will only run between 1 - 5fps.

    With the stock vbios (clevo) the fps is high, running between 100fps and up. With the vmodded vbios the fps runs at 40 - 50 fps only both run at the same core and mem frequency and at ultra settings.

  3. I followed the procedure.

    and did the following (under command prompt - admin)

    -Disabled 970m under device manager

    - command prompt with administrative priviledges

    - Went to Mnvflash and input the following command:

    ex: c:\mnvflash -6 bios.rom

    and i get this error

    "ERROR: FIrmware image filename must have a valid extension. (.rom .nvr. efr. ef)

    I've got the vbios version Clevo 970M vbios version 84.04.22.00.13. used with MSI GT60-16F3

    ====

    Update :

    Got to flashed it.. the file name is too long so the solution is just to put the name like this . ex: c:\mnvflash -6 Nvidia~1.rom

    then follow the procedure.

  4. Is there a way for the latest version nvflash 5.19 to force flash the vbios? I am getting an error in mismatched id E910 vs e905 for gt 970m.. one got optimus enabled (for gt60 haswell) the other came from gt72 which I know doesn't use optimus... Can someone please help me what command I must put in? cos the one I use for the command is this : "c:\nvflash -6 file.rom" .. error : board id mismatch. theres no "-4" with the latest version

  5. @everybody

    M17XR3/R4 are optimus enabled (muxeless) compared to MX18 which is muxed right? So it's possible to disable the optimus (muxeless in bios) on this nb for the discrete gpu to be independent with the internal graphics (hd4000)?

    M17xR3/R4 BIOS settings: IGP disabled (integrated graphics) PEG enabled ?

    (muxeless)

    Internal display <-> Intel HD Graphics <-> Nvidia Graphics.

    (muxed)

    Internal display <-> Switch <-> Intel HD Graphics , <-> Nvidia Graphics.

  6. This is a little off topic but I've got a clevo 970m card and this is my problem with my msi-gt60 (16f3). I updated my mxm gpu with an nvidia gtx 970m clevo card and successfully udpate to msi vbios. For the first week it works like a charm, then I re-format and made a fresh install of windows 7 .. All the drivers installed successfully.. But when playing games or any 3d app games, intel 4000 works as the gpu..

    How come the 970m not executing on 3d games... Is this related to bug of hd4000 or optimus drivers not switching to 970m when 3d apps enabled? I selected on the nvidia control panel the 970m during 3d games though... Please help thanks

  7. i m using the latest version( nvflash_windows_5.190.0.1.) , but it just says no nvidia display adapters found , i have asus n56jr with nvidia 760m.

    Thanks,

    I am also having the same issue with my GT60-16F3. I am using a clevo 970m , and is detected by windows (needs modified inf drivers though) but how come it cannot be detected under nvflash with the latest version?

    post-7316-14494998970888_thumb.jpg

  8. The 980m indeed is a dream. Runs smoothly and performs great. Unfortunately the card is locked in terms of overclocking. It supprts the allowed +135mhz without any probelm and bears an equal percentage of vRam ocing.

    Still I believe one could go further - if the bios was unlocked. That`s why I am curious to hear about news.

    Best regards

    phila

    Wait for svl7 to release an official vbios mod for maxwell GPU's I know he got a 980m on hand now, which 970m will follow.. Just be patient people :)

  9. @Prema

    Sir,

    I know you're expertice is with clevo/sager laptops and some MSI GE nb's, but is it possible if you can check other motherboard's bioses like my GT60 (16f3)?

    I want to find out if you can check the gpu's notebook compatibility , if it can read the following mxm gpu's, xt support, , updated Orom and unlock other options for overclocking etc if possible:

    – XTU Support:

    - GTX7xxM, GTX8xxM, GTX9xxM support

    if possible, can you add/unlock gpu's that can support it? Thanks

    Although I dont know how to link yet the file of the bios here but if you have an email I can send it to you.. Thanks sir

  10. look in one of the forums here by Svl7 http://forum.techinferno.com/general-notebook-discussions/1847-nvidia-kepler-vbios-mods-overclocking-editions-modified-clocks-voltage-tweaks.html

    That is for Nvidia card's only used by him in making vbios with his famous aw15 notebook. Not to mention some amd's gpu too (just browse in the forum).. So I think you have the answer now with the compatibility of the cards of your nb.

    • Thumbs Up 1
×
×
  • 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.