Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Constant blue screen of death - ntoskrnl.exe and tcpip.sys


  • Please log in to reply
4 replies to this topic

#1 Thaxcis

Thaxcis

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:12:38 PM

Posted 14 January 2017 - 04:42 PM

Hi everyone! I really need some help please. I am on Windows 10 (WinBuild.160101.0800 [14986.rs_prerelease.161202-1928]) x64. This happend on previous builds too and I am getting really desperate! It usually shows ntoskrnl.exe and tcpip.sys as the cause. It happens randomly. Got BSOD during gaming and also just while on the desktop with nothing in particular running.

 

Desktop Components (bought mid 2014): Intel Core i5 4670K @ 3.40GHz, Gigabyte Z87X-UD3H (No overclocking, latest Bios version), Samsung 840 EVO 250GB, Corsair CMZ8GX3M2A1600C9 Vengeance 8GB (2x4GB) DDR3, Palit Nvidia GeForce GTX 770 OC 2GB, Corsair CX750 Builder Series CX 750W ATX/EPS 80 PLUS Bronze PSU.

 

Up to date: Graphics drivers, network drivers, Bios, bluetooth. I ran a driver updater and manually updated every out of date driver.

I tried with Wifi network adaptor disabled and then the ethernet apaptor disabled. Blue screen happened on both instances.  I also tried disabling IPv6 on my network adaptor.

Uninstalled anti-virus and Malwarebytes, same problem.

Fully ran a chkdsk, and sfc /scannow and it came up with no errors.

I closed all open programs on my taskbar and still got the problem.

Windows Memory Diagnostics showed no problems were found.

I uninstalled tons of other programs without any luck.

 

Did a stress test with Prime 95. 0 errors and 0 warnings.

Speccy: http://speccy.piriform.com/results/PzOjmlwrhz5iOJVtRjYeyKA

 

Please find attached:

  • Recent dumps
  • SysnativeFileCollectionApp
  • BSOD inspector results attached

 

Thank you!!!!

Attached Files


Edited by Thaxcis, 15 January 2017 - 06:22 AM.


BC AdBot (Login to Remove)

 


#2 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:08:38 AM

Posted 16 January 2017 - 07:58 AM

First, plesae realize that this is an Insider program build (14986)- as such it's not expected to be as stable as the release builds

I don't know if this is a Slow Ring build or if you've stopped updating to new builds.

The point here is that these BSOD's may be "normal"

 

Your UEFI/BIOS (version F9) dates from 2014.  Please check at the manufacturer's website to see if there are any UEFI/BIOS updates available for your system.  If you are able to install the update through Windows (without booting from an external drive), then go ahead and update it.  WARNING - if the computer might shut down during this procedure, please don't do it, as this may physically damage the computer and prevent it from booting.
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).

I don't know the number of Windows Update hotfixes for this version of your OS, please double check for any new Windows Updates.  It only takes one update to cause a problem, so it's essential that you have all of them.  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.

These devices are disabled in Device Manager.  Did you deliberately disable them?  If so, why did you disable them?

 

Wondershare PDF Converter    SWD\PRINTENUM\{0D27FFB4-82C5-4818-A1B6-82EAECDECA7E}    This device is disabled.
Fax    SWD\PRINTENUM\{40800B73-034C-45A0-8633-08F7D1480AF5}    This device is disabled.
WP-4525 Series(Network)    SWD\PRINTENUM\{EA2E63FB-01BE-42C2-80C2-7DBE11DFEC3E}    This device is disabled.
Amazon Fire TV Remote    BTHENUM\DEV_747548D3D9E6\7&7626623&0&BLUETOOTHDEVICE_747548D3D9E6    This device is disabled.
Qualcomm Atheros AR938x Wireless Network Adapter    PCI\VEN_168C&DEV_0030&SUBSYS_3112168C&REV_01\4&342BDB25&0&00E6    This device is disabled.
Bluetooth Device (RFCOMM Protocol TDI)    BTH\MS_RFCOMM\6&34BD33FB&0&0    This device is disabled.
Bluetooth Device (Personal Area Network)    BTH\MS_BTHPAN\6&34BD33FB&0&2    This device is disabled.

Drivers for these devices load before Windows disables them.  As such, they remain in memory and can interact with other drivers/system processes - and can even cause BSOD's

As such, if you really want to disable them:

- disable them in the BIOS/UEFI, or

- uninstall their software and physically remove them from the system.

Those that can't be dealt with this way (or can't just be uninstalled) should be re-enabled and updated to the latest, W10 compatible version(s).

This includes the devices that you wish to keep but not use.

 

The memory dumps show a lot of networking issues with a significant amount of MalwareBytes drivers being involved.
I would suggest starting by uninstalling MalwareBytes and see if that helps.  (FWIW - there have been some issues with MalwareBytes and some of the earlier Insider Builds)

 

Out of 9 memory dumps there were 5 different BSOD  (aka STOP or BugCheck) error codes.  The differing error codes are usually symptomatic of a lower level problem within the system. They are usually caused by one of these things (the list is not in any sort of order):
- borked (broken) hardware (several different procedures used to isolate the problem device)
- BIOS issues (check for updates at the motherboard manufacturer's website)
- overclocking/overheating - You'll know if you're overclocking or not. If uncertain we can suggest things to check.
- dirt/dust/hair/fur/crud inside the case.  Blow out the case/vents with canned air (DO NOT use an air compressor or vacuum as they can cause damage to the system)
- missing Windows Updates
- compatibility issues (3rd party hardware/drivers), Insider builds, older systems, or even pirated systems
- low-level driver problems
- or even malware (scanned for when we ask for hardware diagnostics from http://www.carrona.org/initdiag.html or http://www.carrona.org/hwdiag.html ).

Please get a head start on the hardware diagnostics - they are located here:  http://www.carrona.org/hwdiag.html
Please finish ALL of them and let us know the results

Finally, please notice the drivers below that were released before W10 (29 Jul 2015). 

Disregard the intelppm.sys driver as that's a common error in the insider builds

They should be updated to the latest, W10 compatible version.

If unable to update them, please post back and let us know which ones so we can suggest other things to do.

 

Analysis:
The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:
**************************Sat Jan 14 16:13:18.832 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\011417-5031-01.dmp]
Windows 10 Kernel Version 14986 MP (4 procs) Free x64
Built by: 14986.1000.amd64fre.rs_prerelease.161202-1928
System Uptime:1 days 10:54:41.870
Probably caused by :ntkrnlmp.exe ( nt!PspCatchCriticalBreak+c9 )
BugCheck EF, {ffffc00347124080, 0, 0, 0}
BugCheck Info: CRITICAL_PROCESS_DIED (ef)
Arguments:
Arg1: ffffc00347124080, 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:  WIN8_DRIVER_FAULT
FAILURE_BUCKET_ID: 0xEF_svchost.exe_BUGCHECK_CRITICAL_PROCESS_55b32080_nt!PspCatchCriticalBreak
CPUID:        "Intel® Core™ i5-4670K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
  BIOS Version                  F9
  BIOS Release Date             03/18/2014
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  Z87X-UD3H
  Baseboard Product             Z87X-UD3H-CF
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Jan 12 07:50:39.003 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\011217-5203-01.dmp]
Windows 10 Kernel Version 14986 MP (4 procs) Free x64
Built by: 14986.1000.amd64fre.rs_prerelease.161202-1928
System Uptime:0 days 3:02:36.199
*** WARNING: Unable to verify timestamp for mwac.sys
*** ERROR: Module load completed but symbols could not be loaded for mwac.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :memory_corruption
BugCheck 3B, {c0000005, fffff80ab01818a3, ffff8a011091a9c0, 0}
BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80ab01818a3, Address of the instruction which caused the bugcheck
Arg3: ffff8a011091a9c0, 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:  MBAMService.exe
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BYTE
CPUID:        "Intel® Core™ i5-4670K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
  BIOS Version                  F9
  BIOS Release Date             03/18/2014
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  Z87X-UD3H
  Baseboard Product             Z87X-UD3H-CF
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Jan 11 13:37:28.447 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\011117-5546-01.dmp]
Windows 10 Kernel Version 14986 MP (4 procs) Free x64
Built by: 14986.1000.amd64fre.rs_prerelease.161202-1928
System Uptime:0 days 1:50:12.073
*** WARNING: Unable to verify timestamp for mwac.sys
*** ERROR: Module load completed but symbols could not be loaded for mwac.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :memory_corruption
BugCheck 3B, {c0000005, fffff800a95418a3, ffffdc012e7859c0, 0}
BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800a95418a3, Address of the instruction which caused the bugcheck
Arg3: ffffdc012e7859c0, 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:  MBAMService.exe
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
CPUID:        "Intel® Core™ i5-4670K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
  BIOS Version                  F9
  BIOS Release Date             03/18/2014
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  Z87X-UD3H
  Baseboard Product             Z87X-UD3H-CF
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
The rest of the memory dump summaries are hidden in the Spoiler tag below.  Click on "Show" to reveal them.

Spoiler



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:

**************************Sat Jan 14 16:13:18.832 2017 (UTC - 5:00)**************************
intelppm.sys                                  Tue Jun 13 03:21:26 1972 (049B0476)
BthA2DP.sys                                   Sun Mar 11 15:54:14 2001 (3AABD7E6)
pwdrvio.sys                                   Mon Jun 15 21:43:45 2009 (4A36F8D1)
tap0901.sys                                   Wed Nov  5 08:16:32 2014 (545A2330)
HWiNFO64A.SYS                                 Sun Nov 23 11:24:07 2014 (54720A27)
XtuAcpiDriver.sys                             Thu Feb 26 07:51:57 2015 (54EF16ED)
gwdrv.sys                                     Fri May 29 00:15:40 2015 (5567E7EC)
 

**Windows 10 released on 29 July 2015**
 

rzpnk.sys                                     Wed Sep 16 20:16:35 2015 (55FA0663)
rzpmgrk.sys                                   Thu Sep 17 14:42:44 2015 (55FB09A4)
bcbtums.sys                                   Thu Jan 21 14:15:06 2016 (56A12E3A)
RTKVHD64.sys                                  Fri Jan 22 10:09:21 2016 (56A24621)
iaStorA.sys                                   Tue Mar  8 09:00:24 2016 (56DEDAF8)
rzendpt.sys                                   Tue Apr  5 03:09:18 2016 (5703649E)
rzudd.sys                                     Tue Apr  5 03:09:21 2016 (570364A1)
rzvkeyboard.sys                               Tue Apr  5 03:09:21 2016 (570364A1)
rzdaendpt.sys                                 Tue Apr  5 03:09:22 2016 (570364A2)
mbae64.sys                                    Fri Apr 29 06:10:09 2016 (57233301)
IntcDAud.sys                                  Tue May 10 04:08:56 2016 (57319718)
vpnpbus.sys                                   Mon Jun 13 05:06:55 2016 (575E77AF)
e1d65x64.sys                                  Tue Jul 26 12:48:21 2016 (57979455)
iqvw64e.sys                                   Tue Aug 23 21:52:09 2016 (57BCFDC9)
TeeDriverW8x64.sys                            Thu Sep 15 13:08:03 2016 (57DAD573)
cbfs6.sys                                     Wed Sep 21 08:42:02 2016 (57E2801A)
nvhda64v.sys                                  Thu Sep 29 09:25:06 2016 (57ED1632)
igdkmd64.sys                                  Thu Sep 29 10:43:27 2016 (57ED288F)
VBoxUSBMon.sys                                Tue Oct 18 09:43:09 2016 (580626ED)
VBoxNetLwf.sys                                Tue Oct 18 09:43:09 2016 (580626ED)
VBoxDrv.sys                                   Tue Oct 18 09:43:47 2016 (58062713)
MBAMSwissArmy.sys                             Wed Nov  9 09:21:05 2016 (582330D1)
MBAMChameleon.sys                             Sat Nov 19 14:13:08 2016 (5830A444)
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)
Microsoft.Bluetooth.Legacy.LEEnumerator.sys   ***** Invalid 1974 Invalid 1974 Invalid
BthHfAud.sys                                  ***** Invalid 2014 Invalid 2014 Invalid
cldflt.sys                                    ***** Invalid 1996 Invalid 1996 Invalid
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Jan 12 07:50:39.003 2017 (UTC - 5:00)**************************
mbam.sys                                      Wed Sep 28 11:45:44 2016 (57EBE5A8)
farflt.sys                                    Wed Nov  2 10:29:12 2016 (5819F838)
mwac.sys                                      Thu Nov 17 20:02:05 2016 (582E530D)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Jan 11 13:37:28.447 2017 (UTC - 5:00)**************************
gdrv.sys                                      Thu Jul  4 00:27:55 2013 (51D4F9CB)
avc3.sys                                      Thu Sep 15 08:37:35 2016 (57DA960F)
EasyAntiCheat.sys                             Wed Dec  7 04:57:38 2016 (5847DD12)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Jan 11 10:40:51.129 2017 (UTC - 5:00)**************************
RTKVHD64.sys                                  Tue Jun 16 06:55:05 2015 (55800089)
bdfwfpf.sys                                   Tue Feb  9 07:12:25 2016 (56B9D7A9)
trufos.sys                                    Wed Jun 15 05:43:22 2016 (5761233A)
avckf.sys                                     Thu Sep 15 08:46:29 2016 (57DA9825)
gzflt.sys                                     Fri Oct 28 05:28:18 2016 (58131A32)
edrsensor.sys                                 Mon Dec  5 08:25:10 2016 (58456AB6)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Jan 11 05:29:55.682 2017 (UTC - 5:00)**************************
mwac.sys                                      Tue Jun 17 22:07:00 2014 (53A0F444)
mbam.sys                                      Wed Sep  3 13:50:25 2014 (540754E1)
MBAMSwissArmy.sys                             Thu Jan  8 21:45:43 2015 (54AF40D7)
360Box64.sys                                  Mon Jun 27 06:31:59 2016 (5771009F)
360AvFlt.sys                                  Tue Jul 19 04:45:30 2016 (578DE8AA)
360FsFlt.sys                                  Fri Jul 22 04:30:45 2016 (5791D9B5)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Jan 10 12:55:10.489 2017 (UTC - 5:00)**************************
fltsrv.sys                                    Fri Feb  7 02:37:32 2014 (52F48D3C)
snapman.sys                                   Fri Feb  7 04:17:09 2014 (52F4A495)
nvvad64v.sys                                  Tue Oct  4 03:20:09 2016 (57F35829)
nvlddmkm.sys                                  Thu Dec  1 11:37:27 2016 (584051C7)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jan  9 10:15:43.170 2017 (UTC - 5:00)**************************
bcbtums.sys                                   Mon Mar 23 17:31:26 2015 (5510862E)
Smb_driver_Intel.sys                          Fri May 29 15:57:11 2015 (5568C497)
TeeDriverW8x64.sys                            Tue Jul  7 13:43:32 2015 (559C0FC4)
athw10x.sys                                   Wed May 11 22:18:32 2016 (5733E7F8)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Jan  8 18:31:08.739 2017 (UTC - 5:00)**************************
e1i63x64.sys                                  Fri Mar  4 16:46:29 2016 (56DA0235)


http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=BthA2DP.sys
http://www.carrona.org/drivers/driver.php?id=pwdrvio.sys
http://www.carrona.org/drivers/driver.php?id=tap0901.sys
http://www.carrona.org/drivers/driver.php?id=HWiNFO64A.SYS
http://www.carrona.org/drivers/driver.php?id=XtuAcpiDriver.sys
http://www.carrona.org/drivers/driver.php?id=gwdrv.sys
http://www.carrona.org/drivers/driver.php?id=rzpnk.sys
http://www.carrona.org/drivers/driver.php?id=rzpmgrk.sys
http://www.carrona.org/drivers/driver.php?id=bcbtums.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=iaStorA.sys
http://www.carrona.org/drivers/driver.php?id=rzendpt.sys
http://www.carrona.org/drivers/driver.php?id=rzudd.sys
http://www.carrona.org/drivers/driver.php?id=rzvkeyboard.sys
http://www.carrona.org/drivers/driver.php?id=rzdaendpt.sys
http://www.carrona.org/drivers/driver.php?id=mbae64.sys
http://www.carrona.org/drivers/driver.php?id=IntcDAud.sys
http://www.carrona.org/drivers/driver.php?id=vpnpbus.sys
http://www.carrona.org/drivers/driver.php?id=e1d65x64.sys
http://www.carrona.org/drivers/driver.php?id=iqvw64e.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys
cbfs6.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=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys
http://www.carrona.org/drivers/driver.php?id=VBoxUSBMon.sys
http://www.carrona.org/drivers/driver.php?id=VBoxNetLwf.sys
http://www.carrona.org/drivers/driver.php?id=VBoxDrv.sys
http://www.carrona.org/drivers/driver.php?id=MBAMSwissArmy.sys
http://www.carrona.org/drivers/driver.php?id=MBAMChameleon.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
nvvhci.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.sys
Microsoft.Bluetooth.Legacy.LEEnumerator.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=BthHfAud.sys
cldflt.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=mbam.sys
farflt.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=mwac.sys
http://www.carrona.org/drivers/driver.php?id=gdrv.sys
http://www.carrona.org/drivers/driver.php?id=avc3.sys
http://www.carrona.org/drivers/driver.php?id=EasyAntiCheat.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=bdfwfpf.sys
http://www.carrona.org/drivers/driver.php?id=trufos.sys
http://www.carrona.org/drivers/driver.php?id=avckf.sys
http://www.carrona.org/drivers/driver.php?id=gzflt.sys
edrsensor.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=mwac.sys
http://www.carrona.org/drivers/driver.php?id=mbam.sys
http://www.carrona.org/drivers/driver.php?id=MBAMSwissArmy.sys
http://www.carrona.org/drivers/driver.php?id=360Box64.sys
http://www.carrona.org/drivers/driver.php?id=360AvFlt.sys
http://www.carrona.org/drivers/driver.php?id=360FsFlt.sys
http://www.carrona.org/drivers/driver.php?id=fltsrv.sys
http://www.carrona.org/drivers/driver.php?id=snapman.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=bcbtums.sys
http://www.carrona.org/drivers/driver.php?id=Smb_driver_Intel.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys
http://www.carrona.org/drivers/driver.php?id=athw10x.sys
http://www.carrona.org/drivers/driver.php?id=e1i63x64.sys
 
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#3 Thaxcis

Thaxcis
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:12:38 PM

Posted 16 January 2017 - 08:44 AM

Wow. I am completely blown away by your detailed answer. Thank you ever so much Usasma. You are a legend!


Edited by Thaxcis, 16 January 2017 - 10:49 AM.


#4 Thaxcis

Thaxcis
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:12:38 PM

Posted 16 January 2017 - 10:48 AM

The Windows build is on the slow ring and there are currently no further windows updates. 
 
The UEFI/BIOS F9 from 2014 is the latest stable release for the motherboard. There is a F10 beta driver also released in 2014. Not to keen on installing that though as it is a beta driver. Beta bios drivers scare me. I will do this as a last resort.
 
I manually disabled the devices you mentioned in device manager. I did not know that they remain in memory. Thanks for that info. I uninstalled the drivers that I no longer need and re-enabled the rest.
 
Noted on Malwarebytes. I have installed version 3.0.5 recently. I think I had version 2.4 installed before. I will uninstall.
 
I am pretty sure there is no malware on my system. 
 
I found a surprising amount of dust in my computer. I will carefully clean it out as you instructed. 
 
intelppm.sys        (Ignored as you instructed)
BthA2DP.sys         (Could not find update. Will try remove and uninstall my bluetooth dongle if I get further BSOD)        
pwdrvio.sys        (Updated program and then uninstalled)                            
tap0901.sys        (Updated) - I have a feeling this one could have been the cause.                            
HWiNFO64A.SYS      (Updated)                           
XtuAcpiDriver.sys (Updated)                           
gwdrv.sys        (Glasswire - Updated program - will try uninstalling if I get further BSOD)                             
 
I will install the hw diagnostic tools on carrona. Fantastic website by the way!
 
I also removed the paging file on my C: (system) SSD drive and enabled a paging file on my D: (storage) 7200 RPM drive. I currently allocated 4GB there. I saw a paging file error while gaming while it was on my SSD drive. I read that paging files on SSD are bad. No idea if this can cause a BSOD.
 
Final thought: I think it may have been the tap0901.sys driver that caused my BSOD. I just now remembered that I had a BSOD after a just 1-2 minutes of torrenting with my VPN enabled (private internet acccess).
 
I will report back either way. Fingers crossed it is now solved.
 
Thanks for all the help!

Edited by Thaxcis, 16 January 2017 - 10:56 AM.


#5 Thaxcis

Thaxcis
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:12:38 PM

Posted 17 January 2017 - 01:37 PM

No more crashes! Problem solved! It was most likely the drivers in the last reply.

 

Thanks John!






1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users