Question Random BSOD while watching youtube

Colif

Win 11 Master
Moderator
Jun 12, 2015
61,167
5,188
166,290
10,454
Conversion of dumps

report - Click run as fiddle to see report

File: 110522-10140-01.dmp (Nov 6 2022 - 15:17:27)
BugCheck: [MEMORY_MANAGEMENT (1A)]
Probably caused by: memory_corruption (Process: chrome.exe)
Uptime: 21 Day(s), 21 Hour(s), 02 Min(s), and 04 Sec(s)

What are full specs? I can see this but not storage or Power Supply info
CPU: i7-12700K
Motherboard: ROG STRIX Z690-F GAMING WIFI
BIOS: 2004
RAM: 32gb Corsair CMK32GX5M2B5200C40
GPU: Nvidia something

Dump not very informative
try running this and see if anything new - https://www.intel.com.au/content/www/au/en/support/intel-driver-support-assistant.html
 
Sep 26, 2022
21
0
10
0
What are full specs? I can see this but not storage or Power Supply info
CPU: i7-12700K
Motherboard: ROG STRIX Z690-F GAMING WIFI
BIOS: 2004
RAM: 32gb Corsair CMK32GX5M2B5200C40
GPU: Nvidia something
GPU: Nvidia 3080ti
Power supply:
EVGA SuperNOVA 1000 GT, 80 Plus Gold 1000W
SSD m.2: samsung 980 1tb
ram: CORSAIR Vengeance DDR5 32GB


Did the intel driver, just had a new wireless adapter driver. went ahead and installed it. Bios and everything else for the most part all up to date.
Not sure if you saw my memory dump file as well, its the link above the minidump file, this one https://drive.google.com/file/d/1Q-MohvPWL9_GVB4K-1ILBGwagjlq5RDu/view?usp=sharing maybe that one has more info? Unless you saw that too :( Appreciate your help as always!!
 
Last edited:

ubuysa

Honorable
Jul 29, 2016
63
9
10,565
6
I've just taken a look at the kernel dump you uploaded (thanks for that!) and the driver aswVmm.sys features prominently in the call stack, it's also called immediately prior to the page fault that caused the BSOD...
Rich (BB code):
0: kd> dps ffff858b91d7d000 ffff858b91d84000 <-- Call stack range (read from bottom up)
ffff858b`91d7d000  808f6100`ac6d0000
<snip>
ffff858b`91d833c8  fffff803`417f90f0 nt!KeBugCheckEx <-- the BSOD
ffff858b`91d833d0  00000000`0000027f
<snip>
ffff858b`91d83a38  fffff803`4180725e nt!KiPageFault+0x35e <-- the failure (invalid memory access)
<snip>
ffff858b`91d837b0  00000000`00000004
ffff858b`91d837b8  fffff803`440adf33 aswVmm+0xdf33 <-- the most recent (of many) call to aswVmm.sys
The aswVmm.sys driver is a component of the Avast! security system and it does appear to be up to date...
Rich (BB code):
0: kd> lmDvmaswVmm
Browse full module list
start             end                 module name
fffff803`440a0000 fffff803`440ec000   aswVmm     (no symbols)           
    Loaded symbol image file: aswVmm.sys
    Image path: \SystemRoot\system32\drivers\aswVmm.sys
    Image name: aswVmm.sys
    Browse all global symbols  functions  data
    Timestamp:        Tue Sep 13 19:54:16 2022 (6320B5B8)
    CheckSum:         000505B8
    ImageSize:        0004C000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:
Even though it's up to date its fingerprints are all over this BSOD. This won't be the first time I've seen Avast! (and most other third party anti-malware tools) cause BSODs. IMO you don't need Avast!, or any other third-party anti-malware tool, Windows Firewall and Defender are perfectly good - they are all I use.

I think the solution here is to remove Avast!.
 
Sep 26, 2022
21
0
10
0
I've just taken a look at the kernel dump you uploaded (thanks for that!) and the driver aswVmm.sys features prominently in the call stack, it's also called immediately prior to the page fault that caused the BSOD...
Rich (BB code):
0: kd> dps ffff858b91d7d000 ffff858b91d84000 <-- Call stack range (read from bottom up)
ffff858b`91d7d000  808f6100`ac6d0000
<snip>
ffff858b`91d833c8  fffff803`417f90f0 nt!KeBugCheckEx <-- the BSOD
ffff858b`91d833d0  00000000`0000027f
<snip>
ffff858b`91d83a38  fffff803`4180725e nt!KiPageFault+0x35e <-- the failure (invalid memory access)
<snip>
ffff858b`91d837b0  00000000`00000004
ffff858b`91d837b8  fffff803`440adf33 aswVmm+0xdf33 <-- the most recent (of many) call to aswVmm.sys
The aswVmm.sys driver is a component of the Avast! security system and it does appear to be up to date...
Rich (BB code):
0: kd> lmDvmaswVmm
Browse full module list
start             end                 module name
fffff803`440a0000 fffff803`440ec000   aswVmm     (no symbols)          
    Loaded symbol image file: aswVmm.sys
    Image path: \SystemRoot\system32\drivers\aswVmm.sys
    Image name: aswVmm.sys
    Browse all global symbols  functions  data
    Timestamp:        Tue Sep 13 19:54:16 2022 (6320B5B8)
    CheckSum:         000505B8
    ImageSize:        0004C000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:
Even though it's up to date its fingerprints are all over this BSOD. This won't be the first time I've seen Avast! (and most other third party anti-malware tools) cause BSODs. IMO you don't need Avast!, or any other third-party anti-malware tool, Windows Firewall and Defender are perfectly good - they are all I use.

I think the solution here is to remove Avast!.
Good find! Is it really safe too? I know I hear people saying defender is good enough but I get worried at times it might not be enough :(
I did update it, but will try uninstalling it to see how it goes!
 

ubuysa

Honorable
Jul 29, 2016
63
9
10,565
6
I've been around Windows since day 1 and I was a senior systems programmer in a large mainframe installation responsible (amongst a host of other things) for system security. Windows Firewall and Defender in Windows 10 and 11 are plenty safe enough for most users. Defender in particular, contains a host of exploit protection measures and, if you chose to use it, ransomware protection. The firewall is very configurable, although it's not the easiest interface to get your head around.

IMO there is no need to be paying for third-party security these days. Also there is no such thing as "install this and you're safe" security. The most insecure component of any system is the end user, and no software can protect against the end user. With third-party security systems you're often just paying to get BSODs more often. As you have seen. ;)
 

ASK THE COMMUNITY

TRENDING THREADS