CRITICAL_PROCESS_DIED Mavi Ekran Hatası

Mercury

Hectopat
Katılım
11 Kasım 2015
Mesajlar
5
Daha fazla  
Cinsiyet
Erkek
Selam arkadaşlar bu DMP dosyasini analiz eder misiniz?


Kod:
Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\etiba\Desktop\111820-37250-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 10 Kernel Version 18362 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff804`25a00000 PsLoadedModuleList = 0xfffff804`25e461b0
Debug session time: Wed Nov 18 16:35:07.464 2020 (UTC + 4:00)
System Uptime: 0 days 0:13:13.222
Loading Kernel Symbols
...............................................................
................................................................
................................................................

Loading User Symbols
Loading unloaded module list
.....
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`25bc3b20 48894c2408      mov     qword ptr [rsp+8],rcx ss:ffff8288`eb376c20=00000000000000ef
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

CRITICAL_PROCESS_DIED (ef)
A critical system process died
Arguments:
Arg1: ffffbb0ec8b5f480, Process object or thread object
Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.
Arg3: 0000000000000000
Arg4: 0000000000000000

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

ETW minidump data unavailable

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 8827

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-L0NPJ0I

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 28076

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

Key : Analysis.System
Value: CreateObject

Key : WER.OS.Branch
Value: 19h1_release

Key : WER.OS.Timestamp
Value: 2019-03-18T12:02:00Z

Key : WER.OS.Version
Value: 10.0.18362.1


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE: ef

BUGCHECK_P1: ffffbb0ec8b5f480

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

PROCESS_NAME: svchost.exe

CRITICAL_PROCESS: svchost.exe

EXCEPTION_RECORD:  ffffbb0ec8b5fa40 -- (.exr 0xffffbb0ec8b5fa40)
ExceptionAddress: 0000000000000000
   ExceptionCode: 00000000
ExceptionFlags: 00000000
NumberParameters: 0

ERROR_CODE: (NTSTATUS) 0xc7cda080 - <Unable to get error code text>

CUSTOMER_CRASH_COUNT: 1

EXCEPTION_STR: 0x0

STACK_TEXT:
ffff8288`eb376c18 fffff804`262c9a49 : 00000000`000000ef ffffbb0e`c8b5f480 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffff8288`eb376c20 fffff804`261da501 : ffffbb0e`c8b5f480 fffff804`25b20d35 ffffbb0e`c8b5f480 fffff804`25ae9438 : nt!PspCatchCriticalBreak+0x115
ffff8288`eb376cc0 fffff804`26072898 : ffffbb0e`00000000 00000000`00000000 ffffbb0e`c8b5f480 ffffbb0e`c8b5f480 : nt!PspTerminateAllThreads+0x165a35
ffff8288`eb376d30 fffff804`260d6db9 : ffffffff`ffffffff ffff8288`eb376e60 ffffbb0e`c8b5f480 fffff804`25bd5800 : nt!PspTerminateProcess+0xe0
ffff8288`eb376d70 fffff804`25bd588e : 00007ffe`00000410 ffffbb0e`c7cda080 ffffbb0e`c8b5f480 ffff8288`eb376fb0 : nt!NtTerminateProcess+0xa9
ffff8288`eb376de0 fffff804`25bc7940 : fffff804`25be9220 ffff8288`eb377958 ffff8288`eb377958 ffff8288`eb376fb0 : nt!KiSystemServiceExitPico+0x2b9
ffff8288`eb376f78 fffff804`25be9220 : ffff8288`eb377958 ffff8288`eb377958 ffff8288`eb376fb0 00007ffe`2a616bab : nt!KiServiceLinkage
ffff8288`eb376f80 fffff804`25bd5a5d : ffffbb0e`c8b5fa40 fffff804`25adfb81 00000000`00005000 ffff8288`eb377a00 : nt!KiDispatchException+0x1d3470
ffff8288`eb377820 fffff804`25bd1c43 : 00000000`000a04be ffff8288`eb377a80 00000000`00000000 ffffbb0e`c8b5f480 : nt!KiExceptionDispatch+0x11d
ffff8288`eb377a00 00007ffe`2acdccf5 : 000000f4`135817c8 000000f4`13581850 00007ffe`2ae3277c 00000000`00000000 : nt!KiPageFault+0x443
000000f4`135811e0 000000f4`135817c8 : 000000f4`13581850 00007ffe`2ae3277c 00000000`00000000 000000f4`13581e70 : 0x00007ffe`2acdccf5
000000f4`135811e8 000000f4`13581850 : 00007ffe`2ae3277c 00000000`00000000 000000f4`13581e70 000000f4`135817b0 : 0x000000f4`135817c8
000000f4`135811f0 00007ffe`2ae3277c : 00000000`00000000 000000f4`13581e70 000000f4`135817b0 00007ffe`2a616bab : 0x000000f4`13581850
000000f4`135811f8 00000000`00000000 : 000000f4`13581e70 000000f4`135817b0 00007ffe`2a616bab 00007ffe`2acde2d9 : 0x00007ffe`2ae3277c


SYMBOL_NAME: nt!PspCatchCriticalBreak+115

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION: 10.0.18362.1198

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 115

FAILURE_BUCKET_ID: 0xEF_svchost.exe_BUGCHECK_CRITICAL_PROCESS_c7cda080_nt!PspCatchCriticalBreak

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {700f7111-200c-a229-0380-05206177d34f}

Followup: MachineOwner
---------
 
Son düzenleyen: Moderatör:
Lütfen yeni konu açarak minidump dosyanı paylaş.

 
Bu hata genelde RAM belleklerinin kapasitesinin dolmasından dolayı olur. Bence Memtest ile RAM belleklerinize bir test yapın.
 
Uyarı! Bu konu 5 yıl önce açıldı.
Muhtemelen daha fazla tartışma gerekli değildir ki bu durumda yeni bir konu başlatmayı öneririz. Eğer yine de cevabınızın gerekli olduğunu düşünüyorsanız buna rağmen cevap verebilirsiniz.

Technopat Haberler

Yeni konular

Geri
Yukarı