Windows server 2016 OS has crashed

Question

Windows server 2016 OS has crashed

Anonymous

Hi All,

I run into Windows server 2016 OS has crashed. Does anyone help me? Thanks in advance.

the event of system says BugCheck:

Bugcheck 1005 Unable to produce a minidmp file from the full dump file

Bugcheck 1001 The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050.

the event ID 1001's dump file is as follows:

Microsoft (R) Windows Debugger Version 10.0.17134.12 AMD64

Loading Dump File [C:\Users\li.yuewen\Desktop\MEMORY.DMP]

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

Symbol search path is: srv*

Executable search path is:

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

THIS DUMP FILE IS PARTIALLY CORRUPT.

KdDebuggerDataBlock is not present or unreadable.

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

No module list information. Delay kernel load.

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

THIS DUMP FILE IS PARTIALLY CORRUPT.

KdDebuggerDataBlock is not present or unreadable.

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

KdDebuggerData.KernBase < SystemRangeStart

Windows 10 Kernel Version 14393 MP (4 procs) Free x64

Product: LanManNt, suite: TerminalServer DataCenter SingleUserTS

Machine Name:

Kernel base = 0x0000000000000000 PsLoadedModuleList = 0xfffff80216113060

Debug session time: Fri Aug 10 12:38:22.258 2018 (UTC + 8:00)

System Uptime: 0 days 0:56:58.981

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

THIS DUMP FILE IS PARTIALLY CORRUPT.

KdDebuggerDataBlock is not present or unreadable.

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

No module list information. Delay kernel load.

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

THIS DUMP FILE IS PARTIALLY CORRUPT.

KdDebuggerDataBlock is not present or unreadable.

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

KdDebuggerData.KernBase < SystemRangeStart

Loading Kernel Symbols

No module list information. Delay kernel load.

GetContextState failed, 0xD0000147

CS descriptor lookup failed

GetContextState failed, 0xD0000147

Unable to get program counter

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffdf088d762000, 2, fffff80d581428b0, 0}

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

ReadControl failed - kernel symbols must be loaded first

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

1 answer

Answer 1

Sumit D - IA 170.7K Independent Advisor

We need log files(called dump files) that tell us what lead to crash.

Please share them with us for a better analysis of the problem. Instructions can be found here:

https://answers.microsoft.com/en-us/windows/for...

Please let us know if you need any assistance about posting dump files.

0 comments

Share via

Windows server 2016 OS has crashed

1 answer