Çözüldü Windows 11 mavi ekran hatasının sebebi nedir?

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

DarkNestPlus

Picopat
Katılım
8 Mayıs 2023
Mesajlar
731
Çözümler
6
Yer
Türkiye
Daha fazla  
Sistem Özellikleri
Acer Nitro 5 AN515-43 5 Ryzen5 3350 RX 560x 16 gb
Cinsiyet
Erkek
Meslek
Türk Genci
Arkadaşlar bugün az önce mavi ekran yedim. açıklamasında şu yazıyordu:
"Your device ran into a problem and needs to restart."
Neden olduğunu nereden anlayabilirim?
 
Çözüm
Sorun Vanguard kaynaklı.

Rich (BB code):
.trap 0xffff800d835dbea0
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000f49 rbx=0000000000000000 rcx=ffffc100dd9d05d6
rdx=ffffbf0ca5c0bd3a rsi=0000000000000000 rdi=0000000000000000
rip=fffff80544c86c49 rsp=ffff800d835dc038 rbp=ffff9907755db0b0
 r8=0000000000000020 r9=ffffc100dd9d05d6 r10=00000000000005d6
r11=ffffc100dd9d0000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz ac pe cy
vgk+0x46c49:
fffff805`44c86c49 413801 cmp byte ptr [r9],al ds:ffffc100`dd9d05d6=??

Rich (BB code):
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: ffffc100dd9d05d6, 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: fffff80544c86c49, If non-zero, the instruction address which referenced the bad memory
 address.
Arg4: 0000000000000000, (reserved)

Rich (BB code):
ffff800d`835dbc78 fffff805`3168ca98 : 00000000`00000050 ffffc100`dd9d05d6 00000000`00000000 ffff800d`835dbea0 : nt!KeBugCheckEx
ffff800d`835dbc80 fffff805`3146211c : ffff001f`a7c9318b 00000000`00000000 00000000`00000000 ffffc100`dd9d05d6 : nt!MiSystemFault+0x1fd688
ffff800d`835dbd80 fffff805`31627929 : ffff800d`835dbf30 fffff805`3161f5e0 ffff9907`755db150 00000000`00000000 : nt!MmAccessFault+0x29c
ffff800d`835dbea0 fffff805`44c86c49 : fffff805`44d30bc5 ffff9907`625f52f0 00000001`401fee6b 00000001`23e39000 : nt!KiPageFault+0x369
ffff800d`835dc038 fffff805`44d30bc5 : ffff9907`625f52f0 00000001`401fee6b 00000001`23e39000 00000000`00000000 : vgk+0x46c49
ffff800d`835dc040 ffff9907`625f52f0 : 00000001`401fee6b 00000001`23e39000 00000000`00000000 fffdc235`00114b58 : vgk+0xf0bc5
ffff800d`835dc048 00000001`401fee6b : 00000001`23e39000 00000000`00000000 fffdc235`00114b58 00000000`00000001 : 0xffff9907`625f52f0
ffff800d`835dc050 00000001`23e39000 : 00000000`00000000 fffdc235`00114b58 00000000`00000001 00000000`00000001 : 0x00000001`401fee6b
ffff800d`835dc058 00000000`00000000 : fffdc235`00114b58 00000000`00000001 00000000`00000001 ffff9907`7f7c3fc8 : 0x00000001`23e39000

Vanguard bellek erişim hatasına sebep olmuş. Vanguard'ı kaldırmak bir çözümdür. Fakat tek seferlikse göz ardı edilebilir.
Değişik bir problem olmuş türkçesi "cihazınız bir sorunla karşılaştı ve yeniden başlatılması gerekiyor." diyor istersen 10'a geç.
 
Minidump dosyalarını paylaş, format falan atma.

 
Alın hocam.

Alın hocam.
DropBoxdan yaptım ama sıkıntı olurmu
Minidump dosyalarını paylaş, format falan atma.

 
Sorun Vanguard kaynaklı.

Rich (BB code):
.trap 0xffff800d835dbea0
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000f49 rbx=0000000000000000 rcx=ffffc100dd9d05d6
rdx=ffffbf0ca5c0bd3a rsi=0000000000000000 rdi=0000000000000000
rip=fffff80544c86c49 rsp=ffff800d835dc038 rbp=ffff9907755db0b0
 r8=0000000000000020 r9=ffffc100dd9d05d6 r10=00000000000005d6
r11=ffffc100dd9d0000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz ac pe cy
vgk+0x46c49:
fffff805`44c86c49 413801 cmp byte ptr [r9],al ds:ffffc100`dd9d05d6=??

Rich (BB code):
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: ffffc100dd9d05d6, 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: fffff80544c86c49, If non-zero, the instruction address which referenced the bad memory
 address.
Arg4: 0000000000000000, (reserved)

Rich (BB code):
ffff800d`835dbc78 fffff805`3168ca98 : 00000000`00000050 ffffc100`dd9d05d6 00000000`00000000 ffff800d`835dbea0 : nt!KeBugCheckEx
ffff800d`835dbc80 fffff805`3146211c : ffff001f`a7c9318b 00000000`00000000 00000000`00000000 ffffc100`dd9d05d6 : nt!MiSystemFault+0x1fd688
ffff800d`835dbd80 fffff805`31627929 : ffff800d`835dbf30 fffff805`3161f5e0 ffff9907`755db150 00000000`00000000 : nt!MmAccessFault+0x29c
ffff800d`835dbea0 fffff805`44c86c49 : fffff805`44d30bc5 ffff9907`625f52f0 00000001`401fee6b 00000001`23e39000 : nt!KiPageFault+0x369
ffff800d`835dc038 fffff805`44d30bc5 : ffff9907`625f52f0 00000001`401fee6b 00000001`23e39000 00000000`00000000 : vgk+0x46c49
ffff800d`835dc040 ffff9907`625f52f0 : 00000001`401fee6b 00000001`23e39000 00000000`00000000 fffdc235`00114b58 : vgk+0xf0bc5
ffff800d`835dc048 00000001`401fee6b : 00000001`23e39000 00000000`00000000 fffdc235`00114b58 00000000`00000001 : 0xffff9907`625f52f0
ffff800d`835dc050 00000001`23e39000 : 00000000`00000000 fffdc235`00114b58 00000000`00000001 00000000`00000001 : 0x00000001`401fee6b
ffff800d`835dc058 00000000`00000000 : fffdc235`00114b58 00000000`00000001 00000000`00000001 ffff9907`7f7c3fc8 : 0x00000001`23e39000

Vanguard bellek erişim hatasına sebep olmuş. Vanguard'ı kaldırmak bir çözümdür. Fakat tek seferlikse göz ardı edilebilir.
 
Çözüm
Sorun Vanguard kaynaklı.

Rich (BB code):
.trap 0xffff800d835dbea0.
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000f49 rbx=0000000000000000 rcx=ffffc100dd9d05d6
rdx=ffffbf0ca5c0bd3a rsi=0000000000000000 rdi=0000000000000000
rip=fffff80544c86c49 rsp=ffff800d835dc038 rbp=ffff9907755db0b0
 r8=0000000000000020 r9=ffffc100dd9d05d6 r10=00000000000005d6
r11=ffffc100dd9d0000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz ac pe cy.
vgk+0x46c49:
fffff805`44c86c49 413801 cmp byte ptr [r9],al ds:ffffc100`dd9d05d6=??

Rich (BB code):
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: ffffc100dd9d05d6, 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: fffff80544c86c49, If non-zero, the instruction address which referenced the bad memory.
 address.
Arg4: 0000000000000000, (reserved)

Rich (BB code):
ffff800d`835dbc78 fffff805`3168ca98 : 00000000`00000050 ffffc100`dd9d05d6 00000000`00000000 ffff800d`835dbea0 : nt!KeBugCheckEx
ffff800d`835dbc80 fffff805`3146211c : ffff001f`a7c9318b 00000000`00000000 00000000`00000000 ffffc100`dd9d05d6 : nt!MiSystemFault+0x1fd688
ffff800d`835dbd80 fffff805`31627929 : ffff800d`835dbf30 fffff805`3161f5e0 ffff9907`755db150 00000000`00000000 : nt!MmAccessFault+0x29c
ffff800d`835dbea0 fffff805`44c86c49 : fffff805`44d30bc5 ffff9907`625f52f0 00000001`401fee6b 00000001`23e39000 : nt!KiPageFault+0x369
ffff800d`835dc038 fffff805`44d30bc5 : ffff9907`625f52f0 00000001`401fee6b 00000001`23e39000 00000000`00000000 : vgk+0x46c49
ffff800d`835dc040 ffff9907`625f52f0 : 00000001`401fee6b 00000001`23e39000 00000000`00000000 fffdc235`00114b58 : vgk+0xf0bc5
ffff800d`835dc048 00000001`401fee6b : 00000001`23e39000 00000000`00000000 fffdc235`00114b58 00000000`00000001 : 0xffff9907`625f52f0
ffff800d`835dc050 00000001`23e39000 : 00000000`00000000 fffdc235`00114b58 00000000`00000001 00000000`00000001 : 0x00000001`401fee6b
ffff800d`835dc058 00000000`00000000 : fffdc235`00114b58 00000000`00000001 00000000`00000001 ffff9907`7f7c3fc8 : 0x00000001`23e39000

Vanguard bellek erişim hatasına sebep olmuş. Vanguard'ı kaldırmak bir çözümdür. Fakat tek seferlikse göz ardı edilebilir.

Riot Vanguard lama alakalı yani?
 

Yeni konular

Geri
Yukarı