I have been getting these two errors of Service Control Manager 7023 and 7031

Hello DisBlue

You say that you were able to fix the windows search error. Congratulations. Would you mind sharing how you fixed it? (since I have the same error)

Thanks.

Hi DisBlue.

Thanks for your reply.

I understand that you checked the dependencies regarding the Windows Search service and they are all in a normal running state.

So the problem may not be coming from here.

And your black screen issue is most likely not directly related to the current events in the Event Viewer.

In my previous reply, clean boot is checking on the third party software side, and safe mode is checking on the driver side. They are not just for reporting errors in the event viewer, but also check for some other aspects that could be causing the black screen.

I do understand your concern about whether or not an error could have occurred, do you remember what you did before the black screen occurred?

If you still remember, then please do the same in clean boot by opening the least number of third-party software to see if the same problem exists, if not, open the commonly used third-party software one by one to see in which one the problem occurs after opening it to find the conflicting software.

And in Safe Mode, perform the same operation to see if the black screen still occurs. (Some functions are restricted in safe mode, and you may not be able to run some programs)

With these checks, we can determine if the problem is from a conflicting software or a driver error.

Also, you mentioned that currently your computer has not been updated to 24H2, it is still at 23H2.

Generally speaking, there are no problems associated with 23H2, it's a more stable version, while in 24H2, there are some disruptive issues, which you can check via the link below.

Windows 11, version 24H2 known issues and notifications | Microsoft Learn

Therefore, you can wait for a while before updating.

Thank you for your understanding and support.

Best regards,

Zev - MSFT | Microsoft Community Support Specialist

Hello Zev,

I have check to see what services Window Search uses. It use Background Tasks Infrastructure Service and Remote Procedure Call. Both of which I believe are enabled. I would go into their properties and their startup type is automatic and grayed out which doesn't allow me to change it. They appear to be both running.

I have tried reinstalling my Windows 23H2 and build indexing but that hasn't stop the crashing. I haven't been allowed to update to 24H2 yet but would that potentially fix it?

I have not tried a clean/safe boot yet. While in clean boot, should I just use my computer as normal to see if it crashes? If it does crash, will it just record it in the event log again?

Hi DisBlue.

Welcome to Microsoft Community.

In your description, you are experiencing a black screen while using your computer.

I noticed that you looked for the Event Viewer error message for us, and thank you for your search and information gathering to resolve this issue, I do understand the frustration and inconvenience of not being able to use your computer properly at this time.

Based on your reported error message, it appears that your computer is having some issues with the Windows Search services and they have been terminated unexpectedly.

We judge that this may be caused by the dependencies about Windows Search service are not turned on, or some third-party software conflicts.

Please refer to the following steps to check the dependencies of Windows Search.

1 Search for “Services” in the taskbar and open it.

2 Find Windows Search, right-click on it, and select Properties.

3 Click on the Dependencies tab and check the dependencies below.

4 Ensure that the dependency service it requires is enabled in the “Services” page.

If the dependencies are enabled but the problem still exists, then it may be caused by some third-party software conflicts. I recommend trying a clean boot which starts Windows with a minimal set of drivers and startup programs. It can be used to determine whether a background service or program is interfering or causing 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.

In a clean boot, do not open any third-party software to see if you have the same problem.

Also, in order to determine if the issue is coming from the driver, you can refer to the following link to enter Safe Mode

Windows startup settings - Microsoft Support

Check if the same issue is present in safe mode.

Please do the above test and let me know the result and I will provide you further assistance based on your test result.

Thank you for your understanding and support.

Best regards,

Zev - MSFT | Microsoft Community Support Specialist

I have manage to fix the windows search error and so the error doesn't appear anymore. However my computer is still crashing randomly. The screen will go black and the fans ramp up while my music/video audio is still playing. I've checked the event viewer to see what errors I got before/during the crash and it seems to have something to do with TPM-WIN, It reads as follows, "The Secure Boot Dbx update failed as boot manager is not signed with the Windows UEFI CA 2023 certificate"

I also have a minidump files that I checked with windbg but having trouble understanding what its saying.

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: ffffac000c103000, memory referenced.
Arg2: 0000000000000002, X64: bit 0 set if the fault was due to a not-present PTE.
bit 1 is set if the fault was due to a write, clear if a read.
bit 3 is set if the processor decided the fault was due to a corrupted PTE.
bit 4 is set if the fault was due to attempted execute of a no-execute PTE.
- ARM64: bit 1 is set if the fault was due to a write, clear if a read.
bit 3 is set if the fault was due to attempted execute of a no-execute PTE.
Arg3: fffff8018afe4116, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)

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

KEY_VALUES_STRING: 1

    Key  : AV.Type
    Value: Write

    Key  : Analysis.CPU.mSec
    Value: 625

    Key  : Analysis.Elapsed.mSec
    Value: 5126

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

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

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

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

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

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

    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.LegacyAPI
    Value: 0x50

    Key  : Bugcheck.Code.TargetModel
    Value: 0x50

    Key  : Dump.Attributes.AsUlong
    Value: 1008

    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_W_(null)_nvlddmkm!unknown_function

    Key  : Failure.Hash
    Value: {838100fa-f28b-2ef7-d702-e31713cb338c}

BUGCHECK_CODE:  50

BUGCHECK_P1: ffffac000c103000

BUGCHECK_P2: 2

BUGCHECK_P3: fffff8018afe4116

BUGCHECK_P4: 0

FILE_IN_CAB:  111124-11343-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffff96893669b080

READ_ADDRESS: fffff8015931c470: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
 ffffac000c103000 

MM_INTERNAL_CODE:  0

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  CefSharp.Brows

TRAP_FRAME:  ffffdf8504fa77b0 -- (.trap 0xffffdf8504fa77b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffac000c102000 rbx=0000000000000000 rcx=0000000000000400
rdx=0000000000040200 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8018afe4116 rsp=ffffdf8504fa7940 rbp=0000000000000200
 r8=0000000000000200  r9=ffffdf8504fa7970 r10=0000000000000000
r11=ffffdf8504fa7870 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nvlddmkm+0xc74116:
fffff801`8afe4116 891488          mov     dword ptr [rax+rcx*4],edx ds:ffffac00`0c103000=????????
Resetting default scope

STACK_TEXT:  
ffffdf85`04fa7588 fffff801`58a739ba     : 00000000`00000050 ffffac00`0c103000 00000000`00000002 ffffdf85`04fa77b0 : nt!KeBugCheckEx
ffffdf85`04fa7590 fffff801`5886c29c     : 00000000`00000001 00000000`00000002 00000000`00000000 ffffac00`0c103000 : nt!MiSystemFault+0x2395ca
ffffdf85`04fa7690 fffff801`58a25f7e     : ffffac00`1073b054 00000000`00000001 00000000`00000003 00000000`00000000 : nt!MmAccessFault+0x29c
ffffdf85`04fa77b0 fffff801`8afe4116     : fffffc0e`1edd0c00 fffffc0e`1edd0dec ffff9689`31a63a68 00000000`000005e8 : nt!KiPageFault+0x37e
ffffdf85`04fa7940 fffffc0e`1edd0c00     : fffffc0e`1edd0dec ffff9689`31a63a68 00000000`000005e8 00000000`000003cf : nvlddmkm+0xc74116
ffffdf85`04fa7948 fffffc0e`1edd0dec     : ffff9689`31a63a68 00000000`000005e8 00000000`000003cf fffff801`8b753770 : 0xfffffc0e`1edd0c00
ffffdf85`04fa7950 ffff9689`31a63a68     : 00000000`000005e8 00000000`000003cf fffff801`8b753770 00000000`00000000 : 0xfffffc0e`1edd0dec
ffffdf85`04fa7958 00000000`000005e8     : 00000000`000003cf fffff801`8b753770 00000000`00000000 fffffc0e`1edd0dbc : 0xffff9689`31a63a68
ffffdf85`04fa7960 00000000`000003cf     : fffff801`8b753770 00000000`00000000 fffffc0e`1edd0dbc ffff9689`2001fff1 : 0x5e8
ffffdf85`04fa7968 fffff801`8b753770     : 00000000`00000000 fffffc0e`1edd0dbc ffff9689`2001fff1 00000000`000005e8 : 0x3cf
ffffdf85`04fa7970 00000000`00000000     : fffffc0e`1edd0dbc ffff9689`2001fff1 00000000`000005e8 00000000`000003cf : nvlddmkm+0x13e3770

SYMBOL_NAME:  nvlddmkm+c74116

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .process /r /p 0xffff96893d6bf0c0; .thread 0xffff96893669b080 ; kb

BUCKET_ID_FUNC_OFFSET:  c74116

FAILURE_BUCKET_ID:  AV_W_(null)_nvlddmkm!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {838100fa-f28b-2ef7-d702-e31713cb338c}

Followup:     MachineOwner