Windows 10 several PCs got blue screen in the office

[kaitokid]

While using the PC with OS Windows 10 pro, after rebooting the PC, blue screen occurs during boot process, and the PC cannot be booted.

• Blue Screen Error Code : 0xc000000e (Stop cod : REGISTRY ERROR)
  It happens at several PCs in the my office randomly without any sign.

I tried to almost everything to find website, however it was not working.

I found a old system32 folder of one PC, then overwrite it
then it can be booted and the dump file was created.

Could anyone explain what it means and what the problem is, please?
is it possible to find exact reason of it? if it is how?

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

REGISTRY_ERROR (51)
Something has gone badly wrong with the registry. If a kernel debugger
is available, get a stack trace. It can also indicate that the registry got
an I/O error while trying to read one of its files, so it can be caused by
hardware problems or filesystem corruption.
It may occur due to a failure in a refresh operation, which is used only
in by the security system, and then only when resource limits are encountered.
Arguments:
Arg1: 0000000000000008, (reserved)
Arg2: 0000000000000000, (reserved)
Arg3: ffffcb805505c000, depends on where Windows BugChecked, may be pointer to hive
Arg4: fffff8030e86d3b4, depends on where Windows BugChecked, may be return code of
HvCheckHive if the hive is corrupt.

Debugging Details:​

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 5718

Key : Analysis.Elapsed.mSec
Value: 6004

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

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

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

Key : Bugcheck.Code.KiBugCheckData
Value: 0x51

Key : Bugcheck.Code.LegacyAPI
Value: 0x51

Key : Bugcheck.Code.TargetModel
Value: 0x51

Key : Failure.Bucket
Value: 0x51_nt!CmpValueToData

Key : Failure.Hash
Value: {0744fd72-c943-02ce-bd88-8225efaab793}

Key : Hypervisor.Enlightenments.Value
Value: 0

Key : Hypervisor.Enlightenments.ValueHex
Value: 0

Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 0

Key : Hypervisor.Flags.ApicEnlightened
Value: 0

Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 0

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

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

Key : Hypervisor.Flags.ValueHex
Value: 20000

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

Key : WER.OS.Branch
Value: 19h1_release

Key : WER.OS.Version
Value: 10.0.18362.1

BUGCHECK_CODE: 51

BUGCHECK_P1: 8

BUGCHECK_P2: 0

BUGCHECK_P3: ffffcb805505c000

BUGCHECK_P4: fffff8030e86d3b4

FILE_IN_CAB: MEMORY-b.DMP

PROCESS_NAME: Registry

STACK_TEXT:
ffffbe03`02c077c8 fffff803`15e15677 : 00000000`00000051 00000000`00000008 00000000`00000000 ffffcb80`5505c000 : nt!KeBugCheckEx
ffffbe03`02c077d0 fffff803`1600eb80 : 00000000`008f33b0 ffffcb80`5505c000 00000000`00000000 00000000`008f3348 : nt!CmpValueToData+0xb78b3
ffffbe03`02c07830 fffff803`1600e4fb : 00000000`000043ae 00000000`00000000 ffffcb80`572b2010 00000000`ffffffff : nt!CmpSortDriverList+0x150
ffffbe03`02c078a0 fffff803`1600c92c : fffff803`0db96330 fffff803`15d5c6f0 fffff803`0db96300 00000000`00000000 : nt!CmGetSystemDriverList+0x293
ffffbe03`02c07a90 fffff803`1600bc1a : fffff803`1b660000 fffff803`0db96330 fffff803`15d5c6f0 fffff803`0db96330 : nt!IopInitializeSystemDrivers+0x54
ffffbe03`02c07b30 fffff803`15d5c732 : fffff803`0db96330 fffff803`0db96330 fffff803`15d5c6f0 fffff803`0db96330 : nt!IoInitSystem+0x12
ffffbe03`02c07b60 fffff803`1572f725 : ffff850b`f0ca1380 fffff803`15d5c6f0 fffff803`0db96330 48fffea9`24e9d88b : nt!Phase1Initialization+0x42
ffffbe03`02c07b90 fffff803`157c3e6a : fffff803`0deff180 ffff850b`f0ca1380 fffff803`1572f6d0 0d158d48`fffea944 : nt!PspSystemThreadStartup+0x55
ffffbe03`02c07be0 00000000`00000000 : ffffbe03`02c08000 ffffbe03`02c01000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a

SYMBOL_NAME: nt!CmpValueToData+b78b3

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.18362.239

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: b78b3

FAILURE_BUCKET_ID: 0x51_nt!CmpValueToData

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

dump.zip

 

[ChatGPT]

It appears that your system encountered a REGISTRY_ERROR (51), indicating that something went wrong with the registry.

The crash dump analysis pointed out nt!CmpValueToData+b78b3 function as the possible root cause which is part of the Windows kernel (ntkrnlmp.exe).

There are few reasons this could be happening:

1. Damaged or Corrupted Windows Registry: The Windows registry can become corrupt or damaged due to software installation or removal, or even because of malware.

2. Hardware Error: This could be due to faulty RAM which could be causing the data in the registry to become corrupt. Hard disk errors also could possibly lead to this issue.

3. Outdated Drivers: Sometimes, outdated or incompatible drivers can cause various problems, including REGISTRY_ERROR.

4. Incomplete software uninstall/install: Occasionally, if a software is not properly installed or uninstalled, it may cause issues in the registry.

To fix this, you could try:

1. Using System Restore: If the problem started recently, you could try performing a system restore to a point where you did not have this problem.

2. Updating your drivers: Make sure all your drivers are up-to-date. You can use the in-built Device Manager in Windows for this.

3. Checking your Hardware: Use Windows' inbuilt Memory Diagnostic tool to check if it's a hardware related issue, including any errors with your hard disk.

4. Performing a clean boot: This could help determine if the problem is being caused by a program or service.

Though these steps may solve your problem, the crash dump indicates a systemic issue which may not be permanently resolved just by these methods. Your Windows installation seems to be compromised at the core system level causing multiple computers in your office to experience the same problem. You may need to consider reformatting and reinstalling Windows on affected systems, or you could contact a professional IT support to look at the systems affected since it's occurring in a corporate environment. Additionally, to prevent such problems in the future, ensure all computers are updated regularly and consider implementing a robust system recovery plan.