OK.... I wouldn't worry too much about it then right now.
IF the problem (BSOD) was actually being caused by the
iaStorA.sys
I would expect it to have been called out in the original stack which it was not.
Something like this
Which AGAIN it was not. I only mentioned it because it was briefly mentioned in a stack unwind I did searching for more detail about your BSOD.
AND
It is a storage "controller" driver / software package and not a driver specific to any particular hard disk / SSD.
As for the DCOM event viewer messages....
One of our staff members wrote extensively about it here
https://www.windows10forums.com/articles/event-id-10016-distributedcom.47/
IF you want to pursue it you can follow his instructions.
I actually went through all the steps and it successfully resolved the issue, but.....
Subsequently a Windows 10 upgrade (which happens about every 6 months or so now) brought those same errors back again.
Now..... I just ignore them.
I'm thinking about ignoring the DCOM errors, but the Perflib and AppReadiness and Kernel-EventTracing are something which I'm unfamiliar with.