Share via

Recurring Critical Events and Unexpected Shutdowns on Windows 11 System

Anonymous
2024-06-22T11:45:27+00:00

Summary of the Problem: I am experiencing recurring critical events and unexpected shutdowns on my Windows 11 Home system. The critical events, as logged in Event Viewer, include:

  1. Event ID 41 (Microsoft-Windows-Kernel-Power): The system reboots without cleanly shutting down first, indicating potential system crashes or power failures.
  2. Event ID 161 (volmgr): Dump file creation fails due to errors during dump creation, hindering troubleshooting efforts.
  3. Event ID 6008 (EventLog): Confirms the unexpected nature of previous system shutdowns.

System Information:

  • Operating System: Windows 11 Home, Version 10.0.22631 Build 22631
  • Manufacturer: LENOVO
  • Model: 82GN (LENOVO_MT_82GN_BU_idea_FM_Legion 5 17ARH05H)
  • Processor: AMD Ryzen 7 4800H with Radeon Graphics
  • Installed RAM: 16.0 GB
  • Disk Health: Checked and verified by Lenovo Diagnostic and Samsung Magician software
  • BIOS Firmware: Up to date (LENOVO FSCN28WW, 9/21/2023)
  • Secure Boot State: On

Description of Attempts Made:

  1. Hardware Diagnostics: Ran diagnostics to check RAM, CPU, and hard disk stability, all returned clean results.
  2. Driver and Firmware Updates: Ensured all device drivers, chipset drivers, and firmware (BIOS/UEFI) are up to date via Windows Update, Lenovo Vantage, and Lenovo Diagnostic tool.
  3. Overheating Monitoring: Monitored system temperatures and verified that overheating is not the cause of the issues.
  4. Disk Health Check: Checked disk health using Lenovo Diagnostic and Samsung Magician software, all checks returned normal.
  5. Clean Install of Windows 11: Performed a clean installation of Windows 11 to rule out software-related issues.
  6. System File Check (SFC): Ran the SFC tool, which returned no violations or corrupted system files.

Despite these efforts, the issue persists, with recurring critical events and unexpected shutdowns disrupting normal system operation. Given the detailed troubleshooting steps taken, what further actions or recommendations would you suggest to diagnose and resolve these recurring critical events and unexpected shutdowns effectively?

Thank you for your assistance.

Windows for home | Windows 11 | Performance and system failures

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.

0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-06-25T11:58:10+00:00

    This may be premature but it's been two days without any critical errors or BSOD. This is what I changed to improve the stability of my Laptop. After experiencing frequent BSODs and critical errors, I found that adjusting the paging file size resolved the issue. Below is a quick guide to adjusting your paging file, which can help stabilize your system.

    Steps to Adjust the Paging File on Windows:

    1. Open System Properties:
      • Press Windows + R, type sysdm.cpl, and press Enter.
    2. Access Performance Options:
      • Go to the Advanced tab.
      • Under Performance, click Settings.
    3. Adjust Virtual Memory:
      • In the Performance Options window, go to the Advanced tab.
      • Under Virtual memory, click Change.
    4. Modify the Paging File Size:
      • Uncheck Automatically manage paging file size for all drives.
      • Select the drive where you want to adjust the paging file.
      • Choose Custom size, and enter a value for both Initial size (MB) and Maximum size (MB).
    5. Recommended Settings:
      • Initial size: Set this to at least the amount of your system’s RAM (e.g., for 16 GB of RAM, set it to 16000 MB).
      • Maximum size: Typically, 1.5 to 2 times the amount of your system’s RAM (e.g., for 16 GB of RAM, set it to 32000 MB).
    6. Apply and Restart:
      • Click Set, then OK.
      • Restart your computer for the changes to take effect.

    Additional Tips:

    • Ensure your paging file is on the fastest drive available.
    • If you have multiple drives, you can split the paging file across them to improve performance.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2024-06-22T12:06:37+00:00

    I Ran MemTest86 and Memory Diagnostic Tool for memory, and it came back clean. I Ran Prime95 to stress test the CPU and recreate the overheating scenario, and it passed without errors.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2024-06-22T11:47:21+00:00

    0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * *******************************************************************************

    KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common BugCheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80383aa1aff, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 00000000ab318aaa, Parameter 1 of the exception

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ExceptionRecord                               ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ContextRecord                                 ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3984

    Key  : Analysis.Elapsed.mSec
    Value: 4465

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

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

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

    Key  : Bugcheck.Code.KiBugCheckData
    Value: 0x1e

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x1e

    Key  : Bugcheck.Code.TargetModel
    Value: 0x1e

    Key  : Dump.Attributes.AsUlong
    Value: 1800

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0

    Key  : Dump.Attributes.LastLine
    Value: Dumping physical memory to disk:  100% 

    Key  : Dump.Attributes.ProgressPercentage
    Value: 100

    Key  : Failure.Bucket
    Value: AV_R_nt!CmpLockKcbStackShared

    Key  : Failure.Hash
    Value: {55850975-a367-a8ad-a29e-51f759ee0a77}

    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

    Key  : SecureKernel.HalpHvciEnabled
    Value: 1

    Key  : WER.OS.Branch
    Value: ni_release

    Key  : WER.OS.Version
    Value: 10.0.22621.1

BUGCHECK_CODE:  1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff80383aa1aff

BUGCHECK_P3: 0

BUGCHECK_P4: ab318aaa

FILE_IN_CAB:  MEMORY.DMP

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

DUMP_FILE_ATTRIBUTES: 0x1800

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  00000000ab318aaa

READ_ADDRESS: unable to get nt!PspSessionIdBitmap
 00000000ab318aaa 

PROCESS_NAME:  Registry

STACK_TEXT:  
ffffe307`ab317fc8 fffff803`8386d391     : 00000000`0000001e ffffffff`c0000005 fffff803`83aa1aff 00000000`00000000 : nt!KeBugCheckEx
ffffe307`ab317fd0 fffff803`8383027c     : 00000000`00001000 ffffba85`f42e6780 00000000`00000000 ffffe307`ab3187b0 : nt!KiDispatchException+0x267681
ffffe307`ab3186b0 fffff803`8382b563     : 00000000`00000000 00000000`00000000 ffffe605`4be452f0 00000000`00000000 : nt!KiExceptionDispatch+0x13c
ffffe307`ab318890 fffff803`83aa1aff     : ffffe605`4be452f0 00000000`00000002 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x463
ffffe307`ab318a20 fffff803`83aa6e8b     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!CmpLockKcbStackShared+0xf
ffffe307`ab318a50 fffff803`83aa92cb     : ffffffff`00000008 00000000`00000000 00000000`00000000 ffff6fa2`e4d6bf01 : nt!CmQueryValueKey+0x16b
ffffe307`ab318b70 fffff803`8382f808     : 00000000`00000a5e 00000000`00000000 ffffba85`f41b3d20 fffff803`8364a237 : nt!NtQueryValueKey+0x56b
ffffe307`ab318e50 fffff803`8381fd30     : fffff803`83b29094 00000000`0000040a 00000000`00000000 ffffba85`00000003 : nt!KiSystemServiceCopyEnd+0x28
ffffe307`ab319058 fffff803`83b29094     : 00000000`0000040a 00000000`00000000 ffffba85`00000003 00000000`00000440 : nt!KiServiceLinkage
ffffe307`ab319060 fffff803`83c61143     : ffffe307`ab319650 00000000`00000401 00000000`00000412 00000000`00000000 : nt!_RegRtlQueryValue+0x94
ffffe307`ab319180 fffff803`83c602a1     : ffffffff`00000000 00000000`00000000 ffffe307`00000000 fffff803`834021e8 : nt!DrvDbGetRegValueMappedProperty+0x67
ffffe307`ab3191d0 fffff803`83cedb9b     : ffffe605`3a33c8d0 ffffe605`474ea4e0 00000000`00000000 00000000`00000400 : nt!DrvDbGetDriverPackageMappedProperty+0x199
ffffe307`ab3192b0 fffff803`83c60081     : ffffe605`3a33c8d0 ffffe605`474ea4e0 ffffe307`ab319430 00000000`00000400 : nt!DrvDbGetDriverPackageMappedProperty+0x8da93
ffffe307`ab319390 fffff803`83b2e82c     : ffffe605`3a27bcd0 00000000`00000409 00000000`00000044 00000000`00000000 : nt!DrvDbDispatchDriverPackage+0xc1
ffffe307`ab3193f0 fffff803`83b2e6b2     : 00000000`00000008 00000000`00000412 ffffe605`3ed224f0 ffffe307`ab319650 : nt!PnpGetMappedPropertyDispatch+0xa4
ffffe307`ab319480 fffff803`83b2e58b     : 00000000`00000008 ffffe605`474ea4e0 ffffe307`ab3195c1 ffffe605`3a27bcd0 : nt!_PnpGetObjectPropertyWorker+0xba
ffffe307`ab319520 fffff803`83b2c8e3     : 00000000`00000008 ffffe605`3ed224f0 00000000`00000000 ffffe307`ab319670 : nt!_PnpGetObjectProperty+0x127
ffffe307`ab3195f0 fffff803`83b2c563     : 00000000`00000000 fffff803`83ac8887 00000000`00000000 00000000`00000000 : nt!PiCMGetObjectProperty+0x17f
ffffe307`ab319720 fffff803`83b2c4d3     : ba861f65`04a09f3d 00000000`00120089 00010101`011fffff 00000000`00000048 : nt!PiCMHandleIoctl+0x73
ffffe307`ab319760 fffff803`83bc5b4a     : 00000000`00000426 ffffba86`1f6504d0 ffffba86`162ce100 fffff803`83bb5b4f : nt!PiCMFastIoDeviceDispatch+0x53
ffffe307`ab3197b0 fffff803`83ac7c5e     : 00000000`00000000 00007ffe`3c11d101 ffffba86`162ce100 00000000`00000000 : nt!PiDaFastIoDispatch+0x6a
ffffe307`ab319810 fffff803`83ac77e6     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x45e
ffffe307`ab319a00 fffff803`8382f808     : ffffba86`0e319580 fffff803`83bb7064 00000000`00000000 00000000`00000000 : nt!NtDeviceIoControlFile+0x56
ffffe307`ab319a70 00007ffe`44e90084     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
000000e0`beafaef8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`44e90084

SYMBOL_NAME:  nt!CmpLockKcbStackShared+f

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  f

FAILURE_BUCKET_ID:  AV_R_nt!CmpLockKcbStackShared

OS_VERSION:  10.0.22621.1

BUILDLAB_STR:  ni_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {55850975-a367-a8ad-a29e-51f759ee0a77}

Followup:     MachineOwner
---------
Most recent bugcheck from windbg.

    Was this answer helpful?

    0 comments