Hi technodos,
The debugging of the 2 mini dump files indicates problems with the Nvidia drivers or GPU related hardware.
A VIDEO_TDR_ERROR always relates to the system's graphics card (TDR = Timeout Detection Recovery). This could be down to a number of reasons including drivers, heat, power to the card, a faulty PCI-e slot or simply a defective GPU. It's in your best interests to employ common sense trouble shooting techniques in these situations.
Try later and/or earlier drivers
Measure the GPU's temperatures at idle and under load
Ensure the GPU is free from dust build up and that the fan is working correctly
Reseat the GPU and check all connections are securely made
Check PSU voltages in BIOS
Try a different card in the system
The memtest86+ you had reported is in progress. Please make sure that there are at least 8 passes and that a camera photo is made to post an image into the thread.
Addition:
If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
If errors show up and you see them a lot later, no problem, the errors don't affect the test.
Make sure that there is no over clocking while troubleshooting.Sometimes there are problems in the bios that produce bsod.
Let us know whether or not the computer can boot to lock screen/wall paper/splash screen after the memory testing has completed or whether you are still in a boot loop.
If you are in a boot loop please explain what you see each time you power on and off.
If you have not yet tried to break the boot loop please do so with 3 power on/power off with the power off timed to the Microsoft icon. The timing is important. Let us know whether you can or cannot open the windows recovery or windows advanced troubleshooting menu.
Create a bootable windows 10 iso: Download Windows 10
The bios in your computer: BIOS Version/Date American Megatrends Inc. F7, 3/23/2012
Please check to see if this is the most up to date version.
To ensure that there are no improper bios settings please reset the bios.
Sometimes there can be failure to boot after resetting the bios.
So please make sure your files are backed up.
Please make a backup image with Macrium:
Macrium Software | Macrium Reflect Free: Macrium Software | Your image is everything
And please create a restore point.How to Clear Your Computers CMOS to Reset BIOS Settings:
How to Clear Your Computers CMOS to Reset BIOS Settings Ways to Reset Your BIOS - wikiHow:3 Ways to Reset Your BIOS - wikiHow
Open administrative command prompt and type of copy and paste:
1) sfc /scannow
2) dism /online /cleanup-image /restorehealth
3) chkdsk /scan
4) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on copy > paste into the thread
5) Uninstall all Nvidia drivers/software.
The best way to do this is to uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from the computer manufacturer website using serial or product number with operating system or from the NVidia website.
If there is not a suitable driver on the computer manufacturer's web site or if it is a custom computer and you use the Nvidia web site be sure the "clean install" box is checked and only install the Graphics driver and the PhysX driver.
Display Driver Uninstaller Download version 17.0.6.7: https://www.wagnardsoft.com/https://...se.html?filter[2]=Hardware%20and%20Drivers
NVIDIA
Code:
nvlddmkm nvlddmkm nvlddmkm Kernel Manual Stopped OK FALSE FALSE 5,820,416 6,438,912 0 5/1/2017 12:55:53 PM C:\Windows\system32\DriverStore\FileRepository\n 36,864
Code:
BugCheck 116, {ffffd50f538d0010, fffff80981caf44c, ffffffffc0000001, 5}Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_f9309145156afb40\nvlddmkm.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for nvlddmkm.sys*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sysProbably caused by : nvlddmkm.sys ( nvlddmkm+15f44c )
Code:
BugCheck 116, {ffff9f8e20f09010, fffff80438fef44c, ffffffffc0000001, 5}Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_f9309145156afb40\nvlddmkm.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for nvlddmkm.sys*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sysProbably caused by : nvlddmkm.sys ( nvlddmkm+15f44c )Followup: MachineOwner---------0: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************VIDEO_TDR_FAILURE (116)Attempt to reset the display driver and recover from timeout failed.Arguments:Arg1: ffff9f8e20f09010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).Arg2: fffff80438fef44c, The pointer into responsible device driver module (e.g. owner tag).Arg3: ffffffffc0000001, Optional error code (NTSTATUS) of the last failed operation.Arg4: 0000000000000005, Optional internal context dependent data.Debugging Details:------------------FAULTING_IP: nvlddmkm+15f44cfffff804`38fef44c 48ff252d4c6700 jmp qword ptr [nvlddmkm+0x7d4080 (fffff804`39664080)]DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULTCUSTOMER_CRASH_COUNT: 1BUGCHECK_STR: 0x116PROCESS_NAME: SystemCURRENT_IRQL: 0ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64freSTACK_TEXT: ffffb701`fec33b68 fffff804`37008498 : 00000000`00000116 ffff9f8e`20f09010 fffff804`38fef44c ffffffff`c0000001 : nt!KeBugCheckExffffb701`fec33b70 fffff804`37008155 : fffff804`38fef44c ffff810b`ae10a5b0 00000000`00000080 fffff804`370080f0 : dxgkrnl!TdrBugcheckOnTimeout+0xecffffb701`fec33bb0 fffff804`37008106 : 00000000`00000000 00000000`00000000 00000000`00000001 fffff801`b7451000 : dxgkrnl!CTDR_GDI_RESET_THREAD::Worker+0x25ffffb701`fec33be0 fffff801`b56d7a37 : fffff801`b4b64180 fffff801`b578f3d7 00000000`03ac3863 ffff9f8e`20e16040 : dxgkrnl!CVP_SYSTEM_THREAD::ThreadRoutine+0x16ffffb701`fec33c10 fffff801`b578f456 : fffff801`b4b64180 ffff9f8e`20e16040 fffff801`b56d79f0 00000000`00000000 : nt!PspSystemThreadStartup+0x47ffffb701`fec33c60 00000000`00000000 : ffffb701`fec34000 ffffb701`fec2e000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16STACK_COMMAND: .bugcheck ; kbFOLLOWUP_IP: nvlddmkm+15f44cfffff804`38fef44c 48ff252d4c6700 jmp qword ptr [nvlddmkm+0x7d4080 (fffff804`39664080)]SYMBOL_NAME: nvlddmkm+15f44cFOLLOWUP_NAME: MachineOwnerMODULE_NAME: nvlddmkmIMAGE_NAME: nvlddmkm.sysDEBUG_FLR_IMAGE_TIMESTAMP: 590792c9FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sysBUCKET_ID: 0x116_IMAGE_nvlddmkm.sysANALYSIS_SOURCE: KMFAILURE_ID_HASH_STRING: km:0x116_image_nvlddmkm.sysFAILURE_ID_HASH: {c89bfe8c-ed39-f658-ef27-f2898997fdbd}
Bug Check 0x116 VIDEO_TDR_ERROR | Microsoft Docs