Bilgisayar açılırken CRITICAL_PROCESS_DIED hatası

x3pos · 20 Eylül 2020

Bilgisayar açılırken çoğu zaman mavi ekran hatası veriyor.

Hata isimleri:
CRITICAL_PROCESS_DIED
ATTEMPTED_WRITE_TO_READONLY_MEMORY
MEMORY_MANAGEMENT
INTERNAL_POWER_EROOR
APC_INDEX_MISMATCH

Minidump dosyalarım: Yeni klasör.zip.

Evilmonster · 20 Eylül 2020

x3pos dedi:
Bilgisayar açılırken çoğu zaman mavi ekran hatası veriyor.

Hata isimleri:
CRITICAL_PROCESS_DIED
ATTEMPTED_WRITE_TO_READONLY_MEMORY
MEMORY_MANAGEMENT
INTERNAL_POWER_EROOR
APC_INDEX_MISMATCH

Minidump dosyalarım: Yeni klasör.zip.

Dump dosyalarını henüz incelemedim fakat sorunun RAM kaynaklı olduğunu düşünüyorum, daha detaylı inceledikten sonra bunu güncelleyeceğim.

bir2bir3bir4 · 20 Eylül 2020

RAM testi yapın.

yika38 · 20 Eylül 2020

Bellek hatası gibi duruyor.

XMP ayarı açıksa kapatın, MemTest86 ile belleklerinizi test edin.

Kod:

INTERNAL_POWER_ERROR (a0)
The power policy manager experienced a fatal error.
Arguments:
Arg1: 000000000000010e, The disk subsystem returned corrupt data while reading from the
    hibernation file.
Arg2: 000000000000000a
Arg3: 000000000000bc4a, Incorrect checksum
Arg4: 00000000000005a1, Previous disk read's checksum

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4671

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 13719

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

    Key  : Analysis.System
    Value: CreateObject


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

DUMP_FILE_ATTRIBUTES: 0x9
  Hiber Crash Dump
  Kernel Generated Triage Dump

BUGCHECK_CODE:  a0

BUGCHECK_P1: 10e

BUGCHECK_P2: a

BUGCHECK_P3: bc4a

BUGCHECK_P4: 5a1

CUSTOMER_CRASH_COUNT:  1

STACK_TEXT: 
ffffa504`14cf4648 fffff802`30bb149c     : 00000000`000000a0 00000000`0000010e 00000000`0000000a 00000000`0000bc4a : nt!KeBugCheckEx
ffffa504`14cf4650 fffff802`30bbedf1     : 00000000`00000001 ffff9387`9739c4f0 00000000`040f1cc0 ffff9387`b542c000 : nt!PopHiberChecksumHiberFileData+0x1083c
ffffa504`14cf46b0 fffff802`30bb0a75     : 00000000`00000000 ffffe38b`33131f38 00000000`00000001 00000000`00000001 : nt!PopRequestRead+0x7d
ffffa504`14cf4720 fffff802`30b9fdf0     : 00014541`7bd55221 ffffe38b`33131f38 00000000`00000000 00000000`00000000 : nt!PopRestoreHiberContext+0x10b2d
ffffa504`14cf47b0 fffff802`30b9fb2e     : fffff802`30e503f0 ffffa504`14cf4930 fffff802`30e503f0 00000000`00000100 : nt!PopHandleNextState+0x210
ffffa504`14cf4800 fffff802`30b9f8ab     : 00000000`00000100 fffff802`30e503f0 000001cc`c29f674e 00000000`00989680 : nt!PopIssueNextState+0x1a
ffffa504`14cf4830 fffff802`30ba2ac9     : 00000000`00000001 00000000`00000000 00000000`00000000 fffff802`3044bae5 : nt!PopInvokeSystemStateHandler+0x33b
ffffa504`14cf4a30 fffff802`30ba1cdd     : ffffffff`00000000 ffffffff`ffffffff ffffa504`14cf4bb0 00000000`00000000 : nt!PopEndMirroring+0x1e9
ffffa504`14cf4af0 fffff802`30ba1a25     : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000001 : nt!MmDuplicateMemory+0x261
ffffa504`14cf4b80 fffff802`30546745     : ffff9387`a46b6000 ffff9387`a46b6040 fffff802`30ba18f0 ffff9387`00000001 : nt!PopTransitionToSleep+0x135
ffffa504`14cf4c10 fffff802`305e5598     : ffffc080`3ae80180 ffff9387`a46b6040 fffff802`305466f0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffa504`14cf4c60 00000000`00000000     : ffffa504`14cf5000 ffffa504`14cef000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  nt!PopHiberChecksumHiberFileData+1083c

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.450

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  1083c

FAILURE_BUCKET_ID:  0xa0_10e_nt!PopHiberChecksumHiberFileData

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {28ba2091-a476-6f77-2dec-6241bccd4685}

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

Kod:

APC_INDEX_MISMATCH (1)
This is a kernel internal error. The most common reason to see this
bugcheck is when a filesystem or a driver has a mismatched number of
calls to disable and re-enable APCs. The key data item is the
Thread->CombinedApcDisable field. This consists of two separate 16-bit
fields, the SpecialApcDisable and the KernelApcDisable. A negative value
of either indicates that a driver has disabled special or normal APCs
(respectively) without re-enabling them; a positive value indicates that
a driver has enabled special or normal APCs (respectively) too many times.
Arguments:
Arg1: 00007fff5c24c564, Address of system call function or worker routine
Arg2: 0000000000000000, Thread->ApcStateIndex
Arg3: 00000000ffff0000, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
Arg4: ffffb8085cc45b80, Call type (0 - system call, 1 - worker routine)

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3218

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 10572

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

    Key  : Analysis.System
    Value: CreateObject

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  1

BUGCHECK_P1: 7fff5c24c564

BUGCHECK_P2: 0

BUGCHECK_P3: ffff0000

BUGCHECK_P4: ffffb8085cc45b80

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  firefox.exe

STACK_TEXT: 
ffffb808`5cc459b8 fffff807`639efe29     : 00000000`00000001 00007fff`5c24c564 00000000`00000000 00000000`ffff0000 : nt!KeBugCheckEx
ffffb808`5cc459c0 fffff807`639efcf3     : ffffce07`1015c080 ffffce07`1015c080 ffffce07`1015c080 00000022`0fa9f4f7 : nt!KiBugCheckDispatch+0x69
ffffb808`5cc45b00 00007fff`5c24c564     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x1fe
00000022`0fa9f3e8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`5c24c564


SYMBOL_NAME:  nt!KiSystemServiceExitPico+1fe

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.450

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  1fe

FAILURE_BUCKET_ID:  0x1_SysCallNum_3d_nt!KiSystemServiceExitPico

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {4dc00784-d9e4-d667-d0a8-e76801c389ec}

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

Kod:

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041792, A corrupt PTE has been detected. Parameter 2 contains the address of
    the PTE. Parameters 3/4 contain the low/high parts of the PTE.
Arg2: ffff98807b228b28
Arg3: 8000000000000000
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4156

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 7378

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

    Key  : Analysis.System
    Value: CreateObject

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  1a

BUGCHECK_P1: 41792

BUGCHECK_P2: ffff98807b228b28

BUGCHECK_P3: 8000000000000000

BUGCHECK_P4: 0

MEMORY_CORRUPTOR:  ONE_BIT

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  WerFault.exe

STACK_TEXT: 
ffff9988`6e0ca338 fffff802`6272abba     : 00000000`0000001a 00000000`00041792 ffff9880`7b228b28 80000000`00000000 : nt!KeBugCheckEx
ffff9988`6e0ca340 fffff802`627293ef     : ffffaa0f`a71259c0 00000000`00000000 ffff9880`00000002 00000000`00000000 : nt!MiDeleteVa+0x153a
ffff9988`6e0ca440 fffff802`62701670     : 00000000`00000001 ffff9988`00000000 ffffaa0f`a7125810 ffffaa0f`a93c45c0 : nt!MiDeletePagablePteRange+0x48f
ffff9988`6e0ca750 fffff802`62a9939f     : ffffaa0f`a93c45c0 00000000`00000000 ffffaa0f`00000000 ffffaa0f`00000000 : nt!MiDeleteVad+0x360
ffff9988`6e0ca860 fffff802`62ae4dd3     : ffffaa0f`a6f63100 ffffaa0f`a6f63100 ffffaa0f`ab706230 ffffaa0f`a7125340 : nt!MiCleanVad+0x43
ffff9988`6e0ca890 fffff802`62a81f5f     : ffffffff`00000000 ffffffff`ffffffff 00000000`00000001 ffffaa0f`a7125340 : nt!MmCleanProcessAddressSpace+0x137
ffff9988`6e0ca910 fffff802`62a9ea8a     : ffffaa0f`a7125340 ffffe406`77a82730 00000000`00000000 00000000`00000000 : nt!PspRundownSingleProcess+0x13b
ffff9988`6e0ca990 fffff802`629f3eae     : ffffaa0f`00000000 00000000`00000001 000002a7`6e5e1250 000000f6`44fc1000 : nt!PspExitThread+0x5f6
ffff9988`6e0caa90 fffff802`628058b8     : ffffaa0f`a7125340 ffffaa0f`a93c45c0 ffff9988`6e0cab80 ffffaa0f`a871c150 : nt!NtTerminateProcess+0xde
ffff9988`6e0cab00 00007fff`6f9cc344     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
000000f6`44d3fdb8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`6f9cc344


MODULE_NAME: hardware

IMAGE_NAME:  memory_corruption

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {e3faf315-c3d0-81db-819a-6c43d23c63a7}

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

Kod:

ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
An attempt was made to write to readonly memory.  The guilty driver is on the
stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: ffffccbffcaa5700, Virtual address for the attempted write.
Arg2: 1a000001497fe025, PTE contents.
Arg3: ffff860c468ecd60, (reserved)
Arg4: 000000000000000a, (reserved)

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4030

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 10590

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

    Key  : Analysis.System
    Value: CreateObject

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  be

BUGCHECK_P1: ffffccbffcaa5700

BUGCHECK_P2: 1a000001497fe025

BUGCHECK_P3: ffff860c468ecd60

BUGCHECK_P4: a

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  sihost.exe

TRAP_FRAME:  ffff860c468ed360 -- (.trap 0xffff860c468ed360)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00007ff954adff00 rbx=0000000000000000 rcx=0000000000005a4d
rdx=00007ff954ae0000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8033ed36925 rsp=ffff860c468ed4f8 rbp=ffff860c468ed640
 r8=0000000000000000  r9=ffff860c468ed538 r10=0000000000000000
r11=ffffbb8e1293c7b0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!RtlImageNtHeaderEx+0x35:
fffff803`3ed36925 66390a          cmp     word ptr [rdx],cx ds:00007ff9`54ae0000=????
Resetting default scope

STACK_TEXT: 
ffff860c`468ecb68 fffff803`3ee2f11a     : 00000000`000000be ffffccbf`fcaa5700 1a000001`497fe025 ffff860c`468ecd60 : nt!KeBugCheckEx
ffff860c`468ecb70 fffff803`3eceec6f     : 1a000001`497fe025 00000000`00000003 ffff860c`468ecde0 00000000`00000000 : nt!MiRaisedIrqlFault+0x1e28fe
ffff860c`468ecbc0 fffff803`3ee0205e     : ffffbb8e`1c6c3b50 00000000`00000000 ffffbb8e`1a807080 ffffcce6`5ffe5528 : nt!MmAccessFault+0x4ef
ffff860c`468ecd60 fffff803`3ed31d5e     : ffff860c`468ed038 ffff860c`468ecef0 ffffccbf`fcaa6000 00000000`00000000 : nt!KiPageFault+0x35e
ffff860c`468ecef0 fffff803`3ecec976     : ffffbb8e`00000100 ffff860c`00000000 00000000`00000002 00000007`ff954ae0 : nt!MiResolveSharedZeroFault+0x46e
ffff860c`468ed040 fffff803`3ecef66d     : ffff860c`468ed280 ffff860c`468ed1c0 ffff860c`468ed1c8 ffff860c`468ed1d8 : nt!MiZeroFault+0x316
ffff860c`468ed130 fffff803`3ecee8ea     : 00000000`00000000 ffffbb8e`00000100 ffffbb8e`1297d710 ffffaa81`a2e8ad80 : nt!MiUserFault+0x80d
ffff860c`468ed1c0 fffff803`3ee0205e     : ffffbb8e`1dc34400 fffff803`4f3bd30f 00000000`00000000 ffffbb8e`1a0e8601 : nt!MmAccessFault+0x16a
ffff860c`468ed360 fffff803`3ed36925     : fffff803`3ed368de ffffbb8e`1293c7c8 ffff860c`468ed9e0 ffffbb8e`1293c7b0 : nt!KiPageFault+0x35e
ffff860c`468ed4f8 fffff803`3ed368de     : ffffbb8e`1293c7c8 ffff860c`468ed9e0 ffffbb8e`1293c7b0 fffff803`3d412203 : nt!RtlImageNtHeaderEx+0x35
ffff860c`468ed500 fffff803`3f09d242     : ffffbb8e`1293c7b0 00000000`00000000 00000000`00000000 fffff803`3d449f1f : nt!RtlImageNtHeader+0x1e
ffff860c`468ed530 fffff803`3f09c7ea     : ffff860c`468ed720 ffffbb8e`1a1796b8 ffffbb8e`1a179660 ffffbb8e`1df233e8 : nt!PerfLogImageLoad+0xb6
ffff860c`468ed610 fffff803`3f09bb0d     : 00000000`0000085a ffffaa81`b292a6b0 ffff860c`468ed780 ffffbb8e`1df23300 : nt!PsCallImageNotifyRoutines+0xaa
ffff860c`468ed680 fffff803`3f0e587c     : ffffbb8e`1a155320 00000000`00000000 ffff860c`468ed858 ffff860c`468ed9b8 : nt!MiMapViewOfImageSection+0x74d
ffff860c`468ed800 fffff803`3f0e48a9     : 00000000`00000000 ffff860c`468edb80 00000210`7d3cf2b0 00000000`00000000 : nt!MiMapViewOfSection+0x3fc
ffff860c`468ed950 fffff803`3ee058b8     : ffffbb8e`21846580 00000089`b947f598 00000000`00000000 00000000`00000000 : nt!NtMapViewOfSection+0x159
ffff860c`468eda90 00007ff9`5802c2c4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000089`b947f578 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`5802c2c4


SYMBOL_NAME:  nt!MiRaisedIrqlFault+1e28fe

MODULE_NAME: nt

IMAGE_VERSION:  10.0.19041.508

STACK_COMMAND:  .thread ; .cxr ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  1e28fe

FAILURE_BUCKET_ID:  0xBE_nt!MiRaisedIrqlFault

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {1c5b4d11-09e0-def3-d2d0-70a11d69b92d}

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

Kod:

CRITICAL_PROCESS_DIED (ef)
        A critical system process died
Arguments:
Arg1: ffffb98ef103c240, 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:
------------------


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4202

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 9615

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

    Key  : Analysis.System
    Value: CreateObject

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  ef

BUGCHECK_P1: ffffb98ef103c240

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

PROCESS_NAME:  svchost.exe

CRITICAL_PROCESS:  svchost.exe

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

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

STACK_TEXT: 
ffff8b03`41653938 fffff807`3cd081c2     : 00000000`000000ef ffffb98e`f103c240 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffff8b03`41653940 fffff807`3cc3a90b     : 00000000`00000000 fffff807`3c60d6fd 00000000`00000002 fffff807`3c60bc9b : nt!PspCatchCriticalBreak+0x10e
ffff8b03`416539e0 fffff807`3c9f4070     : ffffb98e`00000000 00000000`00000000 ffffb98e`f103c240 ffffb98e`f103c678 : nt!PspTerminateAllThreads+0x151faf
ffff8b03`41653a50 fffff807`3c9f3e6c     : ffffb98e`eaa16080 00000000`00000000 00007ffa`bfdafc98 00000000`00002efc : nt!PspTerminateProcess+0xe0
ffff8b03`41653a90 fffff807`3c8058b8     : ffffb98e`f103c240 ffffb98e`f14bf080 ffff8b03`41653b80 ffffb98e`00000000 : nt!NtTerminateProcess+0x9c
ffff8b03`41653b00 00007ffa`de32c344     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
000000a4`9327ed28 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`de32c344


SYMBOL_NAME:  nt!PspCatchCriticalBreak+10e

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.508

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  10e

FAILURE_BUCKET_ID:  0xEF_svchost.exe_BUGCHECK_CRITICAL_PROCESS_f14bf080_nt!PspCatchCriticalBreak

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {19a1355d-3031-b09a-00ad-87bb07e43120}

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

Evilmonster · 20 Eylül 2020

Sorunun kaynağı ntoskernel.exe dosyasındaymış, temiz format gerekli.

Çözüldü: Windows 10 "Ntoskrnl.exe" Mavi Ekran Hatası

Bu hatayı 4-5 ay önce alıyordum. Format atmıştık ve düzelmişti. Şimdi 5 ay sonra tekrardan bu hata ile karşılaşmak beni üzdü. BlueScreenView görüntüsünü atıyorum.

www.technopat.net

İşte burada çözümler bulunuyor.

bir2bir3bir4 dedi:
Bu içeriği görüntülemek için üçüncü taraf çerezlerini yerleştirmek için izninize ihtiyacımız olacak.
Daha detaylı bilgi için, çerezler sayfamıza bakınız.

RAM testi yapın.

Bunu da yapmanızda fayda var.

yika38 · 20 Eylül 2020

Evilmonster dedi:
Sorunun kaynağı ntoskrnl.exe dosyasındaymış, temiz format gerekli.

Mavi ekran hatasında açık açık sorunun donanımsal ve bellekte bozulma kaynaklı olduğu yazıyor. Bu durumda formatla çözülmez.

Kod:

MEMORY_MANAGEMENT (1a)

MODULE_NAME: hardware

IMAGE_NAME:  memory_corruption

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

x3pos · 20 Eylül 2020

bellek 3200 mhz destekliyor. bios ekranında 3 adet profil var. acaba hazır profil yüzünden olabilir mi? çünkü sadece bilgisayar başlarken oluyor ve bilgisayarı daha yeni aldım 1 ay oldu. bütün parçalar yeni.
profili kapatınca 2400 mhz'e düşüyor. profiller dışında 3200 mhz yapmayı bulamadım.
Anakart
GIGABYTE B450M S2H 3200MHz(OC) DDR4 Soket AM4
RAM:
GSKILL 8GB Ripjaws V Siyah 3200MHz CL16 DDR4 Single Kit

yika38 · 20 Eylül 2020

Hazır profil ayarını şimdilik kapatın ve MemTest86 ile bellek testini yapın.

Bilgisayar açılırken CRITICAL_PROCESS_DIED hatası

Ayrıntılı düzenleme

x3pos

Hectopat

Evilmonster

Hectopat

bir2bir3bir4

Hectopat

yika38

Gigapat

Evilmonster

Hectopat

Çözüldü: Windows 10 "Ntoskrnl.exe" Mavi Ekran Hatası

yika38

Gigapat

x3pos

Hectopat

yika38

Gigapat

Benzer konular

Yeni konular

Yeni mesajlar

Gizliliğinize önem veriyoruz