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

Following the above, I ran 3 "sfc /scannow" since online references says it should be done 3 times.

C:\WINDOWS\system32>sfc /scannowBeginning system scan. This process will take some time.Beginning verification phase of system scan.Verification 100% complete.Windows Resource Protection found corrupt files and successfully repairedthem. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. Forexample C:\Windows\Logs\CBS\CBS.log. Note that logging is currently notsupported in offline servicing scenarios.C:\WINDOWS\system32>

C:\WINDOWS\system32>sfc /scannowBeginning 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>sfc /scannowBeginning 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>findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfclogs.txt"C:\WINDOWS\system32>

Seems like the logs got archived for what it fixed.

C:\WINDOWS\system32>dir c:\windows\logs\cbs
Volume in drive C is OS
Volume Serial Number is 2484-EBDD


Directory of c:\windows\logs\cbs


06/17/2017 05:06 AM <DIR> .
06/17/2017 05:06 AM <DIR> ..
06/17/2017 05:24 AM 4,619,089 CBS.log
06/10/2017 04:54 PM 862,821 CbsPersist_20170611001655.cab
06/14/2017 04:15 AM 1,840,649 CbsPersist_20170614112455.cab
06/15/2017 11:19 PM 869,815 CbsPersist_20170616062117.cab
06/17/2017 05:00 AM 19,316,729 CbsPersist_20170617120636.log
06/17/2017 12:22 AM 962 FilterList.log
6 File(s) 27,510,065 bytes
2 Dir(s) 1,528,356,352,000 bytes free


C:\WINDOWS\system32>findstr /c:"[SR]" %windir%\Logs\CBS\CbsPersist_20170617120636.log >"%userprofile%\Desktop\sfclogsold.txt"


C:\WINDOWS\system32>

Attached below:

sfclogs.zip

Uptime since last reboot 16:00 and no BSOD

 

Have you had any new bsod?

2017-06-17 03:55:36, Info CSI 000083ba [SR] Repairing corrupted file \??\C:\WINDOWS\SysWOW64\gpedit.dll from store
2017-06-17 03:55:36, Info CSI 000083bd [SR] Repairing corrupted file \??\C:\WINDOWS\SysWOW64\gptext.dll from store
2017-06-17 03:55:37, Info CSI 000083c0 [SR] Repairing corrupted file \??\C:\WINDOWS\SysWOW64\fdeploy.dll from store
2017-06-17 03:55:37, Info CSI 000083c3 [SR] Repairing corrupted file \??\C:\WINDOWS\SysWOW64\fde.dll from store
2017-06-17 03:55:37, Info CSI 000083c5 [SR] Repair complete
2017-06-17 03:55:37, Info CSI 000083c6 [SR] Committing transaction
2017-06-17 03:55:37, Info CSI 000083cb [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired



Run a new sfc /scannow to see if it will now display that it found no integrity violations.

For any google chrome problems can you save all of your bookmarks to a file or another browser? Then use control panel to uninstall it. Then reinstall it and restore your bookmarks.

 

What case do you have? How old is your hardware?

50C+ is high for drives.

 

No new BSOD yet... I'll post if I experience a BSOD.

If you look at the 2 log files, you will see the other log file already did two additional sfc /scannow done which is in the newer sfclogs.txt but in any case, here is a new current one:

C:\WINDOWS\system32>sfc /scannowBeginning 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>

For the Google Chrome problems, it is not the URL's I'm concerned about but there are financial institution sites which requires a cookie that is verified by e-mail only and my e-mail (gmail account) on file cannot send/receive emails because it is full and I don't have time to go over 350,000 emails in the next few days either. I don't use bookmarks but I keep those browser tabs opened because each one is something I need to do so when I am done with that task, I'll just close that tab.

The google chrome problem is not really a google chrome problem as it has something to do with the Intel WiFi connection as it stops all network traffic to/from the internet that only a disconnect and reconnect will fix and resume on it's own.

 

As I mentioned in the original post, this is a ASUS G74SX-3DE desktop replacement 17.3" laptop computer so ofcourse it will be hot. The hardware is 5 years and comes with whatever casing the laptop uses as a standard. 50c+ is high for desktop drives but not for laptops as remember laptops especially gaming machines that runs a nVidia GeForce GTX 560m for a video card.

ROG G74SX | ROG - Republic Of Gamers | ASUS Global

 

If you have not already done so please open administrative command prompt and run chkdsk x /f /r on the drive. It may take many hours to run so plan to run it overnight. Please post the eventvwr report in the thread.

Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials
CHKDSK: What is it and how do I run it? - Ask Leo!
How do I see the results of a CHKDSK that ran on boot? - Ask Leo!
How to find chkdsk results in Windows 10 - Winaero uses 26226 find

 

zbook, already done that as mentioned in my earlier response. As the drive is the system drive, it can only run on system startup and even though it says hit any key to abort or chkdsk will be run, it went to the Windows 10 welcome login screen within a 10 seconds and as mentioned earlier, eventvwr has no report at all about the chkdsk. See item #5 in post #10 above.

 

The chkdsk I don't yet understand. Is it that the command is malfunctioning? How come there is no log in the eventvwr?

 

I have no idea. I know in Windows XP, you can see the chkdsk run at bootup, think Win7 too but like the link you provided said, Win8 and above runs the chkdsk hidden. I mean I searched and filtered the logs exactly the way it said and there is no WinInit for the source anywhere with or without using the filter.

 

In any case, I'll just do a "chkdsk c: /x /f /r" now so it'll run on the next reboot or BSOD.

Current uptime 1 day 7 hours and 7 minutes since last reboot without a BSOD.

 

It seems like chkdsk in Windows 10 creators update has a issue of not running according to this but I already have all the latest updates so it should have fixed the problem.

Chkdsk not working? - Windows 10 Forums
How to Fix CHKDSK /F/R Not Working after Windows 10 Creators Update | Driver Talent

Using the later, already checked registry entries and it's correct and we already did the sfc /scannow so autochk.exe is not corrupted.

Current uptime 1 day 10 hours and 40 minutes since last reboot without a BSOD.

 

The uptime is 2 days 11 hours and 42 minutes since the last reboot and there have been no BSODs. Should I try to update to the most current (the original) driver for the Intel 7260 WiFi drivers again as both the current installed driver and the most current driver did BSOD before but no longer does and see if it is running without generating a BSOD and also see if the chkdsk during startup that I did in the previous message actually works or not. It seems I only have the chrome problem hanging and killing the connection on the first use of chrome after the system boots as I have closed chrome by killing all the chrome.exe processes with Process Hacker and reopened all the tabs without any issue a few times already.

 

All looking very promising so far. Yes, I would try to update to the latest driver, you can always rollback if it starts the BSOD again but things do look more stable for you.

 

It is unclear which driver to choose as it has behaved differently.

To find misbehaving drivers there is a windows tool named Windows driver verifier.
It stimulates all non-Microsoft drivers and makes the misbehaving ones bsod.
The minidump files are then processed.
The misbehaving drivers and applications are then uninstalled.
The process continues until there are no longer any Windows driver verifier produced bsod.
Then new drivers are installed. The new or replacement drivers are tested using Windows driver verifier.
If the replacement driver produces a bsod another driver is found.
Sometimes software produces bsod. In these cases the software is uninstalled and reinstalled.
And sometimes another software needs to be chosen. For example replacing Cyberlink with VLC player or replacing one antivirus with another.

In order to run windows driver verifier you need to have your files backed up and create a restore point.
You must be comfortable navigating through the Windows recovery or advanced troubleshooting menu.
In the left lower corner search typing verifier opens the windows driver verifier application.
It needs to be customized by choosing the tests and choosing the drivers.
To turn off Windows driver verifier you will need to navigate through the Windows advanced troubleshooting menu to startup options (not startup repair). Once in startup options it will restart and you will choose safe mode with command prompt and type or copy and paste: verifier /reset to turn off windows driver verifier.

Windows driver verifier is designed to repetitively bsod unless it is turned off or unless there are no more misbehaving drivers.

To practice navigating the Windows recovery or advanced troubleshooting menu open administrative command prompt and type or copy and paste this command: shutdown /r /o /f /t 00
The computer will reboot to the windows recovery or advanced troubleshooting menu.

When using windows driver verifier the bsod windows will display a stop code. The stop code is typically driver detected violation. Sometimes displayed after the stop code is the misbehaving driver. It is in this form: *.sys. If you see a driver please record it for later use.

In order to view the bsod window you may need to modify what happens during a bsod. Type system in the left lower corner search > in the left pane click on advanced system settings > on the system properties menu view startup and recovery and click on settings > on the startup and recovery window make sure for system failure that the box for Automatically restart is unchecked. This will then enable you to view the bsod window and record any information.

Each time you turn off Windows driver verifier you will reboot to the desktop. On the desktop you will run two software programs to analyze the bsod: Bluescreenview and Whocrashed. They will offer immediate analysis of the minidump files. Sometimes one of the software programs has additional information. You will then uninstall the misbehaving driver or application.

Now there are two options. One is to keep running windows driver verifier until there are no longer any bsod. Then start installing new or replacement drivers. The alternative is to reinstall a driver as soon as it is removed and then restart windows driver verifier to test the new driver. The method is personal preference. The ending result should be the same: all misbehaving drivers and applications should be uninstalled and all replacement drivers and applications should no longer bsod with windows driver verifier.

When you get to the point where there are no longer any bsod you will run windows driver verifier for 36 hours under normal or typical computer use. If there are no longer any bsod the troubleshooting for the tool will be completed. The bsod should be fixed and preventative maintenance should be completed too.

This is a link to make sure that automatic restart is off:
BSOD Finding and fixing them - Microsoft Community

This is a link for the windows driver verifier settings:

Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community
This above link should be studies so that you understand how to use windows driver verifier (turning it on and off)

These are the links to install software before using windows driver verifier:
Resplendence Software - WhoCrashed, automatic crash dump analyzer
Blue screen of death (STOP error) information in dump files.


Each time you have a bsod please update the zip file or post a new one so that we can debug the minidump files:
BSOD - Posting Instructions - Windows 10 Forums

 

Actually, both the current installed driver and the newest driver had BSOD before. What I think fixed the problem was the chkdsk that we never saw running or it was the sfc /scannow or the dism. It could even be the clean boot and then reenabling everything again which somehow fixed it.

As for the other stuff, this is my only computer and I need to be able to use it and stay online since every minute is worth $US25.28. There are some things that there are no longer drivers available for it or I can't get to the source for the drivers, same thing for software so uninstall will work but it will never reinstall. It's easier to just use the system and like now, if it doesn't BSOD, then it's fine which is the reason I am rebooting and updating to the most current driver. I will post the next BSOD and if I don't get a BSOD in 2 days or so, then the problem is already solved.