Çözüldü System Service Exception Mavi Ekran Hatası

Bu konu çözüldü olarak işaretlenmiştir. Çözülmediğini düşünüyorsanız konuyu rapor edebilirsiniz.
İşletim sistemi
Windows 10

kaankrk

Femtopat
Katılım
15 Aralık 2020
Mesajlar
4
Daha fazla  
Cinsiyet
Erkek
Birkaç gündür mavi ekran hatası almaya başladım. Minidump dosyalarımı aşağıda bağlantı şeklinde paylaştım. Sorunun nedenini ve çözümünü bilen birisi bana yardımcı olabilirse çok mutlu olurum.
Mavi ekran hatasını normal PC kullanımımda veya oyun oynarken sadece 1 kez yaşadım ama ne zaman Epic Games'i açmaya çalışsam mavi ekran alıyorum.
2 tane farklı mavi ekran hatasıyla karşılaştım. Biri System Service Exception diğeri ise Kernel Data Inpage Error.

Minidump dosyalarım bu bağlantıda.
 
Çözüm
Evet, HDD'nizde sorun var. CMD'yi yönetici olarak çalıştırıp chkdsk /f /r komutunu girin, çıkan soruya "y" diye cevap verin ve sistemi yeniden başlatın. Bir de öyle yapın testi. Sorunu tam olarak çözmese bile biraz daha zaman kazandırabilir. En kısa zamanda verilerinizi yedekleyip bu HDD'den kurtulun, mavi ekran almanızın sebebi de bu.
Bellek testi yapın. Belleklerde sorun çıkarsa değiştirmeniz gerekecek, şimdiden belirteyim.

Ayrıca Windows'u güncelleyin. XIGNCODE3 Anti-Cheat'i kaldırın. Logitech Gaming Software'i kaldırın. Sisteme klavye ve fare dışında USB ile takılı bir aygıt varsa çıkarın, özellikle kontrolcü.

Kod:
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c000001d, Exception code that caused the bugcheck
Arg2: fffff80331c692e2, Address of the instruction which caused the bugcheck
Arg3: ffffe1815d0f9920, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 7437

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on BORA

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 9587

    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:  3b

BUGCHECK_P1: c000001d

BUGCHECK_P2: fffff80331c692e2

BUGCHECK_P3: ffffe1815d0f9920

BUGCHECK_P4: 0

CONTEXT:  ffffe1815d0f9920 -- (.cxr 0xffffe1815d0f9920)
rax=0000000000000001 rbx=ffff9e8462bf7650 rcx=ffff9e84639a1e90
rdx=0000000000000000 rsi=0000000000000000 rdi=ffff9e84639a1ea8
rip=fffff80331c692e2 rsp=ffff808d08738860 rbp=ffff808d08738b80
 r8=00000001000001c2  r9=ffffe1815d0a0180 r10=0000000000000000
r11=0000000000000000 r12=ffff9e84613a5080 r13=ffff9e84639a1d70
r14=0000000000000000 r15=ffff9e84639a1d70
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00210246
nt!NtWaitForWorkViaWorkerFactory+0x4f2:
fffff803`31c692e2 ff              ???
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  AMDRSServ.exe

MISALIGNED_IP:
nt!NtWaitForWorkViaWorkerFactory+4f2
fffff803`31c692e2 ff              ???

BAD_STACK_POINTER:  ffffe1815d0f9018

STACK_TEXT: 
ffff808d`08738860 fffff803`31e071b8     : ffff9e84`613a5080 00000069`4c5ff708 00000208`00000000 00000208`82ad3e08 : nt!NtWaitForWorkViaWorkerFactory+0x4f2
ffff808d`08738a90 00007fff`e102fa04     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000069`4c5ff7c8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`e102fa04


CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
32 errors : !nt (fffff80331c692e1-fffff80331c69300)
fffff80331c692e0  0d *ff *ff *ff *ff *ff *ff *ff *ff *ff *ff *ff *ff *ff *ff *ff ................
fffff80331c692f0 *ff *ff *ff *ff *ff *ff *ff *ff *ff *ff *ff *ff *ff *ff *ff *ff ................

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

MEMORY_CORRUPTOR:  LARGE_32

STACK_COMMAND:  .cxr 0xffffe1815d0f9920 ; kb

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE_32

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {8f482df0-6cb7-502d-3bf6-ac850e6d1520}

Followup:     memory_corruption
---------



KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: ffff858a76010338, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000009c, error status (normally i/o status code)
Arg3: 00002000111308c0, current process (virtual address for lock type 3, or PTE)
Arg4: fffff80551667000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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

*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 5624

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on BORA

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 15919

    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:  7a

BUGCHECK_P1: ffff858a76010338

BUGCHECK_P2: ffffffffc000009c

BUGCHECK_P3: 2000111308c0

BUGCHECK_P4: fffff80551667000

ERROR_CODE: (NTSTATUS) 0xc000009c - STATUS_DEVICE_DATA_ERROR

DISK_HARDWARE_ERROR: There was error with disk hardware

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  explorer.exe

TRAP_FRAME:  ffff840dc8ee4f70 -- (.trap 0xffff840dc8ee4f70)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000b086c3cf rbx=0000000000000000 rcx=00000000fcd4d6bd
rdx=000000008f14a8b0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8054c700dbe rsp=ffff840dc8ee5100 rbp=ffff840dc8ee5200
 r8=00000000bfb801d4  r9=000000006f933431 r10=00000000361e7d84
r11=00000000eefda3a4 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
cng!SymCryptSha256AppendBlocks_ul1+0x64e:
fffff805`4c700dbe 8b4b2c          mov     ecx,dword ptr [rbx+2Ch] ds:00000000`0000002c=????????
Resetting default scope

STACK_TEXT: 
ffff840d`c8ee4bc8 fffff805`4a8b6e29     : 00000000`0000007a ffff858a`76010338 ffffffff`c000009c 00002000`111308c0 : nt!KeBugCheckEx
ffff840d`c8ee4bd0 fffff805`4a8b4b35     : ffff840d`00001000 ffff840d`c8ee4d00 ffff840d`c8ee4d60 fffff805`00000000 : nt!MiWaitForInPageComplete+0x7d9
ffff840d`c8ee4cc0 fffff805`4a80c9c8     : 00000000`c0033333 00000000`00000000 fffff805`51667000 00000000`00000000 : nt!MiIssueHardFault+0x3c5
ffff840d`c8ee4dd0 fffff805`4aa0395e     : 00000000`9dfe77ef 00000000`00000000 00000000`c0000016 00000000`00000000 : nt!MmAccessFault+0x468
ffff840d`c8ee4f70 fffff805`4c700dbe     : ffffd705`e2acccf7 fffff805`4a850cb9 ffffffff`eefda3a4 ffff840d`d3441f54 : nt!KiPageFault+0x35e
ffff840d`c8ee5100 fffff805`4c6ffc8f     : fffff805`4d01d91b ffff840d`c8ee54f0 fffff805`51600000 ffffd705`c38f2730 : cng!SymCryptSha256AppendBlocks_ul1+0x64e
ffff840d`c8ee52c0 fffff805`4c6ff94d     : 00000000`00000000 00000000`00000000 00000000`01f153c8 ffffd705`c1c6d8b0 : cng!SymCryptSha256Append+0x4f
ffff840d`c8ee5300 fffff805`4c6ff857     : 00000000`00000000 00000000`00000000 fffff805`4c6fe1c0 fffff805`4c6fd70a : cng!MSCryptHashDataInternal+0xc9
ffff840d`c8ee5330 fffff805`4c6f5a22     : fffff805`51600238 00000000`00001790 00000000`000000a8 ffffd705`c38f2730 : cng!MSCryptHashData+0x87
ffff840d`c8ee53d0 fffff805`4d9fd490     : fffff805`51600188 fffff805`51600000 ffffd705`c38f2730 00000000`00001d01 : cng!BCryptHashData+0x82
ffff840d`c8ee5420 fffff805`51600188     : fffff805`51600000 ffffd705`c38f2730 00000000`00001d01 00000000`00000000 : FACEIT+0x9fd490
ffff840d`c8ee5428 fffff805`51600000     : ffffd705`c38f2730 00000000`00001d01 00000000`00000000 00000000`00000000 : 0xfffff805`51600188
ffff840d`c8ee5430 ffffd705`c38f2730     : 00000000`00001d01 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff805`51600000
ffff840d`c8ee5438 00000000`00001d01     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000202 : 0xffffd705`c38f2730
ffff840d`c8ee5440 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000202 00001790`01f15600 : 0x1d01


SYMBOL_NAME:  cng!SymCryptSha256AppendBlocks_ul1+64e

MODULE_NAME: cng

IMAGE_NAME:  cng.sys

IMAGE_VERSION:  10.0.19041.1131

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  64e

FAILURE_BUCKET_ID:  0x7a_c000009c_cng!SymCryptSha256AppendBlocks_ul1

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {295e4e5c-ac18-9396-3cf4-2d21c7faa644}

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



KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: ffffab0d7d8cd338, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000009c, error status (normally i/o status code)
Arg3: 0000200118ad28c0, current process (virtual address for lock type 3, or PTE)
Arg4: fffff80436e67000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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

*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 6796

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on BORA

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 17610

    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:  7a

BUGCHECK_P1: ffffab0d7d8cd338

BUGCHECK_P2: ffffffffc000009c

BUGCHECK_P3: 200118ad28c0

BUGCHECK_P4: fffff80436e67000

ERROR_CODE: (NTSTATUS) 0xc000009c - STATUS_DEVICE_DATA_ERROR

DISK_HARDWARE_ERROR: There was error with disk hardware

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  rundll32.exe

TRAP_FRAME:  fffff8828afcbf70 -- (.trap 0xfffff8828afcbf70)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000b086c3cf rbx=0000000000000000 rcx=00000000fcd4d6bd
rdx=000000008f14a8b0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80439100dbe rsp=fffff8828afcc100 rbp=fffff8828afcc200
 r8=00000000bfb801d4  r9=000000006f933431 r10=00000000361e7d84
r11=00000000eefda3a4 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
cng!SymCryptSha256AppendBlocks_ul1+0x64e:
fffff804`39100dbe 8b4b2c          mov     ecx,dword ptr [rbx+2Ch] ds:00000000`0000002c=????????
Resetting default scope

STACK_TEXT: 
fffff882`8afcbbc8 fffff804`35eb6e29     : 00000000`0000007a ffffab0d`7d8cd338 ffffffff`c000009c 00002001`18ad28c0 : nt!KeBugCheckEx
fffff882`8afcbbd0 fffff804`35eb4b35     : fffff882`00001000 fffff882`8afcbd00 fffff882`8afcbd60 fffff804`00000000 : nt!MiWaitForInPageComplete+0x7d9
fffff882`8afcbcc0 fffff804`35e0c9c8     : 00000000`c0033333 00000000`00000000 fffff804`36e67000 00000000`00000000 : nt!MiIssueHardFault+0x3c5
fffff882`8afcbdd0 fffff804`3600395e     : 00000000`171dbcce 00000000`00000000 00000000`c0000016 00000000`00000000 : nt!MmAccessFault+0x468
fffff882`8afcbf70 fffff804`39100dbe     : ffffd40a`e2acccf7 fffff804`35e50cb9 ffffffff`eefda3a4 fffff882`d3441f54 : nt!KiPageFault+0x35e
fffff882`8afcc100 fffff804`390ffc8f     : fffff804`39a1d91b fffff882`8afcc4f0 fffff804`36e00000 ffffd40a`cf1f9e10 : cng!SymCryptSha256AppendBlocks_ul1+0x64e
fffff882`8afcc2c0 fffff804`390ff94d     : 00000000`00000000 00000000`00000000 00000000`01f153c8 ffffd40a`cf66cd50 : cng!SymCryptSha256Append+0x4f
fffff882`8afcc300 fffff804`390ff857     : 00000000`00000000 00000000`00000000 fffff804`390fe1c0 fffff804`390fd70a : cng!MSCryptHashDataInternal+0xc9
fffff882`8afcc330 fffff804`390f5a22     : fffff804`36e00238 00000000`00001790 00000000`000000a8 ffffd40a`cf1f9e10 : cng!MSCryptHashData+0x87
fffff882`8afcc3d0 fffff804`3a3fd490     : fffff804`36e00188 fffff804`36e00000 ffffd40a`cf1f9e10 00000000`00001901 : cng!BCryptHashData+0x82
fffff882`8afcc420 fffff804`36e00188     : fffff804`36e00000 ffffd40a`cf1f9e10 00000000`00001901 00000000`00000000 : FACEIT+0x9fd490
fffff882`8afcc428 fffff804`36e00000     : ffffd40a`cf1f9e10 00000000`00001901 00000000`00000000 00000000`00000000 : 0xfffff804`36e00188
fffff882`8afcc430 ffffd40a`cf1f9e10     : 00000000`00001901 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff804`36e00000
fffff882`8afcc438 00000000`00001901     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000202 : 0xffffd40a`cf1f9e10
fffff882`8afcc440 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000202 00001790`01f15600 : 0x1901


SYMBOL_NAME:  cng!SymCryptSha256AppendBlocks_ul1+64e

MODULE_NAME: cng

IMAGE_NAME:  cng.sys

IMAGE_VERSION:  10.0.19041.1131

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  64e

FAILURE_BUCKET_ID:  0x7a_c000009c_cng!SymCryptSha256AppendBlocks_ul1

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {295e4e5c-ac18-9396-3cf4-2d21c7faa644}

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



KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: ffffda8ab74d2338, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000009c, error status (normally i/o status code)
Arg3: 00002001931be8c0, current process (virtual address for lock type 3, or PTE)
Arg4: fffff8041a867000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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

*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 5687

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on BORA

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 22172

    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:  7a

BUGCHECK_P1: ffffda8ab74d2338

BUGCHECK_P2: ffffffffc000009c

BUGCHECK_P3: 2001931be8c0

BUGCHECK_P4: fffff8041a867000

ERROR_CODE: (NTSTATUS) 0xc000009c - STATUS_DEVICE_DATA_ERROR

DISK_HARDWARE_ERROR: There was error with disk hardware

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  EpicGamesLauncher.exe

TRAP_FRAME:  ffff8c81094c8f70 -- (.trap 0xffff8c81094c8f70)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000b086c3cf rbx=0000000000000000 rcx=00000000fcd4d6bd
rdx=000000008f14a8b0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80415900dbe rsp=ffff8c81094c9100 rbp=ffff8c81094c9200
 r8=00000000bfb801d4  r9=000000006f933431 r10=00000000361e7d84
r11=00000000eefda3a4 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
cng!SymCryptSha256AppendBlocks_ul1+0x64e:
fffff804`15900dbe 8b4b2c          mov     ecx,dword ptr [rbx+2Ch] ds:00000000`0000002c=????????
Resetting default scope

STACK_TEXT: 
ffff8c81`094c8bc8 fffff804`108b6e29     : 00000000`0000007a ffffda8a`b74d2338 ffffffff`c000009c 00002001`931be8c0 : nt!KeBugCheckEx
ffff8c81`094c8bd0 fffff804`108b4b35     : ffff8c81`00001000 ffff8c81`094c8d00 ffff8c81`094c8d60 fffff804`00000000 : nt!MiWaitForInPageComplete+0x7d9
ffff8c81`094c8cc0 fffff804`1080c9c8     : 00000000`c0033333 00000000`00000000 fffff804`1a867000 00000000`00000000 : nt!MiIssueHardFault+0x3c5
ffff8c81`094c8dd0 fffff804`10a0395e     : 00000000`8217c0d3 00000000`00000000 00000000`c0000016 00000000`00000000 : nt!MmAccessFault+0x468
ffff8c81`094c8f70 fffff804`15900dbe     : ffffc108`e2acccf7 fffff804`10850cb9 ffffffff`eefda3a4 ffff8c81`d3441f54 : nt!KiPageFault+0x35e
ffff8c81`094c9100 fffff804`158ffc8f     : fffff804`1621d91b ffff8c81`094c94f0 fffff804`1a800000 ffffc108`c7f5b5d0 : cng!SymCryptSha256AppendBlocks_ul1+0x64e
ffff8c81`094c92c0 fffff804`158ff94d     : 00000000`00000000 00000000`00000000 00000000`01f153c8 ffffc108`c846dd90 : cng!SymCryptSha256Append+0x4f
ffff8c81`094c9300 fffff804`158ff857     : 00000000`00000000 00000000`00000000 fffff804`158fe1c0 fffff804`158fd70a : cng!MSCryptHashDataInternal+0xc9
ffff8c81`094c9330 fffff804`158f5a22     : fffff804`1a800238 00000000`00001790 00000000`000000a8 ffffc108`c7f5b5d0 : cng!MSCryptHashData+0x87
ffff8c81`094c93d0 fffff804`16bfd490     : fffff804`1a800188 fffff804`1a800000 ffffc108`c7f5b5d0 00000000`00001d01 : cng!BCryptHashData+0x82
ffff8c81`094c9420 fffff804`1a800188     : fffff804`1a800000 ffffc108`c7f5b5d0 00000000`00001d01 00000000`00000000 : FACEIT+0x9fd490
ffff8c81`094c9428 fffff804`1a800000     : ffffc108`c7f5b5d0 00000000`00001d01 00000000`00000000 00000000`00000000 : 0xfffff804`1a800188
ffff8c81`094c9430 ffffc108`c7f5b5d0     : 00000000`00001d01 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff804`1a800000
ffff8c81`094c9438 00000000`00001d01     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000202 : 0xffffc108`c7f5b5d0
ffff8c81`094c9440 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000202 00001790`01f15600 : 0x1d01


SYMBOL_NAME:  cng!SymCryptSha256AppendBlocks_ul1+64e

MODULE_NAME: cng

IMAGE_NAME:  cng.sys

IMAGE_VERSION:  10.0.19041.1131

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  64e

FAILURE_BUCKET_ID:  0x7a_c000009c_cng!SymCryptSha256AppendBlocks_ul1

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {295e4e5c-ac18-9396-3cf4-2d21c7faa644}

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



KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: ffff8d8ae979e338, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000009c, error status (normally i/o status code)
Arg3: 00002002018a38c0, current process (virtual address for lock type 3, or PTE)
Arg4: fffff8045e467000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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

*** WARNING: Unable to verify timestamp for FACEIT.sys
*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 7608

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on BORA

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 20552

    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:  7a

BUGCHECK_P1: ffff8d8ae979e338

BUGCHECK_P2: ffffffffc000009c

BUGCHECK_P3: 2002018a38c0

BUGCHECK_P4: fffff8045e467000

ERROR_CODE: (NTSTATUS) 0xc000009c - STATUS_DEVICE_DATA_ERROR

DISK_HARDWARE_ERROR: There was error with disk hardware

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  EpicGamesLauncher.exe

TRAP_FRAME:  ffff898749be0f70 -- (.trap 0xffff898749be0f70)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000b086c3cf rbx=0000000000000000 rcx=00000000fcd4d6bd
rdx=000000008f14a8b0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80459100dbe rsp=ffff898749be1100 rbp=ffff898749be1200
 r8=00000000bfb801d4  r9=000000006f933431 r10=00000000361e7d84
r11=00000000eefda3a4 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
cng!EntropyProvideData+0x18de:
fffff804`59100dbe 8b4b2c          mov     ecx,dword ptr [rbx+2Ch] ds:00000000`0000002c=????????
Resetting default scope

STACK_TEXT: 
ffff8987`49be0bc8 fffff804`556b6e29     : 00000000`0000007a ffff8d8a`e979e338 ffffffff`c000009c 00002002`018a38c0 : nt!KeBugCheckEx
ffff8987`49be0bd0 fffff804`556b4b35     : ffff8987`00001000 ffff8987`49be0d00 ffff8987`49be0d60 fffff804`00000000 : nt!MiWaitForInPageComplete+0x7d9
ffff8987`49be0cc0 fffff804`5560c9c8     : 00000000`c0033333 00000000`00000000 fffff804`5e467000 00000000`00000000 : nt!MiIssueHardFault+0x3c5
ffff8987`49be0dd0 fffff804`5580395e     : 00000000`03ef0ee6 00000000`00000000 00000000`c0000016 00000000`00000000 : nt!MmAccessFault+0x468
ffff8987`49be0f70 fffff804`59100dbe     : ffffc285`e2acccf7 fffff804`55650cb9 ffffffff`eefda3a4 ffff8987`d3441f54 : nt!KiPageFault+0x35e
ffff8987`49be1100 fffff804`590ffc8f     : fffff804`59a1d91b ffff8987`49be14f0 fffff804`5e400000 ffffc285`4d89d5d0 : cng!EntropyProvideData+0x18de
ffff8987`49be12c0 fffff804`590ff94d     : 00000000`00000000 00000000`00000000 00000000`01f153c8 ffffc285`4bc6d230 : cng!EntropyProvideData+0x7af
ffff8987`49be1300 fffff804`590ff857     : 00000000`00000000 00000000`00000000 fffff804`590fe1c0 fffff804`590fd70a : cng!EntropyProvideData+0x46d
ffff8987`49be1330 fffff804`590f5a22     : fffff804`5e400238 00000000`00001790 00000000`000000a8 ffffc285`4d89d5d0 : cng!EntropyProvideData+0x377
ffff8987`49be13d0 fffff804`5a3fd490     : fffff804`5e400188 fffff804`5e400000 ffffc285`4d89d5d0 00000000`00001301 : cng!BCryptHashData+0x82
ffff8987`49be1420 fffff804`5e400188     : fffff804`5e400000 ffffc285`4d89d5d0 00000000`00001301 00000000`00000000 : FACEIT+0x9fd490
ffff8987`49be1428 fffff804`5e400000     : ffffc285`4d89d5d0 00000000`00001301 00000000`00000000 00000000`00000000 : 0xfffff804`5e400188
ffff8987`49be1430 ffffc285`4d89d5d0     : 00000000`00001301 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff804`5e400000
ffff8987`49be1438 00000000`00001301     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000202 : 0xffffc285`4d89d5d0
ffff8987`49be1440 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000202 00001790`01f15600 : 0x1301


SYMBOL_NAME:  cng!EntropyProvideData+18de

MODULE_NAME: cng

IMAGE_NAME:  cng.sys

IMAGE_VERSION:  10.0.19041.1131

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  18de

FAILURE_BUCKET_ID:  0x7a_c000009c_cng!EntropyProvideData

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {b5895d44-40b8-6a29-8649-2a14f82c3dad}

Followup:     MachineOwner
---------
 
güncelleme.PNG


Öncelikle ilgilendiğiniz için teşekkür ederim. Dediğiniz gibi uygulamaları sildim ama Memtest'i yapamadım. Çok ilginçki siyah ekranda kalıyor ve ekrana hiçbir şey gelmiyor USB'yi çıkarıp PC'yi reslemediğim sürece öyle kalıyor. İşin garip yanı PC'de hiçbir sorun yok tüm uygulamalarım ve oyunlarım çalışıyor ama nezamanki Epic Games'e tıklasam mavi ekran alıyorum. 3-4 gün öncesine kadar böyle bir sorunumda yoktu. Epic Games'i silmeye kalktığımda bile mavi ekran alıyorum. Yani Epic Games'e hiçbir şekilde dokunamıyorum. Acaba son gelen Win güncellemerinden dolayımı oldu merak ediyorum. Laptopum eski olduğu için arada böyle saçma sapan problemlerle karşılaşabiliyorum. Formatla eski haline geri dönüyor ve uzun bir süre sorunsuz kullanabiliyorum. Sorunum artarsada format atmayı deneyeceğim. Yüklü Win güncellemerimide resim olarak ekledim.
 
Memtest önemliydi. Rehberi düzgün uygulamaya dikkat edin, olmazsa USB belleği başka bir porta takıp öyle yapmayı deneyin. Güncelleme geçmişinizde 20H2 görünüyor fakat şu anki sürümünüz 2004, isteğe bağlı güncelleştirmelerin altında 20H2 varsa yapın.

Ek olarak FACEIT'i de kaldırın. Dosyalarınıza tekrar bakma fırsatı buldum, pek çok yerde görüyorum kendisini. Sanırım cihazınızda HDD var. Ona da HD Tune Pro ile hata ve sağlık taraması yapın. Hata taraması yaparken quick scan seçeneği kapalı olsun.
 
Evet, HDD'nizde sorun var. CMD'yi yönetici olarak çalıştırıp chkdsk /f /r komutunu girin, çıkan soruya "y" diye cevap verin ve sistemi yeniden başlatın. Bir de öyle yapın testi. Sorunu tam olarak çözmese bile biraz daha zaman kazandırabilir. En kısa zamanda verilerinizi yedekleyip bu HDD'den kurtulun, mavi ekran almanızın sebebi de bu.
 
Çözüm

Yeni konular

Geri
Yukarı