BSOD using Google Chrome Browser 64bit 60.0.3112.24 Beta

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:

Attachment 140354

Windows PowerShell
Copyright (C) 2016 Microsoft Corporation. All rights reserved.


PS C:\WINDOWS\system32> get-winevent -FilterHashTable @{logname="Application"; id="1001"}| ?{$_.providername –match "wininit"} | fl timecreated, message




TimeCreated : 6/19/2017 8:20:00 PM
Message :


Checking file system on C:
The type of the file system is NTFS.
Volume label is OS.


A disk check has been scheduled.
Windows will now check the disk.


Stage 1: Examining basic file system structure ...
869888 file records processed.
File verification completed.
23686 large file records processed.
0 bad file records processed.


Stage 2: Examining file name linkage ...
1044072 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.


Stage 3: Examining security descriptors ...
Cleaning up 32 unused index entries from index $SII of file 0x9.
Cleaning up 32 unused index entries from index $SDH of file 0x9.
Cleaning up 32 unused security descriptors.
Security descriptor verification completed.
87093 data files processed.
CHKDSK is verifying Usn Journal...
35356368 USN bytes processed.
Usn Journal verification completed.


Stage 4: Looking for bad clusters in user file data ...
869872 files processed.
File data verification completed.


Stage 5: Looking for bad, free clusters ...
376898883 free clusters processed.
Free space verification is complete.
Adding 17 bad clusters to the Bad Clusters File.


Windows has made corrections to the file system.
No further action is required.


1773682687 KB total disk space.
264772672 KB in 505480 files.
281900 KB in 87094 indexes.
68 KB in bad sectors.
1032583 KB in use by the system.
65536 KB occupied by the log file.
1507595464 KB available on disk.


4096 bytes in each allocation unit.
443420671 total allocation units on disk.
376898866 allocation units available on disk.


Internal Info:
00 46 0d 00 fb fe 08 00 3a e7 0b 00 00 00 00 00 .F......:.......
22 4e 00 00 7a 89 00 00 00 00 00 00 00 00 00 00 "N..z...........


Windows has finished checking your disk.
Please wait while your computer restarts.








PS C:\WINDOWS\system32>

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.

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!

Attachment 142460

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

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

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.

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:
Attachment 142560

There is a timestamp for the file:

Attachment 142589

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.