Ekranda bozulmalar ve mavi ekran hataları

İşletim sistemi
Windows 10

Beccaria38

Kilopat
Katılım
24 Şubat 2018
Mesajlar
291
Makaleler
1
Çözümler
4
Daha fazla  
Cinsiyet
Erkek
RAM
XPG 8GB (2x8GB) Gammix D30 Kırmızı DDR4 3200MHz CL16 1.35V
SSD veya HDD modeli
Samsung SATA SSD 250gb 860 EVO, PNY CS3030 500GB
Ekran kartı
GIGABYTE GeForce RTX 4060 TI GAMING OC 8G
Anakart
MSI PRO H610M-E DDR4 Intel H610 Soket 1700 3200MHz
İşlemci
Intel Core i5 13400F Soket 1700 13.Nesil
Merhaba arkadaşlar, minidump dosyalarımı sizle paylaştım. Yaşadığım sorunlar şunlar:
1-Ekranda göz kırpma, ekranın herhangi bir köşesinde anlık bölgesel kararma (belli bir yerde ve sürekli olmuyor sürekli farklı yerlerde ve belirsiz zamanlarda), ekranı ikiye böldüğümde sağdaki görüntüyü sola aktarma, bazen dikey çizgiler oluyor ve son olarak mavi ekran hataları.

2-Aldığım mavi ekran hataları:
1-M) Durdurma Kodu: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED Başarısız: nvlddmkm.sys
2-M) Durdurma Kodu: PAGE_FAULT_IN_NONPAGED_AREA Başarısız: nvlddmkm.sys
3-M) Durdurma Kodu: ATTEMPTED_SWITCH_FROM_DPC

Minidump dosyaları link: MiniDump Dosyaları.rar
Minidump dosyalarının yalnızca ikisini alabildim. Totalde 6 kere mavi ekran yedim ama format attığım için kaydedemedim.

Not: SS klavye kullanıyorum fakat yazılım yüklü değil.

-Tarayıcı olarak Chrome (Sürüm 120.0.6099.110) ve Microsoft Edge kullanıyorum. (Sürüm 120.0.2210.77)
-Ekran kartı sürücüsünün sürümü 546.33 Sürüm tarihi: 12/12/2023
-Chipset sürümü: 10.1.19199.8340
-W10 sürüm: 22H2 19045.3803
-BIOS sürüm: 7D48vAC

Not: Güncel sürüm (7D48vAD) BIOS kullandığımda Realtek ses sürücüsünü kuramıyorum ve güncel sürüm BIOS varken format atmaya çalıştığımda Windows Güncelleştirmeleri yaparken belli bir nokta sonra sürekli mavi ekran yedim. Bu yüzden bir önceki sürüm yüklü.

Mavi ekran hatası 1.JPGMavi ekran hatası 2.JPGMavi ekran hatası 3.JPG

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: ffffffffffffff08, memory referenced.
Arg2: 0000000000000000, X64: bit 0 set if the fault was due to a not-present PTE.
bit 1 is set if the fault was due to a write, clear if a read.
bit 3 is set if the processor decided the fault was due to a corrupted PTE.
bit 4 is set if the fault was due to attempted execute of a no-execute PTE.
- ARM64: bit 1 is set if the fault was due to a write, clear if a read.
bit 3 is set if the fault was due to attempted execute of a no-execute PTE.
Arg3: fffff80541c7a638, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)

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


KEY_VALUES_STRING: 1

Key : AV.Type
Value: Read

Key : Analysis.CPU.mSec
Value: 2265

Key : Analysis.Elapsed.mSec
Value: 4898

Key : Analysis.IO.Other.Mb
Value: 17

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 22

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

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

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

Key : Bugcheck.Code.LegacyAPI
Value: 0x50

Key : Failure.Bucket
Value: AV_R_(null)_nvlddmkm!unknown_function

Key : Failure.Hash
Value: {f899ea14-805d-2454-345d-ba405310c43d}

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: 50

BUGCHECK_P1: ffffffffffffff08

BUGCHECK_P2: 0

BUGCHECK_P3: fffff80541c7a638

BUGCHECK_P4: 2

FILE_IN_CAB: 120423-4296-01.dmp

READ_ADDRESS: fffff8051cefb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
ffffffffffffff08

MM_INTERNAL_CODE: 2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

TRAP_FRAME: ffffcd01f0a574f0 -- (.trap 0xffffcd01f0a574f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffffbb89c3599870
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80541c7a638 rsp=ffffcd01f0a57680 rbp=000000000000000f
r8=0000000000000001 r9=fffff780000003d8 r10=ffffcd01f0a55840
r11=ffffcd01f0a575e0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nvlddmkm+0x10ca638:
fffff805`41c7a638 488b4608 mov rax,qword ptr [rsi+8] ds:00000000`00000008=????????????????
Resetting default scope

STACK_TEXT:
ffffcd01`f0a57248 fffff805`1c63b7fd : 00000000`00000050 ffffffff`ffffff08 00000000`00000000 ffffcd01`f0a574f0 : nt!KeBugCheckEx
ffffcd01`f0a57250 fffff805`1c424660 : fffff805`1cf25440 00000000`00000000 ffffcd01`f0a57570 00000000`00000000 : nt!MiSystemFault+0x1d829d
ffffcd01`f0a57350 fffff805`1c60d1d8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x400
ffffcd01`f0a574f0 fffff805`41c7a638 : ffffbb89`c3599870 00000000`00000006 00000000`00000000 fffff805`1cf25440 : nt!KiPageFault+0x358
ffffcd01`f0a57680 ffffbb89`c3599870 : 00000000`00000006 00000000`00000000 fffff805`1cf25440 fffff805`41c7e7d0 : nvlddmkm+0x10ca638
ffffcd01`f0a57688 00000000`00000006 : 00000000`00000000 fffff805`1cf25440 fffff805`41c7e7d0 ffffbb89`c35998c0 : 0xffffbb89`c3599870
ffffcd01`f0a57690 00000000`00000000 : fffff805`1cf25440 fffff805`41c7e7d0 ffffbb89`c35998c0 ffffab01`00000008 : 0x6


SYMBOL_NAME: nvlddmkm+10ca638

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 10ca638

FAILURE_BUCKET_ID: AV_R_(null)_nvlddmkm!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {f899ea14-805d-2454-345d-ba405310c43d}

Followup: MachineOwner

ATTEMPTED_SWITCH_FROM_DPC (b8)
A wait operation, attach process, or yield was attempted from a DPC routine.
This is an illegal operation and the stack track will lead to the offending
code and original DPC routine.
Arguments:
Arg1: ffff8d81acce2440, Original thread which is the cause of the failure
Arg2: ffffc88e2f205080, New thread
Arg3: 0000000000000000, Stack address of the original thread
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2327

Key : Analysis.Elapsed.mSec
Value: 5585

Key : Analysis.IO.Other.Mb
Value: 23

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 28

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

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

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

Key : Bugcheck.Code.LegacyAPI
Value: 0x100000b8

Key : Failure.Bucket
Value: 0xB8_sshid!unknown_function

Key : Failure.Hash
Value: {c5f18334-ba57-3396-ea7f-6e96b216d079}

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: b8

BUGCHECK_P1: ffff8d81acce2440

BUGCHECK_P2: ffffc88e2f205080

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FILE_IN_CAB: 121623-3750-01.dmp

FAULTING_THREAD: ffff8d81acce2440

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
fffff60e`852de030 fffff800`23641330 : 00000000`00000000 00000000`00000000 00000000`000000e0 ffffc88e`272fa890 : nt!KiSwapContext+0x76
fffff60e`852de170 fffff800`2364085f : ffff8d81`acce2440 ffffc88e`29a77680 fffff60e`852de330 00000000`00000000 : nt!KiSwapThread+0x500
fffff60e`852de220 fffff800`23640103 : 00000000`000000f3 ffffc88e`00000000 00000000`00000000 ffff8d81`acce2580 : nt!KiCommitThreadWait+0x14f
fffff60e`852de2c0 fffff800`253a1ef6 : fffff60e`852de3f8 00000000`00000000 fffff60e`852de800 00000000`00000000 : nt!KeWaitForSingleObject+0x233
fffff60e`852de3b0 fffff800`2540b3d3 : 00000000`00000002 fffff60e`852de500 fffff60e`00000000 ffffc88e`00000000 : Wdf01000!FxIoTarget::SubmitSync+0x1e6 [minkernel\wdf\framework\shared\targets\general\fxiotarget.cpp @ 1839]
fffff60e`852de480 fffff800`54422fab : ffffc88e`29a898e0 fffff800`237ff734 ffffc88e`29946260 fffff60e`852de809 : Wdf01000!imp_WdfUsbTargetDeviceSendControlTransferSynchronously+0x263 [minkernel\wdf\framework\shared\targets\usb\fxusbdeviceapi.cpp @ 1056]
fffff60e`852de7b0 ffffc88e`29a898e0 : fffff800`237ff734 ffffc88e`29946260 fffff60e`852de809 fffff60e`852de808 : sshid+0x2fab
fffff60e`852de7b8 fffff800`237ff734 : ffffc88e`29946260 fffff60e`852de809 fffff60e`852de808 fffff60e`852de7f0 : 0xffffc88e`29a898e0
fffff60e`852de7c0 0dffffc8`8e29ae32 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatch+0x44
00000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0dffffc8`8e29ae32


SYMBOL_NAME: sshid+2fab

MODULE_NAME: sshid

IMAGE_NAME: sshid.sys

STACK_COMMAND: .process /r /p 0xfffff80024124a00; .thread 0xffff8d81acce2440 ; kb

BUCKET_ID_FUNC_OFFSET: 2fab

FAILURE_BUCKET_ID: 0xB8_sshid!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {c5f18334-ba57-3396-ea7f-6e96b216d079}

Followup: MachineOwner
---------
 
Son düzenleme:
Ben RAM’leri ve Ekran kartını garantiye yolladım. Benim de şüphelerim ya GPU RAM’lerinde ya da normal RAM’lerde bir sorun olduğu yönünde. RAM’leri hem Memtest86 hem de TestMem5 ile uzunca test ettim fakat hiçbir hata gözükmedi. Bu durum Ekran kartının RAM’lerinde sorun olduğunu düşündürtse de MemTest yazılımları belki hatayı görememiş olabilir diye onları da yolladım.
 

Yeni konular

Geri
Yukarı