Question ntoskrnl.exe BSOD

[mkraley]

I've been getting a BSOD almost every night. They all seem to be ntoskrnl.
The system seems to recover just fine after a reboot.
Minidumps are at https://www.dropbox.com/s/gzqii5lhhjt211a/kraley-minidumps.zip?dl=0
I've run dism, sfc /scannow, and checked memory both with the windows tool and memtest86
Computer is Lenovo X1 Gen 7 i5-10210U *GB ram 64 bit Windows 10 Pro 21H2 build 19044.1889
Computer is about 2 months old. I've updated windows and drivers.
Any ideas? TIA.

 

[Colif]

NTOSKRNL = windows kernel. It handles all driver requests, power management, and memory management. It sits between Hardware and Applications. It got blamed but its not the cause

I will ask a friend to convert dumps

 

[gardenman]

Hi, I ran the dump files through the debugger and got the following information: https://jsfiddle.net/tchknz90/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:	080822-9921-01.dmp (Aug 8 2022 - 23:56:25)
Bugcheck:	DPC_WATCHDOG_VIOLATION (133)
Probably caused by:	memory_corruption (Process running at time of crash: System)
Uptime:	0 Day(s), 19 Hour(s), 17 Min(s), and 52 Sec(s)

File information:	080522-23890-01.dmp (Aug 5 2022 - 23:56:18)
Bugcheck:	DPC_WATCHDOG_VIOLATION (133)
Driver warnings:	*** WARNING: Unable to verify timestamp for avgStm.sys
Probably caused by:	memory_corruption (Process running at time of crash: System)
Uptime:	1 Day(s), 0 Hour(s), 02 Min(s), and 42 Sec(s)

File information:	080422-9390-01.dmp (Aug 4 2022 - 00:11:52)
Bugcheck:	DPC_WATCHDOG_VIOLATION (133)
Probably caused by:	memory_corruption (Process running at time of crash: chrome.exe)
Uptime:	1 Day(s), 2 Hour(s), 06 Min(s), and 49 Sec(s)

File information:	080422-17046-01.dmp (Aug 4 2022 - 23:53:11)
Bugcheck:	DPC_WATCHDOG_VIOLATION (133)
Driver warnings:	*** WARNING: Unable to verify timestamp for avgStm.sys
Probably caused by:	memory_corruption (Process running at time of crash: System)
Uptime:	0 Day(s), 22 Hour(s), 41 Min(s), and 50 Sec(s)

File information:	080122-17140-01.dmp (Aug 1 2022 - 23:39:18)
Bugcheck:	DPC_WATCHDOG_VIOLATION (133)
Driver warnings:	*** WARNING: Unable to verify timestamp for avgStm.sys
Probably caused by:	memory_corruption (Process running at time of crash: System)
Uptime:	0 Day(s), 22 Hour(s), 06 Min(s), and 17 Sec(s)

Comment: The overclocking driver "XtuAcpiDriver.sys" was found on your system. (Intel Extreme Tuning Utility)

Part of your issue is AVast is crashing. I would temporarily remove it and use Windows Defender to see if things improve.

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

 

[Colif]

He doesn't have Avast installed directly... he has AVG which is owned by same company. First 3 letters of driver name is a hint.
Either way, take it off and see if it helps

the only one that isn't obviously internet related is crash 3.

try running this and see if newer internet drivers - https://www.intel.com.au/content/www/au/en/support/intel-driver-support-assistant.html
you use wifi don't you, I can tell as I found nwifi.sys in the stack text and having never seen it before, looked it up = NativeWiFi Miniport Driver (Microsoft)