Nvidia Quadro M2200 (memory) not detected post repaste Heatsink the Dell Precision 7520

Rule of thumb is that if it worked fine before the repaste and does not work now, something has changed such as a connection or the GPU was damaged in some way. The 43 error and the nvlddmkm.sys is a driver problem though so that might be a starting point for diagnosis.

@JOcean​ thanks for the insight.

After sometimes, I dared myself to do the vBIOS update using NVFlash64. 

The process itself was successful, but still the GPU not "properly" detected.

Guess I'll need to check and clean the GPU slot

Have had this issue in the past and seen it on forums, something gets misconfigured/broken and the easiest way is to reset the BIOS flash w/ the coin cell, then fresh install Windows. It's very unlikely (and hard) to reinstall hardware where it only mostly works. Resetting the BIOS flash (or reflashing it, but not as reliably) and fresh Windows install is the easiest option at this point. Windows can easily become broken once you start messing with cmd utilities and registry configs trying to troubleshoot, so just restart from clean BIOS and OS before it gets out of hand. Especially with dedicated GPUs and switching, you run into stuff like this.

@Mike1788​ , Yes I've seen also the reset BIOS process w/ the coin cell in some online articles.

I will definitely try it when reseating / clean the MXM GPU slot.

Thanks.

Did you have issues before repasting? Was everything fine but temps? Is this the original Windows install? Do you have a restore point before the problems? Have you downloaded Supportassist or whatever and do you have all the latest BIOS and updates from Dell? The newer GPU-Z screenshot shows it's UEFI isn't checked and if you disabled UEFI and secure boot there'd be a lot of issues.

Before you bother opening it, open BIOS settings and click to reset them to factory or default. Before doing that though, you should see that Supportassist remediation or whatever is installed. I'm remembering more about dealing with something very similar and am increasingly confident the boot partition and config is broken, which no changes in drivers/software will fix.

By far the easiest option to try right now is 1. f2 to BIOS and reset to factory, F12 on reboot to Supportassist to reinstall newest Windows or factory drive image, but only the options that download it and keep no data. If you're confident everything is fully seated and connected there's no reason to open it back up, it simply isn't really possible for the GPU to not be seated and fully connected. Losing even one contact if it were physically possible wouldn't be mostly working like this. HWInfo64 is the most popular program (that I use) and in the main window has a ton of useful info about what's configured and what's connected and even if the OS needs replaced can tell you if everything is connected and communicating correctly, so you can be sure you don't have to open it again.

Hi @Mike1788​ .

There's no issue before repasting (or probably the issue haven't arose yet). And I haven't got a chance to create a restore point before the problem, as I just recently bought this notebook.

Yesterday evening, the notebook managed to work with the Quadro GPU. I've managed to run a Blender render without any issue, and the render time is as expected. While the GPU was operable, I've successfully export the GPU rom. Even I haven't open and clean the GPU yet.

Before it "suddenly" worked again yesterday, below are some of steps I've taken.

1. Clean-up all graphic drivers in DDU Safe Mode. The firstly removed is the NVidia, and followed by Intel driver.

2. Modify BIOS on Discrete redirection for external display. So when an external display is connected, it will works by the discrete GPU.

3. Install the Intel driver.

I leave the notebook to my son as he wanted to have some entertainment stuff in the notebook. The notebook is connected to external display via HDMI while it was used.

Most likely, Windows update was successfully installed while it was used by my son.

This morning the error returns. But the positive side is that I have validated that there's no device faulty in this case.

As per my observation, the error is coming when Windows is loading the GPU driver after logged in. The error message is "System thread extension not handled" (nvlddmkm.sys).

I will focus on troubleshoot for the driver, and will inform for the progress.

@tutorizal​ @Mike1788 is spot on with the driver advice. That error is driver related and could be an old or outdated driver or corrupt system files.

Yes, it is the automatic installation of NVidia driver (from Windows update) that caused the nvlddmkm.sys error. Now I'm currently finding ways to prevent Windows from installing the defective driver (in my case 349.65)