dxgmms2.sys, watchdog.sys, Wdf01000.sys, igdkmd64.sys Mavi Ekran Hataları

korkusuzmuk · 12 Ocak 2018

Yıllardır bazı spesifik oyunlarda mavi ekran almaktayım görüntü bağdaştırıcıları DDU'yla silinip kurulmuştur, internetteki çoğu şey denenmiştir. Son Minidumpları atıyorum belki şu işi çözen biri çıkar.

Recep Baltaş · 12 Ocak 2018

PC özellikleriniz nedir? İşlemci içindeki GPU sorunlu olabilir.

Kod:

*** STOP: 0x00000119 (0x0000000000000005, 0xffff8c02fe3f9000, 0xffff8c02fded88f0,
0x0000000000046d8b)

*** igdkmd64.sys - Address 0xfffff80880aba120 base at 0xfffff80880800000 DateStamp
0x58e7c022

*** STOP: 0x00000119 (0x0000000000000002, 0xffffffffc000000d, 0xffff968c8712c960,
0xffffb0847cce5ab0)

*** watchdog.sys - Address 0xfffff80b36fb333e base at 0xfffff80b36fb0000 DateStamp
0xee73d2b8

*** STOP: 0x00000119 (0x0000000000000005, 0xffffa4019a1d1000, 0xffffa4019a19aad0,
0x00000000001dd697)

*** watchdog.sys - Address 0xfffff80513d7333e base at 0xfffff80513d70000 DateStamp
0xee73d2b8

korkusuzmuk · 15 Ocak 2018

Kod:

------------------
System Information
------------------
      Time of this report: 1/12/2018, 21:01:06
      Operating System: Windows 10 Home Single Language 64-bit (10.0, Build 16299) (16299.rs3_release.170928-1534)
     Language: Turkish (Regional Setting: Turkish)
     System Manufacturer: ASUSTeK COMPUTER INC.
      System Model: N56VZ
       BIOS: N56VZ.217
  Processor: Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz (8 CPUs), ~2.4GHz
    Memory: 16384MB RAM
      Available OS Memory: 16270MB RAM
                Page File: 5179MB used, 14034MB available
              Windows Dir: C:\WINDOWS
          DirectX Version: DirectX 12
      DX Setup Parameters: Not found
         User DPI Setting: 96 DPI (100 percent)
       System DPI Setting: 120 DPI (125 percent)
          DWM DPI Scaling: Disabled
                 Miracast: Available, with HDCP
Microsoft Graphics Hybrid: Supported
           DxDiag Version: 10.00.16299.0015 64bit Unicode

--------------

Test amaçlı Devil May Cry adlı oyunu oynayayım dedim henüz oynayışa başlamadan hikayeyi anlatan storyline tarzı videoda önce görüntü takıldı, daha sonra ses 1-2 dakka akmaya devam etti sonrasında da ;

hal.dll , ntoskrnl.exe mavi ekran hatası aldım. Önceden aldıklarımdan farklı diye paylaşmak istedim belki çözen çıkar şu işi.

011518-35984-01.dmp

Recep Baltaş · 15 Ocak 2018

Bu hata harici ekran kartı kaynaklı. NVIDIA GPU'nuzda sorun var. Bu tür eski cihazlaarda aşırı ısınmadan dolayı olan, sık karşılaşılan bir durum. Reballing yaptırabilirsiniz ama yüzü astarını geçebilir.

Kod:

Microsoft (R) Windows Debugger Version 10.0.17061.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Recep\Downloads\011518-35984-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 16299 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 16299.15.amd64fre.rs3_release.170928-1534
Machine Name:
Kernel base = 0xfffff803`22006000 PsLoadedModuleList = 0xfffff803`2236cfd0
Debug session time: Mon Jan 15 14:18:35.970 2018 (UTC + 3:00)
System Uptime: 0 days 12:32:17.390
Loading Kernel Symbols
...............................................................
................................................................
.............................................................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 133, {1, 1e00, fffff80322402370, 0}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: TickPeriods                                   ***
***                                                                   ***
*************************************************************************
Probably caused by : nvlddmkm.sys ( nvlddmkm+1c79b5 )

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

nt!KeBugCheckEx:
fffff803`2217b6e0 48894c2408      mov     qword ptr [rsp+8],rcx ss:fffff803`2446bbd0=0000000000000133
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
    DISPATCH_LEVEL or above. The offending component can usually be
    identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff80322402370, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
    additional information regarding the cumulative timeout
Arg4: 0000000000000000

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: TickPeriods                                   ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1


TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  10.0.16299.192 (WinBuild.160101.0800)

SYSTEM_MANUFACTURER:  ASUSTeK COMPUTER INC.

SYSTEM_PRODUCT_NAME:  N56VZ

SYSTEM_SKU:  ASUS-NotebookSKU

SYSTEM_VERSION:  1.0       

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  N56VZ.217

BIOS_DATE:  05/22/2013

BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT:  N56VZ

BASEBOARD_VERSION:  1.0       

DUMP_TYPE:  2

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff80322402370

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

CPU_COUNT: 8

CPU_MHZ: 95b

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3a

CPU_STEPPING: 9

CPU_MICROCODE: 6,3a,9,0 (F,M,S,R)  SIG: 1B'00000000 (cache) 1B'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x133

PROCESS_NAME:  DMC-DevilMayCry.exe

CURRENT_IRQL:  d

ANALYSIS_SESSION_HOST:  DESKTOP-HH6FM2D

ANALYSIS_SESSION_TIME:  01-15-2018 17:05:34.0215

ANALYSIS_VERSION: 10.0.17061.1000 amd64fre

LAST_CONTROL_TRANSFER:  from fffff803221b5fd1 to fffff8032217b6e0

STACK_TEXT: 
fffff803`2446bbc8 fffff803`221b5fd1 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff803`22402370 : nt!KeBugCheckEx
fffff803`2446bbd0 fffff803`220b5916 : 000038f6`4914c075 fffff803`20f33180 00000000`002c1459 00000000`00000000 : nt!KeAccumulateTicks+0xfde11
fffff803`2446bc30 fffff803`228de3c5 : 000038f6`4914a719 00000000`00000000 fffff803`22931450 ffff8580`9f971ab0 : nt!KeClockInterruptNotify+0xc6
fffff803`2446bf40 fffff803`220804d5 : fffff803`2446bf50 00000000`00000010 ffff775e`8220cc34 00000000`00000100 : hal!HalpTimerClockIpiRoutine+0x15
fffff803`2446bf70 fffff803`2217cfca : fffff803`24464390 fffff803`22931450 00000000`00000000 00000000`00400500 : nt!KiCallInterruptServiceRoutine+0xa5
fffff803`2446bfb0 fffff803`2217d4d7 : fffff803`24464360 00000000`00000004 fffff803`244643f0 00000000`00000018 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
fffff803`24464310 fffff805`cd2d79b5 : fffff805`cd4acda9 ffffdd04`76ffd000 ffffdd04`76ffd000 ffffdd04`758c1940 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff803`244644a8 fffff805`cd4acda9 : ffffdd04`76ffd000 ffffdd04`76ffd000 ffffdd04`758c1940 ffffdd04`76ffd000 : nvlddmkm+0x1c79b5
fffff803`244644b0 ffffdd04`76ffd000 : ffffdd04`76ffd000 ffffdd04`758c1940 ffffdd04`76ffd000 ffffdd04`76febe90 : nvlddmkm+0x39cda9
fffff803`244644b8 ffffdd04`76ffd000 : ffffdd04`758c1940 ffffdd04`76ffd000 ffffdd04`76febe90 fffff805`cd4a5a4c : 0xffffdd04`76ffd000
fffff803`244644c0 ffffdd04`758c1940 : ffffdd04`76ffd000 ffffdd04`76febe90 fffff805`cd4a5a4c ffffdd04`758c1940 : 0xffffdd04`76ffd000
fffff803`244644c8 ffffdd04`76ffd000 : ffffdd04`76febe90 fffff805`cd4a5a4c ffffdd04`758c1940 fffff805`cd3a9a2c : 0xffffdd04`758c1940
fffff803`244644d0 ffffdd04`76febe90 : fffff805`cd4a5a4c ffffdd04`758c1940 fffff805`cd3a9a2c 00000000`00000100 : 0xffffdd04`76ffd000
fffff803`244644d8 fffff805`cd4a5a4c : ffffdd04`758c1940 fffff805`cd3a9a2c 00000000`00000100 ffffdd04`76ffd000 : 0xffffdd04`76febe90
fffff803`244644e0 ffffdd04`758c1940 : fffff805`cd3a9a2c 00000000`00000100 ffffdd04`76ffd000 00000000`00000000 : nvlddmkm+0x395a4c
fffff803`244644e8 fffff805`cd3a9a2c : 00000000`00000100 ffffdd04`76ffd000 00000000`00000000 ffffdd04`76ffd000 : 0xffffdd04`758c1940
fffff803`244644f0 00000000`00000100 : ffffdd04`76ffd000 00000000`00000000 ffffdd04`76ffd000 ffffdd04`772f14d0 : nvlddmkm+0x299a2c
fffff803`244644f8 ffffdd04`76ffd000 : 00000000`00000000 ffffdd04`76ffd000 ffffdd04`772f14d0 fffff805`cd2f731c : 0x100
fffff803`24464500 00000000`00000000 : ffffdd04`76ffd000 ffffdd04`772f14d0 fffff805`cd2f731c ffffdd04`76ffde40 : 0xffffdd04`76ffd000


THREAD_SHA1_HASH_MOD_FUNC:  b86eb0ede139f3640b246b1dedbff78803b5e1fb

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  1ea1de9b5ada4025e48512d88aa1991bad9397cb

THREAD_SHA1_HASH_MOD:  137ac73acf8eaea962c40c10a4a9cd772d232e44

FOLLOWUP_IP:
nvlddmkm+1c79b5
fffff805`cd2d79b5 c3              ret

FAULT_INSTR_CODE:  8accccc3

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  nvlddmkm+1c79b5

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5a4d69d6

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  1c79b5

FAILURE_BUCKET_ID:  0x133_ISR_nvlddmkm!unknown_function

BUCKET_ID:  0x133_ISR_nvlddmkm!unknown_function

PRIMARY_PROBLEM_CLASS:  0x133_ISR_nvlddmkm!unknown_function

TARGET_TIME:  2018-01-15T11:18:35.000Z

OSBUILD:  16299

OSSERVICEPACK:  192

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  784

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE: 

USER_LCID:  0

OSBUILD_TIMESTAMP:  2018-01-01 14:07:05

BUILDDATESTAMP_STR:  160101.0800

BUILDLAB_STR:  WinBuild

BUILDOSVER_STR:  10.0.16299.192

ANALYSIS_SESSION_ELAPSED_TIME:  73fc

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x133_isr_nvlddmkm!unknown_function

FAILURE_ID_HASH:  {f97493a5-ea2b-23ca-a808-8602773c2a86}

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

korkusuzmuk · 15 Ocak 2018

İlgi ve alakanız için teşekkür ederim hocam benim aklıma takılan, oyunu entegre grafikle çalıştırdığımda da donma ve mavi ekranla karşılaşmam ve de bazı oyunlar sorunsuz akarken bazılarında bu problemle karşılaşmak kafamı karıştırdı. Bir gelişme olursa tekrar konuya eklerim.

Bilgi açısından problemin olduğu ve olmadığı oyunları yazayım belki aynı problemlerle karşılaşanlar olur;

Sorunsuz Oyunlar

Farming Simulator 15
Rocket League
Don't Starve Together

Hata Aldıklarım

Devil May Cry
Aura Kingdom
Human : Fall Flat

Recep Baltaş · 15 Ocak 2018

Oyunlar farklı farklı grafik motoru kullanır. Kimisi sisteme çok yüklenirken kimisi o kadar yüklenmez. Bu durumda sisteme aşırı yüklenme olduğunda ekran kartı cevapsız kalıyor.

Windows'unuz güncel. Ekran kartı sürücüleriniz de güncel ise sorun donanımsaldir ki mavi ekran da genelde donanımsal hatalardaan kaynaklanır.

Onboard GPU'da da hata olması anakartın güç beslemesinde bir sorun olabileceğini gösterir diye düşünüyorum.

dxgmms2.sys, watchdog.sys, Wdf01000.sys, igdkmd64.sys Mavi Ekran Hataları

Ayrıntılı düzenleme

korkusuzmuk

Hectopat

Recep Baltaş

Technopat

korkusuzmuk

Hectopat

Recep Baltaş

Technopat

korkusuzmuk

Hectopat

Recep Baltaş

Technopat

Benzer konular

Yeni konular

Yeni mesajlar

Gizliliğinize önem veriyoruz