Question Win10 BSOD when start up chrome. KMODE_EXCEPTION_NOT_HANDLED & DPC_WATCHDOG_VIOLATION

[elbot7]

Hi experts,

I've been having BSOD since a week ago and I can reproduce it quite consistently. It happens when I tried to use some of my chrome profiles or use the chrome starter. I have no problem starting chrome from other profiles. This problem happens both on a clean and my main profile so I don't think it's related to the plug-ins.

At first, the error is DPC_WATCHDOG_VIOLATION and it happens a while (~1min) after I open the problematic profile. Starting from yesterday, it becomes KMODE_EXCEPTION_NOT_HANDLED and it happens way earlier, right after I open the profile.

I've uploaded 3 minidump files and my sysinfo in the Google Drive. Any help would be appreciated!

Thanks,
Elo

 

[Koekieezz]

it would be better if you posted your full pc specs here.

 

[elbot7]

Is there a better way than the sysinfo in the Google Drive?

it would be better if you posted your full pc specs here.

 

[Colif]

i have to guess you use Ethernet since I don't see any WIFI drivers

Jun 11 2018

e1i65x64.sys

Intel(R) Gigabit Adapter driver

I would run this and see if any newer - https://www.intel.com.au/content/www/au/en/support/intel-driver-support-assistant.html

conversion of dumps (I don't expect you to read them, this just for me): https://jsfiddle.net/zt985qxr/show

try running an Hitman Pro or Malwarebytes and check PC as some of your drivers are a little suspect.

Nov 28 2016

kisnetm64_ev.sys

Jul 03 2017

kdhacker64_ev.sys

Sep 26 2018

kisnetflt64.sys

All show as malware

 

[elbot7]

Hi Colif,

Thanks for your reply. Some update from me.

I do removed the those kxxx64_ev.sys. I did a binary search with verifier and they seems to crash on start up. It turns out that they are from a anti-virus software (kingsoft) which I haven't been used since 2018 so I uninstalled it. After that, I tried to use my chrome again but it still gets me BSOD.

I then updated the intel drivers as you posted, it didn't solve the problem so I tried to see if there's new memdump file to provide updated info, but weirdly, there's none.

I checked my settings for the memdump, and found out that it pops up an warning that my virtual memory is not enough for the memdump file. I then checked my virtual memory setting, it seems like I set it on my Drive F instead of Drive C, so I changed it back.

After restarting, I can use my chrome without any problem. Do you have any idea why the virtual memory on other Drive would make chrome crashes?

 

[Colif]

what make/models are the drives? Google drive is dumb and thinks the 2 system nfo files are actually music and tries to play them. So I can't really tell what you have drive wise

The virtual memory on the other drive, was the page file. Its just space used by windows if you run out of ram or need to create a full dump.

Some drive makers have tools we could use to test their drives.

 

[elbot7]

Did you mean the harddisk models? I have 2 SSDs, 1 HDD and 1 external harddisk (I think it's a HDD as well.)
The model numbers are: CT1000MX500SSD1, CT500BX100SSD1, WDC WD10EZEX-75ZF5A0 and the external one is PHD 3.0 Silicon-Power SCSI Disk Device

Also, I just encountered 2 more BSODs today and I uploaded the dump files in the same drive as well. I briefly checked the winDBG and it seems like the same error as before.

 

[Colif]

which drive was the page file on before you moved it?
Crucial have this for ssd - https://www.crucial.com/support/storage-executive
Western Digital - https://support.wdc.com/downloads.aspx?lang=en&p=279

I assume page file wasn't on an external drive

if you getting BSOD since moving page file, its obviously not the cause.

I will ask a friend to convert dumps, he will post later with an answer. Wonder if that AV you had is really gone.

 

[elbot7]

which drive was the page file on before you moved it?
Crucial have this for ssd - https://www.crucial.com/support/storage-executive
Western Digital - https://support.wdc.com/downloads.aspx?lang=en&p=279

I assume page file wasn't on an external drive

if you getting BSOD since moving page file, its obviously not the cause.

I will ask a friend to convert dumps, he will post later with an answer. Wonder if that AV you had is really gone.

Actually I have not idea. My original setup was use the CT500 for Drive C and WDC for Drive D, E, F. Then I found my Drive C is too small so I bought a new CT1000, copy-pasted all stuff on the CT500 to CT1000 and allocate the rest space on CT1000 propotionally if I remember correctly. I then reset the CT500 and also allocate the space propotionally.

I don't know if the AV is related to the DPC_WATCHDOG_VIOLATION though, since I got it before and after removing it. The sys file of the kingsoft disappeared from the list of the verifier so I think I get rid of it succssfully.

 

[Colif]

If F was on Western Digital, scan it with its tests.

i have a 1tb NVME with 592gb free, I often think I could get away with 500gb but then i would be thinking I am too close if I only had 90gb left, so perhaps not. I have a 3tb hdd I just don't use as well. If I were on 500gb I wouldn't have installed all my games on nvme.

 

[gardenman]

Hi, I'm not sure which ones are new because they are all in the same folder. I'll look at the most recent 2. If you post more, be sure to put them in a new folder each time. Thanks.

Results: https://jsfiddle.net/x2rh7tw1/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.

Spoiler: Dump File Results

File information:	021422-15171-01.dmp (Feb 14 2022 - 01:05:05)
Bugcheck:	DPC_WATCHDOG_VIOLATION (133)
Probably caused by:	ntkrnlmp.exe (Process running at time of crash: chrome.exe)
Uptime:	2 Day(s), 20 Hour(s), 59 Min(s), and 32 Sec(s)

File information:	021422-12093-01.dmp (Feb 14 2022 - 01:55:10)
Bugcheck:	DPC_WATCHDOG_VIOLATION (133)
Probably caused by:	ntkrnlmp.exe (Process running at time of crash: chrome.exe)
Uptime:	0 Day(s), 0 Hour(s), 05 Min(s), and 43 Sec(s)

Possible Motherboard page: https://www.asrock.com/mb/Intel/Z390 Extreme4/index.asp
There is a BIOS update available for your system. You are using version 4.00. Wait for additional information before deciding to update or not. Important: Verify that I have linked to the correct motherboard. Updating your BIOS can be risky. Never try it when you might lose power (lightning storms, recent power outages, etc).

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[elbot7]

If F was on Western Digital, scan it with its tests.

i have a 1tb NVME with 592gb free, I often think I could get away with 500gb but then i would be thinking I am too close if I only had 90gb left, so perhaps not. I have a 3tb hdd I just don't use as well. If I were on 500gb I wouldn't have installed all my games on nvme.

I installed both, updated the firmware for the CT500. Ran all tests and no error was found. I somehow didn't get the BSOD before I did the test so I don't know if this will fix the BSOD. I'll update this thread if I still encounter new BSODs.

@gardenman

Thanks for the info! The name of the memdump is the time they are created, but I'll put them in a separate folder next time!

 

[Colif]

Both errors have same 2 lines in them
ffff9c82f96eedf0 fffff80433ab76d3 : 0000000000000000 0000000000000000 000000000000001c 0000000000000000 : nt!MmAccessFault+0x263
ffff9c82f96eef90 fffff80433a6e080 : ffffcb8400000000 ffff9c8200000000 ffff9c82f96ef1f8 ffff9c82f96ef1dc : nt!MmCheckCachedPageStates+0x1243

access faults happen when CPU tries to access ram it doesn't have access to, so its possible both are a driver as well.
Both are Chrome as victim so could be same driver, the 2 errors aren't perfectly identical (some times I see 5 reports and all the results look the same)

Below are just possible problems
I have seen this cause BSOD before

Sep 24 2015	dtlitescsibus.sys	DAEMON Tools Lite Virtual SCSI Bus (Disc Soft Ltd)
Dec 28 2015	dtliteusbbus.sys	DAEMON Tools Lite Virtual USB Bus (Disc Soft Ltd)

Anything before 2015 could be cause, though I seen a lot of these before and they seem to be okay with windows

Jun 25 2010	npf.sys	NetGroup Packet Filter driver, a component of WinPCap by Riverbed
Nov 24 2011	tap0901.sys	TAP-Win32 Virtual Private Network Driver 0901 (OpenVPN by OpenVPN Technologies) https://openvpn.net/
Feb 27 2012	iusb3hcs.sys	Intel USB 3.0 Host Controller Switch driver http://www.intel.com/
May 03 2012	GEARAspiWDM.sys	Gear Software Advanced SCSI Programming Interface Windows Driver Model http://www.gearsoftware.com/
Oct 22 2012	lvrs64.sys	Logitech Kernel Audio Improvement Filter Driver http://support.logitech.com/
May 16 2014	VBoxDrv.sys	VirtualBox Support driver https://www.virtualbox.org/
May 06 2015	CorsairVBusDriver.sys	Corsair Virtual Device driver (Corsair Utility Engine) http://www.corsair.com/
May 06 2015	CorsairVHidDriver.sys	Corsair Virtual Device driver (Corsair Utility Engine) http://www.corsair.com/
Jun 12 2015	ctxusbm.sys	Citrix USB Filter Driver https://www.citrix.com

lots of old drivers for a fairly new PC

Try running this and see if it offers any new LAN drivers - https://www.intel.com.au/content/www/au/en/support/intel-driver-support-assistant.html

Jun 11 2018

e1i65x64.sys

Intel(R) Gigabit Adapter driver

should be newer ones that 2018


if lan drivers don't help
Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors.

Memtest is created as a bootable USB so that you don’t need windows to run it