daily BSOD during normal windows use (not gameplay)

here you go: MEMORY (1).DMP - Google Drive

Last saterday, I swapped the videocard from my other PC system with my problematic computer.
I installed the most recent drivers on both computers. And continued to use the computers as usual.

Today (tuesday), I had the first BSOD on my problematic computer.
On the other, correct working computer, no BSOD so far.

I attached the DM log and created a link to memory.dmp MEMORY.DMP - Google Drive

There were no misbehaving drivers in the debugging of the mini dump.
The memory dump debugging displayed Nvidia dGPU misbehaving drivers.

Was the Nvidia GPU card working without problems in another computer?
Were you able to find another computer to test the AMD card?
If so was the computer stable or were there BSOD?

If the computer that had the Nvidia GPU was stable then there are two different GPU cards that have had BSOD in the problematic computer.

This can be a port or motherboard problem.

View the computer manual to view all of the possible ports for the GPU card.
List the number and names of the ports.
Try each of the ports with the Nvidia GPU card.

Code:

Name	NVIDIA GeForce GTX 770
PNP Device ID	PCI\VEN_10DE&DEV_1184&SUBSYS_28251462&REV_A1\4&1C3D25BB&0&0019
Adapter Type	GeForce GTX 770, NVIDIA compatible
Adapter Description	NVIDIA GeForce GTX 770
Adapter RAM	(2.147.483.648) bytes
Installed Drivers	C:\Windows\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_2e7fa54192fe16d0\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_2e7fa54192fe16d0\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_2e7fa54192fe16d0\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_2e7fa54192fe16d0\nvldumdx.dll
Driver Version	23.21.13.8813
INF File	oem5.inf (Section022 section)
Color Planes	Not Available
Color Table Entries	4294967296
Resolution	2560 x 1440 x 59 hertz
Bits/Pixel	32
Memory Address	0xF6000000-0xF6FFFFFF
Memory Address	0xE8000000-0xEFFFFFFF
Memory Address	0xF0000000-0xF1FFFFFF
I/O Port	0x0000E000-0x0000E07F
IRQ Channel	IRQ 54
I/O Port	0x000003B0-0x000003BB
I/O Port	0x000003C0-0x000003DF
Memory Address	0xA0000-0xBFFFF
Driver	c:\windows\system32\driverstore\filerepository\nv_ref_pubwu.inf_amd64_2e7fa54192fe16d0\nvlddmkm.sys (23.21.13.8813, 16,15 MB (16.936.048 bytes), 9-11-2017 04:40)

Code:

Event[12087]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-PnP
  Date: 2019-02-16T13:22:47.884
  Event ID: 219
  Task: N/A
  Level: Waarschuwing
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Fractal
  Description: 
The driver \Driver\amdkmafd failed to load for the device PCI\VEN_1002&DEV_AAF0&SUBSYS_AAF01462&REV_00\4&1c3d25bb&0&0119.

Code:

amdkmafd.sys
AMD Audio Bus Lower Filter
http://support.amd.com/us/gpudownload/Pages/index.aspx

Code:

nvlddmkm	nvlddmkm	c:\windows\system32\driverstore\filerepository\nv_ref_pubwu.inf_amd64_2e7fa54192fe16d0\nvlddmkm.sys	Kernel Driver	No	Manual	Stopped	OK	Ignore	No	No

Code:

nvlddmkm.sys Fri Oct 27 10:49:39 2017 (59F35593)

@zbook Once again you are focusing on GPU issues that are not the problem. You have incorrectly implicated the GPU driver when it was not involved in the crash. Recheck your analysis.

@philc43 There are other ways to communicate. Instead of criticizing with "you statements" use positive statements so that others have the opportunity to learn.

zbook said:

@philc43 There are other ways to communicate. Instead of criticizing with "you statements" use positive statements so that others have the opportunity to learn.

If I have offended you I apologise. I should have asked you to explain the analysis in post #24 of the memory dump which led to the conclusion that the GPU driver was implicated.

In another thread there was a timing question. Please comment on how you determined the timing.

Apologies for chiming in yet again: bit of a context from me.

I too was plagued by unexplained and entirely random BSODs in the past (throughout last year). It suffices to say that the ultimate lengthy analysis of DMP files with @cwsink kind help was kind-of inconclusive and the result might have been either CPU, or GPU, or MoBo, or Memory, or SSD that would be at fault (sic!).

Now, I sincerely believe that the relevant hardware test software can (should) expose these quickly. There's always margin for error here and there, but: either something is proved to work, or is not.
All hardware tests on my PC confirmed that all is well, with temperatures being within the expected range etc. (This is HP PC we're talking about here). And yet, every now and then: BSOD out of the woodwork. Genuinely puzzling!

And then: BSODs have suddenly stopped, just like that - funnily enough, from around 1809 release. To this day I have no idea whether it's Intel RST drivers that were to blame (most likely in my view) or any other driver (Realtek Audio? Realtek Ethernet? Logitech SetPoint? Anything else? Driver verifier has not thrown anything up). I've not changed anything internally hardware-wise, installed software remains broadly the same.

My Windows remains the same since 1607 release (so HP factory config, plus MS forced upgrade every 6 months, that is), I never had to - nor wanted to - reinstall or refresh OS from scratch or recovery disks.

So: go figure.