Windows 10 Critical Process Died Hatası

rbl

Kilopat
Katılım
8 Kasım 2015
Mesajlar
79
Makaleler
1
Daha fazla  
Cinsiyet
Erkek
Merhaba arkadaşlar. Bilgisayarda bazen günde 1 bazen daha fazla olacak şekilde mavi ekran hatası veriyor. Nedenini anlamış değilim. Dump dosyası da bu Dropbox - Herkese Açık ama bunla ne yapacağımı bilmiyorum. Yardımlarınız için şimdiden teşekkürler.
 
Windows sürümünüz çok eski. Öncelikle 1903'e geçin.


BIOS'unuz da çok eski güncelleyin:


Bellek testi yapın:


Kod:
CRITICAL_PROCESS_DIED (ef)
        A critical system process died
Arguments:
Arg1: ffffe0012c77a840, 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.Sec
Value: 2

Key : Analysis.Elapsed.Sec
Value: 23

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


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10586.839.amd64fre.th2_release.170303-1605

SYSTEM_MANUFACTURER: MSI

SYSTEM_PRODUCT_NAME: MS-7978

SYSTEM_SKU: Default string

SYSTEM_VERSION: 2.0

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: C.90

BIOS_DATE: 12/21/2016

BASEBOARD_MANUFACTURER: MSI

BASEBOARD_PRODUCT: H170 GAMING M3 (MS-7978)

BASEBOARD_VERSION: 2.0

DUMP_TYPE: 2

BUGCHECK_P1: ffffe0012c77a840

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

PROCESS_NAME: csrss.exe

CRITICAL_PROCESS: csrss.exe

EXCEPTION_RECORD:  ffffc001ad8ec150 -- (.exr 0xffffc001ad8ec150)
ExceptionAddress: ffffe0012b043b20
   ExceptionCode: 02480705
ExceptionFlags: 30020260
NumberParameters: 200704
Parameter[0]: 0000000000030600
Parameter[1]: 0000000000030600
Parameter[2]: ffffe0012b043a38
Parameter[3]: ffffc001ad8ec188
Parameter[4]: ffffc001ad8ec188
Parameter[5]: 0000000000000000
Parameter[6]: ffffc001ad8ec140
Parameter[7]: 0000000000000000
Parameter[8]: ffffe0012c75d908
Parameter[9]: 0000000000000000
Parameter[10]: ffffc001ad8ec1c0
Parameter[11]: ffffc001ad8ec1c0
Parameter[12]: ffffc001ad8ec150
Parameter[13]: 0000000000000000
Parameter[14]: 000000000000002e

EXCEPTION_CODE: (Win32) 0x2480705 (38274821) - <Unable to get error code text>

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

CPU_COUNT: 4

CPU_MHZ: cf0

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

CPU_MICROCODE: 6,5e,3,0 (F,M,S,R) SIG: A6'00000000 (cache) A6'00000000 (init)

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0xEF

CURRENT_IRQL: 0

EXCEPTION_CODE_STR: 2480705

EXCEPTION_PARAMETER1: 0000000000030600

EXCEPTION_PARAMETER2: 0000000000030600

EXCEPTION_PARAMETER3: ffffe0012b043a38

EXCEPTION_PARAMETER4: 0

ANALYSIS_SESSION_HOST: DESKTOP-HH6FM2D

ANALYSIS_SESSION_TIME: 07-24-2019 16:29:21.0203

ANALYSIS_VERSION: 10.0.18914.1001 amd64fre

LAST_CONTROL_TRANSFER: from fffff802b0ab506c to fffff802b05b9940

STACK_TEXT:
ffffd001`90c9fbd8 fffff802`b0ab506c : 00000000`000000ef ffffe001`2c77a840 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffd001`90c9fbe0 fffff802`b08ba568 : 00000000`00000000 ffffe001`2b0233a0 00000000`00000001 fffff802`b04d7eda : nt!PspCatchCriticalBreak+0xa4
ffffd001`90c9fc20 fffff802`b08bab2d : ffffe001`2c77a840 ffffe001`2c77a840 ffffe001`2b0233a0 00000000`00000000 : nt!PspTerminateAllThreads+0x74
ffffd001`90c9fc80 fffff802`b0938b40 : ffffe001`2c77a840 00000000`c0000006 ffffe001`2c77a840 ffffe001`2b023080 : nt!PspTerminateProcess+0x101
ffffd001`90c9fcc0 fffff802`b05c41a3 : ffffe001`2c77a840 ffffe001`2b023080 ffffd001`90c9fdb0 fffff802`b08395b0 : nt!NtTerminateProcess+0x9c
ffffd001`90c9fd30 fffff802`b05bc830 : fffff802`b047e07d ffffd001`90ca0958 ffffd001`90ca0958 ffffd001`90ca0a00 : nt!KiSystemServiceCopyEnd+0x13
ffffd001`90c9fec8 fffff802`b047e07d : ffffd001`90ca0958 ffffd001`90ca0958 ffffd001`90ca0a00 00000000`00000003 : nt!KiServiceLinkage
ffffd001`90c9fed0 fffff802`b05c45c2 : ffffc001`ad8ec150 00003200`000001dc 00000000`00000000 fffff6fb`7dbedf68 : nt!KiDispatchException+0x5b9
ffffd001`90ca0820 fffff802`b05c2ca1 : ffffe001`2b023080 00000000`00000000 ffffe001`2b023080 ffffd001`90ca0a80 : nt!KiExceptionDispatch+0xc2
ffffd001`90ca0a00 00007ffe`0dd0630a : 00000000`00000000 00000058`00000000 00007ffe`0a286aa0 00007ffe`0dd79aed : nt!KiPageFault+0x221
00000058`b0281620 00000000`00000000 : 00000058`00000000 00007ffe`0a286aa0 00007ffe`0dd79aed 00007ffe`0a296000 : 0x00007ffe`0dd0630a


THREAD_SHA1_HASH_MOD_FUNC: f6b0f7fafbd5253fc3d42ad0a11af14fddabdcf0

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 54f9fdb9b3a5878961cc9439862ecadbf543a678

THREAD_SHA1_HASH_MOD: bc100a5647b828107ac4e18055e00abcbe1ec406

FOLLOWUP_IP:
nt!PspCatchCriticalBreak+a4
fffff802`b0ab506c cc int 3

FAULT_INSTR_CODE: 5c8b48cc

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!PspCatchCriticalBreak+a4

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 58ba3ece

IMAGE_VERSION: 10.0.10586.839

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: a4

FAILURE_BUCKET_ID: 0xEF_csrss.exe_BUGCHECK_CRITICAL_PROCESS_2b023080_nt!PspCatchCriticalBreak

BUCKET_ID: 0xEF_csrss.exe_BUGCHECK_CRITICAL_PROCESS_2b023080_nt!PspCatchCriticalBreak

PRIMARY_PROBLEM_CLASS: 0xEF_csrss.exe_BUGCHECK_CRITICAL_PROCESS_2b023080_nt!PspCatchCriticalBreak

TARGET_TIME: 2017-03-31T10:21:04.000Z

OSBUILD: 10586

OSSERVICEPACK: 839

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2017-03-04 07:13:02

BUILDDATESTAMP_STR: 170303-1605

BUILDLAB_STR: th2_release

BUILDOSVER_STR: 10.0.10586.839.amd64fre.th2_release.170303-1605

ANALYSIS_SESSION_ELAPSED_TIME: 5c1e

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0xef_csrss.exe_bugcheck_critical_process_2b023080_nt!pspcatchcriticalbreak

FAILURE_ID_HASH: {5d140ef1-18be-ca68-ad9a-650422119c3b}

Followup: MachineOwner
---------
 
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.

Yeni konular

Geri
Yukarı