Mavi ekran hatası

MFO10

Kilopat
Katılım
21 Temmuz 2016
Mesajlar
450
Çözümler
1
Daha fazla  
Cinsiyet
Erkek
İyi akşamlar arkadaşlar. Format attıktan sonra uzun bir süre hiç mavi ekran hatası almamıştım. Ancak bugün aldım. Fotoğrafını çekebildim onu da bırakıyorum. Ne yapabilirim bu konu ile alakalı?

20200927_200128.jpg
 
Evet maç izlerken telefonun internetini bağlıyorum.



Bunu yapmıştım ve 1 tane hata bulmuştum sadece. Recep hocam RAM'leri değiştirin isterseniz demişti ancak değiştirmeme kararı almıştım.

Ağ kartı sürücüsü ile alakalı olma ihtimali var mı?
Ram'den kaynaklı gibi. RAM'lerini değiştirin. Eğer öyle bir bütçeniz yoksa mavi ekran devam edebilir.
 
İşlemciye hız aşırtma yaptıysanız kaldırın. İki farklı RAM kullanıyorsunuz ya Samsung ya da Micron marka Rami kullanın uyumsuz olabilirler.
Kod:
KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure.  The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: ffff9a08ae3bed30, Address of the trap frame for the exception that caused the bugcheck
Arg3: ffff9a08ae3bec88, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved

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


TRAP_FRAME:  ffff9a08ae3bed30 -- (.trap 0xffff9a08ae3bed30)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffdb83cdcaf358 rbx=0000000000000000 rcx=0000000000000003
rdx=ffffdb83cdcaf258 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80209447237 rsp=ffff9a08ae3beec0 rbp=ffffdb83cdcaf350
 r8=0000000000000000  r9=0000000000000fff r10=ffffb580280c0000
r11=ffff9a08ae3bede0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz ac pe cy
nt!RtlInsertElementGenericTableFull+0x137d07:
fffff802`09447237 cd29            int     29h
Resetting default scope

EXCEPTION_RECORD:  ffff9a08ae3bec88 -- (.exr 0xffff9a08ae3bec88)
ExceptionAddress: fffff80209447237 (nt!RtlInsertElementGenericTableFull+0x0000000000137d07)
   ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
  ExceptionFlags: 00000001
NumberParameters: 1
   Parameter[0]: 0000000000000003

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x139

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000409 - Sistem, bu uygulamada y

EXCEPTION_CODE: (NTSTATUS) 0xc0000409 - Sistem, bu uygulamada y

EXCEPTION_PARAMETER1:  0000000000000003

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre

EXCEPTION_STR:  0x0

LAST_CONTROL_TRANSFER:  from fffff802093d41e9 to fffff802093c23c0

STACK_TEXT: 
ffff9a08`ae3bea08 fffff802`093d41e9 : 00000000`00000139 00000000`00000003 ffff9a08`ae3bed30 ffff9a08`ae3bec88 : nt!KeBugCheckEx
ffff9a08`ae3bea10 fffff802`093d4610 : 00000000`00001010 ffffcb03`10a02000 fffff802`09200000 fffff802`0929b8c6 : nt!KiBugCheckDispatch+0x69
ffff9a08`ae3beb50 fffff802`093d29a3 : 00000000`00000000 ffff9a08`ae3bf538 ffffb580`280c0000 ffff9a08`00000000 : nt!KiFastFailDispatch+0xd0
ffff9a08`ae3bed30 fffff802`09447237 : ffffcb03`209d60c0 ffffcb03`11d89800 ffffcb03`209d64a0 fffff802`092cebf8 : nt!KiRaiseSecurityCheckFailure+0x323
ffff9a08`ae3beec0 fffff802`0930f508 : ffff9a08`ae3bef90 ffff9a08`ae3bef60 00000000`00000010 00000000`00000000 : nt!RtlInsertElementGenericTableFull+0x137d07
ffff9a08`ae3beef0 fffff802`1e7181f9 : ffffdb83`d3fefb70 ffffdb83`cdcaf350 ffffdb83`cdcaf290 ffffdb83`cdcaf290 : nt!RtlInsertElementGenericTable+0x48
ffff9a08`ae3bef40 fffff802`1e7063c6 : 00000000`00000000 ffffdb83`dd32d708 00000000`00000000 ffffdb83`d3fefb98 : dxgkrnl!CTokenManager::EnsureTokenQueueForPresent+0x69
ffff9a08`ae3bef90 fffff802`1e705efe : ffff9a08`ae3bf120 ffffcb03`16be1078 ffff9a08`ae3bf928 00000000`00000001 : dxgkrnl!NotifyPendingFlipPresent+0x416
ffff9a08`ae3bf070 fffff802`1e7ea109 : 00000000`00000000 ffff9a08`ae3bf120 ffff9a08`ae3bf828 ffff9a08`ae3bf828 : dxgkrnl!DxgkQuerySwapChainBindingStatus+0x1a
ffff9a08`ae3bf0a0 fffff802`1e7f90d0 : 00000000`00000000 fffff802`0915dc45 ffffcb03`16be1000 00000000`00000000 : dxgkrnl!SubmitPresentHistoryTokenPreparation+0x309
ffff9a08`ae3bf160 fffff802`1e7fda03 : ffffdb83`dd32d5a0 ffffdb83`dd32d5a0 ffffdb83`d7c82de0 ffffcb03`16be1000 : dxgkrnl!DXGCONTEXT::Present+0x9e0
ffff9a08`ae3bf740 fffff802`093d3c15 : ffffcb03`209d60c0 ffffcb03`209d60c0 00000000`00009000 0000023a`3d9a43f4 : dxgkrnl!DxgkPresent+0x813
ffff9a08`ae3bfa00 00007ffc`75845384 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
000000ed`717fa9c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`75845384


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !hal
    fffff8020915dc5a-fffff8020915dc5f  6 bytes - hal!HalSendSoftwareInterrupt+10a
    [ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
6 errors : !hal (fffff8020915dc5a-fffff8020915dc5f)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE

BUCKET_ID:  MEMORY_CORRUPTION_LARGE

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:memory_corruption_large

FAILURE_ID_HASH:  {e29154ac-69a4-0eb8-172a-a860f73c0a3c}

Followup: memory_corruption
---------
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80138711257, Address of the instruction which caused the bugcheck
Arg3: ffffcc8127d3c930, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - 0x%08lx adresindeki y nerge, 0x%08lx bellek adresine ba

FAULTING_IP:
nt!KeWakeWaitChain+8b
fffff801`38711257 488b00          mov     rax,qword ptr [rax]

CONTEXT:  ffffcc8127d3c930 -- (.cxr 0xffffcc8127d3c930;r)
rax=0020000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0020000000000000 rsi=0000000000000000 rdi=ffffbc0d8fe94700
rip=fffff80138711257 rsp=ffff8c0c16a4ee70 rbp=0020000000000000
 r8=0000000000000000  r9=0000000000000001 r10=fffff80138c2b000
r11=ffff8c0c16a4ef58 r12=0000000000000002 r13=ffffcc8127dc7180
r14=0000000000000001 r15=0000000000000001
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050246
nt!KeWakeWaitChain+0x8b:
fffff801`38711257 488b00          mov     rax,qword ptr [rax] ds:002b:00200000`00000000=????????????????
Last set context:
rax=0020000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0020000000000000 rsi=0000000000000000 rdi=ffffbc0d8fe94700
rip=fffff80138711257 rsp=ffff8c0c16a4ee70 rbp=0020000000000000
 r8=0000000000000000  r9=0000000000000001 r10=fffff80138c2b000
r11=ffff8c0c16a4ef58 r12=0000000000000002 r13=ffffcc8127dc7180
r14=0000000000000001 r15=0000000000000001
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050246
nt!KeWakeWaitChain+0x8b:
fffff801`38711257 488b00          mov     rax,qword ptr [rax] ds:002b:00200000`00000000=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x3B

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre

LAST_CONTROL_TRANSFER:  from fffff8013870dac3 to fffff80138711257

STACK_TEXT: 
ffff8c0c`16a4ee70 fffff801`3870dac3 : ffff8c0c`16a4ef60 ffffbc0d`8fe947a8 00000000`00000000 00000000`00000000 : nt!KeWakeWaitChain+0x8b
ffff8c0c`16a4ef10 fffff801`3870d9dc : 00200000`00000000 ffffbc0d`91444770 ffff8c0c`16a4f049 ffff8c0c`16a4f4f0 : nt!ExpConvertExclusiveToSharedLite+0x8b
ffff8c0c`16a4ef60 fffff801`38c2e917 : ffffbc0d`8fe94770 ffffbc0d`91444770 ffffbc0d`92b02b40 ffffbc0d`92b02b40 : nt!ExConvertExclusiveToSharedLite+0x2c
ffff8c0c`16a4efa0 fffff801`38c2b64f : ffffbc0d`8a9f7080 00000000`00000004 ffffbc0d`840c9a60 ffffbc0d`91444770 : nt!PspAllocateAndQueryNotificationChannel+0x8b
ffff8c0c`16a4f0b0 fffff801`387d3c15 : ffffbc0d`00000000 ffffcc81`00000001 00000291`29651d50 ffff8c0c`16a4fa80 : nt!NtQueryInformationJobObject+0x56f
ffff8c0c`16a4f990 00007ffb`6455e8e4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
000000dc`224ff6f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`6455e8e4


CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff801386be9b4-fffff801386be9b5  2 bytes - nt!KiUnstackDetachProcess+1d4
    [ 48 ff:4c 8b ]
    fffff801386be9bb-fffff801386be9be  4 bytes - nt!KiUnstackDetachProcess+1db (+0x07)
    [ 0f 1f 44 00:e8 60 b7 9f ]
    fffff8013871185f-fffff80138711863  5 bytes - nt!MiDetachProcessFromSession+2f (+0x52ea4)
    [ d0 be 7d fb f6:50 b1 62 c5 8a ]
    fffff80138711ea4 - nt!MiPrivateFixup+f0 (+0x645)
    [ f6:8a ]
    fffff80138711ec1 - nt!MiPrivateFixup+10d (+0x1d)
    [ fa:f2 ]
    fffff80138711f62 - nt!MiPrivateFixup+1ae (+0xa1)
    [ fa:f2 ]
14 errors : !nt (fffff801386be9b4-fffff80138711f62)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE

STACK_COMMAND:  .cxr 0xffffcc8127d3c930 ; kb

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE

BUCKET_ID:  MEMORY_CORRUPTION_LARGE

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:memory_corruption_large

FAILURE_ID_HASH:  {e29154ac-69a4-0eb8-172a-a860f73c0a3c}

Followup: memory_corruption
---------
 
@Assecreed hocam işlemciye ellemedim. Bilgisayarı aldığımdan beri de RAM değişikliği vs hiç yapmadım. 2 defa tamirciye verdim bilgisayarı. Farklı marka RAM kullanıldığından emin misiniz acaba? Eğer öyleyse verdiğim tamirciler değiştirmiştir.
 
@Assecreed hocam işlemciye ellemedim. Bilgisayarı aldığımdan beri de RAM değişikliği vs hiç yapmadım. 2 defa tamirciye verdim bilgisayarı. Farklı marka RAM kullanıldığından emin misiniz acaba? Eğer öyleyse verdiğim tamirciler değiştirmiştir.
Evet dump dosyalarında iki farklı RAM gözüküyor. Bakkal amca bir şeyler yapmış bilgisayara.
 
8. teste 1 tane hata bulmuş 10GB bölgesinde. Ramler sorunlu anlamına gelmiyor bu tabi. İki farklı RAM kullanınca uyumsuzluklar böyle hatalar çıkabiliyor.
 
Bilgisayarın sadece kapağını açarak çok kurcalamadan anlayabilir miyim RAM farklılığını?

İyi kötü şu an çalışıyor sonuçta. Komple eldekinden olmak istemem.
 

Geri
Yukarı