The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.

M4700 GPU Upgrade

Discussion in 'Dell Latitude, Vostro, and Precision' started by mx90, Dec 18, 2018.

Thread Status:
Not open for further replies.
  1. silverchairbg

    silverchairbg Notebook Geek

    Reputations:
    0
    Messages:
    82
    Likes Received:
    14
    Trophy Points:
    16
    Also can you try to save the vbios from GPU-Z WHEN it recognizes the card bios version? It should also recognize the other params such as GPU clock, memory, texture bandwidth etc.
     
  2. mx90

    mx90 Notebook Enthusiast

    Reputations:
    0
    Messages:
    21
    Likes Received:
    0
    Trophy Points:
    5
    The issue I have is "Board ID Mismatch". I believe this is because the vbios is for the M2000 Desktop, as I mentioned. I've tried the techpowerup one and yours, but I get that same error. When I tried a version with the certs bypassed, it seemed to go through until nvflash simply crashes. I think GPU-Z being able to see any card info may be based on the current drivers I have installed. I'll fiddle with them again later, but I can tell you now that the firmware version was the same one I provided earlier. I am able to install the unmodified drivers, but with or without the modifications I still get Code 43 in Device Manager.

    I sent you a PM regarding what I was quoted for sending a padded envelope to a zip code in Bulgaria.

    I also want to point out that I did disable the card in Device Manager when using nvflash, and that checking the .rom generated from nvflash with Maxwell II Bios Editor reveals that it is the same vbios I have provided - the one for the M2000 Desktop card.

    edit: I'll post the GPU-Z with the Bios showing when I can.
     
  3. Aaron44126

    Aaron44126 Notebook Prophet

    Reputations:
    874
    Messages:
    5,544
    Likes Received:
    2,045
    Trophy Points:
    331
    I assume you've tried some of this already, but, I Googled around for ways to get around the board ID mismatch. In my experience there is a way to get nvflash to override lots of different things. I remember having to type in a cryptic command I found on Reddit to turn off protection, to get around a failed K5000M flash.

    Saw a few failures but found this one that someone managed to get around.
    https://forums.extremeoverclocking.com/showthread.php?t=149569
    (Admittedly quite an old thread)
    Looks like a simple erase before re-flash.

    Also numerous people saying
    Code:
    nvflash -4 -5 -6 filename.rom
    should work.
     
  4. mx90

    mx90 Notebook Enthusiast

    Reputations:
    0
    Messages:
    21
    Likes Received:
    0
    Trophy Points:
    5
    Here's a pic of the results after using the unmodified installer, btw
    I've been trying the -4 -5 -6 commands, but every time I do it tells me I'm using an invalid command :vbconfused: Same for using -f. I'll look through that thread and try some more!
     
  5. mx90

    mx90 Notebook Enthusiast

    Reputations:
    0
    Messages:
    21
    Likes Received:
    0
    Trophy Points:
    5
    Here it is:
    [​IMG]

    edit: This is with the stock nVidia drivers installed, no modified .inf. (ver. 411.95 Win10 64bit).
     
  6. silverchairbg

    silverchairbg Notebook Geek

    Reputations:
    0
    Messages:
    82
    Likes Received:
    14
    Trophy Points:
    16
    1.gif Everything matches with what mine shows except the memory vendor and Boost. Your boost shows 1163 Mhz - same as what m2000 is, while mine is 1036 Mhz. I found a contact through a friend, who has Zbook G4 with this card, he promised he would save the vbios and give it to me over the weekend. So I would just wait to see what his is. If it is the same as yours, then I would have to take the chance and try to flash it over, or consider making a swap.
     
  7. mx90

    mx90 Notebook Enthusiast

    Reputations:
    0
    Messages:
    21
    Likes Received:
    0
    Trophy Points:
    5
    Please share his vbios here as well! As far as swapping, perhaps we could purchase each others cards through ebay for the same price?
     
  8. mx90

    mx90 Notebook Enthusiast

    Reputations:
    0
    Messages:
    21
    Likes Received:
    0
    Trophy Points:
    5
    Do you know anything about the -o command in nvflash? I can't seem to get it to work. I'm trying -o 3 GM206.ROM
     
  9. mx90

    mx90 Notebook Enthusiast

    Reputations:
    0
    Messages:
    21
    Likes Received:
    0
    Trophy Points:
    5
    Update - I was refunded for the M2200 that came from the HP with the M2000 vbios! I purchased one that came from a later Dell model (I believe it was the Precision 7520). The new card worked fully and immediately after a single Windows crash (I hadn't even been able to log into my account before the crash occurred and it has not happened since). Thanks to everyone who helped with troubleshooting the previous card and good luck to others when trying to circumvent HP's (or Dell's) proprietary measures!
     
Loading...
Thread Status:
Not open for further replies.

Share This Page