**** SYSTEM SERVICE EXCEPTION

Question

When i start the pc with windows 11 at when I entered the password the mouse and keyboard did not respond and after a few seconds the blue screen appeared with this message : "SYSTEM SERVICE EXCEPTION"

This is the dump file open with windbg:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000006, Exception code that caused the BugCheck
Arg2: fffff803432be362, Address of the instruction which caused the BugCheck
Arg3: ffffb7070e926440, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.

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                                 ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: 2796

    Key  : Analysis.Elapsed.mSec
    Value: 3065

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x3b

    Key  : Bugcheck.Code.TargetModel
    Value: 0x3b

    Key  : Dump.Attributes.AsUlong
    Value: 808

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Failure.Bucket
    Value: 0x3B_C0000006_nt!HvpGetCellPaged

    Key  : Failure.Hash
    Value: {68f3db38-ae8e-4bae-c37a-85819946495f}

    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

BUGCHECK_CODE:  3b

BUGCHECK_P1: c0000006

BUGCHECK_P2: fffff803432be362

BUGCHECK_P3: ffffb7070e926440

BUGCHECK_P4: 0

FILE_IN_CAB:  042924-8187-01.dmp

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

DUMP_FILE_ATTRIBUTES: 0x808
  Kernel Generated Triage Dump

CONTEXT:  ffffb7070e926440 -- (.cxr 0xffffb7070e926440)
rax=000002a086b68000 rbx=00000000ffffffce rcx=ffff80060291b000
rdx=000002a086b68000 rsi=0000000000027030 rdi=0000000000000030
rip=fffff803432be362 rsp=ffffb7070e926e60 rbp=000000000000001f
 r8=ffffb7070e926ed4  r9=0000000000000027 r10=ffff80060291b000
r11=00000000000cd1e8 r12=0000000000000298 r13=000002a086bf5560
r14=ffffb7070e926ed0 r15=000000000000001f
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050206
nt!HvpGetCellPaged+0xa2:
fffff803`432be362 8b0417          mov     eax,dword ptr [rdi+rdx] ds:002b:000002a0`86b68030=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Registry

STACK_TEXT:  
ffffb707`0e926e60 fffff803`432be093     : 00000000`ffffffce 00000000`00000000 ffffb707`0e9270e0 fffff803`42e3831c : nt!HvpGetCellPaged+0xa2
ffffb707`0e926ea0 fffff803`432be6da     : ffffb707`0e926ff9 ffff8006`166ac720 ffffb707`0e9270e0 00000000`00000000 : nt!CmpFindNameInListFromIndex+0xc3
ffffb707`0e926f30 fffff803`432c154b     : 00000000`00000008 00000000`00000000 00000000`00000000 00000000`00000001 : nt!CmQueryValueKey+0x2aa
ffffb707`0e927050 fffff803`4302d535     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtQueryValueKey+0x56b
ffffb707`0e927330 00007ff9`fb82fc34     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000010`9e3fe438 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`fb82fc34

SYMBOL_NAME:  nt!HvpGetCellPaged+a2

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22621.3527

STACK_COMMAND:  .cxr 0xffffb7070e926440 ; kb

BUCKET_ID_FUNC_OFFSET:  a2

FAILURE_BUCKET_ID:  0x3B_C0000006_nt!HvpGetCellPaged

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {68f3db38-ae8e-4bae-c37a-85819946495f}

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

Answer 1

Thank you for your reply! I'm glad to know that your issue has been resolved, I understand that you used the SFC solution to fix your computer, which is very true, and since the only thing I could analyze from the dump logs you provided was the kernel issue, I didn't have any more information, so I wanted to assist you in troubleshooting other non-official Microsoft applications that were causing the blue screen in the first place. Then based on your actions, I have fully understood that the cause of your blue screen should be a corrupt Windows system kernel file, which caused your computer to blue screen. You don't need to disable other non-Microsoft applications now, just continue to use your computer as normal.

Thank you for your understanding and support! Feel free to continue posting in the Microsoft community!

Best Regards,

Zhang Yang

Answer 2

The only dump file I have is the one I already inserted in the post, subsequently I no longer encountered the problem.

I repaired the files with the sfc scannow command and checked the memory with the Windows tool but everything is fine.

Do you still advise me to proceed with disabling non-Windows services?.
Thanks for the reply.

Answer 3

Hello GiaccoGP,

Welcome to the Microsoft Community!

Thank you for providing the error log. I analyzed this as a Windows kernel error by looking at the log file you shared. We've tried to replicate the issue here, but it doesn't seem to work the same as I understood his explanation of the problem, so this is very unusual and interesting for us, and we're happy to provide additional support to properly isolate what's actually causing the problem. We would like to share this concern with our internal team, but you may need to request all dump files to help us better understand what's really going on and provide additional help. So, provide all dump files of the issue and upload it to OneDrive or your preferred online storage and share the link here.

At the same time, try the steps below to see if it solves the problem.  

• Press the Windows and R keys on the keyboard at the same time and enter msconfig in the pop-up window.
• Open System Configuration and select the General TAB - Boot with selection.
• Deselect the boot option.
• Go to the Services TAB - click Hide All Microsoft Services in the bottom left corner, then click Disable All.
• Click OK and restart the computer. Be sure to select Hide all Microsoft services first and then disable all, otherwise unforeseen problems such as inability to access the system may occur.
• Check whether the problem reappears.

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. If you need further information on this feature, please refer to this link How to perform a clean boot in Windows.

Tell us the results and we will get back to you as soon as possible. Once the above questions are answered, we may recommend other troubleshooting steps.

We look forward to your response. 

Sincerely,

Zhang Yang - MSFT | Microsoft Community Support Specialist