Windows 10 mavi ekran hatası

BIOS'tan XMP ayarı açıksa kapatınız ve MemTest86 ile belleklerde test yapınız. Sorun büyük ihtimalle belleklerde.

Ayrıca USB'den ses alıyorsanız şimdilik ilgili cihazı kullanmayınız.

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: 000000000000001d, Type of memory safety violation
Arg2: ffffb68f1214cf90, Address of the trap frame for the exception that caused the bugcheck
Arg3: ffffb68f1214cee8, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 6171

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

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

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

BUGCHECK_P1: 1d

BUGCHECK_P2: ffffb68f1214cf90

BUGCHECK_P3: ffffb68f1214cee8

BUGCHECK_P4: 0

TRAP_FRAME:  ffffb68f1214cf90 -- (.trap 0xffffb68f1214cf90)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffebdc06253f98 rbx=0000000000000000 rcx=000000000000001d
rdx=ffffebdc06254f98 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8005a2666c7 rsp=ffffb68f1214d128 rbp=000000000000016c
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=ffffebdc062d5f98 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po cy
nt!RtlRbRemoveNode+0x198c17:
fffff800`5a2666c7 cd29 int 29h
Resetting default scope

EXCEPTION_RECORD:  ffffb68f1214cee8 -- (.exr 0xffffb68f1214cee8)
ExceptionAddress: fffff8005a2666c7 (nt!RtlRbRemoveNode+0x0000000000198c17)
   ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
ExceptionFlags: 00000001
NumberParameters: 1
Parameter[0]: 000000000000001d
Subcode: 0x1d FAST_FAIL_INVALID_BALANCED_TREE

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: EBA Canli Ders.exe

ERROR_CODE: (NTSTATUS) 0xc0000409 - Sistem, bu uygulamada y n tabanl bir arabelle in ta t n alg lad . Bu ta ma, k t niyetli bir kullan c n n bu uygulaman n denetimini ele ge irmesine olanak verebilir.

EXCEPTION_CODE_STR: c0000409

EXCEPTION_PARAMETER1: 000000000000001d

EXCEPTION_STR: 0xc0000409

STACK_TEXT:
ffffb68f`1214cc68 fffff800`5a205e69 : 00000000`00000139 00000000`0000001d ffffb68f`1214cf90 ffffb68f`1214cee8 : nt!KeBugCheckEx
ffffb68f`1214cc70 fffff800`5a206290 : ffff8006`7e2ec700 fffffc7e`3f000000 fffffc7e`3f1f8000 fffffc7e`3f1f8fc0 : nt!KiBugCheckDispatch+0x69
ffffb68f`1214cdb0 fffff800`5a204623 : 00000000`00000000 ffff8006`7e2ec080 fffffc00`00006d50 ffff8006`7e2ec700 : nt!KiFastFailDispatch+0xd0
ffffb68f`1214cf90 fffff800`5a2666c7 : 0000002a`00050000 00010005`016c0002 fffff800`5a0cd870 00000000`0000016c : nt!KiRaiseSecurityCheckFailure+0x323
ffffb68f`1214d128 fffff800`5a0cd870 : 00000000`0000016c ffffebdc`06254fe0 00000000`00000000 ffffebdc`06254f90 : nt!RtlRbRemoveNode+0x198c17
ffffb68f`1214d140 fffff800`5a0cd2b8 : ffffebdc`00200280 ffffebdc`06248000 00000000`00000000 ffffb68f`1214d248 : nt!RtlpHpVsChunkCoalesce+0xb0
ffffb68f`1214d1a0 fffff800`5a0cbc44 : 00000000`00000000 ffffebdc`00000000 00000000`00000001 fffff800`00000000 : nt!RtlpHpVsContextFree+0x188
ffffb68f`1214d240 fffff800`5a7b2019 : ffffebdc`000016b0 ffffb68f`1214d3f0 ffffebbc`59d537b0 01000000`00100000 : nt!ExFreeHeapPool+0x4d4
ffffb68f`1214d320 ffffebbc`59d53802 : 00000000`00000001 00000000`00000000 fffff800`00000000 ffffebbc`00000000 : nt!ExFreePool+0x9
ffffb68f`1214d350 ffffebbc`59045697 : 00000000`00000000 ffffebdc`06255000 ffffebdc`06255000 ffffebdc`06255000 : win32kfull!Win32FreePoolImpl+0x52
ffffb68f`1214d380 ffffebbc`59044b20 : ffffb68f`1214d5a8 00000000`00000b99 ffffebdc`00602a20 ffffb68f`1214d5a8 : win32kbase!Win32FreePool+0x37
ffffb68f`1214d3b0 ffffebbc`59c81e43 : ffffebdc`042e72c0 00000000`00000000 ffffebdc`05fa7990 00000000`00001204 : win32kbase!SURFMEM::~SURFMEM+0xa60
ffffb68f`1214d4e0 ffffebbc`59d032ba : ffffebdc`060fc1b0 00000000`00000000 ffffb68f`1214dbe0 00000000`00000001 : win32kfull!EngAlphaBlend+0x3f3
ffffb68f`1214d830 ffffebbc`593796b2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32kfull!NtGdiAlphaBlend+0xffa
ffffb68f`1214dd50 fffff800`5a2058b8 : ffff8a5b`d03da816 00000000`00000000 00000000`00050fac 00000000`00000018 : win32k!NtGdiAlphaBlend+0x82
ffffb68f`1214ddd0 00007ff9`8c930e94 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000000`003a9008 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`8c930e94


SYMBOL_NAME: nt!ExFreePool+9

IMAGE_NAME: Pool_Corruption

IMAGE_VERSION: 10.0.19041.508

MODULE_NAME: Pool_Corruption

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 9

FAILURE_BUCKET_ID: 0x139_1d_INVALID_BALANCED_TREE_nt!ExFreePool

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {ab43366d-59cb-5971-8e17-b53398bf3f90}

Followup: Pool_corruption
---------

REFERENCE_BY_POINTER (18)
Arguments:
Arg1: 0000000000000000, Object type of the object whose reference count is being lowered
Arg2: fffff40f12bbfa00, Object whose reference count is being lowered
Arg3: 0000000000000002, Reserved
Arg4: fffff40f12bbfb7f, Reserved
The reference count of an object is illegal for the current state of the object.
Each time a driver uses a pointer to an object the driver calls a kernel routine
to increment the reference count of the object. When the driver is done with the
pointer the driver calls another kernel routine to decrement the reference count.
Drivers must match calls to the increment and decrement routines. This bugcheck
can occur because an object's reference count goes to zero while there are still
open handles to the object, in which case the fourth parameter indicates the number
of opened handles. It may also occur when the object's reference count drops below zero
whether or not there are open handles to the object, and in that case the fourth parameter
contains the actual value of the pointer references count.

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

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 5281

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

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

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

BUGCHECK_P1: 0

BUGCHECK_P2: fffff40f12bbfa00

BUGCHECK_P3: 2

BUGCHECK_P4: fffff40f12bbfb7f

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: EpicGamesLauncher.exe

STACK_TEXT:
fffff40f`12bbfa18 fffff806`3326ba35 : 00000000`00000018 00000000`00000000 fffff40f`12bbfa00 00000000`00000002 : nt!KeBugCheckEx
fffff40f`12bbfa20 fffff806`334d6281 : 00000000`00000102 00000000`00000000 00000000`00000001 00000000`00000000 : nt!ObfDereferenceObjectWithTag+0x18bb35
fffff40f`12bbfa60 fffff806`334d630a : ffffb98a`26ee1080 000000fb`4ddef6e8 00000000`00000000 fffff806`33205718 : nt!ObWaitForSingleObject+0xb1
fffff40f`12bbfac0 fffff806`332058b8 : 00000225`0e1d8e00 00000000`00000000 fffff40f`12bbfb18 ffffffff`fffe7960 : nt!NtWaitForSingleObject+0x6a
fffff40f`12bbfb00 00007fff`13e0be44 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
000000fb`4ddef6b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`13e0be44


SYMBOL_NAME: nt!ObfDereferenceObjectWithTag+18bb35

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.508

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 18bb35

FAILURE_BUCKET_ID: 0x18_CORRUPT_REF_COUNT_nt!ObfDereferenceObjectWithTag

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {fa6b3516-71cb-1e92-b987-b8bebd3458ac}

Followup: MachineOwner
---------
 
Abi biz İtopya'ya göndermiştik sistemi mavi ekran hatası veriyor diye tekrar ggönderdiler bugün elime ulaştı yine veriyor hata RAM'lerin MHz'ini 3200'e çektim XMP'den.

Abi demene gerek yok belki ben senden daha küçük olabilirim hocam demeniz yeterli olacaktır.

RAM'lerin frekansını biraz düşürüp deneyin.
 
BIOS'tan XMP ayarı açıksa kapatınız ve Memtest86 ile belleklerde test yapınız.

Ayrıca USB'den ses alıyorsanız şimdilik ilgili cihazı kullanmayınız.

X.M.P'yi kapatıp mı test edeyim? Kulaklıktan ses alıyorum şu anda.

Abi demene gerek yok belki ben senden daha küçük olabilirim hocam demeniz yeterli olacaktır.

RAM'lerin frekansını biraz düşürüp deneyin.

Profile 1'i normal hale mi getireyim?
 
Son düzenleyen: Moderatör:
Evet, tamamen kapatın. BIOS'u sıfırlarsanız iyi olur hatta.

Şimdilik kulaklığı çıkarın ve bir süre kullanmayın.

Tamam.
Evet, tamamen kapatın. Hatta BIOS'u sıfırlarsanız daha iyi olur.

Şimdilik kulaklığı çıkarın ve bir süre kullanmayın.
hocam testi yaptım hiç hata yok neden kaynaklı acaba mavi ekran
Evet, tamamen kapatın. Hatta BIOS'u sıfırlarsanız daha iyi olur.
X.M.P yi kapatıp yaptım testleri bıos zaten sıfırlanmıştı sorun çıkmadı tekrar xmp yi açtım
 
Son düzenleme:
Yeni konu açmayın artık, eskisinden devam edin. Her hatada yeni konu açmanıza gerek yok.
 

Geri
Yukarı