Gaming laptop rtx 2070: Disappearing GPU after BSOD, Only using integrated graphic now

[gshark1]

Hi, I've exhausted lots of software side options to try and fix why my nvidia 2070 GPU has disappeared from my gaming laptop MSI GL75-10SFK. The system boots and functions normally but only using Intel integrated graphics. Before, it was working fine then began having some blue screens. (I will attach the system event and mini-dump at the end of post). After a few days of the occasional BSODs it finally disappeared from device manager and never came back. I researched and attempted to troubleshoot this issue but im out of options and was wondering if yall had some ideas maybe on the hardware side.

Things ive already completed: Fresh windows install, Update MSI bios and vbios from official website, checking Device Manager with show hidden files and scanning new hardware, checking with GPU-Z, using DDU to uninstall drivers, turning fast boot and hibernation off CMOS and battery reset, re-pasting with K5 on vram and arctic silver 5 on dies. After hours of doing these things the 2070 is still missing.

Often hardware issues cause the entire system to not boot or power on however this system boots and functions fine only using Intel graphics. I am not thinking it is software related because ive exhausted all potential trouble shooting options ive found.
Does anyone have any steps on how to proceed to try and recover the 2070 or find answers?

A link to my model mobo and schematics from another post: https://www.badcaps.net/forum/troubl...rd-msi-ms-17e5

Event Viewer of last BSOD: Faulting application name: SearchHost.exe, version: 623.27905.60.0, time stamp: 0x6536b7a6

Faulting module name: nvwgf2umx.dll, version: 31.0.15.4633, time stamp: 0x6570b433

Exception code: 0xc0000005

Fault offset: 0x0000000000420716

Faulting process id: 0x0x2384

Faulting application start time: 0x0x1DA381320C9A217

Faulting application path: C:\Windows\SystemApps\MicrosoftWindows.Client.CBS_ cw5n1h2txyewy\SearchHost.exe

Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\nvm iig.inf_amd64_649395c294ad3a68\nvwgf2umx.dll

Report Id: 40737fed-f085-42ef-9d13-d2862f7dd859

Faulting package full name: MicrosoftWindows.Client.CBS_1000.22681.1000.0_x64_ _cw5n1h2txyewy

Faulting package-relative application ID: CortanaUI

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

Faulting application name: dwm.exe, version: 10.0.22621.2506, time stamp: 0xdef1fe51

Faulting module name: dwmcore.dll, version: 10.0.22621.2715, time stamp: 0xc95a35c0

Exception code: 0xc00001ad

Fault offset: 0x0000000000271a18

Faulting process id: 0x0x604

Faulting application start time: 0x0x1DA38131ED601C5

Faulting application path: C:\WINDOWS\system32\dwm.exe

Faulting module path: C:\WINDOWS\system32\dwmcore.dll

Report Id: 72ca8406-9093-4925-838b-7a6917ee47a4

Faulting package full name:

Faulting package-relative application ID:

Mini Dump:
Dump file analyzed:

VIDEO_DXGKRNL_FATAL_ERROR (113) The dxgkrnl has detected that a violation has occurred. This resulted in a condition that dxgkrnl can no longer progress. By crashing, dxgkrnl is attempting to get enough information into the minidump such that somebody can pinpoint the crash cause. Any other values after parameter 1 must be individually examined according to the subtype. Arguments: Arg1: 0000000000000019, The subtype of the BugCheck:
Arg2: 0000000000000002
Arg3: 00000000000010de
Arg4: 0000000000001f14

Debugging Details: ------------------ *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** WARNING: Check Image - Checksum mismatch - Dump: 0x20b519, File: 0x20b59d - C:\ProgramData\Dbg\sym\BTHport.sys\CA3C6A82202000\ BTHport.sys KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec Value: 1687
Key : Analysis.Elapsed.mSec Value: 3791
Key : Analysis.IO.Other.Mb Value: 0
Key : Analysis.IO.Read.Mb Value: 0

Key : Analysis.IO.Write.Mb Value: 3
Key : Analysis.Init.CPU.mSec Value: 187
Key : Analysis.Init.Elapsed.mSec Value: 46806
Key : Analysis.Memory.CommitPeak.Mb Value: 118
Key : Bugcheck.Code.LegacyAPI Value: 0x113
Key : DirectX.FatalError.Code Value: 19
Key : DirectX.FatalError.Desc Value: UNEXPECTED_DEFERRED_DESTRUCTION
Key : Dump.Attributes.AsUlong Value: 1008
Key : Dump.Attributes.DiagDataWrittenToHeader Value: 1
Key : Dump.Attributes.ErrorCode Value: 0
Key : Dump.Attributes.KernelGeneratedTriageDump Value: 1
Key : Dump.Attributes.LastLine Value: Dump completed successfully.
Key : Dump.Attributes.ProgressPercentage Value: 0
Key : Failure.Bucket Value: 0x113_19_nvlddmkm!unknown_function
Key : Failure.Hash Value: {fb504da1-90a7-64ec-e7aa-d0c04338976f}

BUGCHECK_CODE: 113 BUGCHECK_P1: 19 BUGCHECK_P2: 2 BUGCHECK_P3: 10de BUGCHECK_P4: 1f14 FILE_IN_CAB: 122623-6328-01.dmp DUMP_FILE_ATTRIBUTES: 0x1008 Kernel Generated Triage Dump
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System

STACK_TEXT: ffff8003`eda17658 fffff806`4a5a5685 : 00000000`00000113 00000000`00000019 00000000`00000002 00000000`000010de : nt!KeBugCheckEx ffff8003`eda17660 fffff806`4a3ad96b : 00000000`00000000 ffff9a84`730e6710 ffff9a84`730e6718 ffff9a84`730e6720 : watchdog!WdLogSingleEntry5+0x3b45 ffff8003`eda17710 fffff806`4a3027d1 : ffff9a84`7370c030 00000000`00989600 ffff9a84`69f1fd00 ffff9a84`00000000 : dxgkrnl!DpiFdoHandleDevicePower+0xaacfb ffff8003`eda177b0 fffff806`4a304201 : ffff9a84`79f83ab0 ffff9a84`7370c180 ffff9a84`7370c030 ffff8003`eda178d0 : dxgkrnl!DpiFdoDispatchPower+0x21 ffff8003`eda177e0 fffff806`5c253810 : ffff9a84`73a70000 ffff9a84`7a9ec000 ffff9a84`73a70000 ffff9a84`79f83ca0 : dxgkrnl!DpiDispatchPower+0xe1 ffff8003`eda17900 ffff9a84`73a70000 : ffff9a84`7a9ec000 ffff9a84`73a70000 ffff9a84`79f83ca0 ffff9a84`00000004 : nvlddmkm+0x10f3810 ffff8003`eda17908 ffff9a84`7a9ec000 : ffff9a84`73a70000 ffff9a84`79f83ca0 ffff9a84`00000004 ffff8003`00000000 : 0xffff9a84`73a70000 ffff8003`eda17910 ffff9a84`73a70000 : ffff9a84`79f83ca0 ffff9a84`00000004 ffff8003`00000000 ffff9a84`00000001 : 0xffff9a84`7a9ec000 ffff8003`eda17918 ffff9a84`79f83ca0 : ffff9a84`00000004 ffff8003`00000000 ffff9a84`00000001 ffff8003`000000ff : 0xffff9a84`73a70000 ffff8003`eda17920 ffff9a84`00000004 : ffff8003`00000000 ffff9a84`00000001 ffff8003`000000ff ffff9a84`73a70000 : 0xffff9a84`79f83ca0 ffff8003`eda17928 ffff8003`00000000 : ffff9a84`00000001 ffff8003`000000ff ffff9a84`73a70000 fffff806`35183291 : 0xffff9a84`00000004 ffff8003`eda17930 ffff9a84`00000001 : ffff8003`000000ff ffff9a84`73a70000 fffff806`35183291 ffff9a84`73ccb530 : 0xffff8003`00000000 ffff8003`eda17938 ffff8003`000000ff : ffff9a84`73a70000 fffff806`35183291 ffff9a84`73ccb530 ffff8003`eda179c8 : 0xffff9a84`00000001 ffff8003`eda17940 ffff9a84`73a70000 : fffff806`35183291 ffff9a84`73ccb530 ffff8003`eda179c8 00000000`00000004 : 0xffff8003`000000ff ffff8003`eda17948 fffff806`35183291 : ffff9a84`73ccb530 ffff8003`eda179c8 00000000`00000004 00000000`00000000 : 0xffff9a84`73a70000 ffff8003`eda17950 fffff806`35107a94 : ffff2270`a72ce1c5 00000000`00000000 00000000`00000001 00000000`00000001 : Wdf01000!FxPkgFdo::_DispatchSetPower+0x21 [minkernel\wdf\framework\shared\irphandlers\pnp\fdo power.cpp @ 122] ffff8003`eda17980 ffff9a84`7370c030 : ffff9a84`79f83ab0 00000000`c0000002 ffff9a84`79f83ca0 fffff806`5c25254e : Wdf01000!FxPkgPnp::Dispatch+0xd4 [minkernel\wdf\framework\shared\irphandlers\pnp\fxp kgpnp.cpp @ 771] ffff8003`eda179f0 ffff9a84`79f83ab0 : 00000000`c0000002 ffff9a84`79f83ca0 fffff806`5c25254e ffff9a84`7370c030 : 0xffff9a84`7370c030 ffff8003`eda179f8 00000000`c0000002 : ffff9a84`79f83ca0 fffff806`5c25254e ffff9a84`7370c030 00000000`00000001 : 0xffff9a84`79f83ab0 ffff8003`eda17a00 ffff9a84`79f83ca0 : fffff806`5c25254e ffff9a84`7370c030 00000000`00000001 ffff9a84`69f1fd30 : 0xc0000002 ffff8003`eda17a08 fffff806`5c25254e : ffff9a84`7370c030 00000000`00000001 ffff9a84`69f1fd30 ffff9a84`00000000 : 0xffff9a84`79f83ca0 ffff8003`eda17a10 ffff9a84`7370c030 : 00000000`00000001 ffff9a84`69f1fd30 ffff9a84`00000000 ffff9a84`7370c030 : nvlddmkm+0x10f254e ffff8003`eda17a18 00000000`00000001 : ffff9a84`69f1fd30 ffff9a84`00000000 ffff9a84`7370c030 fffff806`3252dcda : 0xffff9a84`7370c030 ffff8003`eda17a20 ffff9a84`69f1fd30 : ffff9a84`00000000 ffff9a84`7370c030 fffff806`3252dcda ffff9a84`69eab040 : 0x1 ffff8003`eda17a28 ffff9a84`00000000 : ffff9a84`7370c030 fffff806`3252dcda ffff9a84`69eab040 ffff8003`eda17ac0 : 0xffff9a84`69f1fd30 ffff8003`eda17a30 ffff9a84`7370c030 : fffff806`3252dcda ffff9a84`69eab040 ffff8003`eda17ac0 ffff9a84`7ad23000 : 0xffff9a84`00000000 ffff8003`eda17a38 fffff806`3252dcda : ffff9a84`69eab040 ffff8003`eda17ac0 ffff9a84`7ad23000 fffff806`00000000 : 0xffff9a84`7370c030 ffff8003`eda17a40 fffff806`32507167 : ffff9a84`69eab040 00000000`00000000 fffff806`3252d870 00000000`00000000 : nt!PopIrpWorker+0x46a ffff8003`eda17af0 fffff806`3261bb94 : ffffe401`7575f180 ffff9a84`69eab040 fffff806`32507110 00000000`00000000 : nt!PspSystemThreadStartup+0x57 ffff8003`eda17b40 00000000`00000000 : ffff8003`eda18000 ffff8003`eda11000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34

SYMBOL_NAME: nvlddmkm+10f3810
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 10f3810
FAILURE_BUCKET_ID: 0x113_19_nvlddmkm!unknown_function OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {fb504da1-90a7-64ec-e7aa-d0c04338976f} Followup: MachineOwner ---------

[tronitas46]

hi! I have an MSI laptop with a rtx 3060 with the same issue, although I'm unsure if it had BSODs since it's a laptop someone gave me, the laptop works just fine with the IGP but the 3060 is nowhere to be seen, just like you I checked all the software possibilities with no success, then I decided to take a look at the hardware and found that the power delivery GPU side was shorted to ground, at the moment I'm not properly equipped to diagnose dead shorts so I haven't checked it further, but maybe you have the same problem

[piernov]

https://www.badcaps.net/forum/troubl...61#post1459061

2.2. Don't suspect that something is shorted with no reason
Shorted components are not the only failure mode of a laptop. Additionally, some places will measure low resistance to ground under normal operation. In general, high power low voltage (<2V) power rails will measure less than a few hundred ohms to ground. CPU VCore will measure a few ohms only. GPU VCore with newer NVidia GPU can even measure less than 1 ohm. It's normal. If you suspect a short to ground, always report your exact resistance to ground measurements.

[tronitas46]

hi! thanks for the response, yes you're right! from experience sometimes smd caps and stuffs can go short just because they feel like to, or sometimes it's a symptom of another cause, that's why you never assume and it's important to verify, in my case it's really a short though (reading 0.1ohm between vcore and ground) and there's no power getting into the GPU! (but yeah I should've been more precise, I'm kinda new on the forum so sorry about that ^^')

[tronitas46]

hi! thanks for the response, yes you're right! from experience sometimes smd caps and stuffs can go short just because they feel like to, or sometimes it's a symptom of another cause, that's why you never assume and it's important to verify, in my case it's really a short though (reading 0.1ohm between vcore and ground) and there's no power getting into the GPU! (but yeah I should've been more precise, I'm kinda new on the forum so sorry about that ^^')

well it seems that I was wrong! I just saw someone measuring around 0.150ohm on a known good RTX 3060 ti saying that it's normal for recent GPUs to have such a low reading, I definitely didn't know about that, my bad!

also did you find the issue on your laptop gshark1?