R7 4800H 1650 Ti boştayken mavi ekran hatası

İşletim sistemi
Windows 11
S

STRoNq

Hectopat
Katılım
11 Eylül 2020
Mesajlar
8
RAM
16 GB 3200 MHz
SSD veya HDD modeli
Silicon Power SP01KGBP34UD7005 1TB M.2 Nvme Pcıe G
Ekran kartı
GTX 1650 Ti
İşlemci
R7 4800H
Chrome gezinirken ve laptop boşta duruken mavi ekran hatası almaya başladım. Ve bunun üstüne birkaç defa format attım her şeyi temizledim PC'den ama gine sürekli almaya devam ediyorum hatayı. Bunun yanında League of Legends oynarken oyun donup atmaya başladı ama oyunu oynarken hiçbir şekilde mavi ekran hatası almıyorum. Attıktan sonra veya boşta dururken hatayı alıyorum.

Minidump.zip

drive.google.com drive.google.com
 
Tarihe göre sırala Puana göre sırala
Hata hâlâ devam ediyorsa güncel (en azından Mayıs-Haziran tarihli) minidumpları da paylaşır mısınız?

Eski minidumpları hızlıca gözden geçirme sonucu dosya sistemi ile alakalı problemler var gibi görünüyor.

CMD'yi yönetici olarak çalıştırıp sırayla şu komutları kopyalayıp yapıştırır mısınız?
Biri bitsin diğerini yazın, sonuçlarını paylaşın.

SFC /scannow
DISM /Online /Cleanup-Image /RestoreHealth

Üsttekiler tamamlandıktan sonra şunu da yapın:

chkdsk /f /r

Bunu yazınca Y/N uyarısı gelecek. Gelen uyarıya Y yazıp enterlayın. PC'yi yeniden başlatın. Tarama yapacak.

SSD'nin sağlığına CrystalDiskInfo ile bakın, ekran görüntüsü gönderin. SSD'nin üreticisinden programını indirip varsa firmware güncellemelerini kontrol edin.

Sistemde HDD varsa HD Tune indirip Health sekmesini paylaşın.
Error Scan sekmesini açıp "Quick Scan" tikli olmayacak şekilde tarama yapıp sonuçları paylaşın.

Windows sürümüne bakamadım, ancak güncellemeler geldiyse mutlaka Windows Update üzerinden güncelleyin.
 
Son düzenleme:
Artı 0 Eksi

Minidump.zip

drive.google.com drive.google.com
Bu haziran ayı minidump klasörü kusura bakma işteydim şehir dışında yeni gelebildim bildirimi yeni gördüm.

EgeN7 dedi:
Hata hâlâ devam ediyorsa güncel (en azından Mayıs-Haziran tarihli) minidumpları da paylaşır mısınız?

Eski minidumpları hızlıca gözden geçirme sonucu dosya sistemi ile alakalı problemler var gibi görünüyor.

CMD'yi yönetici olarak çalıştırıp sırayla şu komutları kopyalayıp yapıştırır mısınız?
Biri bitsin diğerini yazın, sonuçlarını paylaşın.

SFC /scannow
DISM /Online /Cleanup-Image /RestoreHealth

Üsttekiler tamamlandıktan sonra şunu da yapın:

chkdsk /f /r

Bunu yazınca Y/N uyarısı gelecek. Gelen uyarıya Y yazıp enterlayın. PC'yi yeniden başlatın. Tarama yapacak.

SSD'nin sağlığına CrystalDiskInfo ile bakın, ekran görüntüsü gönderin. SSD'nin üreticisinden programını indirip varsa firmware güncellemelerini kontrol edin.

Sistemde HDD varsa HD Tune indirip Health sekmesini paylaşın.
Error Scan sekmesini açıp "Quick Scan" tikli olmayacak şekilde tarama yapıp sonuçları paylaşın.

Windows sürümüne bakamadım, ancak güncellemeler geldiyse mutlaka Windows Update üzerinden güncelleyin.
Genişletmek için tıkla...
Minidump.zip Bu haziran ayı minidump klasörü işteydim şehir dışında yeni gördüm cevabını kusura bakma.
 
Artı 0 Eksi
* Öncelikle ilk mesajımdaki adımları da eksiksiz uygular mısınız?

* Hatalar yine genel görünüyor, HDD veya Windows'un dosya sistemi ile ilgili gibi.

* Sadece birinde RTKVHD64.sys = Realtek High Definition Audio Function sürücüsünden dolayı kaynaklanmış.
Rich (BB code): 
nt!ExFreePoolWithTag+0x17f
nt!IopProcessBufferedIoCompletion+0x7e
nt!IopCompleteRequest+0x10e
nt!IopfCompleteRequest+0xf61
nt!IofCompleteRequest+0x17
portcls!CPortPinWaveRT::DeviceIoControl+0xc8
portcls!DispatchDeviceIoControl+0x110
ks!KsDispatchIrp+0x5b
portcls!PcDispatchIrp+0x6f
RTKVHD64+0x2be88a
0xc0000001
0xffffaf8f`4d03bcd8
0xffffaf8f`423471a0
ksthunk!CKSThunkPin::DispatchIoctl+0x2f
nt!IofCallDriver+0x55
ksthunk!CKernelFilterDevice::DispatchIrp+0xf5
ksthunk!CKernelFilterDevice::DispatchIrpBridge+0x13
nt!IofCallDriver+0x55
nt!IopSynchronousServiceTail+0x1d0
nt!IopXxxControlFile+0x72c
nt!NtDeviceIoControlFile+0x56
nt!KiSystemServiceCopyEnd+0x28
0x00007ff8`7dd8ed34

Sürücünüz de epey eski kalmış:
Rich (BB code): 
    Loaded symbol image file: RTKVHD64.sys
    Image path: \SystemRoot\system32\drivers\RTKVHD64.sys
    Image name: RTKVHD64.sys
    Browse all global symbols  functions  data
    Timestamp:        Tue Jun 23 13:34:50 2020 (5EF1DACA)

* Güncelleyin:

laptops and netbooks :: legion series :: legion 5 15arh05 :: 82b5 - Lenovo Support US

pcsupport.lenovo.com pcsupport.lenovo.com

* Sistemde Windows'un Hyper-V (sanallaştırma sistemi) açık. Sanal makine, sanal makine yazılımı, emülatör (BlueStacks vs.) kullanmıyorsanız Hyper-V'yi kapatabilirsiniz.

* Özellikle Hyper-V bazı oyunlar ve anti-hileler ile problem çıkarmasıyla ünlü. Laptop BIOS'unuzda SVM (sanallaştırma) modu var mı bilmiyorum ama varsa kapatabilirsiniz sanallaştırmayla işiniz yoksa.

* Wi-Fi & Bluetooth, yani kısaca ağ sürücülerinizi güncelleyin. Aşağıdaki Intel aracını kullanabilirsiniz. Intel'in aracı başka eksik/güncel olmayan sürücü bulursa onları da yükleyin/güncelleyin.

www.intel.com

Intel® Driver & Support Assistant

The Intel® Driver & Support Assistant helps keeps your system up-to-date by detecting when updates are available.
www.intel.com www.intel.com


----
Not: Tüm dökümleri bilgi olarak ekleyemiyorum, 5 ifadeden daha fazla kullanamazsınız diyor.
 
Artı 0 Eksi
Öncellikle il adımlarınızı uyguladım
C:\Windows\System32>SFC /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

sonra pc yeniden başladı ve tarama yaptı
intel driverlerına kurdum realtek ide kurdum sonra uptaden güncelleştirme aldım onları da yapınca eski sürücü kurdu uptade ve sonra amd software sürümü windows uptade sürümünüzü otomatik olarak değiştirmiş aygıt yöneticisinden bakınca uptade 2020 sürümlü sürücü kurmuş sonra amd den söyle bir mesaj geldi adrenalin programından amd kaynaklı mavi ekran çökme yaşadığınızı tespit ettik amd bu hata ile rapor hazırladı bunu göndermenizi istiyoruz diye onunda resmini atıyorum. birde bunlardan sonra mavi ekran aldım 3 kere tekrardan onlarında minidump klasörünü bırakıyorum SVM YİDE BİOS üzerinden kapattım

Minidump (2).zip

drive.google.com drive.google.com
 

Dosya Ekleri

  • Adsız.png
    Adsız.png
    937 KB · Görüntüleme: 34
Artı 0 Eksi
Realtek sürücüsü hala aynı bir, bir değişiklik yok. Sizdeki Haziran sürümü, ancak Ocak'ta gelmiş bir sürüm daha var. Önceki sürücüleri silmiş miydiniz yüklemeden önce?

Rich (BB code): 
start             end                 module name
fffff806`c3150000 fffff806`c37c3000   RTKVHD64   (deferred)         
    Image path: \SystemRoot\system32\drivers\RTKVHD64.sys
    Image name: RTKVHD64.sys
    Browse all global symbols  functions  data
    Timestamp:        Tue Jun 23 13:34:50 2020 (5EF1DACA)


Evet son dosyalarınızda da ağırlıklı olarak bahsettiğiniz AMD işlemcinizin dahili grafik sürücüleri ile alakalı problemler var.

DDU ile AMD ile alakalı sürücüleri tamamen temizleyin. Daha sonra güncelini kurmanız gerekecek. Adımları paylaşıyorum.

- Güncel sürücüyü indirin, bir köşede dursun.
msedge_ilHRbzk1jq.png


- İnterneti kesin.
- Daha sonra DDU ile Sürücü Kaldırma rehberini takip edin.
- Sürücüyü kaldırdıktan sonra bilgisayar yeniden başlayacak.
- Bilgisayar açılınca indirdiğiniz sürücüyü kurun.
- İşlemler bitince interneti bağlayın.


Kod: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1874

    Key  : Analysis.Elapsed.mSec
    Value: 3151

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x3b

    Key  : Failure.Bucket
    Value: AV_dxgkrnl!DXGADAPTER::AcquireCoreResourceShared

    Key  : Failure.Hash
    Value: {ea68fb24-d507-488d-00b3-5dce3c196ff6}

    Key  : WER.OS.Branch
    Value: ni_release

    Key  : WER.OS.Version
    Value: 10.0.22621.1


BUGCHECK_CODE:  3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff8068ada10a4

BUGCHECK_P3: fffffa897aa1abd0

BUGCHECK_P4: 0

FILE_IN_CAB:  060723-11156-01.dmp

CONTEXT:  fffffa897aa1abd0 -- (.cxr 0xfffffa897aa1abd0)
rax=ffffd5820000003c rbx=ffffd582a0b4a000 rcx=ffffab058466d5c0
rdx=0000000000000005 rsi=00000000ffffffff rdi=00000000ffffffff
rip=fffff8068ada10a4 rsp=fffffa897aa1b5f0 rbp=ffffd582969b9060
 r8=ffffab0584617050  r9=0000000000000015 r10=ffffab058466d540
r11=fffffa897aa1b580 r12=0000015dfdd38b50 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050286
dxgkrnl!DXGADAPTER::AcquireCoreResourceShared+0x184:
fffff806`8ada10a4 8b7038          mov     esi,dword ptr [rax+38h] ds:002b:ffffd582`00000074=????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  dwm.exe

STACK_TEXT:
fffffa89`7aa1b5f0 fffff806`8ada53b3     : ffffd582`a308cd20 ffffd582`a0b4a088 fffffa89`7aa1bb60 ffffab05`84fafc70 : dxgkrnl!DXGADAPTER::AcquireCoreResourceShared+0x184
fffffa89`7aa1b800 fffff806`7be406e8     : ffffd582`a31c6080 ffffd582`a31c6080 0000015d`fdd39220 ffffab05`8d273498 : dxgkrnl!DxgkPresentMultiPlaneOverlay3+0x633
fffffa89`7aa1bae0 00007ffb`f0b65954     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000027`1db1ca68 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`f0b65954


SYMBOL_NAME:  dxgkrnl!DXGADAPTER::AcquireCoreResourceShared+184

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

IMAGE_VERSION:  10.0.22621.1702

STACK_COMMAND:  .cxr 0xfffffa897aa1abd0 ; kb

BUCKET_ID_FUNC_OFFSET:  184

FAILURE_BUCKET_ID:  AV_dxgkrnl!DXGADAPTER::AcquireCoreResourceShared

OS_VERSION:  10.0.22621.1

BUILDLAB_STR:  ni_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {ea68fb24-d507-488d-00b3-5dce3c196ff6}

Followup:     MachineOwner
---------


*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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: ffff9e8600000074, 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: fffff8075ae110a4, 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: 1765

    Key  : Analysis.Elapsed.mSec
    Value: 2550

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x50

    Key  : Failure.Bucket
    Value: AV_R_(null)_dxgkrnl!DXGADAPTER::AcquireCoreResourceShared

    Key  : Failure.Hash
    Value: {28c943b2-619b-a696-cbad-e5e95eb32841}

    Key  : WER.OS.Branch
    Value: ni_release

    Key  : WER.OS.Version
    Value: 10.0.22621.1


BUGCHECK_CODE:  50

BUGCHECK_P1: ffff9e8600000074

BUGCHECK_P2: 0

BUGCHECK_P3: fffff8075ae110a4

BUGCHECK_P4: 2

FILE_IN_CAB:  060723-15187-01.dmp

READ_ADDRESS: fffff8074f51c468: 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
 ffff9e8600000074

MM_INTERNAL_CODE:  2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  dwm.exe

TRAP_FRAME:  ffff9e864a3a92f0 -- (.trap 0xffff9e864a3a92f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff9e860000003c rbx=0000000000000000 rcx=ffffde04230a2498
rdx=0000000000000006 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8075ae110a4 rsp=ffff9e864a3a9480 rbp=ffffc906d1004060
 r8=ffffde0419abde50  r9=0000000000000016 r10=ffffde04230a2400
r11=ffff9e864a3a9410 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
dxgkrnl!DXGADAPTER::AcquireCoreResourceShared+0x184:
fffff807`5ae110a4 8b7038          mov     esi,dword ptr [rax+38h] ds:ffff9e86`00000074=????????
Resetting default scope

STACK_TEXT:
ffff9e86`4a3a90c8 fffff807`4eca7541     : 00000000`00000050 ffff9e86`00000074 00000000`00000000 ffff9e86`4a3a92f0 : nt!KeBugCheckEx
ffff9e86`4a3a90d0 fffff807`4eaeb42c     : ffffc906`00000001 00000000`00000000 ffff9e86`4a3a9289 00000000`00000000 : nt!MiSystemFault+0x1bf031
ffff9e86`4a3a91d0 fffff807`4ec3c529     : ffffc906`d79d4f20 ffffc906`d2eb1010 ffff9e86`4a3a9b00 00000000`00000002 : nt!MmAccessFault+0x29c
ffff9e86`4a3a92f0 fffff807`5ae110a4     : ffffc906`d917d000 00000000`ffffffff 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x369
ffff9e86`4a3a9480 fffff807`5ac6baeb     : ffffc906`e4aeb960 ffff9e86`4a3a97b8 00000000`00000000 00000000`00000000 : dxgkrnl!DXGADAPTER::AcquireCoreResourceShared+0x184
ffff9e86`4a3a9690 fffff807`5af7ccfc     : ffffde04`0b03e700 ffff9e86`4a3a97d0 00000000`00000001 00000000`00000000 : dxgkrnl!COREADAPTERACCESS::AcquireShared+0x63
ffff9e86`4a3a96d0 fffff807`5af87f91     : ffff9e86`4a3a9b00 ffff9e86`4a3a9b00 ffffc906`d9709008 ffffc906`d9709008 : dxgkrnl!OutputDuplThunks<void (__cdecl OUTPUTDUPL_MGR::*)(_DXGKARG_SETPOINTERPOSITION const * __ptr64) __ptr64,_DXGKARG_SETPOINTERPOSITION const * __ptr64>::RunForAdapter+0x1d4
ffff9e86`4a3a9850 fffff807`5af866d1     : 00000000`0000d682 ffff9e86`4a3a9a70 00000000`00000000 ffffc906`d9709008 : dxgkrnl!SetPointerPositionForDisplaySource+0x9ed
ffff9e86`4a3a9a00 fffff807`5af863a8     : 00000000`00000000 ffffc906`d917d001 ffffc906`d917d000 ffff9e86`4a3a9b00 : dxgkrnl!DxgkSetPointerPosition+0x311
ffff9e86`4a3a9aa0 fffff394`95712e38     : ffffde04`0e5c8480 00000000`000003fb ffffc906`d9fbf790 fffff807`86b710ed : dxgkrnl!DxgkCddSetPointerPosition+0x48
ffff9e86`4a3a9ae0 fffff394`95712dc4     : 00000000`000003fb fffff807`86b71269 00000000`000730e1 ffffde04`0e4d0000 : cdd!MovePointerInternal+0x60
ffff9e86`4a3a9b30 fffff394`9538f738     : fffff807`86b71260 fffff394`9538f63c 00000000`00000002 ffff9e86`4a3a9bf0 : cdd!DrvMovePointerEx+0x14
ffff9e86`4a3a9b60 fffff394`9538f312     : 00000000`00000000 ffff9e86`4a3a9bf0 ffffde04`1ed68010 00000000`00000000 : win32kfull!vMovePointer+0x70
ffff9e86`4a3a9ba0 fffff394`954140c2     : 00000000`00000000 fffff807`000003fb 00000000`000002b3 00000000`00000000 : win32kfull!GreMovePointer+0x152
ffff9e86`4a3a9c30 fffff394`95413722     : fffff394`95694668 00000000`00000000 ffff9e86`4a3a9d41 00000000`00000009 : win32kfull!CursorApiRouter::MovePointer+0x8e
ffff9e86`4a3a9c80 fffff394`95412967     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32kfull!xxxMoveEventAbsolute+0x43e
ffff9e86`4a3a9d90 fffff394`9526bbbf     : 00000000`00000000 ffff9e86`4a3a9f68 ffff9e86`4a3aa4d8 00000000`00000000 : win32kfull!EditionCommitMousePosAndMove+0x97
ffff9e86`4a3a9e00 fffff394`95237015     : 00000000`00000001 00000000`00000000 00000000`0000003f ffff9e86`4a3a9fc0 : win32kbase!EditionCommitMousePosAndMove+0x83
ffff9e86`4a3a9e70 fffff394`950f0dda     : 00000000`00000001 ffff9e86`4a3a9f79 00000000`00000000 00000000`00000000 : win32kbase!ApiSetEditionCommitMousePosAndMove+0x125
ffff9e86`4a3a9f00 fffff394`95135983     : 000002b3`000003fc ffff9e86`4a3aa0e0 ffff9e86`4a3aa4c0 00000000`00000000 : win32kbase!CMouseProcessor::CommitMousePosAndMoveCursor+0x17a
ffff9e86`4a3a9fe0 fffff394`950f1bdf     : 000002b3`000003fb 000002b3`000003fc 00000000`00000000 00000000`00000001 : win32kbase!CMouseProcessor::ProcessMouseInputData+0xab44b
ffff9e86`4a3aa340 fffff394`950f00fa     : ffffde04`0e4df000 fffff394`950f017d ffffde04`0e4df590 ffffde04`0e4df010 : win32kbase!CMouseProcessor::ProcessInput+0x61b
ffff9e86`4a3aa570 fffff394`950f0333     : ffffde04`0e4df010 00000001`190c7f22 ffffde04`0e4df590 ffffc906`e12ea658 : win32kbase!CMouseSensor::FlushMouseReports+0x42
ffff9e86`4a3aa5b0 fffff394`950f0264     : ffffde04`204d8b70 00000000`00000018 ffffde04`0e4df000 ffffde04`0e4df010 : win32kbase!CMouseSensor::ProcessInputWithRateLimitingIfEnabled+0xb3
ffff9e86`4a3aa600 fffff394`95002baf     : 00000000`00000000 ffff9e86`4a3aa740 ffffde04`0e4df001 00000000`00000000 : win32kbase!CMouseSensor::ProcessInput+0x54
ffff9e86`4a3aa640 fffff394`95089edd     : 00000000`00000002 00000000`00000002 ffffde04`0e4df010 00000000`00000002 : win32kbase!CBaseInput::OnReadNotification+0xef
ffff9e86`4a3aa780 fffff394`9508a092     : 00000000`00000001 00000000`00000001 ffffde04`12591010 00000000`00000002 : win32kbase!CBaseInput::OnDispatcherObjectSignaled+0xf1
ffff9e86`4a3aa8b0 fffff394`9508d811     : 00000000`00000001 00000000`00000001 ffffde04`12591010 ffffde04`12591010 : win32kbase!CBaseInput::_OnDispatcherObjectSignaled+0x12
ffff9e86`4a3aa8e0 fffff394`9508a515     : 00000000`00000000 00000000`00000000 00000000`00000000 fffff394`9508cb16 : win32kbase!IOCPDispatcher::HandleSensorDispatcherSignal+0x75
ffff9e86`4a3aa940 fffff394`9508a2c0     : 00000000`00000001 00000000`00000001 00000000`00000000 fffff394`958710cb : win32kbase!IOCPDispatcher::Dispatch+0x15
ffff9e86`4a3aa9a0 fffff394`950cbd31     : 00000000`00000000 0000017e`a9871290 00000000`00000020 0000017e`a9871290 : win32kbase!UserKSTWait+0x130
ffff9e86`4a3aaa80 fffff394`95880a7d     : 00000000`00000000 ffffc906`e2632080 ffffc906`e2632080 00000000`00000000 : win32kbase!NtKSTWait+0x21
ffff9e86`4a3aaab0 fffff807`4ec406e8     : ffffc906`0000032f 00000000`0000048c 00000000`00000490 00000000`00000001 : win32k!NtKSTWait+0x15
ffff9e86`4a3aaae0 00007ffd`49267ab4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000061`f2f7f9b8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`49267ab4


SYMBOL_NAME:  dxgkrnl!DXGADAPTER::AcquireCoreResourceShared+184

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

IMAGE_VERSION:  10.0.22621.1702

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  184

FAILURE_BUCKET_ID:  AV_R_(null)_dxgkrnl!DXGADAPTER::AcquireCoreResourceShared

OS_VERSION:  10.0.22621.1

BUILDLAB_STR:  ni_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {28c943b2-619b-a696-cbad-e5e95eb32841}

Followup:     MachineOwner
---------


*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_SCHEDULER_INTERNAL_ERROR (119)
The video scheduler has detected that fatal violation has occurred. This resulted
in a condition that video scheduler can no longer progress. Any other values after
parameter 1 must be individually examined according to the subtype.
Arguments:
Arg1: 0000000000000001, The driver has reported an invalid fence ID.
Arg2: 0000000000000089
Arg3: 000000000000008a
Arg4: ffff9c8b47e43000

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

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1578

    Key  : Analysis.Elapsed.mSec
    Value: 2447

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x119

    Key  : Failure.Bucket
    Value: 0x119_1_DRIVER_REPORTED_INVALID_FENCE_ID_dxgmms2!VidSchiVerifyDriverReportedFenceId

    Key  : Failure.Hash
    Value: {7790a251-8ea1-2e4a-c5ce-5acaee0f2787}

    Key  : WER.OS.Branch
    Value: ni_release

    Key  : WER.OS.Version
    Value: 10.0.22621.1


BUGCHECK_CODE:  119

BUGCHECK_P1: 1

BUGCHECK_P2: 89

BUGCHECK_P3: 8a

BUGCHECK_P4: ffff9c8b47e43000

FILE_IN_CAB:  060723-13718-01.dmp

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  SystemSettings.exe

STACK_TEXT:
fffff803`08d3f758 fffff803`1a4a5685     : 00000000`00000119 00000000`00000001 00000000`00000089 00000000`0000008a : nt!KeBugCheckEx
fffff803`08d3f760 fffff803`2991bb92     : 00000000`0000080b ffff9c8b`36b07d00 ffff9c8b`36b07d08 ffff9c8b`36b07d10 : watchdog!WdLogSingleEntry5+0x3b45
fffff803`08d3f810 fffff803`29900107     : ffff9c8b`49a6f010 fffff803`1a02f1b6 00000000`00000001 ffff9c8b`4ac75000 : dxgmms2!VidSchiVerifyDriverReportedFenceId+0x11b5a
fffff803`08d3f850 fffff803`298ffcfd     : 00000000`00000089 fffff803`08d3f9d0 ffff9c8b`47e43000 ffff9c8b`47e43000 : dxgmms2!VidSchDdiNotifyInterruptWorker+0x267
fffff803`08d3f8d0 fffff803`1a033760     : ffff9c8b`3f1eb030 fffff803`1a033760 ffff9c8b`3f1eb030 00000000`00000000 : dxgmms2!VidSchDdiNotifyInterrupt+0xcd
fffff803`08d3f930 fffff803`4bb0fc07     : fffff803`08d3faa0 ffff9c8b`40762000 ffff9c8b`40762000 ffff9c8b`40762000 : dxgkrnl!DxgNotifyInterruptCB+0xa0
fffff803`08d3f9a0 fffff803`08d3faa0     : ffff9c8b`40762000 ffff9c8b`40762000 ffff9c8b`40762000 ffff9c8b`40762000 : amdkmdag+0xffc07
fffff803`08d3f9a8 ffff9c8b`40762000     : ffff9c8b`40762000 ffff9c8b`40762000 ffff9c8b`40762000 fffff803`4bbf20e4 : 0xfffff803`08d3faa0
fffff803`08d3f9b0 ffff9c8b`40762000     : ffff9c8b`40762000 ffff9c8b`40762000 fffff803`4bbf20e4 00000000`00000002 : 0xffff9c8b`40762000
fffff803`08d3f9b8 ffff9c8b`40762000     : ffff9c8b`40762000 fffff803`4bbf20e4 00000000`00000002 00000089`00000005 : 0xffff9c8b`40762000
fffff803`08d3f9c0 ffff9c8b`40762000     : fffff803`4bbf20e4 00000000`00000002 00000089`00000005 00000000`00000000 : 0xffff9c8b`40762000
fffff803`08d3f9c8 fffff803`4bbf20e4     : 00000000`00000002 00000089`00000005 00000000`00000000 00000004`00000efb : 0xffff9c8b`40762000
fffff803`08d3f9d0 00000000`00000002     : 00000089`00000005 00000000`00000000 00000004`00000efb 00000000`00000000 : amdkmdag+0x1e20e4
fffff803`08d3f9d8 00000089`00000005     : 00000000`00000000 00000004`00000efb 00000000`00000000 00000003`a6eca925 : 0x2
fffff803`08d3f9e0 00000000`00000000     : 00000004`00000efb 00000000`00000000 00000003`a6eca925 00000000`00000009 : 0x00000089`00000005


SYMBOL_NAME:  dxgmms2!VidSchiVerifyDriverReportedFenceId+11b5a

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

IMAGE_VERSION:  10.0.22621.1702

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  11b5a

FAILURE_BUCKET_ID:  0x119_1_DRIVER_REPORTED_INVALID_FENCE_ID_dxgmms2!VidSchiVerifyDriverReportedFenceId

OS_VERSION:  10.0.22621.1

BUILDLAB_STR:  ni_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {7790a251-8ea1-2e4a-c5ce-5acaee0f2787}

Followup:     MachineOwner
---------


*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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: ffff900d41451550, Address of the trap frame for the exception that caused the BugCheck
Arg3: ffff900d414514a8, 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: 1671

    Key  : Analysis.Elapsed.mSec
    Value: 3099

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x139

    Key  : FailFast.Name
    Value: CORRUPT_LIST_ENTRY

    Key  : FailFast.Type
    Value: 3

    Key  : Failure.Bucket
    Value: 0x139_3_CORRUPT_LIST_ENTRY_KTIMER_LIST_CORRUPTION_nt!KiInsertTimerTable

    Key  : Failure.Hash
    Value: {f89e8bcc-9d62-a3aa-7602-6fa1ac774850}

    Key  : WER.OS.Branch
    Value: ni_release

    Key  : WER.OS.Version
    Value: 10.0.22621.1


BUGCHECK_CODE:  139

BUGCHECK_P1: 3

BUGCHECK_P2: ffff900d41451550

BUGCHECK_P3: ffff900d414514a8

BUGCHECK_P4: 0

FILE_IN_CAB:  060723-10578-01.dmp

TRAP_FRAME:  ffff900d41451550 -- (.trap 0xffff900d41451550)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff800f1c0f2160 rbx=0000000000000000 rcx=0000000000000003
rdx=fffff80719e82180 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8071ec7dd16 rsp=ffff900d414516e0 rbp=0000000000000034
 r8=0000000038d3ee5a  r9=fffff8071e800000 r10=fffff80719e85d80
r11=ffff800f1c0f2180 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac pe cy
nt!KiInsertTimerTable+0x256026:
fffff807`1ec7dd16 cd29            int     29h
Resetting default scope

EXCEPTION_RECORD:  ffff900d414514a8 -- (.exr 0xffff900d414514a8)
ExceptionAddress: fffff8071ec7dd16 (nt!KiInsertTimerTable+0x0000000000256026)
   ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
  ExceptionFlags: 00000001
NumberParameters: 1
   Parameter[0]: 0000000000000003
Subcode: 0x3 FAST_FAIL_CORRUPT_LIST_ENTRY

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

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

EXCEPTION_STR:  0xc0000409

STACK_TEXT:
ffff900d`41451228 fffff807`1ec40fa9     : 00000000`00000139 00000000`00000003 ffff900d`41451550 ffff900d`414514a8 : nt!KeBugCheckEx
ffff900d`41451230 fffff807`1ec41532     : ffff800f`1c0f2040 ffff800f`15eee040 00000000`00000000 00000000`00000002 : nt!KiBugCheckDispatch+0x69
ffff900d`41451370 fffff807`1ec3f306     : 00000000`00000000 00000002`00000000 00000000`00000001 00000000`00000000 : nt!KiFastFailDispatch+0xb2
ffff900d`41451550 fffff807`1ec7dd16     : 00000000`00000000 00000000`00000000 ffff900d`41451990 00000000`00000000 : nt!KiRaiseSecurityCheckFailure+0x346
ffff900d`414516e0 fffff807`1ea38dd8     : ffff800f`1c0f2040 00000000`00000000 00000000`00000014 fffff807`1eb689db : nt!KiInsertTimerTable+0x256026
ffff900d`41451760 fffff807`1ea3b296     : 00000002`00000000 00000014`00000001 00000000`00000034 00000000`38d3ee5a : nt!KiCommitThreadWait+0x2c8
ffff900d`41451810 fffff807`2d3e1983     : ffff900d`41451bf8 ffff900d`41451bf8 fffff807`2d3d6538 ffff900d`41451bf8 : nt!KeWaitForSingleObject+0x256
ffff900d`41451bb0 fffff807`1ea0dc67     : ffff800f`1c0f2040 ffffffff`ffdc0268 00000000`00000080 fffff807`2d3e18c0 : bam!BampThrottlingWorker+0xc3
ffff900d`41451bf0 fffff807`1ec30854     : ffffa781`f921d180 ffff800f`1c0f2040 fffff807`1ea0dc10 86db4478`146f3ddf : nt!PspSystemThreadStartup+0x57
ffff900d`41451c40 00000000`00000000     : ffff900d`41452000 ffff900d`4144c000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME:  nt!KiInsertTimerTable+256026

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22621.1702

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  256026

FAILURE_BUCKET_ID:  0x139_3_CORRUPT_LIST_ENTRY_KTIMER_LIST_CORRUPTION_nt!KiInsertTimerTable

OS_VERSION:  10.0.22621.1

BUILDLAB_STR:  ni_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {f89e8bcc-9d62-a3aa-7602-6fa1ac774850}

Followup:     MachineOwner
---------
 
Son düzenleme:
Artı 0 Eksi
realtek sürücüsünü güncelliyorum fakat güncelledikten sonra pc yeniden başlatınca aynı eski sürücü duruyor yeni sürümü kurmuyor bunun üzerine ddu adımları ile ekran kartı driverlarını kurdum fakat herhangi bir düzelme olmadı mavi ekran hatasını tekrardan alıyorum özellikle pc boşta chrome da gezinirken alıyorum vede microsft word uygulamalarını kullanırken. drivelerı güncelledikten sonra aldığım mindump dosyası bırakıyorum.

mindump4.zip

drive.google.com drive.google.com
 
Artı 0 Eksi
* Bazı hataların neden kaynaklandığı tam olarak belli olmasa da diğerleri ipuçları veriyor.

* Genel olarak görüntü sürücüleri kaynaklı hatalar var.

* Harici ekran kartınız veya AMD işlemcinizin entegre grafiğiyle alakalı bir problem gibi.

* Hangi sürücüleri DDU ile temizleyip tekrar güncellerini kurdunuz?

* NVIDIA mı yoksa AMD işlemcinizin dahili grafik sürücüleri mi?

* Çünkü AMD ile alakalı problem yaşadığınızı söylemişsiniz. Yaptıysanız bile tekrar yapmanız gerekecek çünkü tam olmamış gibi.

* Güvenli modda ve internet kesik olarak yapın.

Şu adımları tekrar yapar mısınız?

- Güncel sürücüyü indirin.
https://www.amd.com/en/support/apu/...-processors-radeon-graphics/amd-ryzen-7-4800h
msedge_ilHRbzk1jq.png


- İnterneti kesin.
- Daha sonra DDU ile Sürücü Kaldırma rehberini takip edin.
- Sürücüyü kaldırdıktan sonra bilgisayar yeniden başlayacak.
- Bilgisayar açılınca indirdiğiniz sürücüyü kurun.
- İşlemler bitince interneti bağlayın.
 
Artı 0 Eksi

Benzer konular

C
  • Soru
R7 4800H 1650 Ti sistem boştayken mavi ekran hatası
Mesaj
2
Görüntüleme
10.631
Celebi1
C
M
  • Soru
GTX 1650 Ti-R7 4800H Laptop mavi ekran hatası
Mesaj
1
Görüntüleme
370
altotziki
altotziki
Wradern
  • Soru
R7 4800H 1650 Ti Sistem Mavi Ekran
2
Mesaj
14
Görüntüleme
763
Wradern
Wradern
K
  • Çözüldü
Çözüldü  Lenovo Ideapad Gaming 3 R7 4800H 1650 Ti mavi ekran hatası
Mesaj
4
Görüntüleme
378
Kooltrik
K
M
  • Soru
R7 4800H GTX 1650 Ti Youtube Videosu İzlerken Mavi Ekran
Mesaj
4
Görüntüleme
451
Mehmet41
M

Technopat Haberler

Yeni konular

Yeni mesajlar

Geri
Yukarı