Welcome to PCHF vande096,
Stop any overclocking asap, the best way to do this is by restoring the MBs default factory settings in the BIOS.
We are going to have to do a bit of work here by the looks of things so the following for your information first.
Speccy info first;
Windows 10 Home 64-bit
Computer type: Desktop
Installation Date: 12/20/2018 8:39:46 PM
After clean installing Windows, did you then install the drivers for the MB and starting with the chipset drivers first.
Power Profile
Active power scheme: Ultimate Performance
This is a form of overclocking that is known to cause overheating which in turn leads to instability, change the setting to Balanced in the Windows Power Plan.
Scheduler
12/23/2018 10:12 PM;:
AvastUpdateTaskMachineUA
12/23/2018 10:17 PM;:
GoogleUpdateTaskMachineUA
12/24/2018 2:17 AM;: GoogleUpdateTaskMachineCore
12/24/2018 3:12 AM;:
AvastUpdateTaskMachineCore
12/24/2018 10:11 AM;: IUM-F1E24CA0-B63E-4F13-A9E3-4ADE3BFF3473
12/24/2018 4:29 PM;: IntelSURQC-Upgrade-86621605-2a0b-4128-8ffc-15514c247132
12/24/2018 7:15 PM;: OneDrive Standalone Update Task-S-1-5-21-457641620-3306163222-536632250-1001
AsrAPPShop
CCleanerSkipUAC
Driver Booster Scheduler
Driver Booster SkipUAC (Ryan)
IntelSURQC-Upgrade-86621605-2a0b-4128-8ffc-15514c247132-Logon
MSIAfterburner
Avast.
Windows 8, 8.1 and 10 come with an improved Windows Defender, it offers the same real-time anti-virus/anti-malware protection as Microsoft Security Essentials. Windows Defender also shares the same malware signature definitions as Microsoft Security Essentials, and Forefront Endpoint Protection. Technically, Microsoft Security Essentials has not been renamed Windows Defender, or combined with it in Windows 8, 8.1 and 10.
Having more than one AV installed on your computer is bad, it will slow down the computer, cause internet connection problems and leave you with no AV protection at all if they cancel each other out as they fight for resources.
If any AV product that you have is a paid for version you should always make sure that you have a copy of the product key kept somewhere safe just in case you ever wish to reinstall it.
Avast clean removal info
here
Driver Booster.
Nothing should be allowed to search for and/or install updates on a computer, it is one sure fire way of you ending up with issues, some companies are worse than others but fwiw you will not find any reputable tech or tech forum recommend the use of anything from this company.
Once Windows has been installed, you install the necessary drivers for the MB and other hardware and then leave well alone, drivers should not be allowed to auto update and you should never update any driver/s unless the new drivers are intended to resolve a specific issue that you are having, installing the new drivers can actually cause you the very issues that they are intended to resolve and uninstalling the new drivers may not resolve the problem/s.
CCleaner, Google Updater,
IntelSURQC-Upgrade and MSI Afterburner.
As above regarding them not being allowed to auto update but in addition something that is flagged up in your crash dmp necessitates the mention of them, the info below in red are what are shown to have caused the issue/s, I say issues because we can see at least two,
watchdog!WdLogEvent5_WdCriticalError+0xdb and dxgmms2!VidSchiWorkerThread+0xca, the first can be both CPU and GPU related, overclocking could trigger this, the second issue is self explanatory in that it is related to DirectX, there are only a couple of drivers that are failing to load according to your crash dmp one of them being specifically related to your GPU, this driver is nvlddmkm.sys, more significantly is the driver WinRing0x64. which if I was able to count it correctly failed to load 44 times, there is little to no information on this driver but what there is names both Google and Intel by name, se DRT info here
DDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
MODULE_NAME: dxgmms2
FAULTING_MODULE: fffff8001b49b000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 0
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x119
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff800317440db to fffff8001b64cb40
STACK_TEXT:
ffffc102`0e39f778 fffff800`317440db : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffffc102`0e39f860 : nt+0x1b1b40
ffffc102`0e39f780 fffff800`342cb3e8 : 00000000`00000000 ffffd989`f0dd4000 ffffc102`0e39f8c0 ffffd989`f0dd4000 : watchdog!WdLogEvent5_WdCriticalError+0xdb
ffffc102`0e39f7c0 fffff800`3432594d : ffffd989`00000000 ffffd989`f0dd6bd0 ffffd989`f59e2000 ffffd989`f67d6050 : dxgmms2!VidSchiSendToExecutionQueue+0x15578
ffffc102`0e39f900 fffff800`34335285 : ffffd989`f67d6050 ffffd989`f338e010 00000000`00000000 ffffd989`f338e010 : dxgmms2!VidSchiSubmitPagingCommand+0x2ed
ffffc102`0e39fa80 fffff800`343350fa : ffffd989`f59e2400 fffff800`34335030 ffffd989`f59e2000 00000000`00000000 : dxgmms2!VidSchiRun_PriorityTable+0x175
ffffc102`0e39fad0 fffff800`1b52a625 : ffffd989`f4a5d040 fffff800`00000001 ffffd989`f59e2000 ffffd989`f46ee000 : dxgmms2!VidSchiWorkerThread+0xca
ffffc102`0e39fb10 ffffd989`f4a5d040 : fffff800`00000001 ffffd989`f59e2000 ffffd989`f46ee000 ffffc680`00000001 : nt+0x8f625
ffffc102`0e39fb18 fffff800`00000001 : ffffd989`f59e2000 ffffd989`f46ee000 ffffc680`00000001 00000000`00000000 : 0xffffd989`f4a5d040
ffffc102`0e39fb20 ffffd989`f59e2000 : ffffd989`f46ee000 ffffc680`00000001 00000000`00000000 00000000`00000002 : 0xfffff800`00000001
ffffc102`0e39fb28 ffffd989`f46ee000 : ffffc680`00000001 00000000`00000000 00000000`00000002 00000000`00000001 : 0xffffd989`f59e2000
ffffc102`0e39fb30 ffffc680`00000001 : 00000000`00000000 00000000`00000002 00000000`00000001 ffffc680`c8989100 : 0xffffd989`f46ee000
ffffc102`0e39fb38 00000000`00000000 : 00000000`00000002 00000000`00000001 ffffc680`c8989100 fffff800`1b653f9c : 0xffffc680`00000001
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgmms2!VidSchiSendToExecutionQueue+15578
fffff800`342cb3e8 0f1f440000 nop dword ptr [rax+rax]
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: dxgmms2!VidSchiSendToExecutionQueue+15578
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: dxgmms2.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
The C: partition where Windows is located, don`t let it go below 24% or you risk Windows becoming corrupt;
Partition 1
Partition ID: Disk #1, Partition #1
Disk Letter: C:
File System: NTFS
Volume Serial Number: 6628A845
Size: 222 GB
Used Space: 170 GB (76%)
Free Space: 52 GB (24%)
For Windows to be able to run efficiently and to be able to update you need to have between 20 and 25% of the partition or drive available as free storage space at all times, if you don`t you risk Windows becoming corrupt or not being able to update which puts you at risk of malware attack.
Data only storage devices should not be allowed to get any lower than 10% of free storage space of the full capacity of the drive/partition on the drive.
