Question HYPERVISOR_ERROR BSOD amdppm.sys ?

[TorxFighter]

Hello. I have gotten multiple BSOD's over the last week or so after a windows update (i suspect).

I have tried to update to newest bios version, reinstall windows, updated chipset drivers and some cmd commands like chkdsk and sfc /scannow. also tried disableing HyperV

I'm at a loss and i'm thinking it might be the processor failing?.

Here is the dump file

 

[johnbl]

it is a hypervisor error. (not really documented)
looks like control was passed to a strange kernel address that caused the bugcheck.

I would update the bios to the current version,

ROG STRIX B650E-F GAMING WIFI | ROG Strix | Gaming motherboards｜ROG - Republic of Gamers｜ROG Global

The ROG Strix B650E-F Gaming WiFi takes you to the future with 12 + 2 power stages, hyperspeed DDR5 memory, and next-gen PCIe® 5.0 connectivity. It is equipped with three M.2 slots with heatsinks, a USB 3.2 Gen 2x2 port, WiFi 6E, AI Networking, Two-Way AI Noise Cancelation, and Aura Sync RGB...

rog.asus.com

looks like it was released 6-18-2025
then update the firmware for the audio if you have not all ready
(it is old 2023)

after you get the bios update, update the cpu chipset drivers, and remove any of the asus utilities and disable the asus ai suite if installed.

check the voltages in bios for the 3.3v, 5 v, and 12 volt lines
they should be +/- 5%

if you continue getting a hypervisor error, I would install amd ryzenmaster driver since it would patch known bugs in the CPU. (bios update should also install the CPU patches so you would not need the ryzenmaster driver)

Note: you did not have the microsoft cpu patch installed
4: kd> !sysinfo cpumicrocode
Initial Microcode Version: 00000000:0a601206
Cached Microcode Version: 00000000:00000000
Processor Family: 19
Processor Model: 61
Processor Stepping: 02
Note: Cached Microcode Version is not detected!
14: kd> !sysinfo machineid
BiosVersion = 3024
BiosReleaseDate = 08/02/2024
BaseBoardManufacturer = ASUSTeK COMPUTER INC.
BaseBoardProduct = ROG STRIX B650E-F GAMING WIFI

ProcessorNameString = REG_SZ AMD Ryzen 7 7800X3D 8-Core Processor

cpu released April 6, 2023

 

[TorxFighter]

it is a hypervisor error. (not really documented)
looks like control was passed to a strange kernel address that caused the bugcheck.

I would update the bios to the current version,

ROG STRIX B650E-F GAMING WIFI | ROG Strix | Gaming motherboards｜ROG - Republic of Gamers｜ROG Global

The ROG Strix B650E-F Gaming WiFi takes you to the future with 12 + 2 power stages, hyperspeed DDR5 memory, and next-gen PCIe® 5.0 connectivity. It is equipped with three M.2 slots with heatsinks, a USB 3.2 Gen 2x2 port, WiFi 6E, AI Networking, Two-Way AI Noise Cancelation, and Aura Sync RGB...

rog.asus.com

looks like it was released 6-18-2025
then update the firmware for the audio if you have not all ready
(it is old 2023)

after you get the bios update, update the cpu chipset drivers, and remove any of the asus utilities and disable the asus ai suite if installed.

check the voltages in bios for the 3.3v, 5 v, and 12 volt lines
they should be +/- 5%

if you continue getting a hypervisor error, I would install amd ryzenmaster driver since it would patch known bugs in the CPU. (bios update should also install the CPU patches so you would not need the ryzenmaster driver)

Note: you did not have the microsoft cpu patch installed
4: kd> !sysinfo cpumicrocode
Initial Microcode Version: 00000000:0a601206
Cached Microcode Version: 00000000:00000000
Processor Family: 19
Processor Model: 61
Processor Stepping: 02
Note: Cached Microcode Version is not detected!
14: kd> !sysinfo machineid
BiosVersion = 3024
BiosReleaseDate = 08/02/2024
BaseBoardManufacturer = ASUSTeK COMPUTER INC.
BaseBoardProduct = ROG STRIX B650E-F GAMING WIFI

ProcessorNameString = REG_SZ AMD Ryzen 7 7800X3D 8-Core Processor

cpu released April 6, 2023

Bios is already the newest version. Also checked the voltages and they seem perfectly fine too.

Virtualization is also turned off and it still crashes. XMP is disabled, Hyper_V disabled, Ryzenmaster and chipset driver is downloaded. Have ran a 4 hour test on Memtest5 with no errors

Here is another dump file. that doesn't say the same crash

 

[johnbl]

you might consider updating this driver:
RzDev_022b.sys Mon Mar 22 18:38:31 2021
and
RzCommon.sys Mon Sep 25 20:29:57 2023

some razer driver, you might uninstall, update firmware and reinstall the driver.

there was no indication that it is the cause but this driver fails verifier testing so it is suspect.

in both dumps, a call that is outside of any module was the source of the bugcheck. I would go into bios and make sure asus armory crate is not enabled. then after windows boots, I would look at the list of running services and processes and make sure there is no asus armory crate service running.
(first bugcheck started from a kernel address, the second one had a usermode address) I am thinking the first was a call from bios the second a call from a .exe or service back to the bios.

you would have to provide a kernel memory dump to show what was making the call. (even then it is kind of screwy since it is not from inside a file/driver)

you also have this driver installed:
AVoluteSS3Vad.sys Tue Aug 6 01:38:40 2019
I think it does 3d sound effect, I had a lot of problem on my machine until I deleted this driver. You might want to disable it or update it.
here is the only update for the driver that I know of:https://www.catalog.update.microsoft.com/Search.aspx?q=AVoluteSS3Vad

if you want to disable the driver you can download and run
microsoft autoruns64.exe and just disable it for testing.
https://learn.microsoft.com/en-us/sysinternals/downloads/autoruns

 

[TorxFighter]

you might consider updating this driver:
RzDev_022b.sys Mon Mar 22 18:38:31 2021
and
RzCommon.sys Mon Sep 25 20:29:57 2023

some razer driver, you might uninstall, update firmware and reinstall the driver.

there was no indication that it is the cause but this driver fails verifier testing so it is suspect.

in both dumps, a call that is outside of any module was the source of the bugcheck. I would go into bios and make sure asus armory crate is not enabled. then after windows boots, I would look at the list of running services and processes and make sure there is no asus armory crate service running.
(first bugcheck started from a kernel address, the second one had a usermode address) I am thinking the first was a call from bios the second a call from a .exe or service back to the bios.

you would have to provide a kernel memory dump to show what was making the call. (even then it is kind of screwy since it is not from inside a file/driver)

you also have this driver installed:
AVoluteSS3Vad.sys Tue Aug 6 01:38:40 2019
I think it does 3d sound effect, I had a lot of problem on my machine until I deleted this driver. You might want to disable it or update it.
here is the only update for the driver that I know of:https://www.catalog.update.microsoft.com/Search.aspx?q=AVoluteSS3Vad

if you want to disable the driver you can download and run
microsoft autoruns64.exe and just disable it for testing.
https://learn.microsoft.com/en-us/sysinternals/downloads/autoruns

Thanks. I have now updated the Razer drivers, Uninstalled the AvoluteSS3VAD.sys drivers and disabled armoury crate and checked that the service isn't running.

Thank you so far for taking time to help, i apreciate it. I will update you if it crashed again

 

[TorxFighter]

you might consider updating this driver:
RzDev_022b.sys Mon Mar 22 18:38:31 2021
and
RzCommon.sys Mon Sep 25 20:29:57 2023

some razer driver, you might uninstall, update firmware and reinstall the driver.

there was no indication that it is the cause but this driver fails verifier testing so it is suspect.

in both dumps, a call that is outside of any module was the source of the bugcheck. I would go into bios and make sure asus armory crate is not enabled. then after windows boots, I would look at the list of running services and processes and make sure there is no asus armory crate service running.
(first bugcheck started from a kernel address, the second one had a usermode address) I am thinking the first was a call from bios the second a call from a .exe or service back to the bios.

you would have to provide a kernel memory dump to show what was making the call. (even then it is kind of screwy since it is not from inside a file/driver)

you also have this driver installed:
AVoluteSS3Vad.sys Tue Aug 6 01:38:40 2019
I think it does 3d sound effect, I had a lot of problem on my machine until I deleted this driver. You might want to disable it or update it.
here is the only update for the driver that I know of:https://www.catalog.update.microsoft.com/Search.aspx?q=AVoluteSS3Vad

if you want to disable the driver you can download and run
microsoft autoruns64.exe and just disable it for testing.
https://learn.microsoft.com/en-us/sysinternals/downloads/autoruns

Just got another BSOD. Here is the temporary files and the dump

 

[johnbl]

Just got another BSOD. Here is the temporary files and the dump

this bugcheck was while chrome was running, something started running from a strange location.
maybe turn off chrome extensions?

I would now change your memory dump type to kernel and provide the memory.dmp file. It will be much bigger but will show everything that is running.
notes:
looks like
AVoluteSS3Vad.sys Tue Aug 6 01:38:40 2019
still running.
RzDev_022b.sys Wed Aug 3 03:14:05 2022 (this was updated)
RzCommon.sys Mon Sep 25 20:29:57 2023

you could turn on verifier.exe testing to make the system bugcheck faster if the problem is in a driver.

basically start cmd.exe as an admin
then run
verifier.exe /standard /all /bootmode oneboot

https://learn.microsoft.com/en-us/windows-hardware/drivers/devtest/verifier-command-line

the /bootmode options are useful to make it easier to turn of verifer. This option will only have verifier on for the next boot and will turn it off automatically. Otherwise you have to turn it off by running cmd.exe as an admin then run
verifier.exe /reset
(or your machine will run slowly until you run the command)
i think AVoluteSS3Vad.sys fails verifier testing so you might want to disable this driver with microsft autoruns64 before you do any testing. (assuming you do not think the driver is the cause of problems)

you could also use the option to exclued a driver from testing by adding /driver.exclude DriverList command option to the verifier.

something like
verifier.exe /standard /all /driver.exclude avolutess3vad.sys /bootmode oneboot

this would run standard tests on all driver except your avolutess3vad.sys 3d sound driver which we already know messes up the system because of some DMA problem.
(i would disable the driver with auto runs rather than skipping the problem driver since it might screw up something else)

note: RBG light controllers also tend to mess up the system when you have more than one led light.
logi_lamparray.sys Mon Apr 15 11:33:13 2024
mostly you see it with mouse light control, AIO coolers with light, fan lights, RAM lights. Often you have to update the firmware of the device to avoid the problems.

you might also consider running a testing tool to check out your amd processor. Someone would have to recommend one. I normally just run a stress test like prime95 but there may be a better tool now for trying to isolate specific areas/functions of the cpu. intel has there own tool(intel processor diagnostics tool) I would expect amd should have something similar.
(simple tool that tests basic functions rather than a stress tool)

in your case control is moving from different areas.
kernel, user mode, and what looks like kernel heap.
none were within a known module.

more notes:
vwifibus.sys (virtual wi fi bus driver)
vwififlt.sys (virtual wifi fliter driver)
vwifimp.sys (virtual network miniport driver)

running (are these network virtual drivers? do they require the bios virtualization to be turned on?

take a look at the last two entries in this thread:
https://learn.microsoft.com/en-us/answers/questions/1496217/hypervisor-error-blue-screen

person, disabled hypervisor in bios then had to disable the software in windows to prevent bugchecks.

 

[ubuysa]

Ignore

 

[TorxFighter]

this bugcheck was while chrome was running, something started running from a strange location.
maybe turn off chrome extensions?

I would now change your memory dump type to kernel and provide the memory.dmp file. It will be much bigger but will show everything that is running.
notes:
looks like
AVoluteSS3Vad.sys Tue Aug 6 01:38:40 2019
still running.
RzDev_022b.sys Wed Aug 3 03:14:05 2022 (this was updated)
RzCommon.sys Mon Sep 25 20:29:57 2023

you could turn on verifier.exe testing to make the system bugcheck faster if the problem is in a driver.

basically start cmd.exe as an admin
then run
verifier.exe /standard /all /bootmode oneboot

https://learn.microsoft.com/en-us/windows-hardware/drivers/devtest/verifier-command-line

the /bootmode options are useful to make it easier to turn of verifer. This option will only have verifier on for the next boot and will turn it off automatically. Otherwise you have to turn it off by running cmd.exe as an admin then run
verifier.exe /reset
(or your machine will run slowly until you run the command)
i think AVoluteSS3Vad.sys fails verifier testing so you might want to disable this driver with microsft autoruns64 before you do any testing. (assuming you do not think the driver is the cause of problems)

you could also use the option to exclued a driver from testing by adding /driver.exclude DriverList command option to the verifier.

something like
verifier.exe /standard /all /driver.exclude avolutess3vad.sys /bootmode oneboot

this would run standard tests on all driver except your avolutess3vad.sys 3d sound driver which we already know messes up the system because of some DMA problem.
(i would disable the driver with auto runs rather than skipping the problem driver since it might screw up something else)

note: RBG light controllers also tend to mess up the system when you have more than one led light.
logi_lamparray.sys Mon Apr 15 11:33:13 2024
mostly you see it with mouse light control, AIO coolers with light, fan lights, RAM lights. Often you have to update the firmware of the device to avoid the problems.

you might also consider running a testing tool to check out your amd processor. Someone would have to recommend one. I normally just run a stress test like prime95 but there may be a better tool now for trying to isolate specific areas/functions of the cpu. intel has there own tool(intel processor diagnostics tool) I would expect amd should have something similar.
(simple tool that tests basic functions rather than a stress tool)

in your case control is moving from different areas.
kernel, user mode, and what looks like kernel heap.
none were within a known module.

more notes:
vwifibus.sys (virtual wi fi bus driver)
vwififlt.sys (virtual wifi fliter driver)
vwifimp.sys (virtual network miniport driver)

running (are these network virtual drivers? do they require the bios virtualization to be turned on?

take a look at the last two entries in this thread:
https://learn.microsoft.com/en-us/answers/questions/1496217/hypervisor-error-blue-screen

person, disabled hypervisor in bios then had to disable the software in windows to prevent bugchecks.

Hi. Sorry for the late response. Full disclosure this is a PC I built for a friend and he brought it to me yesterday so I could test. Funny thing though is that it has not crashed since even with stress tests running. Y-cruncher stress test, OCCT and furmark.

It must then be some driver of what he is using at home causing issues. We will try testing this.

 

[TorxFighter]

Update again. He's not getting it back yet. It has crashed twice now but only while idling which is weird.

Kernel-Power 41 (63). All data is zeroes.

Should i try a new power supply?.

 

[TorxFighter]

After disabling Global C-State it has not crashed yet. I will have to try a new motherboard as I believe that is the biggest suspect in this case