Question Win11 random BSOD, Need help.

[Varthog]

Good afternoon,

I am writing this post with a bit sour feeling in the mouth since all components are new in this PC and now i have no idea how to fix it. It started today with random freezing and resetting with BSOD "KERNEL_MODE_HEAP_CORRUPTION" and i have now idea what to do next.

Edition Windows 11 Pro
Version 24H2
Installed on ‎5/‎17/‎2025
OS build 26100.4484
Experience Windows Feature Experience Pack 1000.26100.128.0

My config:
CPU Ryzen 7 7700x
GPU 3060TI
Ram 32 GB 6000Mhz DDR5
Motherboard - X670-P CSM

Down here are dump files, which i have hard time understanding.
https://drive.google.com/file/d/1UBlTxsXfctU7fkjdXCbOda5vH1C0EOAN/view?usp=sharing

I beg you for assistance

​

 

[johnbl]

you might consider a bios update first.
then look at the avast vm monitor next.
(look for a bug in the service that talks to the driver)
(might remove the service if you have to)
otherwise you will have to run verifier.exe testing to get the system to bugcheck faster at the time of corruption.
===============

All the bugchecks were due to heap corruptions.
a heap is a data structure used for allocation of memory for programs. This error generally means some software is using some memory, freeing it back to the system (windows) windows then gives it to another process but the first process still uses it. (causing a bugcheck)

1 bugcheck did not show a process,
1 showed the system process,
1 showed a service control process.
the very first bugcheck showed

aswVmm.sys
Timestamp: Mon Jun 16 09:11:05 2025

the stack looked corrupted.
the driver is for avast vm monitor.

you have about a 60 % chance that this driver or its service host is what is corrupting the data structure.
The problem is that the corruption is not detected at the time, it is detected later when windows tries free up the data and recycle the memory to other processes.

you can see if avast has a fix or you will have to run verifier.exe tests to make the system bugcheck at the time of corruption rather than later.

BiosReleaseDate = 11/21/2022
SystemManufacturer = ASUS
BaseBoardProduct = PRIME X670-P
Identifier = REG_SZ AMD64 Family 25 Model 97 Stepping 2
ProcessorNameString = REG_SZ AMD Ryzen 7 7700X 8-Core Processor

your windows files pass checksums in the debugger.
so your build looks ok

 

[Varthog]

All the bugchecks were due to heap corruptions.
a heap is a data structure used for allocation of memory for programs. This error generally means some software is using some memory, freeing it back to the system (windows) windows then gives it to another process but the first process still uses it. (causing a bugcheck)

1 bugcheck did not show a process,
1 showed the system process,
1 showed a service control process.
the very first bugcheck showed

aswVmm.sys
Timestamp: Mon Jun 16 09:11:05 2025

the stack looked corrupted.
the driver is for avast vm monitor.

you have about a 60 % chance that this driver or its service host is what is corrupting the data structure.
The problem is that the corruption is not detected at the time, it is detected later when windows tries free up the data and recycle the memory to other processes.

you can see if avast has a fix or you will have to run verifier.exe tests to make the system bugcheck at the time of corruption rather than later.

BiosReleaseDate = 11/21/2022
SystemManufacturer = ASUS
BaseBoardProduct = PRIME X670-P
Identifier = REG_SZ AMD64 Family 25 Model 97 Stepping 2
ProcessorNameString = REG_SZ AMD Ryzen 7 7700X 8-Core Processor

your windows files pass checksums in the debugger.
so your build looks ok

Well for now i have removed the Avast antivirus to try and see whether this issue is going to happen again. IT just started randomly doing it.

 

[Varthog]

For now it holds no BSOD seems Avast was the culprit. I am scared even to try new Driver for GPU 😛

 

[johnbl]

For now it holds no BSOD seems Avast was the culprit. I am scared even to try new Driver for GPU 😛

you might have to wait a week or two before you know. Even then it could be some other service messing up the avast driver. Since it was a vm driver, it can also be a bug in bios, or the cpu. if it is a bug in the avast driver whe should see a lot more of these bugchecks over the next week or two.

if it is a cpu bug, it would be fixed in bios or a cpu microcode patch from microsoft or from the cpu vendor (ryzenmaster driver in this case)