Frequent and random appearing BSOD 'internal power error'.

Hereby the result of step 5 and 6 for Model WDC WD10

D drive
Attachment 163991
Attachment 163992

E drive
Attachment 163993
Attachment 163994

And hereby the result of step 5 and 6 for Model Samsung SSD 850 EVO 500GB.
(in windows10, this is my boot C-drive)

I did this in "full" command prompt mode [started win10 in command prompt mode], because when I tried it in a command prompt window within win10, I got the error that it could not get exclusive rights to this drive. I hope this is OK.

In "full" command prompt mode, the Model Samsung SSD 850 EVO apparently got drive letter E.

Attachment 163996

Now, I will continu to step 7.
Please let me know in case I did something wrong in steps 1 through 6.

Open disk management > expand each volume and health columns so the contents in the rows is in full view > post an image into the thread.
The chkdsk reports above display d drive followed by e drive followed by another e drive.
How did e drive become c drive?
Download and install minitool partition wizard (free non-trial edition) and post an image into the thread:
MiniTool Partition Wizard | Best partition magic alternative for Windows PC and Server

I do not know why the drive letter was different when I started win10 in command prompt mode.

Here are the screenshots you requested:
disk management:
Attachment 164018

minitool partition wizard
Attachment 164019

There were corrections made on the C: drive in the volume bitmap (Samsung SSD 850 EVO 500GB)
The other drives had some cleaning.

Please post a new zip today and whenever there is a new BSOD:
BSOD - Posting Instructions - Windows 10 Forums

See post #8 step #9:
Post the HD Tune results for each drive when available:
Images for each:
Health
Full error scan
Benchmark

I first did step 7:
I downloaded avastclear with the link provided. According to the instruction on the avast site, I rebooted in safe mode and started avastclear.exe

However:
After login, I got this [system error] message:
Attachment 164133

Then I starten avastclear and received these 2 error messages:
Attachment 164135

As this didn't work, I rebooted normally, and uninstalled avast the normal way with "add/remove programms".

AV products often leave residual software that requires the use of the manufacturers uninstall software.
Please use the Avast contact us link to get help with the Avast error messages so that there is no residual software.
Official Avast Support | Contact Form
If there are no further BSOD after 2 weeks of computer stability you could reinstall Avast.
If there are recurrent BSOD then you will need to uninstall Avast and find an alternative AV.
If there are no recurrent BSOD then you can continue using Avast.
Having sufficient time (2 weeks) to evaluate the computer stability/instability is important so that there are few confounding factors.

And here the zip of today (I ran dm_log_collector just after uninstalling avast)

Open device manager > click view > show hidden devices > expand storage controllers > look for AMD storage controller driver > right click then left click properties > click details tab > under the property drop down > click hardware ids > post an image into the thread

amdxata.sys

AMD storage controller driver - usually from the Windows 7 DVD

Windows Update

Code:

amdxata	amdxata	c:\windows\system32\drivers\amdxata.sys	Kernel Driver	Yes	Boot	Running	OK	Normal	No	Yes