Durup dururken alınan mavi ekran

İşletim sistemi
Windows 10
Sorun RAM'de görünüyor. Lütfen Memtest86 testi uygulayıp sonucu bizimle paylaşın.

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.


[CODE title="Dökümler"]Microsoft (R) Windows Debugger Version 10.0.21306.1007 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Enes3078\Downloads\032721-8421-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 19041 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff802`17400000 PsLoadedModuleList = 0xfffff802`1802a490
Debug session time: Sat Mar 27 23:33:48.311 2021 (UTC + 3:00)
System Uptime: 0 days 0:01:54.073
Loading Kernel Symbols
...............................................................
................................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
...............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`177f5db0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffc50a`2b27d940=00000000000001c7
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

STORE_DATA_STRUCTURE_CORRUPTION (1c7)
The store component detected a corruption in its data structures.
Arguments:
Arg1: 0000000000000000, A chunk heap buffer's hash doesn't match.
Arg2: ffffd9894131c000, Chunk heap buffer whose hash didn't match.
Arg3: 00000000ba54d43b, Expected buffer hash.
Arg4: 000000000012b11c, Page frame number of the corrupted page.

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

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 8686

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 34684

Key : Analysis.Init.CPU.mSec
Value: 2843

Key : Analysis.Init.Elapsed.mSec
Value: 33778

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

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


BUGCHECK_CODE: 1c7

BUGCHECK_P1: 0

BUGCHECK_P2: ffffd9894131c000

BUGCHECK_P3: ba54d43b

BUGCHECK_P4: 12b11c

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: MemCompression

STACK_TEXT:
ffffc50a`2b27d938 fffff802`1782827e : 00000000`000001c7 00000000`00000000 ffffd989`4131c000 00000000`ba54d43b : nt!KeBugCheckEx
ffffc50a`2b27d940 fffff802`1763fd15 : 6de3e000`1ccab573 00000000`0012b11c 00000000`00000012 ffffc50a`2b27da69 : nt!SmHpBufferProtectEx+0x1e855a
ffffc50a`2b27d9a0 fffff802`1763f348 : 00000000`ffffffff ffff923b`f3ae9959 ffffd989`4131b888 00000000`200017e6 : nt!SmHpChunkUnprotect+0x2d
ffffc50a`2b27d9d0 fffff802`176c518c : 00000000`00000000 00000000`00000000 ffffc50a`2b27da69 00000000`00000000 : nt!ST_STORE<SM_TRAITS>::StDmPageRecordUnprotect+0x1c
ffffc50a`2b27da00 fffff802`1763eda2 : 00000000`00000000 ffffd989`3fab4f50 00000000`00000000 fffff802`1763ec93 : nt!ST_STORE<SM_TRAITS>::StDmPageRemove+0x130
ffffc50a`2b27dad0 fffff802`1763e2ce : ffffd989`3ebbd000 ffffc50a`2b27db98 00000000`00000001 ffffd989`3ecb9080 : nt!ST_STORE<SM_TRAITS>::StWorkItemProcess+0xc2
ffffc50a`2b27db20 fffff802`177223f1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SMKM_STORE<SM_TRAITS>::SmStWorker+0x12a
ffffc50a`2b27dbe0 fffff802`17717e85 : ffffd989`3ebbd000 fffff802`177223e0 ffffc50a`2b21b3a8 00000000`00000000 : nt!SMKM_STORE<SM_TRAITS>::SmStWorkerThread+0x11
ffffc50a`2b27dc10 fffff802`177fd408 : ffff9c80`967c6180 ffffd989`3ecb9080 fffff802`17717e30 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffc50a`2b27dc60 00000000`00000000 : ffffc50a`2b27e000 ffffc50a`2b278000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: nt!SmHpBufferProtectEx+1e855a

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.906

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 1e855a

FAILURE_BUCKET_ID: 0x1C7_0_nt!SmHpBufferProtectEx

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {677f42d4-ea31-d924-1621-3373689c0a0a}

Followup: MachineOwner
---------[/CODE]
 
Sorun RAM'de görünüyor. Lütfen Memtest86 testi uygulayıp sonucu bizimle paylaşın.

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.


[CODE title="Dökümler"]Microsoft (R) Windows Debugger Version 10.0.21306.1007 AMD64.
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\Enes3078\Downloads\032721-8421-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 19041 MP (4 procs) Free x64.
Product: WinNt, suite: TerminalServer SingleUserTS Personal.
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff802`17400000 PsLoadedModuleList = 0xfffff802`1802a490
Debug session time: Sat Mar 27 23:33:48.311 2021 (UTC + 3:00)
System Uptime: 0 days 0:01:54.073
Loading Kernel Symbols.
...............................................................
................................................................
................................................................
................................
Loading User Symbols.
Loading unloaded module list.
...............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`177f5db0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffc50a`2b27d940=00000000000001c7
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

STORE_DATA_STRUCTURE_CORRUPTION (1c7)
The store component detected a corruption in its data structures.
Arguments:
Arg1: 0000000000000000, A chunk heap buffer's hash doesn't match.
Arg2: ffffd9894131c000, Chunk heap buffer whose hash didn't match.
Arg3: 00000000ba54d43b, Expected buffer hash.
Arg4: 000000000012b11c, Page frame number of the corrupted page.

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

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 8686.

Key : Analysis.DebugAnalysisManager
Value: Create.

Key : Analysis.Elapsed.mSec
Value: 34684.

Key : Analysis.Init.CPU.mSec
Value: 2843.

Key : Analysis.Init.Elapsed.mSec
Value: 33778.

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

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

BUGCHECK_CODE: 1c7.

BUGCHECK_P1: 0

BUGCHECK_P2: ffffd9894131c000.

BUGCHECK_P3: ba54d43b.

BUGCHECK_P4: 12b11c.

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: MemCompression.

STACK_TEXT:
ffffc50a`2b27d938 fffff802`1782827e : 00000000`000001c7 00000000`00000000 ffffd989`4131c000 00000000`ba54d43b : nt!KeBugCheckEx
ffffc50a`2b27d940 fffff802`1763fd15 : 6de3e000`1ccab573 00000000`0012b11c 00000000`00000012 ffffc50a`2b27da69 : nt!SmHpBufferProtectEx+0x1e855a
ffffc50a`2b27d9a0 fffff802`1763f348 : 00000000`ffffffff ffff923b`f3ae9959 ffffd989`4131b888 00000000`200017e6 : nt!SmHpChunkUnprotect+0x2d
ffffc50a`2b27d9d0 fffff802`176c518c : 00000000`00000000 00000000`00000000 ffffc50a`2b27da69 00000000`00000000 : nt!ST_STORE<SM_TRAITS>::StDmPageRecordUnprotect+0x1c
ffffc50a`2b27da00 fffff802`1763eda2 : 00000000`00000000 ffffd989`3fab4f50 00000000`00000000 fffff802`1763ec93 : nt!ST_STORE<SM_TRAITS>::StDmPageRemove+0x130
ffffc50a`2b27dad0 fffff802`1763e2ce : ffffd989`3ebbd000 ffffc50a`2b27db98 00000000`00000001 ffffd989`3ecb9080 : nt!ST_STORE<SM_TRAITS>::StWorkItemProcess+0xc2
ffffc50a`2b27db20 fffff802`177223f1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SMKM_STORE<SM_TRAITS>::SmStWorker+0x12a
ffffc50a`2b27dbe0 fffff802`17717e85 : ffffd989`3ebbd000 fffff802`177223e0 ffffc50a`2b21b3a8 00000000`00000000 : nt!SMKM_STORE<SM_TRAITS>::SmStWorkerThread+0x11
ffffc50a`2b27dc10 fffff802`177fd408 : ffff9c80`967c6180 ffffd989`3ecb9080 fffff802`17717e30 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffc50a`2b27dc60 00000000`00000000 : ffffc50a`2b27e000 ffffc50a`2b278000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28

SYMBOL_NAME: nt!SmHpBufferProtectEx+1e855a

MODULE_NAME: nt.

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.906

STACK_COMMAND: .thread ; .cxr ; kb.

BUCKET_ID_FUNC_OFFSET: 1e855a.

FAILURE_BUCKET_ID: 0x1C7_0_nt!SmHpBufferProtectEx

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release.

OSPLATFORM_TYPE: x64.

OSNAME: Windows 10.

FAILURE_ID_HASH: {677f42d4-ea31-d924-1621-3373689c0a0a}

Followup: MachineOwner.
---------[/CODE]


Hemen deniyorum hocam. Uzun zamandır RAM ile alakalı bir sıkıntım yoktu ama? 🤔
 
PC de SSD var. Memtest sonucunda hiç hata çıkmadı. Formattan başka çözüm var mıdır? Oyunları da geri yüklemeye uğraşmak istemiyorum. Yardım ettiğiniz için teşekkürler.
1616884275795.png


BlueStacks bu hatayı veriyor. Zula da oyun hiç açılmıyor. Öbür programlarda skıntı yok gibi.
Az önceki Process Monitor dosyaları gitmiş. Tekrardan yüklüyorum.
Bu 2 oyunda alınan hatalar.
 
Son düzenleme:
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ı