No problem at all my friend, I just want to help you get back up and running and BSOD are not an exact science and require trial and error. So I've looked at the latest ones:
Code:
Bugcheck code 0000001A (Memory_Management)
Bugcheck code 0000001A (Memory_Management)
Bugcheck code 0000001A (Memory_Management)
Bugcheck code 000001c7 (STORE_DATA_STRUCTURE_CORRUPTION)
Now the last one is a bit more interesting and perhaps does shed a little bit more light. So all of these first of all can indeed be caused by faulty drivers.
However on inspection, there doesn't appear to be any
obvious third party drivers leading up to the crash, just plenty of loaded third party drivers running generally.
Code:
3ware.sys Mon May 18 23:28:03 2015 (555A6773)
ADP80XX.SYS Thu Apr 9 21:49:48 2015 (5526E5EC)
AMDPCIDev.sys Tue Mar 3 05:28:00 2020 (5E5DEAE0)
AtihdWT6.sys Mon Feb 24 20:48:15 2020 (5E54368F)
HpSAMD.sys Tue Mar 26 21:36:54 2013 (515214F6)
ItSas35i.sys Thu Jun 20 08:35:34 2019 (5D0B3746)
LGBusEnum.sys Mon Jun 13 19:47:08 2016 (575EFFAC)
LGJoyXlCore.sys Mon Jun 13 19:47:06 2016 (575EFFAA)
LGVirHid.sys Mon Jun 13 19:47:03 2016 (575EFFA7)
MegaSas2i.sys Thu Apr 4 14:28:53 2019 (5CA60695)
RTCore64.sys Thu Sep 19 11:45:31 2019 (5D835C4B)
Rt630x64.sys Fri Dec 28 00:04:06 2012 (50DCE1F6)
SiSRaid2.sys Wed Sep 24 19:28:20 2008 (48DA86C4)
SmartSAMD.sys Thu Feb 21 17:54:44 2019 (5C6EE5E4)
amdgpio2.sys Mon Sep 30 04:56:01 2019 (5D917CD1)
amdgpio3.sys Mon Mar 14 10:19:36 2016 (56E69038)
amdkmdag.sys Mon May 25 19:41:44 2020 (5ECC1168)
amdkmpfd.sys Thu Jan 16 19:05:42 2020 (5E20B406)
amdlog.sys Thu Apr 30 18:24:23 2020 (5EAB09C7)
amdsata.sys Thu May 14 13:14:52 2015 (555491BC)
amdsbs.sys Tue Dec 11 21:21:44 2012 (50C7A3E8)
amdxata.sys Fri May 1 01:55:35 2015 (5542CF07)
amdxe.sys Thu Mar 26 14:43:11 2020 (5E7CBF7F)
arcsas.sys Thu Apr 9 20:12:07 2015 (5526CF07)
bxvbda.sys Wed May 25 08:03:08 2016 (57454E2C)
cht4sx64.sys Tue Feb 5 13:51:31 2019 (5C5994E3)
evbda.sys Wed May 25 08:01:05 2016 (57454DB1)
iaStorAVC.sys Thu Sep 5 13:07:32 2019 (5D70FA84)
iaStorV.sys Mon Apr 11 19:48:16 2011 (4DA34CF0)
ladfGSS.sys Fri Dec 9 02:38:49 2016 (584A1939)
lgcoretemp.sys Tue Jun 9 17:52:10 2015 (557719BA)
lsi_sas.sys Wed Mar 25 19:36:48 2015 (55130E50)
lsi_sas2i.sys Wed Aug 2 14:29:59 2017 (5981D3D7)
lsi_sas3i.sys Thu Apr 4 07:54:35 2019 (5CA5AA2B)
lsi_sss.sys Fri Mar 15 23:39:38 2013 (5143B13A)
megasas.sys Thu Mar 5 02:36:29 2015 (54F7C12D)
megasas35i.sys Thu Jun 20 11:01:12 2019 (5D0B5968)
megasr.sys Mon Jun 3 23:02:39 2013 (51AD127F)
mvumis.sys Fri May 23 21:39:04 2014 (537FB1E8)
nvraid.sys Mon Apr 21 19:28:42 2014 (5355635A)
nvstor.sys Mon Apr 21 19:34:03 2014 (5355649B)
percsas2i.sys Tue Mar 15 00:50:11 2016 (56E75C43)
percsas3i.sys Fri Jun 1 22:47:02 2018 (5B11BED6)
rt640x64.sys Mon Nov 18 09:14:08 2019 (5DD260E0)
rtwlane.sys Tue Jan 6 03:52:41 2015 (54AB5C09)
sisraid4.sys Wed Oct 1 22:56:04 2008 (48E3F1F4)
stexstor.sys Tue Nov 27 00:02:51 2012 (50B4032B)
t_mouse.sys Mon Dec 3 06:19:30 2012 (50BC4472)
tapwindscribe0901.sys Thu Mar 16 21:37:54 2017 (58CB05B2)
vsmraid.sys Tue Apr 22 20:21:41 2014 (5356C145)
vstxraid.sys Mon Jan 21 19:00:28 2013 (50FD904C)
There does also seem to be a few references to hardware issues. Whilst these don't immediately mean it's hardware, it could be correct:
Code:
MODULE_NAME: hardware
IMAGE_NAME: memory_corruption
However the last bugcheck is usually caused by 3 things:
- Defective RAM.
- A driver misbehaving.
- Corruption from hardware or firmware.
Purely based off the fact that nothing OBVIOUS is coming out through 3rd party drivers, and that it is fairly easy to test, I would test your RAM as per this guide:
https://www.sysnative.com/forums/threads/test-ram-with-passmark-memtest86.24300/
There is still possibility of this being driver based, but I think the above is the best and easiest next step, do you know if you were able to revert all driver downloads made by your app? It could have residual conflciting ones leftover. It's why it's recommended to perform system restores before bulk updating drivers through apps.