Windows 11 stuck after start enter to sleep mode

Hi ArieLub

Welcome to Microsoft Community.

Based on your description, I understand how you feel when your computer goes into sleep mode and the monitor shuts off but the fan and keyboard are still working and it eventually triggers a BSOD and power outage!

From the text description you provided and the information in the dmp file section that WinDbg and analyzed, the error code is 0x9F, which is usually related to device driver or hardware related issues, especially ACPI (Advanced Configuration and Power Interface) related devices.

The following are possible causes of the problem.

1. A device driver may be incompatible or faulty, especially those related to power management (e.g. pci.sys).

2. Some hardware components may be faulty or conflicting, causing the system to fail to process properly when it enters sleep mode.

3. Power management settings may be incorrect, causing the system to fail to properly enter sleep mode.

4. Windows updates or driver updates may have introduced instability.

I will give you some suggestions and troubleshooting options to hopefully resolve your issue or find the cause of the problem! However, this is a first reply as this issue requires different aspects of troubleshooting, so please understand and provide more information (pictures would be great!) in your reply. Thank you very much!

Option 1: Considering that this issue could be caused by a driver that is not fully compatible with the system or a corrupted driver that is causing the problem.

We have tried to update or manually install the drivers for all devices, especially graphics cards, network adapters, BIOS, chipsets, and power management related devices.

1. Update Driver

“WIN + x” to select ‘Device Manager’ -> find your corresponding device -> right-click on the device and select ‘Update Driver’ -> ‘Automatically search for updated drivers’.

2. Install generic driver

Also in Device Manager -> Right-click on the device and select “Remove Device” (if there is one, please make sure “Remove Driver” is checked) -> After restarting the computer, the system will automatically search for and install the universal driver.

3. Manual driver installation

The driver involves the following situations:

(1) If you are a laptop, you can download the driver for the corresponding laptop model through the brand's official website.

(2) If you have a desktop computer, you can download the driver for the corresponding model through the official website of the motherboard brand.

(3) You can also download the driver for the corresponding model through the device manufacturer's website.

Please note: Please try the latest version of the driver as a priority, assuming the problem still exists, we can try some known older and more compatible versions.

4. For discrete graphics cards, I personally recommend the manual installation method.

First of all, we can use DDU tool (Display Driver Uninstaller) to completely uninstall the current graphics card driver, and then download the latest version of the driver from the official website of the graphics card manufacturer and install it.

The main reason for using the DDU tool is to prevent file and registry leftovers, which may cause driver conflicts or problems that may still exist.

Again, if the latest version of the driver still has problems, we can try to install some known older and more compatible versions.

Option 2: Check and adjust power settings.

1. Turn off the link state power management.

Click “WIN key” to open the search bar -> Enter “Control Panel” and open it -> Under “Large icons”, select “Power Options” -> Click “Change plan settings” on the right side of the power plan you are using -> “Change advanced power setting” -> “Change power settings”. settings” -> ”Change advanced power settings”

In the popup window, find and expand PCI Express -> Make sure “Link State Power Management” is set to “Off”.

2. Turn off fastboot.

In “Power Options”, select “Choose what the power buttons do” on the left sidebar -> Make sure “Turn on fast startup” is unchecked.

Option 3: Please try to clean boot your computer.

Since clean boot only uses a limited set of files and drivers, it can help us to effectively troubleshoot the possibility of problems caused by third-party applications, driver conflicts, etc.

You can refer to Clean Boot for more information: How to perform a clean boot in Windows - Microsoft Support

After clean boot, please slide down the webpage after opening the link and find “How to determine what is causing the problem after you do a clean boot” This is a dichotomy that can help us pinpoint the service that is causing the problem and disable it.

When testing the dichotomy, we can try to enter sleep mode to see if there may be some driver or third-party application service that is affecting the proper functioning of sleep mode.

Disclaimer: A “clean boot” starts Windows with a minimal set of drivers and startup programs. It helps to determine whether a background service is interfering with your game or program and to isolate the cause of a problem. These steps of "clean boot" might look complicated at first glance. However, to avoid any trouble for you, please follow them in order and step-by step so that it will help you get back on track.

Option 4: If the problem is recent and sudden and started after some update.

We can try to uninstall the update or restore the system to before the problem occurred via a restore point.

1. Check for and uninstall updates.

Open Settings with “WIN + i” -> on the left sidebar select “Windows Update” -> “Update history” -> “Uninstall updates”.

Check if there are any system updates from around the time the problem first occurred, if there are we try to uninstall them.

2. If necessary, we can also restore the system to a point before the problem occurred via a restore point.

You can refer to Restore Points to restore your system: System Restore - Microsoft Support

Please note: Restore Point Restore System will not delete your personal files and data, but it will delete third party applications, drivers and Windows Update installed after the restore point time.

Option 5: Sometimes it is possible that the system is unable to handle sleep mode properly due to the corruption or loss of some system files.

To avoid this, we try to repair the system completely in two ways, at least to make sure that the problem is not due to system corruption.

1. Scan and repair the system from the command line.

Click on “Windows Logo Key” to open the search bar -> Type “cmd” in the search bar and open it with administrator privileges -> Please enter the following commands

DISM /Online /Cleanup-Image /ScanHealth

DISM /Online /Cleanup-Image /CheckHealth

DISM /Online /Cleanup-Image /RestoreHealth

SFC /Scannow

Please note: The above commands need to be repeated 5~6 times to ensure the completeness of the scan!

2. Please try the non-destructive repair.

The steps are:

(1) First download the ISO image file of Windows 11 via the following link.

The link is: Download Windows 11

(2) After the ISO file is downloaded, double-click it to open and run “setup.exe”.

(3) Under the “Install Windows 11” screen, select “Change how the installer downloads updates”.

(4) Under the “Get Updates, Drivers, and Optional Features” screen, select “Not Now”.

(5) Follow the instructions to continue.

Please note: If you are prompted to enter a key, the downloaded ISO image file does not match the current system version.

(6) Under the “Select what to keep” screen, please make sure to select “Keep personal files and applications” so that the contents of your computer will not be affected or lost.

(7) Start the non-destructive repair.

Option 6: This issue may also be caused by a hardware component failure or conflict. Assuming that a similar situation occurs, it will result in the hardware component not being able to be stopped successfully, even though the system is in sleep mode and the screen is turned off.

1. If you have some knowledge about hardware, we can disassemble the computer and check if all hardware components (e.g. RAM, video card, etc.) are firmly installed.

If necessary, we can try replacing the slots or re-plugging the hardware to test.

2. We also need to diagnose the hardware and check for faults.

I'll use the RAM troubleshooting as an example, you can follow this step to diagnose other hardware (hard disk, video card, etc.).

(1) Start with a preliminary diagnosis of the system through the system's built-in memory diagnostic tool, although many errors cannot be detected by the built-in tool.

Click “WIN key” to open the search bar -> type “Windows Memory Diagnostic” and open it with administrator privileges -> complete it according to the guide.

(2) We can also use some third-party tools for more in-depth hardware diagnostics. (This step is also applicable to diagnose other hardware)

Due to community rules, I can't provide you with specific third-party tools, you can use Github, Reddit and other technical communities to check the relevant information, and choose a reliable and safe third-party tools.

(3) For memory sticks, I have another way of troubleshooting on a physical level.

Currently a computer usually has multiple memory sticks inserted, at this point we can try to remove all the other sticks and keep only one for testing to see if the problem still exists.

Repeat this step to make sure to individually troubleshoot all memory sticks with all memory slots.

Option 7: You can also access the Event Viewer to check for power management, driver, and sleep mode related error messages.

“WIN + x” select “Event Viewer”

This information can help give us more clues or even a breakthrough in solving the problem.

If you are able to send me the dmp file, I will analyze it in depth on my private computer to see exactly what modules may be causing the blue screen with the problem and give you the conclusions from my analysis.

You can upload the dmp file to a cloud drive (e.g. OneDrive, Google Drive, etc.) and include the file sharing link in your reply.

I sincerely hope that the above information and programs will help you! Please feel free to contact me (Photos related to the question would be great!).

I look forward to hearing back from you. 

Best Regards

Arthur Sheng | Microsoft Community Support Specialist

Great,

Now I'm doing the option 5.1, but It still didn't find any integrity violations.

Option 4 isn't relevant.

Option 6, about potencial RAM corruption, I don't think it's a problem.

So, we need to find the problematic driver to cure it.

The dump file, I'll be happy for depth analysis to find the root problem:

I also supply a sleep study report from last 28 days (it's maximum possible):

From it, you can see that I enter my computer to sleep every night before I go to sleep. :)

And something, after fews days from the last reboot, it stuck, then I rebooted.

Just last time when it happened, I waited instead to reboot to see what would happen in the process.

Thank you for your response.

Some updates may cause some compatibility issues resulting in abnormal sleep mode, so if necessary we can check Option 4 and uninstall some updates.

I downloaded your sleep report and analyzed it in depth, but the dmp file I keep opening keeps prompting an error report or permission error.

From the sleep report you provided, I can see that there are multiple “Abnormal Shutdown” and “Bugcheck” events, which suggests that the system is experiencing serious issues when entering sleep mode or waking up from sleep.

I will describe for you a part of the results of my analysis.

1. Abnormal Shutdown

There are multiple “Abnormal Shutdown” records in the report that indicate that the system did not exit sleep or shutdown normally, but that an error occurred.

These records do not show a clear reason for the exit, usually this is due to the system not being able to successfully enter sleep mode or resume from sleep.

2. Bugcheck

At some point on December 22, 2024, there was a “Bugcheck” event in the report, which usually means that the system encountered a blue screen error (such as the 0x9F error you describe). This is often related to a hardware, driver, or power management related conflict.

3. Power State and Energy Change vary widely from event to event, which indicates a possible problem with battery management, especially when the battery is low (e.g., a sleep event occurring while charging at 100%), which may result in the device not being able to handle sleep state transitions.

Based on the information reported, I have some suggestions as follows.

1. Although the report mentions missing battery charging information, if there is an issue with the battery, it may prevent the system from shutting down or rebooting properly. Try unplugging the power adapter and running on battery only to see if the same shutdown issue occurs. If the problem persists, you may want to consider replacing the battery or adapter.

2. Due to the repeated occurrence of “Abnormal Shutdown”, there may be a problem with your power settings or related drivers. Make sure you have installed the latest power management drivers, especially for battery management and power options. Also, check the power settings, especially the configuration of Sleep Mode and Hibernate Mode.

3. If the system does not resume correctly while in hibernation or standby, check the system's Event Viewer logs for other hardware-related errors, especially battery, power button, or hard disk errors. This may help pinpoint the problem more precisely.

4. If the problem is recurring, it is recommended that you use a hardware diagnostic tool to perform a thorough check of the battery, memory, and hard disk to ensure that there are no hardware problems.

Finally, regarding the change in battery capacity when your device enters the “Abnormal Shutdown” state, check to see if you have ever had a sudden power failure when the system was low. Even if the battery appears to be fully charged, there may be a problem with the charge management of the battery itself.

I sincerely hope that the above information can help you! But from the information in the report, you should have a laptop, as there is a lot of information and details related to laptops.

If necessary, we can contact the branded after-sales or technical support team of the laptop, who are more familiar with their branded products and may have other users who have reported similar problems. Perhaps they have already written a tool to fix the problem or a more targeted program. It is best to have the laptop brand's after-sales or technical support staff assist in troubleshooting remotely or offline, especially for battery and power-related parts.

Oops, I forgot to say that my computer is a desktop with UPS and not a laptop.

1. These abnormal shutdown, mostly I do manual every time when it's stuck (keyboard and fans still on).

2. Bugcheck, little old for a very short period, not relevant.

So, mostly what you write for laptops aren't relevant.

Thanks for the clarification.

I have therefore adapted some of the suggestions to your situation.

1. You mentioned that you manually shut down the system every time it gets stuck, this could be caused by a power supply unit (PSU) issue. An unstable or underpowered PSU, especially at high loads, can cause the system to fail to operate properly, resulting in an abnormal shutdown. Even if the UPS is in use, it may not be able to fully compensate for the effects of a power supply problem. If the power supply becomes aged or underpowered after a long period of time, it may not be able to supply power stably during high power demands (such as when gaming or multitasking operations are in progress), which can cause the system to jam or shut down.

(1) Check the power loading capacity of the power supply to ensure that the power supply is able to provide sufficient power for all hardware. You can do this by checking the power rating provided on the label of the power supply against the actual demand of your system.

(2) Check the health of the power supply to see if there is any overheating, fan not spinning, etc. You can use some power supply testing tools to check the stability of the power supply output.

(3) Consider replacing the power supply if it has been in use for many years, especially if you haven't done a replacement, aging problems with power supplies are more common.

2. You mention that this problem is older and short-lived, so it may be less relevant, but Bugcheck errors are usually caused by hardware conflicts, driver problems, memory issues, or power management problems. Even if this problem no longer occurs frequently, it can still be a sign of system instability, especially related to hardware or driver compatibility issues.

(1) Update hardware drivers, especially for important hardware such as graphics cards, motherboard chipsets, and network adapters. Driver updates not only resolve potential bugcheck issues, but also improve hardware performance and stability.

If necessary, we need to install known older and more compatible versions.

(2) If you suspect a power supply related blue screen error, it is recommended to check whether the voltage output of the power supply is stable or not, you can use a hardware monitoring tool to check the voltage changes.

(3) I still personally recommend that you can use MemTest86 to check for memory issues, although this does have a very small probability of occurring, as in the case you mentioned, I still personally recommend checking it to at least rule out this aspect.

3. Although desktop computers do not involve battery problems, UPS may also affect the stability of the system. voltage fluctuation of the UPS or aging problems of the batteries may result in unstable power supply to the system, especially when the batteries are low or the loads are high. the power ratings of the UPS may be mismatched, or the batteries of the UPS may have aging problems, which may also result in unstable power supply.

(1) Check the health condition of the UPS, especially whether the UPS battery is normal. If the battery is aged, it may not be able to provide stable power support.

(2) Confirm whether the power rating of the UPS can meet the power demand of your desktop computer. If the UPS is unable to provide sufficient power, it is recommended to consider replacing it with a higher power UPS to ensure that the stable operation of your desktop will not be affected during power outages or voltage fluctuations.

4. Hardware problems are one of the common root causes of both blue screen errors and abnormal shutdowns. A faulty hard disk, memory or graphics card may cause your system to stall, crash or become unrecoverable. Using a hardware diagnostic tool can help you better identify if there is a hardware problem.

(1) Run a hardware diagnostic tool such as CrystalDiskInfo to check the health of your hard disk, or use MemTest86 to check for memory errors. If the problem is with the graphics card or other hardware, you may need to test it with some specialized tools.

(2) If you suspect a hard disk problem, consider backing up your data and performing a disk scan to check for bad sectors or other physical failures on the disk.

5. You can check the detailed system logs through the Event Viewer, especially the error logs about hardware such as power supply, hard disk, memory, etc. Bugcheck errors, hard disk errors, driver errors, etc. may be recorded in the logs.

For your desktop's problems, the most critical ones are power supply related issues, especially the stability of the power supply unit (PSU) and UPS. Hardware drivers, memory checks, and system log analysis can also help to better troubleshoot the problem. If the power issues are resolved, the stability of the system may be greatly improved.

Assuming that the problem still exists, I would also recommend that you synchronize the issue with the hardware brand's after-sales or technical support team, preferably with professional tools or instruments to perform different aspects of the test, and then help you detect the problem more accurately, especially for hardware-related troubleshooting such as power supply and UPS.

I sincerely hope that the above information can help you!

OK, after three week since I've updated the BIOS to a new version, it's seen that resolve the problem.

Update:
Few days after it, the problem came back and appeared almost everyday!

I've run "verifier /standard /all /bootmode resetonbootfail" for try findind the problematic drivers.

This analized minidump of it's BSOD:

************* Preparing the environment for Debugger Extensions Gallery repositories **************
   ExtensionRepository : Implicit
   UseExperimentalFeatureForNugetShare : true
   AllowNugetExeUpdate : true
   NonInteractiveNuget : true
   AllowNugetMSCredentialProviderInstall : true
   AllowParallelInitializationOfLocalRepositories : true
   EnableRedirectToChakraJsProvider : 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.313 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 42

Microsoft (R) Windows Debugger Version 10.0.27725.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Primary dump contents written successfully


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 22621 MP (24 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 22621.1.amd64fre.ni_release.220506-1250
Kernel base = 0xfffff800`6c41e000 PsLoadedModuleList = 0xfffff800`6d031510
Debug session time: Tue Feb 18 21:16:49.909 2025 (UTC + 2:00)
System Uptime: 0 days 0:00:20.972
Loading Kernel Symbols
...............................................................
................Page 20adf5c not present in the dump file. Type ".hh dbgerr004" for details
.............................................
Loading User Symbols

Loading unloaded module list
......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`6c832c00 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffffa82`a0007310=00000000000000c4
23: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, BugChecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000000062, A driver has forgotten to free its pool allocations prior to unloading.
Arg2: ffffe70f178fa3e8, name of the driver having the issue.
Arg3: ffffe70f182f8d60, verifier internal structure with driver information.
Arg4: 0000000000000002, total # of (paged+nonpaged) allocations that weren't freed.
	Type !verifier 3 drivername.sys for info on the allocations
	that were leaked that caused the bugcheck.

Debugging Details:
------------------

Unable to load image \SystemRoot\system32\DRIVERS\aehd.sys, Win32 error 0n2

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 500

    Key  : Analysis.Elapsed.mSec
    Value: 2431

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 1

    Key  : Analysis.IO.Write.Mb
    Value: 0

    Key  : Analysis.Init.CPU.mSec
    Value: 125

    Key  : Analysis.Init.Elapsed.mSec
    Value: 3607

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 107

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27725.1000

    Key  : Analysis.Version.Description
    Value: 10.2408.27.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2408.27.1

    Key  : Bugcheck.Code.KiBugCheckData
    Value: 0xc4

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xc4

    Key  : Bugcheck.Code.TargetModel
    Value: 0xc4

    Key  : Dump.Attributes.AsUlong
    Value: 1800

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 100

    Key  : Failure.Bucket
    Value: 0xc4_62_VRF_LEAKED_POOL_IMAGE_aehd.sys

    Key  : Failure.Hash
    Value: {6580dc7e-71cb-505f-892f-104712ea8401}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 1417df84

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 1

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 1

    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: 21631230

    Key  : Hypervisor.Flags.ValueHex
    Value: 14a10fe

    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

    Key  : SecureKernel.HalpHvciEnabled
    Value: 1

    Key  : WER.OS.Branch
    Value: ni_release

    Key  : WER.OS.Version
    Value: 10.0.22621.1


BUGCHECK_CODE:  c4

BUGCHECK_P1: 62

BUGCHECK_P2: ffffe70f178fa3e8

BUGCHECK_P3: ffffe70f182f8d60

BUGCHECK_P4: 2

FILE_IN_CAB:  MEMORY.DMP

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


DUMP_FILE_ATTRIBUTES: 0x1800

FAULTING_THREAD:  ffffe70efc711040

IMAGE_NAME:  aehd.sys

MODULE_NAME: aehd

FAULTING_MODULE: fffff80a1c920000 aehd

VERIFIER_DRIVER_ENTRY: dt nt!_MI_VERIFIER_DRIVER_ENTRY ffffe70f182f8d60
Symbol nt!_MI_VERIFIER_DRIVER_ENTRY not found.

BLACKBOXNTFS: 1 (!blackboxntfs)


PROCESS_NAME:  System

STACK_TEXT:  
fffffa82`a0007308 fffff800`6c9f06fb     : 00000000`000000c4 00000000`00000062 ffffe70f`178fa3e8 ffffe70f`182f8d60 : nt!KeBugCheckEx
fffffa82`a0007310 fffff800`6c9ef337     : 00000000`c000018f fffff800`6c850690 fffff800`6c850690 00000000`00000000 : nt!CarInitiateBugcheck+0x47
fffffa82`a0007350 fffff800`6cee733c     : 00000000`000000c4 00000000`00000002 000000d9`00010200 00000000`00000001 : nt!CarReportRuleViolationForTriage+0x147
fffffa82`a00073d0 fffff800`6cef40c8     : ffffe70f`182f8d60 fffffa82`a0007520 ffffe70f`178fa240 ffffe70f`160fdac0 : nt!VerifierBugCheckIfAppropriate+0xc8
fffffa82`a0007470 fffff800`6c8d51f9     : ffffe70f`182f8d60 00000000`00000001 00000000`00000001 ffffe70f`160fdaa0 : nt!VfPoolCheckForLeaks+0x4c
fffffa82`a00074b0 fffff800`6ced724e     : 00000000`00277000 ffffe70f`178fa240 fffff800`6d054e90 fffff800`6d054e90 : nt!VfTargetDriversRemove+0x1a1cb1
fffffa82`a0007530 fffff800`6cb5d3a2     : ffffe70f`178fa240 fffffa82`a0007660 00000000`ffffffff 00000000`00000001 : nt!VfDriverUnloadImage+0x3e
fffffa82`a0007560 fffff800`6cbfe191     : ffffe70f`00000001 00000000`ffffffff 00000000`00000277 ffff9d7c`050e4900 : nt!MiUnloadSystemImage+0x322
fffffa82`a0007740 fffff800`6cc78ae0     : ffffe70f`1654fce0 fffffa82`a0007960 00000000`00000000 ffffe70f`1654fd10 : nt!MmUnloadSystemImage+0x41
fffffa82`a0007770 fffff800`6cae263e     : ffffe70f`1654fce0 ffffe70f`1654fce0 ffff848b`5ccae350 ffffe70f`1654fce0 : nt!IopDeleteDriver+0x40
fffffa82`a00077c0 fffff800`6c689e83     : 00000000`00000000 00000000`00000000 fffffa82`a0007960 ffffe70f`1654fd10 : nt!ObpRemoveObjectRoutine+0x7e
fffffa82`a0007820 fffff800`6cb90a32     : ffffe70f`18995000 00000000`c0000365 00000000`00000600 00000000`00001000 : nt!ObfDereferenceObject+0x93
fffffa82`a0007860 fffff800`6cf724a7     : ffffe70f`178f15c0 ffffe70f`178f15c0 fffffa82`a0007a90 00000000`00000000 : nt!IopLoadDriver+0x786
fffffa82`a0007a20 fffff800`6cf78c42     : fffff800`ffffffa1 ffff848b`5cc5cb90 00000000`00000000 fffff800`697f8dc0 : nt!IopInitializeSystemDrivers+0x157
fffffa82`a0007ac0 fffff800`6cc200bb     : fffff800`6cc20080 fffff800`6d07bb14 fffff800`6cc20080 fffff800`697f8dc0 : nt!IoInitSystem+0x52
fffffa82`a0007af0 fffff800`6c76b207     : ffffe70e`fc711040 fffff800`6cc20080 fffff800`697f8dc0 00000000`00000000 : nt!Phase1Initialization+0x3b
fffffa82`a0007b30 fffff800`6c837d74     : fffff800`69b69180 ffffe70e`fc711040 fffff800`6c76b1b0 00000000`00000000 : nt!PspSystemThreadStartup+0x57
fffffa82`a0007b80 00000000`00000000     : fffffa82`a0008000 fffffa82`a0001000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


IMAGE_VERSION:  2.2.0.0

STACK_COMMAND:  .process /r /p 0xffffe70efc79d040; .thread 0xffffe70efc711040 ; kb

FAILURE_BUCKET_ID:  0xc4_62_VRF_LEAKED_POOL_IMAGE_aehd.sys

OS_VERSION:  10.0.22621.1

BUILDLAB_STR:  ni_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {6580dc7e-71cb-505f-892f-104712ea8401}

Followup:     MachineOwner
---------