This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hello,
We recently upgraded to Windows 11 24H2. After the successful upgrade, our laptops blue screen multiple times a day. The issue happens when the laptops are docked or undocked and one of the triggers seems to be when the computer sleeps or wakes up. The PROCESS_NAME listed in the dump file varies.
We upgraded BIOS, firmware, and all drivers to the latest available from Lenovo and Intel.
I do not have much experience troubleshooting using dump files. Any help would be greatly appreciated.
Events before the crash frequently logs event 506 The system is exiting Modern Standby.
</Event>
C:\WINDOWS\Minidump\100424-20500-01.dmp
************* 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.031 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 42
Microsoft (R) Windows Debugger Version 10.0.27704.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\100424-20500-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 26100 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff807af600000 PsLoadedModuleList = 0xfffff807b04f4770
Debug session time: Fri Oct 4 14:31:50.227 2024 (UTC - 6:00)
System Uptime: 0 days 2:17:09.770
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000d8`1a740018). Type ".hh dbgerr001" for details
Loading unloaded module list
......................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff807afab8b00 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffffc078fb35690=000000000000003b
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the BugCheck
Arg2: fffff80744462c2e, Address of the instruction which caused the BugCheck
Arg3: fffffc078fb35fd0, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.
Debugging Details:
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 3125
Key : Analysis.Elapsed.mSec
Value: 8668
Key : Analysis.IO.Other.Mb
Value: 14
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 26
Key : Analysis.Init.CPU.mSec
Value: 687
Key : Analysis.Init.Elapsed.mSec
Value: 43029
Key : Analysis.Memory.CommitPeak.Mb
Value: 96
Key : Analysis.Version.DbgEng
Value: 10.0.27704.1001
Key : Analysis.Version.Description
Value: 10.2408.27.01 amd64fre
Key : Analysis.Version.Ext
Value: 1.2408.27.1
Key : Bugcheck.Code.LegacyAPI
Value: 0x3b
Key : Bugcheck.Code.TargetModel
Value: 0x3b
Key : Dump.Attributes.AsUlong
Value: 21808
Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1
Key : Dump.Attributes.ErrorCode
Value: 0
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Dump.Attributes.LastLine
Value: Dump completed successfully.
Key : Dump.Attributes.ProgressPercentage
Value: 0
Key : Failure.Bucket
Value: AV\_dam!DampExemptCheckCallbackRoutine
Key : Failure.Hash
Value: {b11d9680-dc31-478c-63cd-1d0eaa74fac4}
Key : Hypervisor.Enlightenments.ValueHex
Value: 7417df84
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: 55185662
Key : Hypervisor.Flags.ValueHex
Value: 34a10fe
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: 3b
BUGCHECK_P1: c0000005
BUGCHECK_P2: fffff80744462c2e
BUGCHECK_P3: fffffc078fb35fd0
BUGCHECK_P4: 0
FILE_IN_CAB: 100424-20500-01.dmp
TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b
DUMP_FILE_ATTRIBUTES: 0x21808
Kernel Generated Triage Dump
FAULTING_THREAD: ffffac05d31c7080
CONTEXT: fffffc078fb35fd0 -- (.cxr 0xfffffc078fb35fd0)
rax=fffff8074445d170 rbx=0000000000000000 rcx=fffff8074445d170
rdx=0000000000000000 rsi=ffffac05ae6f2e78 rdi=0000000000000000
rip=fffff80744462c2e rsp=fffffc078fb36a20 rbp=fffffc078fb36ac9
r8=0000000000000000 r9=0000000000000004 r10=fffff807af81d8b0
r11=0000000000400000 r12=fffffc078fb36ba8 r13=0000000000000001
r14=0000000000000000 r15=ffffffffffffffff
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050246
dam!DampExemptCheckCallbackRoutine+0x17e:
fffff80744462c2e 488b17 mov rdx,qword ptr [rdi] ds:002b:0000000000000000=????????????????
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: taskhostw.exe
STACK_TEXT:
fffffc078fb36a20 fffff807afa17277 : ffffac05b1c76d50 fffff807aff7501e 0000000000000000 0000000000000000 : dam!DampExemptCheckCallbackRoutine+0x17e
fffffc078fb36b30 fffff80741d93eae : ffffe004991de890 0000000000000011 ffffe0046de43050 0000000000000000 : nt!ExNotifyCallback+0xb7
fffffc078fb36b70 fffff80741d93a83 : ffffffff003a0002 0000000000000000 ffffe004991de890 ffffac05b17b3080 : pdc!PdcpInitializeClientOwnershipMask+0xba
fffffc078fb36ba0 fffff80741d8fb1f : 0000000000000011 0000000000000003 ffffac05b17b3080 fffffc078fb36cf0 : pdc!PdcSuspendResumeClientInitialize+0x10b
fffffc078fb36c00 fffff80741d8f2d1 : 0000000000000030 fffffc078fb36d50 0000000000000000 ffffac05aea4ecb0 : pdc!PdcAllocateUserClient+0x19b
fffffc078fb36c50 fffff80741d8f8b4 : ffffac05ae9fc001 fffffc078fb371a0 ffffac05ae9fc001 ffffac05ae9e03c8 : pdc!PdcProcessMessage+0x199
fffffc078fb370a0 fffff80741d8f129 : ffffac05ae9fc090 ffffac05ae9e03d0 0000000000000000 00000000000000f8 : pdc!PdcpAlpcProcessMessages+0x94
fffffc078fb374e0 fffff807afa17277 : ffffe0047a132a30 ffffac05aea4ecb0 7ffffffffffffffc 0000000000000000 : pdc!PdcMessageCallback+0x9
fffffc078fb37510 fffff807afe9f076 : ffffe0047a132a30 ffffac05aea4ecb0 ffffac05ae9e03c0 0000000000000000 : nt!ExNotifyCallback+0xb7
fffffc078fb37550 fffff807afe45d8c : ffffe0047a132a20 0000000000020000 ffffe00400000000 0000000000020000 : nt!AlpcpCompleteDispatchMessage+0xdd6
fffffc078fb37640 fffff807afe48d9f : ffffac05be166070 000000d81a9fe640 000000d81a9fe640 0000000000000001 : nt!AlpcpDispatchConnectionRequest+0x1b4
fffffc078fb376a0 fffff807afe49a2e : ffffac05be166070 fffffc0700002bd8 0000000000000000 000000d81a9fe501 : nt!AlpcpProcessConnectionRequest+0x213
fffffc078fb377b0 fffff807afe48b7e : ffffac05cf2a3df0 0000000000000000 0000000000000000 0000000000000000 : nt!AlpcpConnectPort+0x2f2
fffffc078fb37930 fffff807afc86655 : fffffc078fb37aa0 0000000000000000 0000000000000000 0000000000000000 : nt!NtAlpcConnectPort+0x6e
fffffc078fb379b0 00007fff39abfd54 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x25
000000d81a9fe5a8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007fff`39abfd54
SYMBOL_NAME: dam!DampExemptCheckCallbackRoutine+17e
MODULE_NAME: dam
IMAGE_NAME: dam.sys
IMAGE_VERSION: 10.0.26100.1591
STACK_COMMAND: .cxr 0xfffffc078fb35fd0 ; kb
BUCKET_ID_FUNC_OFFSET: 17e
FAILURE_BUCKET_ID: AV_dam!DampExemptCheckCallbackRoutine
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {b11d9680-dc31-478c-63cd-1d0eaa74fac4}
Followup: MachineOwner
Laptop details:
LENOVO 21CBCTO1WW
Bios
Version
N3AET83W (1.48 )
Date
2024-08-27
Motherboard
Manufacturer
LENOVO
Model
21CBCTO1WW
Version
SDK0T76530 WIN
Operating System
Edition
Microsoft Windows 11 Enterprise (64-bit)
Version (Build)
24H2 (10.0.26100)
Devices and drivers
Processor
12th Gen Intel® Core™ i7-1260P
Graphics
Intel® Iris® Xe Graphics
Microsoft Remote Display Adapter
Audio
Intel® Smart Sound Technology for Digital Microphones
Realtek High Definition Audio(SST)
Intel® Smart Sound Technology for Bluetooth® Audio
Networking and I/O
Cisco AnyConnect Virtual Miniport Adapter for Windows x64
Intel® Wi-Fi 6E AX211 160MHz
Bluetooth Device (Personal Area Network)
Intel® Wireless Bluetooth®
Memory
16 GB
Storage
SAMSUNG MZVL21T0HCLR-00BL7
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
We have exactly the same issue, but with Dell laptops. It's the same instruction that fails due to the nullptr deref in "fffff80744462c2e 488b17 mov rdx,qword ptr [rdi] ds:002b:0000000000000000=???????????????? " (rdi is 0000000000000000).
Unfortunately, it seems Dell doesn't support S1-S3 sleep anymore, so disabling it isn't really possible. For now we'll revert to 23H2.
Hello Martin,
Unfortunately, none of the suggestions appear to be helping. We have not made changes to the BIOS settings yet. I don't want to email instructions covering four different models and trust that users will not make undesired adjustments.
We created a problem report in the feedback hub and uploaded dump files from each model impacted. Link to feedback: https://aka.ms/AAsoj1i
We also opened a case with Lenovo support.
The organization is starting to call for the removal of 24H2.
Please let me know if you have additional recommendations.
Thank you for your help.
Dear Windows 11 BSOD 24H2,
Thank you for providing additional details and updates regarding your concerns.
I will now address each point you’ve mentioned:
While it's possible that legacy power plan settings deployed through Group Policy could potentially conflict with the 24H2 Energy Saver feature, this issue hasn't been officially confirmed by the development team. We also have not received any specific internal information regarding power plan conflicts at this time.
For updates on any known issues in Windows 11 24H2, you may follow this link: Windows 11, version 24H2 known issues and notifications | Microsoft Learn
For further information about the Energy Saver feature, you can refer to this link: Energy Saver | Microsoft Learn
Since Lenovo System Update may not automatically update all drivers, I recommend manually checking and updating the most critical drivers, particularly those that influence power management and system stability.
If the issue persists, it might be related to an unconfirmed bug in 24H2. I encourage you to submit your feedback through the Feedback Hub. The development team regularly reviews feedback submissions and considers them for future updates.
Thank you again for your cooperation and patience as we work to resolve this.
Best Regards,
Martin | Microsoft Community Support Specialist
Hello Martin,
Thank you for your help. We have been manually updating the drivers provided by Lenovo. Their Lenovo System Update application is not currently automatically deploying the drivers. System Update does automatically offer the BIOS Update Utility, published 2024-10-02.
Is it possible that legacy power plan settings supplied by group policy can conflict with 24H2 Energy Saver?
Windows 11 2024 Update: What you need to know about version 24H2 | Windows Central
For other having the issue, as of 2024-10-02 System Update is not automatically installing 20 updates published in the last 30 days.
laptops and netbooks :: thinkpad x series laptops :: thinkpad x1 carbon 11th gen type 21hm 21hn :: 21hm Lenovo PC Support - Lenovo Support US
Intel Processor Power Management (PPM) Package 968.79 KB1003.20240717 /1003.20240417 04 Oct 2024
Intel Processor Power Management (PPM) Package961.52 KB1000.2024061204 Oct 2024
I'll set a group policy to run powercfg /h off and check BIOS settings.
We use group policy to set a standard power plan on all workstations. When we deployed 24H2 I did update the policy definitions files.
Are there new areas in group policy to adjust 24H2 Energy Saver settings.
Currently our policy uses Computer Configuration/Polices/Administrative Templates/System/Power Management
Dear Windows 11 BSOD 24H2,
Thank you for reaching out to the Microsoft Community.
I understand how disruptive blue screen errors can be, especially after upgrading multiple systems to Windows 11 24H2.
Let’s go through some troubleshooting steps to address the blue screen issue and stabilize your systems.
Based on the details you shared, the error message SYSTEM_SERVICE_EXCEPTION (3b) and the crash dump referencing dam.sys suggest that the issue might be related to a driver or a compatibility problem, possibly involving power management or system services when transitioning between different power states (like sleep/wake cycles).
dam.sys is associated with the Windows Device Activity Monitor, which monitors device and power transitions during Modern Standby or connected standby states. Given that the issue triggers during sleep/wake events, it's possible that the driver or related power management services are not handling the state changes correctly.
Let's try the following steps to pinpoint the root cause and resolve the blue screen errors:
**1.**Consider disabling Modern Standby (S0 Low Power Idle) to test system stability. This setting can be adjusted in the Windows Group Policy or via registry modifications:
powercfg /h off
2. Perform a Clean Boot
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.
**3. Verify Power Settings in BIOS and Windows.**Ensure that BIOS and power settings are configured for optimal compatibility. Disable C-States or Advanced Power Management: Enter the BIOS settings and look for C-States or Advanced Power Management options. Disabling these may help stabilize power transitions.****In Windows, go to Control Panel > Power Options and set the power plan to High Performance. Make sure sleep and hybrid sleep options are turned off.
**4. Review the Lenovo and Intel Drivers Again.**While you mentioned that all drivers are updated, there could be compatibility issues with certain drivers not fully optimized for 24H2 yet. Download the latest Intel Power Management Driver and Intel Management Engine (ME) from the Intel website rather than relying solely on OEM updates.****Check for optional Windows Updates in Settings > Update & Security to see if any additional updates are available specifically for 24H2.
Please try the above steps and let us know the outcome. If the issue persists, you can share the updated crash dump files here, and we can help you analyze them further.
Best Regards,
Martin | Microsoft Community Support Specialist
