Going to start with the basics:
Laptop Make/Model- Clevo/Sager P151EM1
Graphics Card -- Device ID (DEV_ID) if known- Nvidia GTX 870m 6GB, NVIDIA_DEV.1199.5105.1558, stock vBIOS1
Current working Driver Version- None (660m working fine on 385.28)
Last Useable Driver Version- None
Operating System- Windows 10 Professional x64
An accurate description of the issue at hand- See below.
The issue is described here (I created a new thread to avoid bulking-up the main 384.80 thread), but essentially it's that no matter what modified inf I use, it always results in a code 43 (aka, the Nvidia driver halts the card because it thinks something is wrong).
The card is detected without problems within Windows and within Linux the drivers install properly (the official ones, without inf mod or anything like that) however the system will not boot (issues with communication between the driver and X-window, which is a common issue looking at Google- probably not relevant in this case though I thought I'd mention it).
It's literally that the Nvidia drivers stop the card when it initializes, and this problem is starting to drive me slightly mad.
The 870m itself is a working pull from a Clevo P170SM (both the P170SM and P151EM1 have identical motherboards, with a few minor differences, so the 870 is compatible hardware-wise).
Might also mention that the drivers install fine and the 870m in Device Manager is apparently working fine without the Intel iGPU drivers being installed, so maybe the Intel iGPU (Intel Graphics 4000) is interfering here?
As the GPU is working fine without drivers installed (and that it works "fine" in Linux (yes, it detects its vRAM size and capabilities), all signs point to a problem with the Nvidia drivers/binaries.
The machine's previous 660m GPU works fine with Nvidia's current drivers without any modifications to the inf.
Does anyone have any suggestions as to what is wrong here, and how I could go about making the 870m work properly in this system?
1 Apparently Premamod's vBIOS should get the 870m to work properly, but as Prema's run into some legal issues regarding the readme in their BIOS/vBIOS files, they've locked access to their website and it seems that nobody is able to get through to Prema in order to provide the required files privately.
↧