F5F Stay Refreshed Software Operating Systems Question BSOD occurs when the PC is idle or performing minimal tasks.

Question BSOD occurs when the PC is idle or performing minimal tasks.

Question BSOD occurs when the PC is idle or performing minimal tasks.

Pages (2): 1 2 Next
X
xp37
Member
Find
60
12-25-2025, 10:28 AM
#1
Since updating from Windows 10 to Windows 11 sometime last year I have been experiencing regular BSOD crashes. The crash message is typically either HYPERVISOR_ERROR or PAGE_FAULT_IN_NON_PAGED_AREA although other error messages do occur. These crashes rarely, if ever, happen when I am doing something serious such as playing a game and they typically occur if I am doing nothing, using EDGE to visit a web site, looking at news feeds or working in file explorer. In fact a HYPERVISOR_ERROR has just occured when I was posting this question and I include the WinDbg output of the dump file below.
I have tried all of the normal things that are recommended (SFC/SCANNOW, DISM, update drivers, memtest86, chkdsk, GPU stress test and even reinstall Windows 11) but none of them have resolved the problem of helped to throw any light on what is going on. I have also checked component operating temperatures using CPUID HWMonitor and nothing seems abnormal (CPU is currently 42 degC and GPU 39 degC). The WinDbg output from the most recent crash is given below - this one is more helpful than most - it highlights amdppm.sys as the module name but it's worth noting that I have tried re-installing AMD drivers before but without solving the problem.
My summary PC spec is AMD Ryzen 3600, Tomahawk B450 Max motherboard, Nvidia GTX 1660 GPU and 16 GByte RAM.
If anyone can suggest what might be causing this I would be most grateful.
************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
NonInteractiveNuget : true
AllowNugetMSCredentialProviderInstall : true
AllowParallelInitializationOfLocalRepositories : true
EnableRedirectToV8JsProvider : false
-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true
>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds
************* Waiting for Debugger Extensions Gallery to Initialize **************
>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.016 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 41
Microsoft ® Windows Debugger Version 10.0.27553.1004 AMD64
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\052624-8406-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 22621 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0xfffff802`0f000000 PsLoadedModuleList = 0xfffff802`0fc13130
Debug session time: Sun May 26 17:57:13.098 2024 (UTC + 1:00)
System Uptime: 0 days 0:46:30.935
Loading Kernel Symbols
...............................................................
................................................................
................................................................
............
Loading User Symbols
Loading unloaded module list
........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`0f417f80 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff8801`b1ccdcb0=0000000000020001
6: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
HYPERVISOR_ERROR (20001)
The hypervisor has encountered a fatal error.
Arguments:
Arg1: 0000000000000011
Arg2: 00000000002f4152
Arg3: 000000000000100f
Arg4: ffffe70000a05cd0
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2515
Key : Analysis.Elapsed.mSec
Value: 4565
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 0
Key : Analysis.Init.CPU.mSec
Value: 327
Key : Analysis.Init.Elapsed.mSec
Value: 3879
Key : Analysis.Memory.CommitPeak.Mb
Value: 104
Key : Bugcheck.Code.LegacyAPI
Value: 0x20001
Key : Bugcheck.Code.TargetModel
Value: 0x20001
Key : Dump.Attributes.AsUlong
Value: 808
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Failure.Bucket
Value: 0x20001_11_2f4152_amdppm!HvRequestIdle
Key : Failure.Hash
Value: {8420b585-745b-2d4d-14e5-01d3ca4497c4}
Key : Hypervisor.Enlightenments.ValueHex
Value: 1497cf94
Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 1
Key : Hypervisor.Flags.ApicEnlightened
Value: 1
Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 0
Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0
Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0
Key : Hypervisor.Flags.CpuManager
Value: 1
Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 0
Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 1
Key : Hypervisor.Flags.Epf
Value: 0
Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 1
Key : Hypervisor.Flags.HardwareMbecAvailable
Value: 1
Key : Hypervisor.Flags.MaxBankNumber
Value: 0
Key : Hypervisor.Flags.MemoryZeroingControl
Value: 0
Key : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0
Key : Hypervisor.Flags.NoNonArchCoreSharing
Value: 1
Key : Hypervisor.Flags.Phase0InitDone
Value: 1
Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0
Key : Hypervisor.Flags.RootScheduler
Value: 0
Key : Hypervisor.Flags.SynicAvailable
Value: 1
Key : Hypervisor.Flags.UseQpcBias
Value: 0
Key : Hypervisor.Flags.Value
Value: 4853999
Key : Hypervisor.Flags.ValueHex
Value: 4a10ef
Key : Hypervisor.Flags.VpAssistPage
Value: 1
Key : Hypervisor.Flags.VsmAvailable
Value: 1
Key : Hypervisor.RootFlags.AccessStats
Value: 1
Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 1
Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 1
Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0
Key : Hypervisor.RootFlags.HostTimelineSync
Value: 1
Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0
Key : Hypervisor.RootFlags.IsHyperV
Value: 1
Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 1
Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 1
Key : Hypervisor.RootFlags.MceEnlightened
Value: 1
Key : Hypervisor.RootFlags.Nested
Value: 0
Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 1
Key : Hypervisor.RootFlags.Value
Value: 1015
Key : Hypervisor.RootFlags.ValueHex
Value: 3f7
BUGCHECK_CODE: 20001
BUGCHECK_P1: 11
BUGCHECK_P2: 2f4152
BUGCHECK_P3: 100f
BUGCHECK_P4: ffffe70000a05cd0
FILE_IN_CAB: 052624-8406-01.dmp
TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b
DUMP_FILE_ATTRIBUTES: 0x808
Kernel Generated Triage Dump
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffff8801`b1ccdca8 fffff802`0f545101 : 00000000`00020001 00000000`00000011 00000000`002f4152 00000000`0000100f : nt!KeBugCheckEx
ffff8801`b1ccdcb0 fffff802`0f46ed58 : 00000000`00000100 fffff802`0f20d14c ffff8801`b1cd6340 ffff8801`b1ccdd30 : nt!HvlSkCrashdumpCallbackRoutine+0x81
ffff8801`b1ccdcf0 fffff802`0f425f82 : 00000000`00000100 ffff8801`b1ccdef0 00000000`00000000 00000000`00000000 : nt!KiProcessNMI+0x261e28
ffff8801`b1ccdd30 fffff802`0f425cee : 00000000`00000100 ffff8801`b1ccdef0 00000000`00000000 00000000`00000000 : nt!KxNmiInterrupt+0x82
ffff8801`b1ccde70 fffff802`0ab20003 : fffff802`0f3cb587 fffff802`0f3c6920 fffff802`0f2df5d8 00000000`00000000 : nt!KiNmiInterrupt+0x26e
ffffcc8d`c4aa74c8 fffff802`0f3cb587 : fffff802`0f3c6920 fffff802`0f2df5d8 00000000`00000000 fffff802`0f2e3a7d : 0xfffff802`0ab20003
ffffcc8d`c4aa74d0 fffff802`0f544355 : 00000000`00000001 fffff802`0f3c693b 00000006`88db5b3b 00000000`00000000 : nt!HvcallInitiateHypercall+0x57
ffffcc8d`c4aa7550 fffff802`38239d5d : 00000000`000100de fffff802`0f2df5d8 ffffbc84`f5ce5168 fffff802`0f2da237 : nt!HvlRequestProcessorHalt+0x35
ffffcc8d`c4aa7580 fffff802`382318d3 : 00000000`00000000 00000000`00000001 ffffbc84`f5ce5168 00000000`00000000 : amdppm!HvRequestIdle+0x2d
ffffcc8d`c4aa75d0 fffff802`0f2e1456 : 00000000`00000000 ffff8801`b1c91180 00000000`00000000 ffff8801`b1c91180 : amdppm!AcpiCStateIdleExecute+0x23
ffffcc8d`c4aa7600 fffff802`0f2e0fcb : ffffbc84`f5ce5718 00000000`00000000 00000000`ffffffff ffffcc8d`c4aa7ab0 : nt!PpmIdleExecuteTransition+0x426
ffffcc8d`c4aa7a50 fffff802`0f41cf44 : 00000000`00000000 ffffbc84`ee35a040 ffffbc84`f9150080 ffffbc85`0050b080 : nt!PoIdle+0x68b
ffffcc8d`c4aa7c40 00000000`00000000 : ffffcc8d`c4aa8000 ffffcc8d`c4aa2000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x54
SYMBOL_NAME: amdppm!HvRequestIdle+2d
MODULE_NAME: amdppm
IMAGE_NAME: amdppm.sys
IMAGE_VERSION: 10.0.22621.3593
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 2d
FAILURE_BUCKET_ID: 0x20001_11_2f4152_amdppm!HvRequestIdle
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {8420b585-745b-2d4d-14e5-01d3ca4497c4}
Followup: MachineOwner
---------
Reply
Reply
X
xp37
12-25-2025, 10:28 AM #1

Since updating from Windows 10 to Windows 11 sometime last year I have been experiencing regular BSOD crashes. The crash message is typically either HYPERVISOR_ERROR or PAGE_FAULT_IN_NON_PAGED_AREA although other error messages do occur. These crashes rarely, if ever, happen when I am doing something serious such as playing a game and they typically occur if I am doing nothing, using EDGE to visit a web site, looking at news feeds or working in file explorer. In fact a HYPERVISOR_ERROR has just occured when I was posting this question and I include the WinDbg output of the dump file below.
I have tried all of the normal things that are recommended (SFC/SCANNOW, DISM, update drivers, memtest86, chkdsk, GPU stress test and even reinstall Windows 11) but none of them have resolved the problem of helped to throw any light on what is going on. I have also checked component operating temperatures using CPUID HWMonitor and nothing seems abnormal (CPU is currently 42 degC and GPU 39 degC). The WinDbg output from the most recent crash is given below - this one is more helpful than most - it highlights amdppm.sys as the module name but it's worth noting that I have tried re-installing AMD drivers before but without solving the problem.
My summary PC spec is AMD Ryzen 3600, Tomahawk B450 Max motherboard, Nvidia GTX 1660 GPU and 16 GByte RAM.
If anyone can suggest what might be causing this I would be most grateful.
************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
NonInteractiveNuget : true
AllowNugetMSCredentialProviderInstall : true
AllowParallelInitializationOfLocalRepositories : true
EnableRedirectToV8JsProvider : false
-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true
>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds
************* Waiting for Debugger Extensions Gallery to Initialize **************
>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.016 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 41
Microsoft ® Windows Debugger Version 10.0.27553.1004 AMD64
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\052624-8406-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 22621 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0xfffff802`0f000000 PsLoadedModuleList = 0xfffff802`0fc13130
Debug session time: Sun May 26 17:57:13.098 2024 (UTC + 1:00)
System Uptime: 0 days 0:46:30.935
Loading Kernel Symbols
...............................................................
................................................................
................................................................
............
Loading User Symbols
Loading unloaded module list
........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`0f417f80 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff8801`b1ccdcb0=0000000000020001
6: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
HYPERVISOR_ERROR (20001)
The hypervisor has encountered a fatal error.
Arguments:
Arg1: 0000000000000011
Arg2: 00000000002f4152
Arg3: 000000000000100f
Arg4: ffffe70000a05cd0
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2515
Key : Analysis.Elapsed.mSec
Value: 4565
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 0
Key : Analysis.Init.CPU.mSec
Value: 327
Key : Analysis.Init.Elapsed.mSec
Value: 3879
Key : Analysis.Memory.CommitPeak.Mb
Value: 104
Key : Bugcheck.Code.LegacyAPI
Value: 0x20001
Key : Bugcheck.Code.TargetModel
Value: 0x20001
Key : Dump.Attributes.AsUlong
Value: 808
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Failure.Bucket
Value: 0x20001_11_2f4152_amdppm!HvRequestIdle
Key : Failure.Hash
Value: {8420b585-745b-2d4d-14e5-01d3ca4497c4}
Key : Hypervisor.Enlightenments.ValueHex
Value: 1497cf94
Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 1
Key : Hypervisor.Flags.ApicEnlightened
Value: 1
Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 0
Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0
Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0
Key : Hypervisor.Flags.CpuManager
Value: 1
Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 0
Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 1
Key : Hypervisor.Flags.Epf
Value: 0
Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 1
Key : Hypervisor.Flags.HardwareMbecAvailable
Value: 1
Key : Hypervisor.Flags.MaxBankNumber
Value: 0
Key : Hypervisor.Flags.MemoryZeroingControl
Value: 0
Key : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0
Key : Hypervisor.Flags.NoNonArchCoreSharing
Value: 1
Key : Hypervisor.Flags.Phase0InitDone
Value: 1
Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0
Key : Hypervisor.Flags.RootScheduler
Value: 0
Key : Hypervisor.Flags.SynicAvailable
Value: 1
Key : Hypervisor.Flags.UseQpcBias
Value: 0
Key : Hypervisor.Flags.Value
Value: 4853999
Key : Hypervisor.Flags.ValueHex
Value: 4a10ef
Key : Hypervisor.Flags.VpAssistPage
Value: 1
Key : Hypervisor.Flags.VsmAvailable
Value: 1
Key : Hypervisor.RootFlags.AccessStats
Value: 1
Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 1
Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 1
Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0
Key : Hypervisor.RootFlags.HostTimelineSync
Value: 1
Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0
Key : Hypervisor.RootFlags.IsHyperV
Value: 1
Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 1
Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 1
Key : Hypervisor.RootFlags.MceEnlightened
Value: 1
Key : Hypervisor.RootFlags.Nested
Value: 0
Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 1
Key : Hypervisor.RootFlags.Value
Value: 1015
Key : Hypervisor.RootFlags.ValueHex
Value: 3f7
BUGCHECK_CODE: 20001
BUGCHECK_P1: 11
BUGCHECK_P2: 2f4152
BUGCHECK_P3: 100f
BUGCHECK_P4: ffffe70000a05cd0
FILE_IN_CAB: 052624-8406-01.dmp
TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b
DUMP_FILE_ATTRIBUTES: 0x808
Kernel Generated Triage Dump
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffff8801`b1ccdca8 fffff802`0f545101 : 00000000`00020001 00000000`00000011 00000000`002f4152 00000000`0000100f : nt!KeBugCheckEx
ffff8801`b1ccdcb0 fffff802`0f46ed58 : 00000000`00000100 fffff802`0f20d14c ffff8801`b1cd6340 ffff8801`b1ccdd30 : nt!HvlSkCrashdumpCallbackRoutine+0x81
ffff8801`b1ccdcf0 fffff802`0f425f82 : 00000000`00000100 ffff8801`b1ccdef0 00000000`00000000 00000000`00000000 : nt!KiProcessNMI+0x261e28
ffff8801`b1ccdd30 fffff802`0f425cee : 00000000`00000100 ffff8801`b1ccdef0 00000000`00000000 00000000`00000000 : nt!KxNmiInterrupt+0x82
ffff8801`b1ccde70 fffff802`0ab20003 : fffff802`0f3cb587 fffff802`0f3c6920 fffff802`0f2df5d8 00000000`00000000 : nt!KiNmiInterrupt+0x26e
ffffcc8d`c4aa74c8 fffff802`0f3cb587 : fffff802`0f3c6920 fffff802`0f2df5d8 00000000`00000000 fffff802`0f2e3a7d : 0xfffff802`0ab20003
ffffcc8d`c4aa74d0 fffff802`0f544355 : 00000000`00000001 fffff802`0f3c693b 00000006`88db5b3b 00000000`00000000 : nt!HvcallInitiateHypercall+0x57
ffffcc8d`c4aa7550 fffff802`38239d5d : 00000000`000100de fffff802`0f2df5d8 ffffbc84`f5ce5168 fffff802`0f2da237 : nt!HvlRequestProcessorHalt+0x35
ffffcc8d`c4aa7580 fffff802`382318d3 : 00000000`00000000 00000000`00000001 ffffbc84`f5ce5168 00000000`00000000 : amdppm!HvRequestIdle+0x2d
ffffcc8d`c4aa75d0 fffff802`0f2e1456 : 00000000`00000000 ffff8801`b1c91180 00000000`00000000 ffff8801`b1c91180 : amdppm!AcpiCStateIdleExecute+0x23
ffffcc8d`c4aa7600 fffff802`0f2e0fcb : ffffbc84`f5ce5718 00000000`00000000 00000000`ffffffff ffffcc8d`c4aa7ab0 : nt!PpmIdleExecuteTransition+0x426
ffffcc8d`c4aa7a50 fffff802`0f41cf44 : 00000000`00000000 ffffbc84`ee35a040 ffffbc84`f9150080 ffffbc85`0050b080 : nt!PoIdle+0x68b
ffffcc8d`c4aa7c40 00000000`00000000 : ffffcc8d`c4aa8000 ffffcc8d`c4aa2000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x54
SYMBOL_NAME: amdppm!HvRequestIdle+2d
MODULE_NAME: amdppm
IMAGE_NAME: amdppm.sys
IMAGE_VERSION: 10.0.22621.3593
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 2d
FAILURE_BUCKET_ID: 0x20001_11_2f4152_amdppm!HvRequestIdle
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {8420b585-745b-2d4d-14e5-01d3ca4497c4}
Followup: MachineOwner
---------

Reply
Reply
L
LatinGuyGamer
Junior Member
Find
8
12-25-2025, 10:28 AM
#2
Thank you for the suggestion. I'll give it a shot. I've already disabled virtualization by turning off SVM in the BIOS (this resolved HYPERVISOR crashes but not others like PAGE_FAULT). Now I'm considering leaving SVM on in the BIOS and disabling it through PowerShell. I'll share my experience after trying it out for a while.
Reply
Reply
L
LatinGuyGamer
12-25-2025, 10:28 AM #2

Thank you for the suggestion. I'll give it a shot. I've already disabled virtualization by turning off SVM in the BIOS (this resolved HYPERVISOR crashes but not others like PAGE_FAULT). Now I'm considering leaving SVM on in the BIOS and disabling it through PowerShell. I'll share my experience after trying it out for a while.

Reply
Reply
M
MegaDisco
Senior Member
Find
352
12-25-2025, 10:28 AM
#3
I am using Windows 11 home and discovered the command
Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-Hypervisor
only functions on Windows 11 Pro. But a different script successfully disables Hyper-V in Windows 11 home via a standard admin prompt.
Reply
Reply
M
MegaDisco
12-25-2025, 10:28 AM #3

I am using Windows 11 home and discovered the command
Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-Hypervisor
only functions on Windows 11 Pro. But a different script successfully disables Hyper-V in Windows 11 home via a standard admin prompt.

Reply
Reply
S
shanleighrose
Member
Find
181
12-25-2025, 10:29 AM
#4
That is indeed part of Windows. It may seem like it comes from AMD, but it belongs to Windows Power Management. You should follow option one on the provided link. Then proceed with the steps below: Small memory dumps – Windows will generate a small memory dump during a BSOD, creating a file in C:\Windows\Minidump after the next crash. Open Windows File Explorer, go to C:\Windows\Minidump, move the mini-dump files to your Desktop. Avoid using Winzip; use the built-in feature in Windows instead. Select the files on your Desktop, right-click and choose 'Send to' – Compressed (zipped) folder. Upload the resulting zip file to the cloud (OneDrive, Dropbox, etc.). Share the link to the zip file so we can review it together. A page fault might indicate a driver issue.
Reply
Reply
S
shanleighrose
12-25-2025, 10:29 AM #4

That is indeed part of Windows. It may seem like it comes from AMD, but it belongs to Windows Power Management. You should follow option one on the provided link. Then proceed with the steps below: Small memory dumps – Windows will generate a small memory dump during a BSOD, creating a file in C:\Windows\Minidump after the next crash. Open Windows File Explorer, go to C:\Windows\Minidump, move the mini-dump files to your Desktop. Avoid using Winzip; use the built-in feature in Windows instead. Select the files on your Desktop, right-click and choose 'Send to' – Compressed (zipped) folder. Upload the resulting zip file to the cloud (OneDrive, Dropbox, etc.). Share the link to the zip file so we can review it together. A page fault might indicate a driver issue.

Reply
Reply
_
_UnicornMen_
Member
Find
70
12-25-2025, 10:29 AM
#5
The Windows Hypervisor operates separately from Hyper-V, even though they share the same underlying technology. I would prefer to view the dump file instead of just analyzing the output (which only covers a part of the dump analysis). There’s a significant hint in the information you shared...
Reply
Reply
_
_UnicornMen_
12-25-2025, 10:29 AM #5

The Windows Hypervisor operates separately from Hyper-V, even though they share the same underlying technology. I would prefer to view the dump file instead of just analyzing the output (which only covers a part of the dump analysis). There’s a significant hint in the information you shared...

Reply
Reply
F
Fliixyzz
Junior Member
Find
31
12-25-2025, 10:29 AM
#6
Thank you for your response; please accept my apologies for the delay. I plan to reset the BIOS as recommended earlier. As you mentioned, I initially thought amdppm.sys was an AMD driver without verifying it. Unfortunately, the original dump file was accidentally deleted by CCleaner. Despite this, I experienced another Hypervisor BSOD last night and shared the DropBox link below. I’m hoping it will open properly!
Reply
Reply
F
Fliixyzz
12-25-2025, 10:29 AM #6

Thank you for your response; please accept my apologies for the delay. I plan to reset the BIOS as recommended earlier. As you mentioned, I initially thought amdppm.sys was an AMD driver without verifying it. Unfortunately, the original dump file was accidentally deleted by CCleaner. Despite this, I experienced another Hypervisor BSOD last night and shared the DropBox link below. I’m hoping it will open properly!

Reply
Reply
I
iTzPandaNuss
Member
Find
144
12-25-2025, 10:29 AM
#7
ccleaner often has a bad tendency to erase important data.
Reply
Reply
I
iTzPandaNuss
12-25-2025, 10:29 AM #7

ccleaner often has a bad tendency to erase important data.

Reply
Reply
K
Kaito22333
Junior Member
Find
2
12-25-2025, 10:29 AM
#8
- Hi - I've downloaded the AMD updated drivers and installed them, and I also set up the AMD Power Plan. I plan to wait a few days to check if this improves stability. If it doesn't, I'll revisit disabling C-states but, initially, I couldn't find an option in the MSI Tomahawk B450 Max BIOS.
Reply
Reply
K
Kaito22333
12-25-2025, 10:29 AM #8

- Hi - I've downloaded the AMD updated drivers and installed them, and I also set up the AMD Power Plan. I plan to wait a few days to check if this improves stability. If it doesn't, I'll revisit disabling C-states but, initially, I couldn't find an option in the MSI Tomahawk B450 Max BIOS.

Reply
Reply
S
Skulhead2a
Member
Find
210
12-25-2025, 10:29 AM
#9
Following the download of the AMD drivers and power plan, the system remained unresponsive, sometimes triggering a BSOD crash and frequently displaying a HYPERVISOR_ERROR. I reviewed the BIOS settings for C_states and found they were already turned off. Out of interest, I reactivated them, expecting compatibility between the AMD drivers and power plan and C_states, but this caused the system to become unstable, resulting in four BSOD crashes within 15 minutes. Therefore, I removed all AMD driver updates, including the power plan, and disabled both SVM and C_states in the BIOS. It might have been better to proceed gradually to pinpoint the issue, but stability was my main goal. Noting that Power Plans could be linked to the crashes, I enabled Ultimate Performance via PowerShell with the command 'powercfg -duplicatescheme e9a42b02-d5df-448d-aa00-03f14749eb61', which stops the PC from sleeping. So far this has led to a more stable system without BSODs. However, further testing is needed to confirm the problem is resolved.

PS - I consulted co-pilot who suggested it could be related to Windows 11, a relatively new OS. I suspect Microsoft would attribute this view to CoPilot rather than the company itself.
Reply
Reply
S
Skulhead2a
12-25-2025, 10:29 AM #9

Following the download of the AMD drivers and power plan, the system remained unresponsive, sometimes triggering a BSOD crash and frequently displaying a HYPERVISOR_ERROR. I reviewed the BIOS settings for C_states and found they were already turned off. Out of interest, I reactivated them, expecting compatibility between the AMD drivers and power plan and C_states, but this caused the system to become unstable, resulting in four BSOD crashes within 15 minutes. Therefore, I removed all AMD driver updates, including the power plan, and disabled both SVM and C_states in the BIOS. It might have been better to proceed gradually to pinpoint the issue, but stability was my main goal. Noting that Power Plans could be linked to the crashes, I enabled Ultimate Performance via PowerShell with the command 'powercfg -duplicatescheme e9a42b02-d5df-448d-aa00-03f14749eb61', which stops the PC from sleeping. So far this has led to a more stable system without BSODs. However, further testing is needed to confirm the problem is resolved.

PS - I consulted co-pilot who suggested it could be related to Windows 11, a relatively new OS. I suspect Microsoft would attribute this view to CoPilot rather than the company itself.

Reply
Reply
D
Dan15432
Member
Find
68
12-25-2025, 10:29 AM
#10
Two things come to mind...
It's well worth checking the CPU BIOS entries to make sure that everything is standard. Unless you have good reason most items should be set to Auto. Question any setting that you can't explain.
Try
starting Windows in Safe Mode
and see whether it will BSOD in that state.
Reply
Reply
D
Dan15432
12-25-2025, 10:29 AM #10

Two things come to mind...
It's well worth checking the CPU BIOS entries to make sure that everything is standard. Unless you have good reason most items should be set to Auto. Question any setting that you can't explain.
Try
starting Windows in Safe Mode
and see whether it will BSOD in that state.

Reply
Reply
Pages (2): 1 2 Next