You've attached three (3) dump files, the most recent of which is semi-worthless because of the way the crash occurred.
The other two are not particularly definitive. One suggesting memory corruption and the other a problem with iaStorA.sys
I think the first thing that I would do is ......
Uninstall AVG. Use the programs and features applet in Control Panel and then follow that up with the vendor specific, proprietary removal tool from here
http://www.avg.com/us-en/utilities
Reboot and make sure that the native Defender product and Firewall are enabled and leave it like that for a while to see if the machine seems to be more stable.
I see you updated your BIOS very recently (since yesterday). You may want to go back to the ASRock download page and re-install your Chipset Driver (INF) as well as the Intel Mgmt Engine driver.
Additionally sort through this list of older drivers
snapman.sys 10/6/2006 (like this one, looks to be a remnant from a very old version of Acronis True Image)
ArvoFltr.sys 5/6/2009 (etc., etc., etc., OLD Roccat keyboard driver)
pwdrvio.sys 6/15/2009 7
WmVirHid.sys 4/27/2010
WmXlCore.sys 4/27/2010
WmBEnum.sys 4/27/2010
SiLib.sys 7/15/2010
SiUSBXp.sys 7/15/2010
AsrAppCharger.sys 5/10/2011
mi2c.sys 6/29/2011
FNETURPX.SYS 5/30/2012
AsrVDrive.sys 10/1/2012
sthid.sys 2/18/2013
AsrRamDisk.sys 5/9/2013
vmci.sys 5/17/2013
LGSHidFilt.Sys 5/30/2013
You may want to pay particular attention to the three beginning with Asr (some older motherboard utilities seem to just cause problems with Windows 10)
Use Google to identify the individual driver files and see if....
1. You still need them, if not get rid of them.... uninstall or break them.
2. If there are updates available that might be more likely to work with Windows 10 64bit.
If BSODs continue attach dump files to your next post.
BugCheck 3B, {c0000005, fffff8014e6df0ff, ffffd00022725cb0, 0}
Probably caused by : memory_corruption ( nt!MiCaptureProtectionFromProto+f )
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff8014e6df0ff, Address of the instruction which caused the bugcheck
Arg3: ffffd00022725cb0, Address of the context record for the exception that caused the bugcheck
PROCESS_NAME: avgnsa.exe
STACK_TEXT:
ffffd000`227266d0 fffff801`4e64357a : 00000000`00000400 00000000`00000001 00000000`00000000 ffffe000`63836d40 : nt!MiCaptureProtectionFromProto+0xf
ffffd000`22726700 fffff801`4e64279f : 00000000`00000080 00000000`00000080 00000000`00000080 00000000`00000003 : nt!MiGetPageProtection+0x1da
ffffd000`22726750 fffff801`4e9ddb55 : 00000000`00000000 ffffd000`227268d0 ffffe000`00000001 00000000`00000000 : nt!MiCommitExistingVad+0x70f
ffffd000`22726860 fffff801`4e9dd7f0 : 00000032`990fb370 00007ff8`6f7e1268 00000032`990ff4c8 00000000`00000000 : nt!MiAllocateVirtualMemory+0x355
ffffd000`22726a30 fffff801`4e759fa3 : ffffd000`22726b10 00000000`00000000 00000000`00000000 00000032`990ff400 : nt!NtAllocateVirtualMemory+0x40
ffffd000`22726a90 00007ff8`84ca50e4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000032`990fa008 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`84ca50e4
IF that C:\ drive is an SSD..... see if there is a Firmware Update available for it.
IF not... run Check Disk on it.
When you have some time on your hands you may also want to test the system memory.
http://www.memtest.org/
Grab the ISO, burn it to a CD (ImgBurn works good for this) and boot your computer.
Let it run 6 passes or so and see if it finds any errors.
If it starts pitching errors right away, stop it and test individual sticks in individual slots to see if you can determine where the problem lies.