Windows 10: BSOD using Google Chrome Browser 64bit 60.0.3112.24 Beta

There are multiple third party software companies that have drivers. Some use Driveeasy and commented that they offer one free driver. I've not yet used them.

If you have no more bsod then you can address the problem if they reoccur. You've got a good understanding how to address the problems if the reoccur.

Please post another bsod zip file and we can look at the event logs to see if there is anything important to fix.

 

The thing is I have things that no other third party company has including the webcam driver for example since it only ships with the system and even ASUS can no longer provide it.
Anyways, just a update as I will be doing a reboot after I finish typing this message.
But this is what happened.
Before I rebooted, I did the chkdsk c: /x /f /r which produced the following:

C:\WINDOWS\system32>chkdsk c: /x /f /r
The type of the file system is NTFS.
Cannot lock current drive.
Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N) y

This volume will be checked the next time the system restarts.

C:\WINDOWS\system32>

At this point, I uninstalled the Intel Wireless driver package and rebooted.
I see "To skip disk checking, press any key within 8 seconds" and then I see the spinning circle for about 10 seconds, then it went straight into the Windows Welcome logon screen.
At this point, I login and check event viewer in the Windows Logs -> Application but there is nothing from the source "Wininit", unless I am looking in the wrong place.
At this point, I came back to this thread to write down the "chkdsk c: /x /f /r" on paper after I did

C:\WINDOWS\system32>chkdsk c: /x /f /r
The type of the file system is NTFS.

Cannot lock current drive.
Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N) y

This volume will be checked the next time the system restarts.

C:\WINDOWS\system32>

I installed the Intel WiFi driver package and rebooted.

This time, I see "To skip disk checking, press any key within 8 seconds" and then I see the spinning circle for about 10 seconds, followed by "Scanning and repairing drive C:" with the WIndows logo above it. After 30 minutes, it was still at 10% so I decided to do something else and stepped away from the computer for an hour or so. Somehow writing down that chkdsk command on paper made windows do it's thing.

When I came back, it was already on the Windows Welcome logon screen so I logged on and check event viewer,
in the Windows Logs -> Application but there is nothing from the source "Wininit", unless I am looking in the wrong place.

At this point, I get a window from "Security and Maintenance" that says "Restart your PC to repair drive errors" so I click on restart now and it said Repairing drive and it can take up to an hour except I took a few minute break and the system restarted windows started booting for 1/2 a second and then it BSOD saying NTFS File System so I powered down by holding down the power button and then turned the system on again, this time within 1/2 a second, it BSOD saying NTFS File System so I powered down by holding down the power button and then turned the system on again and Windows automatically ran Automatic System Repair and then I chose the one saying problems with Starting up. It did the Repairing Disk errors and then back to the Windows Welcome Login screen.

I logged on and check event viewer, in the Windows Logs -> Application but there is nothing from the source "Wininit", unless I am looking in the wrong place.

I used the tool to try to generate the BSOD logs except I noticed the latest minidumps was June 15, 2017 as seen below so I aborted the process:

C:\WINDOWS\system32>dir c:\windows\minidump
Volume in drive C is OS
Volume Serial Number is 2484-EBDD
Directory of c:\windows\minidump
06/15/2017 11:11 PM <DIR> .
06/15/2017 11:11 PM <DIR> ..
06/10/2017 03:39 PM 346,499 061017-16968-01.dmp
06/14/2017 04:05 AM 307,643 061417-18859-01.dmp
06/14/2017 08:47 AM 308,283 061417-19437-01.dmp
06/14/2017 06:16 AM 309,691 061417-20703-01.dmp
06/15/2017 12:13 PM 308,411 061517-17250-01.dmp
06/15/2017 07:30 AM 310,843 061517-19031-01.dmp
06/15/2017 11:11 PM 319,099 061517-19921-01.dmp
7 File(s) 2,210,469 bytes 2 Dir(s) 1,544,694,919,168 bytes free

C:\WINDOWS\system32>

So right now, I did the following with the respective output just to see if there are any issues:

Running sfc /scannow 3 times
C:\WINDOWS\system32>sfc /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\WINDOWS\system32>sfc /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection did not find any integrity violations.

C:\WINDOWS\system32>sfc /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection did not find any integrity violations.
C:\WINDOWS\system32>

C:\WINDOWS\system32>dism /online /cleanup-image /checkhealth
Deployment Image Servicing and Management tool
Version: 10.0.15063.0
Image Version: 10.0.15063.0
No component store corruption detected.
The operation completed successfully.

C:\WINDOWS\system32>dism /online /cleanup-image /scanhealth
Deployment Image Servicing and Management tool
Version: 10.0.15063.0
Image Version: 10.0.15063.0[==========================100.0%==========================]
No component store corruption detected.
The operation completed successfully.

C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth
Deployment Image Servicing and Management tool
Version: 10.0.15063.0
Image Version: 10.0.15063.0[==========================100.0%==========================]
The restore operation completed successfully.
The operation completed successfully.
C:\WINDOWS\system32>

Hopefully there is a way to find out what files were corrupted as part of the drive repair process so I can replace them if they are not Windows OS files.

I'm going to reboot to see if the following actually runs chkdsk again at boot:

C:\WINDOWS\system32>chkdsk c: /x /f /r
The type of the file system is NTFS.Cannot lock current drive.
Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N) y

This volume will be checked the next time the system restarts.

C:\WINDOWS\system32>

 

I rebooted the system yesterday after the last edit of the previous reply and this is what happened:

This time, I see "To skip disk checking, press any key within 8 seconds" and then I see the spinning circle for about 10 seconds, followed by "Scanning and repairing drive C:" with the WIndows logo above it. After 30 minutes, it was still at 10% so I actually went and did something else in the house.

When I came back, it was already on the Windows Welcome logon screen so I logged on and check event viewer,
in the Windows Logs -> Application and this time, there is one event from the source "Wininit" so it seems like both the chkdsk running at startup and the "Wininit" logging when chkdsk is run is waking up from the dead slowly on it's own, not sure why they both were not working before but working now. I've posted the data below:

I wonder what the previous chkdsk fixed if this one still claims there are bad sectors added.
Is there anyway to find out what files were damaged and in the bad sectors?

As of the last edit of this message, system uptime is 15 hours and 55 minutes.

 

Microsoft research is capable of analyzing chkdsk /f so that you can make a decision about a chkdsk /r. Two months ago I was working with Microsoft on a drive and chkdsk /x /f /r turned the drive into a non-bootable drive. A clean install was then performed. Its uncommon but occurs. The level III Microsoft technician said next time he would have only done chkdsk /f and sent the results to his research team.

I'm glad that you finally got chkdsk to finally work. If you don't schedule chkdsk on boot and it attempts to run on boot that typically means that there were drive problems found. It was just a matter of time for it to complete. There were options to turn it off on boot in case that disrupts your ability to use the computer. In the long run it defeats the purpose as there remains an underlying drive problem.

In a week or more you may want to perform another chkdsk to see again what is happening to the drive. It may give you some comfort knowing that no longer were any bad clusters found. And over time you will want to repeat the drive SMART studies.

 

Good point, what I meant was I wonder why the chkdsk would start working but even then, there was no wininit logging then finally wininit works. In the meantime, I just wonder what was in those bad clusters so I can replace them with good copies if they are not from the OS. Just didn't expect bad clusters on SSDs since it has no moving parts. Even though I had a 200MB MicroSD card go bad but that's probably due to the small physical size. I wonder how many bad clusters would be considered bad enough that a warranty replacement is warranted. Thanks everyone for your input especially zbook who really check things outside the drivers which seems to have fixed the problem.

 

Just a update, so far no BSOD after 3 days 18 hours and 9 minutes with the original version of the driver as in the original post.

 

Finally got a BSOD about 10 minutes ago since rebooting on June 19, 2017 which meant a 15+ day uptime. Any ideas what is causing this one? Thanks and Happy 4th of July everyone!

VINCE-ASUSG74SX-Tue_07_04_2017_123939_63.zip

 

Unfortunately the same driver is highlighted again that I first alerted you to:

Code: BugCheck A, {fffffcf638ac9fc0, 2, 0, fffff803adee70c4} *** WARNING: Unable to verify timestamp for Netwbw02.sys *** ERROR: Module load completed but symbols could not be loaded for Netwbw02.sys Probably caused by : memory_corruption[/quote]
Code: 6: kd> lmvm netwbw02 Browse full module list start end module name fffff80a`04080000 fffff80a`0440c000 Netwbw02 T (no symbols) Loaded symbol image file: Netwbw02.sys Image path: Netwbw02.sys Image name: Netwbw02.sys Browse all global symbols functions data Timestamp: Wed Apr 05 18:04:27 2017 (58E5239B) CheckSum: 00362D85 ImageSize: 0038C000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote] What happens is that Windows update keeps looking for new device drivers and loads them back again. You will need to go through the same procedure again to rollback to an earlier driver.

Then you will need to prevent Windows update from updating device drivers.

EDIT: Checking through the thread again, I see it was not entirely clear that the driver above was the true cause of the BSOD - you also did some CHKDSK clean-ups which seemed to help. All I can say is that the driver is highlighted in the crash analysis.

 

Code: BugCheck A, {fffffcf638ac9fc0, 2, 0, fffff803adee70c4}*** WARNING: Unable to verify timestamp for Netwbw02.sys*** ERROR: Module load completed but symbols could not be loaded for Netwbw02.sysProbably caused by : memory_corruption[/quote] Code: 7/4/2017 7:39 PM Application Error Faulting application name: WifiService.exe, version: 1.0.9.20, time stamp: 0x5656d901 Faulting module name: KERNEL32.DLL, version: 10.0.15063.296, time stamp: 0xab7aae51 Exception code: 0xc0000005 Fault offset: 0x00016850 Faulting process id: 0x14e8 Faulting application start time: 0x01d2f4fd2f0f7757 Faulting application path: C:\Program Files (x86)\OSTotoHotspot\WifiService.exe Faulting module path: C:\WINDOWS\System32\KERNEL32.DLL Report Id: 7f29b7d0-b305-4243-9553-fea41400465e Faulting package full name: Faulting package-relative application ID:[/quote]
NETwbw02.sys Intel® Wireless WiFi Link Driver - Intel® Wireless WiFi Link Adapter Drivers & Software spaceport.sys Storage Spaces Drive Windows Update


Macrium was in the event log.
How did you use it during the bsod?

When you run the Intel driver update utility which driver is it displaying?
Intel® Driver Update Utility

 

I didn't use Macrium during the BSOD but I am running Macrium Reflect Server Plus so it may have something running in the background. The problem always seems to happen when I am using Google Chrome but Chrome had always been running 24x7 with the exact same tabs even though I haven't used any of the tabs as I was just doing a google search when this happened. I always have Process Hacker running though and using the latest nightly build, MacriumService.exe is always running.

As for the Intel driver update utility, this is what it is displaying:




There is a timestamp for the file:





One thing is it hasn't BSOD yet since the last reboot with everything already running which was 1 day 3 hours and 53 minutes ago.

 

I updated to a newer Intel WiFi driver and also updated some old drivers for other devices on the system just in case it conflicts, waiting to see when the next BSOD is and will post.

 

I got my first BSOD since the last BSOD mentioned above which was 1 month and 1 day ago a few hours after I rebooted earlier today that happened after my Nielsen Consumer Panel USB Scanner's software was not detecting the scanner for transmission over the internet so I unplugged the USB and plugged the USB back in. The BSOD happened within 10 seconds after I plugged back in and if it is related, then it would have been caused by one of the FTDI (Future Technology Devices International) Ltd. files which is for the USB to Serial Converter. Anyways, attached is the files collected this time.

VINCE-ASUSG74SX-Sat_08_05_2017_132839_95.zip

 

There were 2 new bsod mini dump files and 2 misbehaving drivers.
These are the drivers.
If you can temporarily make a wired connection and turn off wireless the uninstall and reinstall can be performed.
If you don't have wired available then you can download to the desktop.

1) Open the Asus website enter the computer's serial or product number and the operating system and view available drivers.
2) Find replacement drivers for each:
Netwbw02.sys
npcap.sys
3) Open device manager > find each > confirm the driver using driver details > uninstall
4) Reinstall from the Asus website.
5) For npcap.sys you may need to uninstall the application using control panel and reinstall: WinPcap - Home


Code: NETwNb64 ___ Intel(R) Wireless ___ Intel(R) Wireless Kernel Manual Running OK TRUE FALSE 741,376 2,134,016 0 4/5/2017 10:04:27 AM C:\WINDOWS\system32\drivers\Netwbw02.sys 4,096[/quote]
NETwbw02.sys Intel® Wireless WiFi Link Driver - Intel® Wireless WiFi Link Adapter Drivers & Software
Code: ffffaa00`ed22d120 fffff804`41f96ebcUnable to load image \SystemRoot\system32\DRIVERS\npcap.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for npcap.sys*** ERROR: Module load completed but symbols could not be loaded for npcap.sys npcap+0x6ebc[/quote] Code: npcap Npcap Packet Driver (N Npcap Packet Driver (N Kernel System Running OK TRUE FALSE 8,192 28,672 0 6/12/2017 2:53:39 PM C:\WINDOWS\system32\DRIVERS\npcap.sys 8,192 npcap_wifi Npcap Packet Driver (N Npcap Packet Driver (N Kernel Disabled Stopped OK FALSE FALSE 8,192 28,672 0 6/12/2017 2:53:39 PM C:\WINDOWS\system32\DRIVERS\npcap.sys 8,192[/quote] Code: ffffaa00`ed22c038 fffff804`41675b9fUnable to load image \SystemRoot\System32\Drivers\dump_iaStorA.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for dump_iaStorA.sys*** ERROR: Module load completed but symbols could not be loaded for dump_iaStorA.sys dump_iaStorA+0x75b9f[/quote]

 

zbook,

Many thanks as always!

There should only be one new minidump as the 080517-20000-01.dmp is the only revalent one as the previous analysis from post #36 with the file VINCE-ASUSG74SX-Tue_07_04_2017_123939_63.zip already included the 070417-21109-01.dmp already which is the 2nd newest minidump. But anyways, ASUS does not support anything after Windows 7 as that was the shipping OS for the computer, not to mention, it will only be for the Qualcomm/Atheros MiniPCIe 802.11n/Bluetooth 4.0 Combo card that shipped with the system, not for the Intel 7260AC Mini-PCIe card which was something I replaced on my own so the only drivers available is what Intel supplies which covers the Netwbw02.sys. The npcap has nothing to do with Intel as that is basically what's used by nmap which is installed and not used at the time of the issue since the last time I used it was over a month ago. I had the latest nmap v7.50 which is now v7.60 that I will be installing after this post and also downloaded a newer version of npcap of v0.92 as nmap shipped with v0.91 while v7.60 of nmap ships with v0.93 of npcap which is already the latest version so will post again on the next BSOD as Intel even though you see there is a driver update version change for the package being v19.70.0 at Support for Intel® Dual Band Wireless-AC 7260, the actual drivers for the 7260 is still the same version from April 2017 and have not been updated as seen here Download Intel® PROSet/Wireless Software and Drivers for Windows® 10 as the actual driver it installs for the device in device manager will be v18.33.7.2 while in Windows Apps and Features/Programs and Features, it will show v19.70.0 as I think one is basically the package version which includes other things that the included driver uses.


pcap - Wikipedia

Nmap Announce: Nmap 7.60 released! SSH support, SMB2/SMB3 improvements, 14 more scripts, new Npcap, GSoC work, and more

Npcap: Windows Packet Capture Library & Driver

Npcap: Windows Packet Capture Library & Driver

Support for Intel® Dual Band Wireless-AC 7260

So in a way, it is not easy to figure out exactly what causes the Intel driver to BSOD as other people obviously don't have the problem so I don't know if it is the system load that is doing it or if it is something else. Not to mention that Intel Wireless cards are not known to be problem free and the earlier drivers had their own share of problems. Intel itself has not had good reputation recently with their problems with the motherboard chipsets, processors and even the famous Puma 6 chips used in Cable Modems which has atleast 2 lawsuits against it and after a year, they still haven't fixed the problem yet as you can see on badmodems.com so we can only work with what they provide. npcap driver does run on startup so the problem could actually be the npcap driver if the previous BSOD's actually involves it and not the Intel Wireless driver. If it is indeed npcap, then it would be easier to fix but the problem is one has to prove it's the npcap driver causing the problem as they will likely say they haven't seen the problem and the issue is probably with the Intel driver instead.

It seems the changelog for npcap is here:
Releases · nmap/npcap · GitHub

But does not mention anything about crashes for changes from v0.92 to v0.93.

 

Got a BSOD about 30 minutes ago except for whatever reason, there are no minidump files as it seems like Windows also resetted the dump type to Automatic memory dump and C:\Windows\Minidump has 0 files in it.