BSOD during web browsing in Chrome

I just upgraded my platform (config below) about week ago, all listed components were new.
After a couple of days I started to receive BSOD's (dump files attached). Till now I encountered them only during watching an online stream on twitch or a youtube video and web browsing.
As the dump files indicate NVIDIA drivers with different errors I tried to do clean install of the newest ones (uninstall using DDU, uninstalling GeForce Experience and so on), but that didn't help.
I have Windows 10 x64 Home with all the latest updates.
It is really strange as for example during gaming (DOOM 2016, Overwatch) I have no issues at all.

Does anyone have any suggestions what to do/check next?

CPU: Intel Core i7 7700K
GPU: Zotac GeForce GTX 1080 Ti
RAM: Corsair Vengeance 2x8GB (CMK16GX4M2B3000C15)
Motherboard: MSI Z270 GAMING M7
SSD: Plextor 256GB M.2 PCIe PX-256M8PeG
HDD: Toshiba (DT01ACA200)

Hello and welcome to TenForums :)

I have looked at all three crash dumps in the logfiles and like you I thought at first it was due to the graphics driver as that was the driver named in the stack, but you seem to have checked that out. However, I also noticed that all three recorded that the process running at the time of the crash was the HWMonitor. This might be just coincidence but worth checking and so I wonder if you could uninstall HWMonitor and see if it makes a difference.

Hi Wolfie88,

The logs are in a foreign language and we cannot read them. If you can please change the default language temporarily to create log files so that we can troubleshoot the logs.

Code:

BugCheck 1E, {ffffffffc0000005, fffff801e466b517, 0, ffffffffffffffff}*** WARNING: Unable to verify timestamp for nvlddmkm.sys*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys

dxgkrnl

Code:

BugCheck 3B, {c0000005, fffff80c7190eca5, ffff9580c7cd0160, 0}*** WARNING: Unable to verify timestamp for nvlddmkm.sys*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sysProbably caused by : nvlddmkm.sys ( nvlddmkm+5eca5 )

Code:

0: kd> !threadTHREAD ffffc08220bf5800  Cid 18ec.0518  Teb: 00000000003a3000 Win32Thread: ffffc08220ec3b50 RUNNING on processor 0Not impersonatingGetUlongFromAddress: unable to read from fffff803f6573924Owning Process            ffffc08220f99080       Image:         HWMonitor.exeAttached Process          N/A            Image:         N/Afffff78000000000: Unable to get shared dataWait Start TickCount      32578        Context Switch Count      10123          IdealProcessor: 2             ReadMemory error: Cannot get nt!KeMaximumIncrement value.UserTime                  00:00:00.000KernelTime                00:00:00.000Win32 Start Address 0x0000000140113050Stack Init ffff9580c7cd1c10 Current ffff9580c7ccff00Base ffff9580c7cd2000 Limit ffff9580c7ccb000 Call 0

Code:

BugCheck F7, {ff4609815db198c0, cf68be4fe158, ffff309741b01ea7, 0}Probably caused by : nvlddmkm.sys ( nvlddmkm+1972a6 )

Code:

THREAD ffffd68b782b24c0  Cid 13c0.0878  Teb: 000000000028f000 Win32Thread: ffffd68b78a26350 RUNNING on processor 3Not impersonatingGetUlongFromAddress: unable to read from fffff801c0978924Owning Process            ffffd68b777c5080       Image:         HWMonitor.exeAttached Process          N/A            Image:         N/Afffff78000000000: Unable to get shared dataWait Start TickCount      280657       Context Switch Count      88003          IdealProcessor: 3             ReadMemory error: Cannot get nt!KeMaximumIncrement value.UserTime                  00:00:00.000KernelTime                00:00:00.000Win32 Start Address 0x0000000140113050Stack Init ffff85815db1ac10 Current ffff85815db193b0Base ffff85815db1b000 Limit ffff85815db14000 Call 0

nvlddmkm.sys

nVidia Video drivers

http://www.nvidia.com/Download/index.aspx Get from OEM for laptops

Open administrative command prompt and type or copy and paste:


1) winver (in the pop up about windows > view your windows version and build > type this information into the thread)


2) sfc /scannow


3) dism /online /cleanup-image /restorehealth


4) chkdsk /scan


When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on copy > paste into the thread


5) At times I had had hang, app crashes and bsod with Speed fan so it would not surprise me to find HWmonitor the problem. It was posted in all of the threads.

6) If bsod reoccur after un-installation of hwmonitor then may need proceed to gpu stress test and/or driver verifier.

7) If possible repost the zip file in English so that we can troubleshoot the logs.

OK, I uninstalled HWmonitor. No BSOD's for several hours now. BTW. If HWmonitor really was an issue can you recommend anything else potentially less harmful that can track temps? I like to do it on fresh configs.

Since my first post I also installed the Creators Update. Windows version is now 1703, build 15063.447.

I am attaching log files in English.

In the meantime I found out wierd thing (at least for me) in BIOS and I am not sure if it can somehow influence performance of Windows - My SSD is connected to the M2_1 port but it is not visible anywhere in BIOS except the Boot Priority section. I installed Windows on it without any issues.

Below you can find requested extract from the command prompt.

Microsoft Windows [Version 10.0.15063](c) 2017 Microsoft Corporation. All rights reserved.

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>dism /online /cleanup-image /restorehealthDeployment Image Servicing and Management toolVersion: 10.0.15063.0Image Version: 10.0.15063.0[==========================100.0%==========================]
The restore operation completed successfully.
The operation completed successfully.

C:\WINDOWS\system32>chkdsk /scan
The type of the file system is NTFS.Volume label is HQ.
Stage 1: Examining basic file system structure ... 358400 file records processed.File verification completed. 13080 large file records processed. 0 bad file records processed.
Stage 2: Examining file name linkage ... 485992 index entries processed.Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found.
Stage 3: Examining security descriptors ...Security descriptor verification completed. 63797 data files processed.CHKDSK is verifying Usn Journal... 40754768 USN bytes processed.Usn Journal verification completed.
Windows has scanned the file system and found no problems.
No further action is required.
249588522 KB total disk space. 62296404 KB in 259223 files. 197316 KB in 63798 indexes. 0 KB in bad sectors. 474850 KB in use by the system. 65536 KB occupied by the log file. 186619952 KB available on disk. 4096 bytes in each allocation unit. 62397130 total allocation units on disk. 46654988 allocation units available on disk.

More of the logs are in English. Something happened with msinfo32 as it is still in a foreign language.

Code:

Windows failed fast startup with error status 0xC00000D4.

Code:

The driver \Driver\HidUsb failed to load for the device USB\VID_04D9&PID_A067&MI_00\6&1caed0bf&0&0000.

Code:

HidUsb       Microsoft HID Class Dr Microsoft HID Class Dr Kernel        Manual     Running    OK         TRUE        FALSE        8,192             20,480      0          06/08/2016 05:47:49    C:\Windows\system32\drivers\hidusb.sys           4,096

hidusb.sys

USB Miniport Driver for Input Devices

Windows Update

1) In administrative command prompt type or copy and paste: dism /online /cleanup-image /restorehealth
post results into the thread

2) Turn off Windows fast startup:

Turn On or Off Fast Startup in Windows 10 Windows 10 Performance Maintenance Tutorials

3) Sometimes there are problems in the bios that produce bsod.
The bios in your computer: Wersja/data systemu BIOS American Megatrends Inc. 1.00, 06/12/2016
Please check to see if this is the most up to date version.
To ensure that there are no improper bios settings please reset the bios.
Sometimes there can be failure to boot after resetting the bios.
So please make sure your files are backed up.
Please make a backup image with Macrium: Macrium Software | Macrium Reflect Free: Macrium Software | 404
Please create a restore point.

How to Clear Your Computers CMOS to Reset BIOS Settings:How to Clear Your Computers CMOS to Reset BIOS Settings
Ways to Reset Your BIOS - wikiHow:3 Ways to Reset Your BIOS - wikiHow

4) Click Start, and then click Run.
In the Open box, type devmgmt.msc, and then click OK.
Device Manager opens.
Expand Universal Serial Bus controllers.Note You might have to scroll down the list to find this item.
Right-click the affected USB Root Hub (hidusb.sys), and then click Uninstall to remove it.
Restart the computer.
After the computer starts, Windows will automatically scan for hardware changes and reinstall all the USB root hubs that you uninstalled.
After the computer restarts, check whether the problem is resolved

5) There are many computer software programs to monitor temperatures. The computer environment is a moving target and over time software that was working fine may produce a bsod. Sometimes uninstalling the software and reinstalling it may work. Other times you will need to find replacement software.

On one of my computers there was a bsod. The misbehaving software was Cyberlink. The software was uninstalled and reinstalled using the HP web site. Windows driver verifer produced Cyberlink bsod no matter how many times it was uninstalled and reinstalled. So the choices were to switch to VLC player or continue using Cyberlink knowing that at some time it could be a bsod.

So you could switch to:
Speccy - Free Download - Piriform: Speccy - System Information - Free Download
SpeedFan - Access temperature sensor in your computer: SpeedFan - Access temperature sensor in your computer
or you could attempt to continue to use HW Monitor with a freshly installed version and test it with Windows driver verifier.