通过

dell R710 服务器频繁蓝屏 附上蓝屏代码，请求分析具体原因

匿名
2022-01-29T03:19:29+00:00

蓝屏 dell R710服务器 Windows Server 2012 R2 最近频繁蓝屏，这是2022年1月14日至2022年1月29的蓝屏信息，包括最新的MEMORY，请求分析，如需dmp文件，请在网盘下载：链接: https://pan.baidu.com/s/1inKu8rSpugZfSdxk8_BkPg 提取码: evnk ，谢谢。

Microsoft (R) Windows Debugger Version 10.0.22473.1005 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\yeyang\Desktop\新建文件夹\012822-28156-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

************* Path validation summary **************

Response Time (ms) Location

Deferred srv*

Symbol search path is: srv*

Executable search path is:

Windows 8.1 Kernel Version 9600 MP (8 procs) Free x64

Product: Server, suite: TerminalServer DataCenter SingleUserTS

Edition build lab: 9600.18685.amd64fre.winblue_ltsb.170427-1704

Machine Name:

Kernel base = 0xfffff80252271000 PsLoadedModuleList = 0xfffff80252544670

Debug session time: Fri Jan 28 17:10:15.013 2022 (UTC + 8:00)

System Uptime: 0 days 0:00:01.888

Loading Kernel Symbols

....................................................

Loading User Symbols

Loading unloaded module list

..

For analysis of this file, run !analyze -v

nt!KeBugCheckEx:

fffff802523bf2a0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffd0013e3fa5d0=0000000000000080

2: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

NMI_HARDWARE_FAILURE (80)

This is typically due to a hardware malfunction. The hardware supplier should

be called.

Arguments:

Arg1: 00000000004f4454, 'TDO'

Arg2: 0000000000000000, Status Byte

Arg3: 0000000000000000

Arg4: 0000000000000000

Debugging Details:

KEY_VALUES_STRING: 1 

Key  : Analysis.CPU.mSec  

Value: 1702  

Key  : Analysis.DebugAnalysisManager  

Value: Create  

Key  : Analysis.Elapsed.mSec  

Value: 1703  

Key  : Analysis.Init.CPU.mSec  

Value: 561  

Key  : Analysis.Init.Elapsed.mSec  

Value: 11040  

Key  : Analysis.Memory.CommitPeak.Mb  

Value: 63  

Key  : WER.OS.Branch  

Value: winblue\_ltsb  

Key  : WER.OS.Timestamp  

Value: 2017-04-27T17:04:00Z  

Key  : WER.OS.Version  

Value: 8.1.9600.18685

FILE_IN_CAB: 012822-28156-01.dmp

BUGCHECK_CODE: 80

BUGCHECK_P1: 4f4454

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:

ffffd0013e3fa5c8 fffff802522381c2 : 0000000000000080 00000000004f4454 0000000000000000 0000000000000000 : nt!KeBugCheckEx

ffffd0013e3fa5d0 fffff8025242e27d : 0000000000000001 fffff802522478c0 fffff802522478c0 ffffe00180165968 : hal!HalBugCheckSystem+0x7e

ffffd0013e3fa610 fffff80252238fa1 : ffffd001000006c0 ffffd0013e3fa830 0000000000000001 0000000000000000 : nt!WheaReportHwError+0x22d

ffffd0013e3fa670 fffff80252452050 : ffffd0013e3fa830 0000000000000001 0000000000000000 fffff80252454b3f : hal!HalHandleNMI+0xfe

ffffd0013e3fa6a0 fffff802523c87c2 : 0000000000000000 ffffd0013e3fa8b0 0000000000000000 0000000000000000 : nt!KiProcessNMI+0x150

ffffd0013e3fa6f0 fffff802523c8636 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KxNmiInterrupt+0x82

ffffd0013e3fa830 fffff802523c9a00 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiNmiInterrupt+0x176

ffffd0013e3f8998 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiMcheckAbort

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel.sys

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x80_4F4454_GenuineIntel_NOERRREC_IMAGE_GenuineIntel.sys

OS_VERSION: 8.1.9600.18685

BUILDLAB_STR: winblue_ltsb

OSPLATFORM_TYPE: x64

OSNAME: Windows 8.1

FAILURE_ID_HASH: {d5ef3836-2107-b7ec-b4d4-4d2ae9fc0e02}

Followup: MachineOwner

Microsoft (R) Windows Debugger Version 10.0.22473.1005 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\yeyang\Desktop\新建文件夹\MEMORY.DMP]

Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

************* Path validation summary **************

Response Time (ms) Location

Deferred srv*

Symbol search path is: srv*

Executable search path is:

Windows 8.1 Kernel Version 9600 MP (8 procs) Free x64

Product: Server, suite: TerminalServer DataCenter SingleUserTS

Edition build lab: 9600.18685.amd64fre.winblue_ltsb.170427-1704

Machine Name:

Kernel base = 0xfffff8002a48a000 PsLoadedModuleList = 0xfffff8002a75d670

Debug session time: Fri Jan 28 20:00:49.370 2022 (UTC + 8:00)

System Uptime: 0 days 0:47:23.710

Loading Kernel Symbols

...............................................................

...............................................Page 228905 not present in the dump file. Type ".hh dbgerr004" for details

.................

.....

Loading User Symbols

PEB is paged out (Peb.Ldr = 00007ff6`50223018). Type ".hh dbgerr001" for details

Loading unloaded module list

........

For analysis of this file, run !analyze -v

nt!KeBugCheckEx:

fffff8002a5d82a0 48894c2408 mov qword ptr [rsp+8],rcx ss:ffffd00165ebe5d0=0000000000000080

5: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

NMI_HARDWARE_FAILURE (80)

This is typically due to a hardware malfunction. The hardware supplier should

be called.

Arguments:

Arg1: 00000000004f4454, 'TDO'

Arg2: 0000000000000000, Status Byte

Arg3: 0000000000000000

Arg4: 0000000000000000

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

*** ***

*************************************************************************

KEY_VALUES_STRING: 1 

Key  : Analysis.CPU.mSec  

Value: 1406  

Key  : Analysis.DebugAnalysisManager  

Value: Create  

Key  : Analysis.Elapsed.mSec  

Value: 1406  

Key  : Analysis.Init.CPU.mSec  

Value: 750  

Key  : Analysis.Init.Elapsed.mSec  

Value: 7750  

Key  : Analysis.Memory.CommitPeak.Mb  

Value: 67  

Key  : WER.OS.Branch  

Value: winblue\_ltsb  

Key  : WER.OS.Timestamp  

Value: 2017-04-27T17:04:00Z  

Key  : WER.OS.Version  

Value: 8.1.9600.18685

FILE_IN_CAB: MEMORY.DMP

BUGCHECK_CODE: 80

BUGCHECK_P1: 4f4454

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

PROCESS_NAME: java.exe

STACK_TEXT:

ffffd00165ebe5c8 fffff8002a4511c2 : 0000000000000080 00000000004f4454 0000000000000000 0000000000000000 : nt!KeBugCheckEx

ffffd00165ebe5d0 fffff8002a64727d : 0000000000000001 fffff8002a4608c0 fffff8002a4608c0 ffffe00124d1e968 : hal!HalBugCheckSystem+0x7e

ffffd00165ebe610 fffff8002a451fa1 : ffffd001000006c0 ffffd00165ebe820 0000000000000001 0000000000000000 : nt!WheaReportHwError+0x22d

ffffd00165ebe670 fffff8002a66b050 : ffffd00165ebe830 0000000000000001 0000000000000000 fffff8002a66db3f : hal!HalHandleNMI+0xfe

ffffd00165ebe6a0 fffff8002a5e17c2 : 00000000d69b3b00 ffffd00165ebe8b0 0000000000000000 0000000000000000 : nt!KiProcessNMI+0x150

ffffd00165ebe6f0 fffff8002a5e1636 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KxNmiInterrupt+0x82

ffffd00165ebe830 fffff8002a5e2a00 : 000000006c64c1c2 0000000000000033 0000000000000206 0000000012abf478 : nt!KiNmiInterrupt+0x176

ffffd00165ebc998 000000006c64c1c2 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiMcheckAbort

0000000012abf478 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x6c64c1c2

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel.sys

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x80_4F4454_GenuineIntel_NOERRREC_IMAGE_GenuineIntel.sys

OS_VERSION: 8.1.9600.18685

BUILDLAB_STR: winblue_ltsb

OSPLATFORM_TYPE: x64

OSNAME: Windows 8.1

FAILURE_ID_HASH: {d5ef3836-2107-b7ec-b4d4-4d2ae9fc0e02}

Followup: MachineOwner

Windows 家庭版 | 以前的 Windows 版本 | 设备和驱动程序

锁定的问题。 此问题已从 Microsoft 支持社区迁移。 你可投票决定它是否有用，但不能添加评论或回复，也不能关注问题。 为了保护隐私，对于已迁移的问题，用户个人资料是匿名的。

0 个注释

1 个答案

排序依据： 非常有帮助
非常有帮助 最新 最早
  1. TaoLi 33,170 信誉分 独立顾问
    2022-01-29T08:09:30+00:00

    您好，日志上显示有硬件错误，不过这边主要处理Windows日常使用问题，关于Windows server 的相关问题，请在Microsoft Q&A Community中询问。

    https://docs.microsoft.com/en-us/answers/products/

    0 个注释