windows server 2019 服务器蓝屏

Question

各位好，我有部服务器蓝屏，请问可以帮忙分析下原因么，谢谢

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 000000000000003f, An inpage operation failed with a CRC error. Parameter 2 contains
	the pagefile offset. Parameter 3 contains the page CRC value.
	Parameter 4 contains the expected CRC value.
Arg2: 0000000000157d63
Arg3: 0000000070ecb8a9
Arg4: 0000000007e77061

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 6750

    Key  : Analysis.Elapsed.mSec
    Value: 11548

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

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

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

    Key  : Bugcheck.Code.KiBugCheckData
    Value: 0x1a

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x1a

    Key  : Failure.Bucket
    Value: PAGE_HASH_ERRORS_0x1a_3f

    Key  : Failure.Hash
    Value: {6a2d4548-0eec-578d-e8f1-9e2239aa9a00}

    Key  : Hypervisor.Enlightenments.Value
    Value: 8992

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 2320

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.AsyncMemoryHint
    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: 1

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 0

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

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

    Key  : Hypervisor.Flags.ValueHex
    Value: 3008

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 0

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 0

    Key  : Hypervisor.RootFlags.Value
    Value: 0

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 0

    Key  : Memory.System.Errors.PageHashErrors
    Value: 1

    Key  : WER.OS.Branch
    Value: rs5_release

    Key  : WER.OS.Version
    Value: 10.0.17763.1


BUGCHECK_CODE:  1a

BUGCHECK_P1: 3f

BUGCHECK_P2: 157d63

BUGCHECK_P3: 70ecb8a9

BUGCHECK_P4: 7e77061

FILE_IN_CAB:  MEMORY.DMP

VIRTUAL_MACHINE:  VMware

ADDITIONAL_DEBUG_TEXT:  Memory Manager detected corruption of a pagefile page while performing an in-page operation.
The data read from storage does not match the original data written.
This indicates the data was corrupted by the storage stack, or device hardware.


BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


PROCESS_NAME:  AisEsmEdr.exe

PAGE_HASH_ERRORS_DETECTED: 1

STACK_TEXT:  
fffff982`8049f208 fffff803`5a8e03c2     : 00000000`0000001a 00000000`0000003f 00000000`00157d63 00000000`70ecb8a9 : nt!KeBugCheckEx
fffff982`8049f210 fffff803`5a7fd2ea     : ffffc602`54a074d0 ffffffff`ffffffff 00000000`00000000 ffffc602`54a075c0 : nt!MiValidatePagefilePageHash+0x30e
fffff982`8049f2f0 fffff803`5a64319d     : 00000000`00000002 fffff982`00000000 fffff982`8049f438 ffffeb75`00000000 : nt!MiWaitForInPageComplete+0x1ba75a
fffff982`8049f3e0 fffff803`5a65a69f     : ffff8000`00000000 00000000`c0033333 0000025e`6c969caf ffffc602`5104c580 : nt!MiIssueHardFault+0x1ad
fffff982`8049f490 fffff803`5a72c6f8     : ffffeb75`80979b20 ffffc602`5104c580 ffffeb75`80979b20 0000025e`6c967caf : nt!MmAccessFault+0x32f
fffff982`8049f630 fffff803`5a65861f     : 0000025e`6c969caf 0000025e`6c969caf ffffeb01`2f364b48 ffffeb75`80979b20 : nt!MiFaultInProbeAddress+0xa4
fffff982`8049f6e0 fffff803`5a65765e     : 80000001`bc02f811 0000025e`6c969caf fffff982`8049f850 0000025e`6c967000 : nt!MiLockPageLeafPageTable+0x27f
fffff982`8049f750 fffff803`5a656979     : 00000000`00000002 ffffc602`5e48daa0 ffffc602`5a2c6fb8 ffffc602`00000000 : nt!MiProbeAndLockPages+0x39e
fffff982`8049f8a0 fffff803`5abd1593     : fffff982`8049fb80 00000000`00001770 fffff982`8049fb00 ffffc602`5e48daa0 : nt!MmProbeAndLockPages+0x29
fffff982`8049f8d0 fffff803`5ac95c16     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0xc83
fffff982`8049fa20 fffff803`5a7e18f5     : 00000000`00000000 00007ff6`df4a5538 00000000`00000000 00000000`00000000 : nt!NtDeviceIoControlFile+0x56
fffff982`8049fa90 00007ffa`4d50fcd4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
000000d5`ea2ff8e8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`4d50fcd4


SYMBOL_NAME:  PAGE_HASH_ERRORS_INPAGE

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  PAGE_HASH_ERRORS_0x1a_3f

OS_VERSION:  10.0.17763.1

BUILDLAB_STR:  rs5_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {6a2d4548-0eec-578d-e8f1-9e2239aa9a00}

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

 *** Memory manager detected 1 instance(s) of corrupted pagefile page(s) while performing in-page operations.

Answer

您好

从您提供的信息来看，服务器遇到了一个名为“MEMORY_MANAGEMENT”的蓝屏错误，错误代码为0x1a。这个错误通常表示内存管理子系统检测到问题，可能是由于内存硬件故障、驱动程序问题或存储设备错误导致的。具体来说，错误参数1(0x3f)指示了一个在页文件操作中发生的CRC错误，这意味着存储数据与预期不匹配，可能由存储堆栈或硬件设备导致。

以下是一些可能的解决方案和建议：

1.检查硬件：重点是内存损坏或者硬盘错误。使用内存测试工具（如Memtest86）和硬件自检（如SMART测试）

2.更新驱动程序：确保所有的驱动程序，特别是存储控制器和网络控制器驱动，都是最新的。

3.虚拟化环境检查：由于你提到这是在VMware环境中运行的虚拟机，检查虚拟机设置，确保分配给它的资源充足且正确。同时，检查VMware主机的固件和驱动更新。

4.系统更新：确保操作系统已经安装了所有重要的安全更新和补丁。有时，这些问题可能是由于已知问题的修复。

5.禁用硬件加速：如果内存或存储设备支持硬件加速，尝试禁用这些功能，看看能否解决问题。

6.检查系统日志：查看“事件查看器“中的系统日志，可能会有更多的错误信息，帮助定位问题。

记得在处理过程中备份重要数据，以防丢失。

通过

windows server 2019 服务器蓝屏

2 个答案