Windows 11 latest Security Update KB5068861 caused a BSOD

Question

Windows 11 latest Security Update KB5068861 caused a BSOD

Rustam Hatamli 0

Hi all. Latest windows update KB5068861 caused a bsod on my computer. What do you think might have caused this issue? Which driver or application do you suspect could be responsible, and why? There are so many complaints about this... I unistalled it from fail-safe mode and it helped. Checked memory dump with windbg and it geve me this:

Loading Kernel Symbols
...............................................................
................................................................
................................................................
....
Loading User Symbols

Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS (ce)
A driver unloaded without cancelling timers, DPCs, worker threads, etc.
The broken driver's name is displayed on the screen and saved in
KiBugCheckDriver.
Arguments:
Arg1: fffff806a140da30, memory referenced
Arg2: 0000000000000010, value 0 = read operation, 1 = write operation
Arg3: fffff806a140da30, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000000, Mm internal code.

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3515

    Key  : Analysis.Elapsed.mSec
    Value: 62334

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29482.1003

    Key  : Analysis.Version.Description
    Value: 10.2509.29.03 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2509.29.3

    Key  : Bugcheck.Code.KiBugCheckData
    Value: 0xce

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xce

    Key  : Bugcheck.Code.TargetModel
    Value: 0xce

    Key  : Dump.Attributes.AsUlong
    Value: 0x21000

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0x0

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

    Key  : Dump.Attributes.ProgressPercentage
    Value: 100

    Key  : Failure.Bucket
    Value: 0xCE_IMAGE_mmcss.sys

    Key  : Failure.Exception.IP.Address
    Value: 0xfffff806a140da30

    Key  : Failure.Exception.IP.Offset
    Value: 0xda30

    Key  : Failure.Hash
    Value: {86026600-5fdb-3c93-8433-dfaca371cee4}

    Key  : Faulting.IP.Type
    Value: Unloaded

    Key  : Hypervisor.Enlightenments.Value
    Value: 0

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 0x0

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 0

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

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 0

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 0

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 0

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 0

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 0

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 0

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 0

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 16777216

    Key  : Hypervisor.Flags.ValueHex
    Value: 0x1000000

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 0

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 0

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 0

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 0

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 0

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 0

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 0

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 0

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 0

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 0

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 0

    Key  : Hypervisor.RootFlags.Value
    Value: 0

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 0x0

    Key  : SecureKernel.HalpHvciEnabled
    Value: 0

    Key  : WER.OS.Branch
    Value: ge_release

    Key  : WER.OS.Version
    Value: 10.0.26100.1

    Key  : WER.System.BIOSRevision
    Value: 4.6.0.0


BUGCHECK_CODE:  ce

BUGCHECK_P1: fffff806a140da30

BUGCHECK_P2: 10

BUGCHECK_P3: fffff806a140da30

BUGCHECK_P4: 0

FILE_IN_CAB:  MEMORY.DMP

DUMP_FILE_ATTRIBUTES: 0x21000

FAULTING_THREAD:  ffff8388718e3040

WRITE_ADDRESS:  fffff806a140da30 

IMAGE_NAME:  mmcss.sys

MODULE_NAME: mmcss

FAULTING_MODULE: 0000000000000000 

BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon)


PROCESS_NAME:  System

IP_MODULE_UNLOADED: 
<Unloaded_mmcss.sys>+da30
fffff806`a140da30 ??              ???

STACK_TEXT:  
fffff88d`f60825a8 fffff806`f36d7377     : 00000000`00000050 fffff806`a140da30 00000000`00000010 fffff88d`f6082810 : nt!KeBugCheckEx
fffff88d`f60825b0 fffff806`f3240510     : 00478425`bd9bbfff ffff8000`00000000 fffff806`a140da30 0000007f`fffffff8 : nt!MiSystemFault+0x30610b
fffff88d`f60826a0 fffff806`f36addcb     : ffff8388`718e30b8 00000000`00000000 fffff806`f3ef6e20 fffff806`f32566fb : nt!MmAccessFault+0x630
fffff88d`f6082810 fffff806`a140da30     : fffff806`f36ef0bc fffff88d`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x38b
fffff88d`f60829a8 fffff806`f36ef0bc     : fffff88d`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : <Unloaded_mmcss.sys>+0xda30
fffff88d`f60829b0 fffff806`f348f642     : ffff8388`7a0e09a0 fffff806`f3fcfb40 ffff8388`71680e80 ffff8388`7176eaa0 : nt!CmFcpFeatureUsageProviderSubscriptionWrapper+0x3c
fffff88d`f60829e0 fffff806`f32db8ac     : ffff8388`718e3040 ffff8388`74d75900 00000000`00000000 ffff8388`74dc5f90 : nt!CmpWorkItemWrapper+0x42
fffff88d`f6082a10 fffff806`f34815ea     : ffff8388`718e3040 ffff8388`718e3040 fffff806`f32db2c0 ffff8388`7176eaa0 : nt!ExpWorkerThread+0x5ec
fffff88d`f6082bf0 fffff806`f369fd74     : ffffaf81`afa51180 ffff8388`718e3040 fffff806`f3481590 ca4e5229`d6889499 : nt!PspSystemThreadStartup+0x5a
fffff88d`f6082c40 00000000`00000000     : fffff88d`f6083000 fffff88d`f607d000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


STACK_COMMAND: .process /r /p 0xffff8388716c9040; .thread 0xffff8388718e3040 ; kb

FAILURE_BUCKET_ID:  0xCE_IMAGE_mmcss.sys

OS_VERSION:  10.0.26100.1

BUILDLAB_STR:  ge_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {86026600-5fdb-3c93-8433-dfaca371cee4}

Followup:     MachineOwner

3 answers

Your answer

Answer 1

The BSOD (Blue Screen of Death) you encountered after installing the Windows update KB5068861 appears to be related to the mmcss.sys driver, which is associated with the Multimedia Class Scheduler Service. The bug check code DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS (ce) indicates that a driver unloaded without properly canceling pending operations, which can lead to system instability and crashes.

In your case, the analysis shows that mmcss.sys was the broken driver causing the issue. This driver is critical for managing multimedia tasks, and if it fails to handle its operations correctly, it can result in a BSOD. The fact that you were able to resolve the issue by uninstalling the update suggests that this specific driver version may have compatibility issues with the update or other system components.

If you continue to experience issues, consider checking for updates specifically for the mmcss.sys driver or related multimedia drivers, as well as monitoring for any patches from Microsoft that address this problem. Additionally, keeping your system and drivers updated can help prevent such issues in the future.

Answer 2

JC 7,515 Independent Advisor

Hello,

From the dump file you provided it looks like the mmcss.sys service is what's causing the BSOD, I recommend staying on the previous update of windows to prevent this from happening for the time being, you should also send this report through the built in windows feedback hub to make sure microsoft is aware of the issue and has information to work with on creating a fix.
Hope this helps,

JC

Answer 3

Hi Rustam Hatamli,
Welcome to Microsoft Q&A forum. I'm happy to help.

Your dump files indicate that you either have memory problem, or your CPU Memory controller cannot handle the memory well, or drivers conflicted.

To diagnose the problem, try the following suggestions:

Go to BIOS and disable any overclocking and XMP
Disable the "Memory integrity" feature (if enabled)
1. Click the "Start" button and search for "Core isolation"
2. Disable "Memory integrity"
3. Restart your computer
4. Use your computer normally and see if the problem disappears

If disabling "Memory integrity" doesn't work, please do this workaround. Since this is workaround, it may or may not work with you.

Open Notepad

Insert this code

      [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Multimedia\SystemProfile]
      "SystemResponsiveness"=dword:00000014 
      "NetworkThrottlingIndex"=dword:0000000a
      "LazyModeTimeout"=-

Save as "BSOD-fix.reg" - includes " in file name
Run that file

Disclaimer: Generally, modifying registry subkeys or work group is intended for advanced users, administrators, and IT Professionals. It can help fix some problems, however, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For further protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click How to back up and restore the registry in Windows - Microsoft Support to view the article.

Hopefully, the above information helped you diagnose and resolve the issue.

If you have any other questions, please feel free to let me know via "Comment".

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Share via

Windows 11 latest Security Update KB5068861 caused a BSOD

3 answers

Your answer