I agree with bwv848's advice. Please uninstall Avast while we're testing and use Windows Defender.
Your UEFI/BIOS (version E16JBIMS.108) dates from 2016. Please check at the manufacturer's website to see if there are any UEFI/BIOS updates available for your system. This is just in case there has been a more recent update.
FYI - W8 and W10 communicate more with the UEFI/BIOS than previous versions of Windows, so it's important to ensure that the UEFI/BIOS is kept up to date (and that outdated UEFI/BIOS' may be the cause of some compatibility issues).
Only 5 Windows Update hotfixes installed. Most build 14393 (1607) systems have more than this. Please visit Windows Update and get ALL available Windows Updates.
The actual number is not important. Rather it's important that you checked manually, installed any available updates, and didn't experience any errors when checking or updating.
Please uninstall the MSI Dragon Center. It's driver (NTIOLib_X64.sys) is known to cause BSOD's on some Windows systems.
You have a Rainbow Tech/SafeNet USB Security Device and it's driver ( ) dates from 2008.
It's likely not compatible w/W10. I would suggest uninstalling it's software and physically removing the device from your system.
If you're able to get updated drivers that are W10 compatible - feel free to keep using it. BUT the older driver MUST be removed!
I suspect a hardware issue, but there's not enough in the way of memory dumps to verify my suspicions (It usually takes 4 or 5 memory dumps to see the lack of a pattern in the BSOD error codes).
The 2 things that make me think this are:
- out of 3 memory dumps, there's 3 different BSOD error codes (if this pattern persists in the next couple of memory dumps, then I would firmly suspect hardware problems).
- the Fault Bucket of MEMORY_CORRUPTION_LARGE often is suggestive of a hardware problem
That being said, I'd think that there's enough here to suggest that you start these free hardware diagnostics: http://www.carrona.org.
Please finish ALL of the tests, and let us know the results.
In the event that ALL of the hardware diagnostics pass, please run Driver Verifier according to these directions: http://www.carrona.org/verifier.html
Analysis:
The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:
[**************************Fri Jan 20 11:57:57.571 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\012017-39828-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.693.amd64fre.rs1_release.161220-1747
System Uptime:1 days 21:03:42.284
*** WARNING: Unable to verify timestamp for win32kfull.sys
*** ERROR: Module load completed but symbols could not be loaded for win32kfull.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
*** WARNING: Unable to verify checksum for cdd.dll
*** ERROR: Module load completed but symbols could not be loaded for cdd.dll
Probably caused by :memory_corruption
BugCheck 3B, {c0000005, fffff803a0ec705d, ffff86008d088d10, 0}
BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff803a0ec705d, Address of the instruction which caused the bugcheck
Arg3: ffff86008d088d10, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR: 0x3B
DEFAULT_BUCKET_ID: CODE_CORRUPTION
PROCESS_NAME: explorer.exe
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
CPUID: "Intel® Core i7-6700HQ CPU @ 2.60GHz"
MaxSpeed: 2600
CurrentSpeed: 2592
BIOS Version E16JBIMS.108
BIOS Release Date 12/02/2016
Manufacturer Micro-Star International Co., Ltd.
Product Name GP62MVR 6RF
Baseboard Product MS-16JB
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jan 16 09:38:38.050 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\011617-28234-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.693.amd64fre.rs1_release.161220-1747
System Uptime:0 days 1:04:41.447
Probably caused by :memory_corruption
BugCheck EF, {ffff80048a1c4780, 0, 0, 0}
BugCheck Info: CRITICAL_PROCESS_DIED (ef)
Arguments:
Arg1: ffff80048a1c4780, Process object or thread object
Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.
Arg3: 0000000000000000
Arg4: 0000000000000000
PROCESS_NAME: svchost.exe
BUGCHECK_STR: 0xEF
DEFAULT_BUCKET_ID: CODE_CORRUPTION
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jan 16 08:09:02.575 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\011617-28109-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.693.amd64fre.rs1_release.161220-1747
System Uptime:2 days 22:14:43.290
*** WARNING: Unable to verify timestamp for aswSnx.sys
*** ERROR: Module load completed but symbols could not be loaded for aswSnx.sys
Probably caused by :memory_corruption
BugCheck A, {10000001f, 2, 0, fffff80387300104}
BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a)
Arguments:
Arg1: 000000010000001f, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80387300104, address which referenced memory
BUGCHECK_STR: AV
DEFAULT_BUCKET_ID: CODE_CORRUPTION
PROCESS_NAME: instup.exe
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
3rd Party Drivers:
The following is for information purposes only. My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft. You can find links to the driver information and where to update the drivers in the section after the code box:
**************************Fri Jan 20 11:57:57.571 2017 (UTC - 5:00)**************************
Sentinel64.sys Mon Jun 2 02:14:55 2008 (48438FDF)
winio64.sys Fri Jun 4 00:08:03 2010 (4C087C23)
iaStorA.sys Tue Sep 15 03:35:15 2015 (55F7CA33)
WtfEngineDrv.sys Mon Sep 21 10:31:10 2015 (560014AE)
iwdbus.sys Thu Nov 5 18:10:07 2015 (563BE1CF)
e2xw10x64.sys Tue Jan 26 18:58:16 2016 (56A80818)
TeeDriverW8x64.sys Wed Feb 3 17:41:13 2016 (56B28209)
bwcW10x64.sys Tue Feb 9 13:23:57 2016 (56BA2EBD)
Netwtw04.sys Thu Feb 25 13:26:53 2016 (56CF476D)
asmtxhci.sys Mon Apr 11 02:15:42 2016 (570B410E)
asmthub3.sys Mon Apr 11 02:16:03 2016 (570B4123)
NTIOLib_X64.sys Tue Apr 12 03:04:16 2016 (570C9DF0)
mbae64.sys Fri Apr 29 06:10:09 2016 (57233301)
intelppm.sys Fri Jul 15 22:10:43 2016 (578997A3)
RTKVHD64.sys Tue Jul 26 08:19:23 2016 (5797554B)
aswRvrt.sys Thu Aug 18 10:12:01 2016 (57B5C231)
aswRdr2.sys Thu Aug 18 10:12:58 2016 (57B5C26A)
aswMonFlt.sys Thu Aug 18 10:30:14 2016 (57B5C676)
aswStm.sys Thu Aug 18 10:36:29 2016 (57B5C7ED)
ibtusb.sys Fri Sep 2 15:37:28 2016 (57C9D4F8)
aswSnx.sys Mon Sep 12 08:37:08 2016 (57D6A174)
aswSP.sys Mon Sep 12 08:59:01 2016 (57D6A695)
nvhda64v.sys Thu Sep 29 09:25:06 2016 (57ED1632)
aswVmm.sys Thu Oct 6 05:26:20 2016 (57F618BC)
igdkmd64.sys Fri Oct 7 17:58:09 2016 (57F81A71)
MBAMSwissArmy.sys Wed Nov 9 09:21:05 2016 (582330D1)
MBAMChameleon.sys Sat Nov 19 14:13:08 2016 (5830A444)
SynTP.sys Mon Nov 28 18:35:45 2016 (583CBF51)
Smb_driver_Intel.sys Mon Nov 28 18:36:35 2016 (583CBF83)
nvlddmkm.sys Sun Dec 11 13:13:24 2016 (584D9744)
nvvhci.sys Thu Dec 15 04:29:03 2016 (5852625F)
nvvad64v.sys Mon Dec 19 00:50:05 2016 (5857750D)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jan 16 09:38:38.050 2017 (UTC - 5:00)**************************
SNTUSB64.SYS Mon Dec 10 04:10:28 2012 (50C5A704)
nvhda64v.sys Tue May 10 04:59:01 2016 (5731A2D5)
nvlddmkm.sys Mon Aug 1 08:00:42 2016 (579F39EA)
nvvad64v.sys Fri Nov 25 10:43:56 2016 (58385C3C)
http://www.carrona.org/drivers/driver.php?id=Sentinel64.syshttp://www.carrona.org/drivers/driver.php?id=winio64.syshttp://www.carrona.org/drivers/driver.php?id=iaStorA.sysWtfEngineDrv.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.http://www.carrona.org/drivers/driver.php?id=iwdbus.syse2xw10x64.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.syshttp://www.carrona.org/drivers/driver.php?id=bwcW10x64.sysNetwtw04.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.http://www.carrona.org/drivers/driver.php?id=asmtxhci.syshttp://www.carrona.org/drivers/driver.php?id=asmthub3.syshttp://www.carrona.org/drivers/driver.php?id=NTIOLib_X64.syshttp://www.carrona.org/drivers/driver.php?id=mbae64.syshttp://www.carrona.org/drivers/driver.php?id=intelppm.syshttp://www.carrona.org/drivers/driver.php?id=RTKVHD64.syshttp://www.carrona.org/drivers/driver.php?id=aswRvrt.syshttp://www.carrona.org/drivers/driver.php?id=aswRdr2.syshttp://www.carrona.org/drivers/driver.php?id=aswMonFlt.syshttp://www.carrona.org/drivers/driver.php?id=aswStm.syshttp://www.carrona.org/drivers/driver.php?id=ibtusb.syshttp://www.carrona.org/drivers/driver.php?id=aswSnx.syshttp://www.carrona.org/drivers/driver.php?id=aswSP.syshttp://www.carrona.org/drivers/driver.php?id=nvhda64v.syshttp://www.carrona.org/drivers/driver.php?id=aswVmm.syshttp://www.carrona.org/drivers/driver.php?id=igdkmd64.syshttp://www.carrona.org/drivers/driver.php?id=MBAMSwissArmy.syshttp://www.carrona.org/drivers/driver.php?id=MBAMChameleon.syshttp://www.carrona.org/drivers/driver.php?id=SynTP.syshttp://www.carrona.org/drivers/driver.php?id=Smb_driver_Intel.syshttp://www.carrona.org/drivers/driver.php?id=nvlddmkm.sysnvvhci.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.http://www.carrona.org/drivers/driver.php?id=nvvad64v.syshttp://www.carrona.org/drivers/driver.php?id=SNTUSB64.SYShttp://www.carrona.org/drivers/driver.php?id=nvhda64v.syshttp://www.carrona.org/drivers/driver.php?id=nvlddmkm.syshttp://www.carrona.org/drivers/driver.php?id=nvvad64v.sys