Clevo P151EM1 frequent BSOD

here are the results

Code:

Use !analyze -v to get detailed debugging information.
BugCheck 4E, {99, 138c84, 0, 133884}
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
Followup:     MachineOwner
 
PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 0000000000138c84, page frame number
Arg3: 0000000000000000, current page state
Arg4: 0000000000133884, 0
Debugging Details:

Code:

Use !analyze -v to get detailed debugging information.
BugCheck D1, {108, b, 8, 108}
Probably caused by : dxgkrnl.sys ( dxgkrnl!DpiFdoDpcForIsr+2e )
Followup:     MachineOwner

Code:

Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff80002c93160, 1, 10}
Probably caused by : hardware ( nt!KeAcquireInStackQueuedSpinLock+30 )
Followup:     MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002c93160, The address that the exception occurred at
Arg3: 0000000000000001, Parameter 0 of the exception
Arg4: 0000000000000010, Parameter 1 of the exception

Please open an elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

Also, please make sure all of your Windows Updates are current and make sure your Flash and Flash plugin for Firefox are both up to date. The next time you run a You Tube Video, please disable hardware acceleration and see if that works. Go through Steam or wherever your games are installed and verify the game files.

Code:

Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c000001d, fffff80002fbf298, fffff88009222970, 0}
Probably caused by : memory_corruption
Followup:     memory_corruption

Please Run Memtest86+

   Information

Please download from this site only http://www.memtest.org/ in the middle of the page are the Download links, you can download the ISO.zip or the Auto USB Flash Drive installer.zip

Extract the Zip file. If you chose the ISO image, burn it to a CD using Windows Disk Image Burner or any Image burner you may have. If you downloaded the Auto USB installer, extract it, insert your USB 2.0 Flash Drive and take note of the drive letter. Run the installer, select the Flash Drive Letter, check the format box and press next. It will install memtest86+ to a flash drive. You can use either V4.20 or V5.01. Boot from your selected media. If you use V5.01 it will tell you to press certain buttons at the start, please press no buttons. The test will begin on it's own and continue to run until you stop it. It needs to run for 8 complete passes or until you receive an error. If you receive an error, stop the test. Even 1 error is a fail. Each pass tests a different part of the ram and each of the 10 tests in each pass tests something different. It takes a minimum of 8 passes to completely test the ram, more passes are better. It is quite a long test and will take several hours depending on how much ram you have. Due to the time length it is best to run overnight. If you have any questions, please do not hesitate to ask

We can wait if you want to. Instead run Seatools for DOS https://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html#Part3

Some of the dump files keep saying Hardware. But, that could also be a bad driver causing that.