BSOD After Playing 10 hours of Youtube. Random restarts.

Al 3 dumpfiles from 15 april mention memory corruption

Code:

 BugCheck 1A, {3f, 2dbea, 6e4828b, 6a4828b}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 000000000000003f, The subtype of the bugcheck.
Arg2: 000000000002dbea
Arg3: 0000000006e4828b
Arg4: 0000000006a4828b
BugCheck 50, {ffffc8004c9b0470, 2, fffff8037c43e354, 2}


Could not read faulting driver name
Probably caused by : memory_corruption

Followup: memory_corruption
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
MEMORY_CORRUPTOR:  ONE_BIT

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT

BugCheck BE, {fffff00006646d88, 8000000000600121, ffff9b004fbcb730, a}

Probably caused by : memory_corruption ( nt!MiRaisedIrqlFault+122 )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
An attempt was made to write to readonly memory.  The guilty driver is on the
stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.

I suspect there are problems with your memory modules, do you have different modules inserted?
It could possible also be a faulty driver.

But i advice you to start with testing your memory.
Please start with diagnosing the system RAM first. You can use the free tool "Memtest86+" to stress test the RAM.

How to run "Memtest"
MemTest86+ - Test RAM - Windows 10 BSOD Tutorials
Make sure you are using the latest version 5.01 - Memtest86+ - Advanced Memory Diagnostic Tool

You can stop the test even if a single error is found during the test. Otherwise continue the test for 8-10 passes and post a screenshot with next reply. 8 passes is the recommended bare minimum but more passes will give better result.

Also see if you can update these older drivers for your system
AtihdWT6 Wed Jul 08 03:28:10 2015 (559C7CAA)
atikmdag Wed Nov 04 22:39:32 2015 (563A7B14)
atikmpag Wed Nov 04 22:16:43 2015
ATI video and audio drivers

HECIx64 Thu Sep 17 21:54:16 2009
Driver Description: Intel Management Engine Interface
Driver Update Site: Drivers & Software

RTKVHD64 Tue Jun 16 12:55:05 2015
Driver Description: Realtek High Definition Audio Function Driver
Driver Update Site: Realtek

edit:
I see you have a legacy Radeon HD 5700 Videocard, so i suspect you have already installed the latest ATI drivers.

Noticed that several of the dumps occurred right after Intel(R) Management Engine Interface driver has started successfully.
Looking at that driver, it's very old: 9/18/2009 3:54:16 AM C:\WINDOWS\system32\drivers\HECIx64.sys 4,096

Try updating to the most recent: Download Intel® Management Engine Driver (1.5M) for Windows® 10 for Intel® NUC D54250WYK/B and D34010WYK/B