Jump to content
applepiefly

Problems installing GTX980m into CLEVO P157SM

Recommended Posts

Hi,

(You can refer to this album for screenshots: https://imgur.com/a/1UJ2YSj )

I have a P157SM running Windows 10 and had been running my GTX780M with NVIDIA 391.35 drivers running stable long term. I inserted a new GTX980M and started my laptop. Everything seemed to be working fine (I was halfway through a benchmark and it was clearly using the new GPU with higher performance numbers), until suddenly everything froze and I had to reboot. I kept having issues, my laptop would often freeze, so I did a clean install of Windows 10.

Since the fresh install:

-Device Manager would initially recognise it as "Microsoft Basic Display Adapter" and then automatically install driver 388.xx in the background. I continued to have issues, so I tried to do a regular (no modded infs) install of 391.35, which seemed to install well enough, but after rebooting I would run into errors again.

-I downloaded DDU to do clean removes of the NVIDIA drivers and to stop Windows automatically installing 388.xx. I have tried installing 391.35 with modded nvcvi.inf file. Before installing the modded driver I would reboot with the "Disable Driver Signature Check" option, and then I installed the driver.

Here are the edited sections of that inf file (the line I added is in bold, I included the whole 13D7 section):
[NVIDIA_Devices.NTamd64.10.0...14310]
….
%NVIDIA_DEV.13D7.0376.1558% = Section058, PCI\VEN_10DE&DEV_13D7&SUBSYS_03761558
%NVIDIA_DEV.13D7.0870.1558% = Section060, PCI\VEN_10DE&DEV_13D7&SUBSYS_08701558
%NVIDIA_DEV.13D7.5281.1558% = Section062, PCI\VEN_10DE&DEV_13D7&SUBSYS_52811558
%NVIDIA_DEV.13D7.5106.1558% = Section062, PCI\VEN_10DE&DEV_13D7&SUBSYS_51061558
%NVIDIA_DEV.13D7.6540.1558% = Section064, PCI\VEN_10DE&DEV_13D7&SUBSYS_65401558
%NVIDIA_DEV.13D7.6541.1558% = Section066, PCI\VEN_10DE&DEV_13D7&SUBSYS_65411558
%NVIDIA_DEV.13D7.6556.1558% = Section062, PCI\VEN_10DE&DEV_13D7&SUBSYS_65561558
%NVIDIA_DEV.13D7.6780.1558% = Section064, PCI\VEN_10DE&DEV_13D7&SUBSYS_67801558
%NVIDIA_DEV.13D7.6781.1558% = Section066, PCI\VEN_10DE&DEV_13D7&SUBSYS_67811558
%NVIDIA_DEV.13D7.7481.1558% = Section062, PCI\VEN_10DE&DEV_13D7&SUBSYS_74811558
%NVIDIA_DEV.13D7.7500.1558% = Section068, PCI\VEN_10DE&DEV_13D7&SUBSYS_75001558
%NVIDIA_DEV.13D7.7502.1558% = Section070, PCI\VEN_10DE&DEV_13D7&SUBSYS_75021558
%NVIDIA_DEV.13D7.7700.1558% = Section068, PCI\VEN_10DE&DEV_13D7&SUBSYS_77001558
%NVIDIA_DEV.13D7.7702.1558% = Section070, PCI\VEN_10DE&DEV_13D7&SUBSYS_77021558
.....

[NVIDIA_Devices.NTamd64.10.0]
...
%NVIDIA_DEV.13D7.0376.1558% = Section057, PCI\VEN_10DE&DEV_13D7&SUBSYS_03761558
%NVIDIA_DEV.13D7.0870.1558% = Section059, PCI\VEN_10DE&DEV_13D7&SUBSYS_08701558
%NVIDIA_DEV.13D7.5281.1558% = Section061, PCI\VEN_10DE&DEV_13D7&SUBSYS_52811558
%NVIDIA_DEV.13D7.5106.1558% = Section061, PCI\VEN_10DE&DEV_13D7&SUBSYS_51061558
%NVIDIA_DEV.13D7.6540.1558% = Section063, PCI\VEN_10DE&DEV_13D7&SUBSYS_65401558
%NVIDIA_DEV.13D7.6541.1558% = Section065, PCI\VEN_10DE&DEV_13D7&SUBSYS_65411558
%NVIDIA_DEV.13D7.6556.1558% = Section061, PCI\VEN_10DE&DEV_13D7&SUBSYS_65561558
%NVIDIA_DEV.13D7.6780.1558% = Section063, PCI\VEN_10DE&DEV_13D7&SUBSYS_67801558
%NVIDIA_DEV.13D7.6781.1558% = Section065, PCI\VEN_10DE&DEV_13D7&SUBSYS_67811558
%NVIDIA_DEV.13D7.7481.1558% = Section061, PCI\VEN_10DE&DEV_13D7&SUBSYS_74811558
%NVIDIA_DEV.13D7.7500.1558% = Section067, PCI\VEN_10DE&DEV_13D7&SUBSYS_75001558
%NVIDIA_DEV.13D7.7502.1558% = Section069, PCI\VEN_10DE&DEV_13D7&SUBSYS_75021558
%NVIDIA_DEV.13D7.7700.1558% = Section067, PCI\VEN_10DE&DEV_13D7&SUBSYS_77001558
%NVIDIA_DEV.13D7.7702.1558% = Section069, PCI\VEN_10DE&DEV_13D7&SUBSYS_77021558


- However, I still run into issues. See picture 2 of the imgur album for what Device Manager reports (and to see that Task Manager does not even recognise the GPU). Picture 4 is one of the blue screens I sometimes get. I have tried reinstalling the drivers (picture 1) with different section numbers but it does not seem to work, I reboot and I still get the same thing as Picture 2.

Does anyone know what the root cause of my problems might be? I am open to the possibility that I did not do everything completely properly. For example, I think sometimes when I tried to installed modded inf drivers testing a new section number, when I installed the driver I may have booted Windows without going through the "Disable Driver Signature Check" boot process (however, it seemed like the driver install itself seemed to work fine, although after the reboot I ran into the above described issues). If anyone could point me in the right direction I'd be grateful. Thank you.

Share this post


Link to post
Share on other sites
Posted (edited)

Hey duffman_777, 

 

Thanks for the link. I'm trying to give it a go, but I have two questions so far:

 

1. Under section "Downloads: Standard/Legacy", it gives a link to "GEFORCE 417.71 WIN10" from official NVIDIA servers to download, and then links to "nv_dispi.inf_v417.71_Win10_OPtimus_MSHybrid_AW_ASUS_CLEVO_MSI.zip". The link to the GEFORCE 417.71 drivers is  to "417.71-desktop-win10-64bit-international-whql" - i.e., the desktop drivers, not the notebook drivers. Is this known to be okay?

 

2. Back near the top of the page where the instructions are given, the 3rd point is "Extract driver package using 7-zip … >> Delete Folders as shown above (DON'T SKIP THIS STEP)." I can't see what information above shows which folders I need to delete. Can someone help me out?

 

Thanks!

 

EDIT: 

 

In the mean time, I extracted the driver "417.71-desktop-win10-64bit-international-whql" package linked on the page, I copied just the nvcvi.inf file extracted from the linked "nv_dispi.inf_v417.71_Win10_OPtimus_MSHybrid_AW_ASUS_CLEVO_MSI.zip" file. Still the same problems, after install and reboot, device manager still reports Code 43 error for the card :(

Edited by applepiefly

Share this post


Link to post
Share on other sites

1. I normally download the notebook drivers direct from nvidia myself (https://www.nvidia.com/Download/Find.aspx?lang=en-us) and paste in J95s inf's after extracting

 

2. I think that may be old information (for previous drivers) - I've installed 417.71 without deleting any folders and only copying across the .inf and setup.cfg

Share this post


Link to post
Share on other sites

1. When you download the drivers yourself, do you get the notebook drivers and not the desktop drivers?

 

2. Ok thanks for clearing that up.

Share this post


Link to post
Share on other sites

Yep, I get the notebook ones (i.e., the ones listed when you search for a 980m)

Share this post


Link to post
Share on other sites

I've been downloading the notebook drivers from the official NVIDIA archives and replacing some files according to the J95 page.

 

No matter what I try, after installing drivers and restarting, I open up Device Manager and the GPU is recognised as a GTX  980M but the Device status is reported as "Windows has stopped this device because it has reported problems. (Code 43)". 

 

I have tried multiple driver versions, replacing the nvcvi.inf and setup.cfg with J95s, replacing nvcvi.inf, nv_dispi.inf and setup.cfg with J95s (even though the P157SM Optimus 980M shouldn't require nv_dispi.inf to be replaced). I've fresh installed Windows and tried those again. Nothing seems to work :(

 

If anyone could be so kind, could they package up a set of old NVIDIA drivers with the appropriate files already modified so that I could simply run setup.exe and expect it to work? I have already tried so many permutations but maybe it would just settle the question of whether I'm doing something stupidly incorrect or if the correct instructions simply aren't working on my machine. 

 

Is it possible that BIOS and vBIOS or anything like that could be an issue here? I have just the oldest stock BIOS. 

 

I've attached GPU-Z screenshots. The one with the card name as "GTX 980M" is after installing 398.36 drivers but rebooting and Device Manager showing the error. The one with "Microsoft Basic Display Adapter" is after running DDU to clean remove the NVIDIA drivers. Both of them show 0 Mhz for the clocks and Unknown BIOS. Not sure if this information is useful. 

gpuz980m.gif

gpuz980mnodrivers.gif

Share this post


Link to post
Share on other sites

I was running a 980m on my P150EM up until recently without issues (just upgraded to a 1070), but I've got Prema's V2 BIOS. Maybe this is the cause of the problem?  I have a feeling that the prema BIOS are what allow you to run 9xxm cards whereas the stock BIOS don't (not 100% sure on this). The only issue is it's hard to find these BIOS since the site shut down a few years ago. 

  • Thumbs Up 1

Share this post


Link to post
Share on other sites
Posted (edited)

So after using nvflash to put the Clevo 8gb GTX 980m vBios from techpowerup.com onto the GPU, GPU-Z shows a BIOS version, but still 0 values for the memory and clock speeds on the GPU. Does this seem like I received a faulty GPU, or something that could be resolved by a different BIOS on my mobo and/or vBIOS on the GPU?

 

@duffman_777  - Is the Prema V2 BIOS a BIOS for your mobo, or a vBIOS you put onto the card? I have also heard about maybe needing some special BIOS/vBIOS to install a 980m into a P157SM, but I've also heard some people say it's not required but just helps you overclock etc, so I'm not sure.

clevo980m.gif

Edited by applepiefly

Share this post


Link to post
Share on other sites

On mine, I was running Prema v2 BIOS (mobo) and (as far as I remember) a prema v2 vBIOS (card). I remember reading the same thing in terms of it being for OC instead of for compatibility but can't quite remember where I read it.

 

By the way - what power adaptor are you using? The freezing may be related to a power issue if you're using anything less than a 180W brick.

Share this post


Link to post
Share on other sites

I'm using a 230W adaptor so that shouldn't be the issue. I was afraid I'd need those Prema mods... My Clevo is from Metabox which is listed as a Prema partner, but when I email them they say they can't provide me with the Bios. I've tried contacting Prema directly on various forums and on Twitter, offering donations, but still no reply... :((

Share this post


Link to post
Share on other sites
1 hour ago, applepiefly said:

I'm using a 230W adaptor so that shouldn't be the issue. I was afraid I'd need those Prema mods... My Clevo is from Metabox which is listed as a Prema partner, but when I email them they say they can't provide me with the Bios. I've tried contacting Prema directly on various forums and on Twitter, offering donations, but still no reply... :((

Hi!

I think that you can try update your system bios to 1.03.05 version from this Clevo repo:  https://repo.palkeo.com/clevo-mirror/P1xxSM/

Share this post


Link to post
Share on other sites

@Klem Hi, Thanks for your advice. I updated my BIOS to 1.03.05 and tried to install NVIDIA drivers similarly to my attempts above, and the behaviour is unfortunately the same. 

Share this post


Link to post
Share on other sites
36 minutes ago, applepiefly said:

@Klem Hi, Thanks for your advice. I updated my BIOS to 1.03.05 and tried to install NVIDIA drivers similarly to my attempts above, and the behaviour is unfortunately the same. 

Also, I think that you can try to flash this vbios version:  https://www.techpowerup.com/vgabios/200721/200721

Share this post


Link to post
Share on other sites
Posted (edited)
7 hours ago, Klem said:

Also, I think that you can try to flash this vbios version:  https://www.techpowerup.com/vgabios/200721/200721

When I try to use nvflash with that bios it fails with this message:

-------------------------------------------------------------------------------------------------

NVIDIA Firmware Update Utility (Version 5.556.0)
Copyright (C) 1993-2019, NVIDIA Corporation. All rights reserved.


Checking for matches between display adapter(s) and image(s)...

Adapter: GeForce GTX 980M     (10DE,13D7,1558,5106) H:--:NRM  S:00,B:01,D:00,F:00


EEPROM ID (7F,9D42) : PMC Pm25LQ020 2.3-3.6V 2048Kx1S, page

WARNING: Firmware image PCI Subsystem ID (10DE.110B)
  does not match adapter PCI Subsystem ID (1558.5106).

Please press 'y' to confirm override of PCI Subsystem ID's:
Overriding PCI subsystem ID mismatch
Current      - Version:84.04.2F.00.79 ID:10DE:13D7:10DE:110B
               GM204 Board (Normal Board)
Replace with - Version:84.04.88.00.C1 ID:10DE:13D7:10DE:110B
               GM204 Board (Normal Board)

Update display adapter firmware?
Press 'y' to confirm (any other key to abort):
EEPROM ID (7F,9D42) : PMC Pm25LQ020 2.3-3.6V 2048Kx1S, page

 


BIOS Cert 2.0 Verification Error, Update aborted.


Nothing changed!

 

ERROR: Invalid firmware image detected.

 

-------------------------------------------------------------------------------------------------

 

I think to bypass this error I can try the instructions here: https://www.overclock.net/forum/71-nvidia-drivers-overclocking-software/1521334-official-nvflash-certificate-checks-bypassed-gtx-950-960-970-980-980ti-titan-x.html

 

I'll give those a try. 

Edited by applepiefly

Share this post


Link to post
Share on other sites
1 minute ago, applepiefly said:

When I try to use nvflash with that bios it fails with this message:

-------------------------------------------------------------------------------------------------

NVIDIA Firmware Update Utility (Version 5.556.0)
Copyright (C) 1993-2019, NVIDIA Corporation. All rights reserved.


Checking for matches between display adapter(s) and image(s)...

Adapter: GeForce GTX 980M     (10DE,13D7,1558,5106) H:--:NRM  S:00,B:01,D:00,F:00


EEPROM ID (7F,9D42) : PMC Pm25LQ020 2.3-3.6V 2048Kx1S, page

WARNING: Firmware image PCI Subsystem ID (10DE.110B)
  does not match adapter PCI Subsystem ID (1558.5106).

Please press 'y' to confirm override of PCI Subsystem ID's:
Overriding PCI subsystem ID mismatch
Current      - Version:84.04.2F.00.79 ID:10DE:13D7:10DE:110B
               GM204 Board (Normal Board)
Replace with - Version:84.04.88.00.C1 ID:10DE:13D7:10DE:110B
               GM204 Board (Normal Board)

Update display adapter firmware?
Press 'y' to confirm (any other key to abort):
EEPROM ID (7F,9D42) : PMC Pm25LQ020 2.3-3.6V 2048Kx1S, page

 


BIOS Cert 2.0 Verification Error, Update aborted.


Nothing changed!

 

ERROR: Invalid firmware image detected.

 

-------------------------------------------------------------------------------------------------

Yes of course, to flash this vbios you should use special version of Nvflash. For example like this:  https://www.techinferno.com/index.php?/profile/259-prema/&do=content&type=downloads_file

Share this post


Link to post
Share on other sites
7 hours ago, Klem said:

Yes of course, to flash this vbios you should use special version of Nvflash. For example like this:  https://www.techinferno.com/index.php?/profile/259-prema/&do=content&type=downloads_file

 

Thanks for your help and patience Klem. I don't have promotion to download that file but instead I used this: https://www.techpowerup.com/download/nvidia-nvflash-with-certificate-checks-bypassed/ . The vBIOS seems to have flashed successfully. I'm going to try to install the drivers with modded nvcvi.inf and setup.cfg as per the J95 links discussed above. Wish me luck!

Share this post


Link to post
Share on other sites

No luck :( Before I installed the drivers, I checked with GPU-Z that the new vBIOS was recognised (it indeed reported vBIOS version 84.04.88.00.C1), but after I installed drivers it reports "Unknown" and 0 values for the memory and clocks. Device Manager also reports the Device Status as "Windows has stopped this device because it has reported problems. (Code 43)". I think this card may be faulty? I don't know what else I can even try. 

sadness.gif

Share this post


Link to post
Share on other sites
Posted (edited)
10 minutes ago, applepiefly said:

No luck :( Before I installed the drivers, I checked with GPU-Z that the new vBIOS was recognised (it indeed reported vBIOS version 84.04.88.00.C1), but after I installed drivers it reports "Unknown" and 0 values for the memory and clocks. Device Manager also reports the Device Status as "Windows has stopped this device because it has reported problems. (Code 43)". I think this card may be faulty? I don't know what else I can even try. 

sadness.gif

 

Send me your stock vbios from your card.

 

Edited by Klem

Share this post


Link to post
Share on other sites
7 minutes ago, applepiefly said:

This is the stock vBIOS.

clevo980m.rom

You sure? I ask because this vbios version I see on your screenshot where you told that you flashed vbios from techpowerup.

Share this post


Link to post
Share on other sites
Posted (edited)
7 hours ago, Klem said:

You sure? I ask because this vbios version I see on your screenshot where you told that you flashed vbios from techpowerup.

I originally thought the vBIOS from techpowerup was a new vBIOS but I realised it was the same version number as what was already on the card. I was suspicious when I had run nvflash -6 "techpowerups vBIOS" and it ran instantly. When I did nvflash with the new one you linked it, it indeed showed a different version number and took some time to transfer some data, it was not instant like before. 

 

Hopefully it does not make a difference, but if it matters then I may have messed up. I originally saved the pure stock vBIOS but lost it during one of my fresh reinstalls of Windows. I thought it wouldn't matter since I thought the techpowerup file was identical. Is it possible for the versions to be identical but for the vBIOS to be meaningfully different? 

Edited by applepiefly

Share this post


Link to post
Share on other sites
6 minutes ago, applepiefly said:

I originally thought the vBIOS from techpowerup was a new vBIOS but I realised it was the same version number as what was already on the card. I was suspicious when I had run nvflash -6 "techpowerups vBIOS" and it ran instantly. When I did nvflash with the new one you linked it, it indeed showed a different version number and took some time to transfer some data, it was not instant like before. 

 

Hopefully it does not make a difference, but if it matters then I may have messed up. I originally saved the pure stock vBIOS but lost it during one of my fresh reinstalls of Windows. I thought it wouldn't matter since I thought the techpowerup file was identical. Is it possible for the versions to be identical but for the vBIOS to be meaningfully different? 

Ok. Check your PM.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×

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.