Windows 10: Crash Dump Debugger Report - BSOD

I have been getting a BSOD almost every day now for some reason, because of that I created a dmp file, but I am not familiar with this process to figure out what any of this means. Would anyone be willing to take a look at the dmp file? I'd greatly appreciate it.



******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************VIDEO_DXGKRNL_FATAL_ERROR 113The dxgkrnl has detected that a violation has occurred. This resultedin a condition that dxgkrnl can no longer progress. By crashing, dxgkrnlis attempting to get enough information into the minidump such that somebodycan pinpoint the crash cause. Any other values after parameter 1 must beindividually examined according to the subtype.Arguments:Arg1: 0000000000000019, The subtype of the bugcheck:Arg2: 0000000000000002Arg3: 00000000000010deArg4: 0000000000001199Debugging Details:------------------KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 2827 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on DESKTOP-SI381DE Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 6402 Key : Analysis.Memory.CommitPeak.Mb Value: 81 Key : Analysis.System Value: CreateObjectADDITIONAL_XML: 1OS_BUILD_LAYERS: 1DUMP_FILE_ATTRIBUTES: 0x8 Kernel Generated Triage DumpBUGCHECK_CODE: 113BUGCHECK_P1: 19BUGCHECK_P2: 2BUGCHECK_P3: 10deBUGCHECK_P4: 1199BLACKBOXBSD: 1 !blackboxbsdBLACKBOXNTFS: 1 !blackboxntfsBLACKBOXPNP: 1 !blackboxpnpBLACKBOXWINLOGON: 1CUSTOMER_CRASH_COUNT: 1PROCESS_NAME: SystemSTACK_TEXT: ffffe80f`8401b808 fffff801`8bd841a0 : 00000000`00000113 00000000`00000019 00000000`00000002 00000000`000010de : nt!KeBugCheckExffffe80f`8401b810 fffff801`8bbda3a0 : ffffbf0a`d5b9c180 ffffffff`c000000e ffffbf0a`d5b9c180 ffffbf0a`d5b9c180 : watchdog!WdLogEvent5_WdCriticalError+0xe0ffffe80f`8401b850 fffff801`8bb52180 : ffffe80f`8401b900 00000000`00000000 ffffbf0a`d8b78200 ffffbf0a`d8b78010 : dxgkrnl!DpiFdoHandleDevicePower+0x87bd0ffffe80f`8401b8f0 fffff801`8bb53250 : ffffbf0a`d8b78010 ffffbf0a`d5b9c180 ffffbf0a`d5b9c030 ffffbf0a`d5b9c030 : dxgkrnl!DpiFdoDispatchPower+0x20ffffe80f`8401b920 fffff801`8e82a871 : 00000000`00000001 ffffbf0a`d9958000 00000000`00000001 ffffbf0a`d8b78010 : dxgkrnl!DpiDispatchPower+0xe0ffffe80f`8401ba40 00000000`00000001 : ffffbf0a`d9958000 00000000`00000001 ffffbf0a`d8b78010 ffffe80f`8401bb48 : nvlddmkm+0x19a871ffffe80f`8401ba48 ffffbf0a`d9958000 : 00000000`00000001 ffffbf0a`d8b78010 ffffe80f`8401bb48 ffffe80f`00000004 : 0x1ffffe80f`8401ba50 00000000`00000001 : ffffbf0a`d8b78010 ffffe80f`8401bb48 ffffe80f`00000004 00000000`00000000 : 0xffffbf0a`d9958000ffffe80f`8401ba58 ffffbf0a`d8b78010 : ffffe80f`8401bb48 ffffe80f`00000004 00000000`00000000 fffff801`800a2c01 : 0x1ffffe80f`8401ba60 ffffe80f`8401bb48 : ffffe80f`00000004 00000000`00000000 fffff801`800a2c01 ffffbf0a`d5ca3000 : 0xffffbf0a`d8b78010ffffe80f`8401ba68 ffffe80f`00000004 : 00000000`00000000 fffff801`800a2c01 ffffbf0a`d5ca3000 fffff801`00000000 : 0xffffe80f`8401bb48ffffe80f`8401ba70 00000000`00000000 : fffff801`800a2c01 ffffbf0a`d5ca3000 fffff801`00000000 ffffbf0a`f15d8000 : 0xffffe80f`00000004SYMBOL_NAME: dxgkrnl!DpiFdoHandleDevicePower+87bd0MODULE_NAME: dxgkrnlIMAGE_NAME: dxgkrnl.sysIMAGE_VERSION: 10.0.18362.900STACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: 87bd0FAILURE_BUCKET_ID: 0x113_dxgkrnl!DpiFdoHandleDevicePowerOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {d602ffad-dbab-56f7-4cf4-fd87d40aefc6}Followup: MachineOwner---------

:)

 

BSOD Help (also crashes without BSODs and dump files)

The rebooting issue I am suffering does not generate a blue screen or dump files. After doing some research, it was recommended that I try running Windows' driver reviewer to stress the drivers and potentially generate BSODs to gain some insight into what could be causing the aforementioned reboots. Once I began running reviewer, that is when I was able to create blue screens and the dump files that I attached to this post. Hopefully, they are pointing me in the right direction; however, I am a bit skeptical. Since I cannot seem to cause a reboot using cpu, ram, or gpu stress tests, I find it very difficult to pinpoint whether my problem is with hardware or software. I hope your suggestion to uninstall Panda fixes the problem, but only time will tell.

 

BSOD - No dump files are created

I forced a crash with the kayboard ctrl+2*blockscroll and it dumped...

For the records I did this: *Windows Error Reporting (WER) system service should be set to MANUAL

It was on auto, now is manual(trigger).

If I got on a BSOD "naturally" with a critical_process_died error (it's my usual bsod error) and it does not dump I'll get back here, for now is resolved.

 

Reading driver verifier crash dump

Here are the other two images:
Ill try what you suggested, thank all of you for the help so far.