Premiere Pro mavi ekran hatası

İşletim sistemi
Windows 10

MxKrav

Hectopat
Katılım
12 Şubat 2017
Mesajlar
19
Daha fazla  
Cinsiyet
Erkek
Anakart: MSI H100M-Gaming
CPU: i5 7500.
GPU: ASUS Dual GTX1060 3GB.
RAM: G.Skill Aegis DDR4 15CL 2x8GB 2133MHz.
Minidump - Google Drive dumb dosyam.

Uygulamayı lisanslı kullanıyorum ve çalışırken bu ay sürekli mavi ekran hatası alıyorum daha render aşamasına bile gelemiyorum.
 
VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e) ve dxgmms2.sys
VIDEO_TDR_FAILURE (116) ve nvlddmkm.sys

Ekran kartı sürücüleri ile alakalı duruyor.

  • Güncel sürücüyü indirin: GTX 1060 - 516.94 sürücüsü
  • İndirdikten sonra kurmayın, bir köşede bekletin.
  • Başlattaki arama yerine Aygıt yükleme ayarlarını değiştir yazın.
  • Çıkan pencereyi Hayır olarak seçin ve kapatın.
  • 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.

  • Şimdi de i5-7500 işlemciniz için Intel grafik sürücülerini indirin: Intel® Graphics
  • Üstteki .exe olanı indirin ama kurmayın, yine bir köşede kalsın.
  • Aynı DDU işlemini Intel grafik sürücüleriniz için de yapın. DDU'da Intel GPU silmeyi seçin.
  • Daha sonra indirdiğiniz Intel sürücüsünü kurun.

Hem Nvidia hem de Intel sürücü kurulumları bittikten sonra:
  • Aygıt yükleme ayarlarını değiştir yazıp daha önce Hayır olan kısmı artık "Evet" seçebilirsiniz.
  • rundll32_AL0C6OLwme.png


Bu güncellemelerden sonra mavi ekran alıp almadığınızı kontrol edin.

Bonus olarak, CMD'yi yönetici olarak çalıştırıp şu komutu girin:
SFC /scannow


Yüklenemeyen/geç yüklenen sürücülerde dikkat çekenler:

Rich (BB code):
nvhda64v.sys = Nvidia HDMI Audio Device (nForce chipset driver)
bthhfenum.sys = Bluetooth Hands-Free Driver
bthpan.sys = Bluetooth Personal Area Networking Driver
BthHfAud.sys = Bluetooth Hands-free Audio Device Driver


Dökümler:
Kod:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)
The video memory manager encountered a condition that it can't recover from. By crashing,
the video memory manager is attempting to get enough information into the minidump such that
somebody can pinpoint what lead to this condition.
Arguments:
Arg1: 0000000000000017, Unexpected system command failure.
Arg2: ffffffffc000000d
Arg3: 0000000000000000
Arg4: 0000000000000000

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

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1828

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 18093

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x10e

    Key  : Bugcheck.Code.Register
    Value: 0x10e

    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


FILE_IN_CAB:  092522-8796-01.dmp

BUGCHECK_CODE:  10e

BUGCHECK_P1: 17

BUGCHECK_P2: ffffffffc000000d

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
ffffc486`b7b777a8 fffff804`6d3b3ad0     : 00000000`0000010e 00000000`00000017 ffffffff`c000000d 00000000`00000000 : nt!KeBugCheckEx
ffffc486`b7b777b0 fffff804`6f23a147     : ffffb28a`21a16970 ffffb28a`1cfe5688 ffffcb86`00000000 ffffb28a`1cfe5688 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffffc486`b7b777f0 fffff804`6f23a720     : ffffb28a`21a16800 00000000`00000000 ffffb28a`1cfe5688 ffffc486`b7b778c0 : dxgmms2!VIDMM_WORKER_THREAD::FlushEvictQueue+0x133
ffffc486`b7b77840 fffff804`6f23a48e     : ffffcb86`ae20cc60 ffffcb86`ae20cc60 00000000`00000000 ffffb28a`21a168e0 : dxgmms2!VIDMM_WORKER_THREAD::ProcessEvictQueues+0xcc
ffffc486`b7b77870 fffff804`6f2269c9     : fffff804`6f1c4300 fffff804`6f1c43f4 00000000`00000000 ffffcb86`b786bb00 : dxgmms2!VIDMM_WORKER_THREAD::HandleRecoverablePageInFailure+0xf6
ffffc486`b7b77900 fffff804`6f216499     : ffffb28a`21a168e0 00000000`00000001 00000000`00000401 ffffcb86`ba940000 : dxgmms2!VIDMM_WORKER_THREAD::Run+0x1b539
ffffc486`b7b77ae0 fffff804`56271d25     : ffffcb86`aa681040 fffff804`6f216490 ffffb28a`21a168e0 fffff08f`a5237f01 : dxgmms2!VidMmWorkerThreadProc+0x9
ffffc486`b7b77b10 fffff804`56400628     : ffffe081`f83a4180 ffffcb86`aa681040 fffff804`56271cd0 fffff08f`00000000 : nt!PspSystemThreadStartup+0x55
ffffc486`b7b77b60 00000000`00000000     : ffffc486`b7b78000 ffffc486`b7b71000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  dxgmms2!VIDMM_WORKER_THREAD::FlushEvictQueue+133

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

IMAGE_VERSION:  10.0.19041.1940

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  133

FAILURE_BUCKET_ID:  0x10e_17_dxgmms2!VIDMM_WORKER_THREAD::FlushEvictQueue

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {8b70aac8-c9b8-15d4-254c-a3e0828fa53b}

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


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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffff898813b9b460, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff80471b53d00, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.

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

Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispsi.inf_amd64_9751f6c72c23c322\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2015

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 15741

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x116

    Key  : Bugcheck.Code.Register
    Value: 0x116

    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


FILE_IN_CAB:  092522-6062-01.dmp

BUGCHECK_CODE:  116

BUGCHECK_P1: ffff898813b9b460

BUGCHECK_P2: fffff80471b53d00

BUGCHECK_P3: ffffffffc000009a

BUGCHECK_P4: 4

VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffff898813b9b460
Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.

PROCESS_OBJECT: 0000000000000004

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
ffff8385`bab1f918 fffff804`6804638e     : 00000000`00000116 ffff8988`13b9b460 fffff804`71b53d00 ffffffff`c000009a : nt!KeBugCheckEx
ffff8385`bab1f920 fffff804`67ff6b04     : fffff804`71b53d00 ffff8988`0fa466e0 00000000`00002000 ffff8988`0fa467a0 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
ffff8385`bab1f960 fffff804`67fef63c     : ffff8988`0fa44000 00000000`01000000 00000000`00000004 00000000`00000004 : dxgkrnl!ADAPTER_RENDER::Reset+0x174
ffff8385`bab1f990 fffff804`68045ab5     : 00000000`00000100 ffff8988`0fa44a70 00000000`08404d50 fffff804`4fef6ecc : dxgkrnl!DXGADAPTER::Reset+0x4dc
ffff8385`bab1fa10 fffff804`68045c27     : fffff804`50925440 ffff8988`11c67d70 00000000`00000000 00000000`00000400 : dxgkrnl!TdrResetFromTimeout+0x15
ffff8385`bab1fa40 fffff804`4fe52b65     : ffff8988`102ca040 fffff804`68045c00 ffff8988`05caacf0 ffff8988`00000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27
ffff8385`bab1fa70 fffff804`4fe71d25     : ffff8988`102ca040 00000000`00000080 ffff8988`05ca0040 000fa4ef`bd9bbfff : nt!ExpWorkerThread+0x105
ffff8385`bab1fb10 fffff804`50000628     : ffffda00`b87e6180 ffff8988`102ca040 fffff804`4fe71cd0 00000266`d8b1ce50 : nt!PspSystemThreadStartup+0x55
ffff8385`bab1fb60 00000000`00000000     : ffff8385`bab20000 ffff8385`bab19000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  nvlddmkm+eb3d00

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  0x116_IMAGE_nvlddmkm.sys

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {c89bfe8c-ed39-f658-ef27-f2898997fdbd}

Followup:     MachineOwner
---------
 
Son düzenleme:

Yeni konular

Geri
Yukarı