APU laptopta oyun oynarken mavi ekran sorunu

lucas2k

Zeptopat
Katılım
25 Temmuz 2021
Mesajlar
18
Daha fazla  
Cinsiyet
Erkek
Dosyayı herkese açık yapın.

Rica etsem benim de dosyalarımı kontrol eder misiniz? Oyuna girince mavi ekran veriyor veya görüntü kesildi hatası alıyorum. ( APU laptop )
 
Son düzenleyen: Moderatör:
Görmedim hocam. Raporu paylaşayım hemen.
[CODE title="1"]0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

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

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

Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 9983

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 30804

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

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

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

Key : WER.OS.Branch
Value: th1_st1

Key : WER.OS.Timestamp
Value: 2015-07-17T17:19:00Z

Key : WER.OS.Version
Value: 10.0.10240.16393


BUGCHECK_CODE: 116

BUGCHECK_P1: ffffe00191f061b0

BUGCHECK_P2: fffff8017cbdce98

BUGCHECK_P3: 0

BUGCHECK_P4: d

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

PROCESS_OBJECT: 000000000000000d

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffffd001`fc58c7c8 fffff801`7c742a7c : 00000000`00000116 ffffe001`91f061b0 fffff801`7cbdce98 00000000`00000000 : nt!KeBugCheckEx
ffffd001`fc58c7d0 fffff801`7c742213 : fffff801`7cbdce98 ffffe001`91f061b0 ffffd001`fc58c8a9 00000000`0000009f : dxgkrnl!TdrBugcheckOnTimeout+0xec
ffffd001`fc58c810 fffff801`8305e3b1 : ffffe001`91f061b0 ffffd001`fc58c8a9 00000000`000001b8 00000000`00000000 : dxgkrnl!TdrIsRecoveryRequired+0x193
ffffd001`fc58c840 fffff801`8308b0f8 : ffffe001`947f7000 00000000`00000002 ffffe001`947f7000 ffffe001`940c5000 : dxgmms2!VidSchiReportHwHang+0x3fd
ffffd001`fc58c910 fffff801`83077855 : 00000000`00000002 00000000`01d8d30d 00000000`00000010 fffff801`00000000 : dxgmms2!VidSchiCheckHwProgress+0x13888
ffffd001`fc58c950 fffff801`83045c2d : 00000000`00000000 ffffe001`940c5000 ffffd001`fc58cb00 00000000`00000000 : dxgmms2!VidSchiWaitForSchedulerEvents+0x265
ffffd001`fc58ca00 fffff801`83083363 : ffffe001`940c5000 ffffd001`fc58cbc8 ffffe001`95035010 ffffe001`00000000 : dxgmms2!VidSchiScheduleCommandToRun+0x32d
ffffd001`fc58cb90 fffff801`83083340 : ffffe001`940c5000 ffffe001`940c5000 ffffe001`90b72780 ffffd001`f99a8bc0 : dxgmms2!VidSchiRun_PriorityTable+0x1f
ffffd001`fc58cbc0 fffff801`34cf1698 : ffffe001`90b72780 ffffd001`fc58cc90 ffffd001`f999c180 fffff801`34d5e230 : dxgmms2!VidSchiWorkerThread+0x80
ffffd001`fc58cc00 fffff801`34d5e306 : ffffd001`f999c180 ffffe001`94fba800 ffffd001`f99a8bc0 00000000`00000000 : nt!PspSystemThreadStartup+0x58
ffffd001`fc58cc60 00000000`00000000 : ffffd001`fc58d000 ffffd001`fc587000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


SYMBOL_NAME: atikmpag+ce98

MODULE_NAME: atikmpag

IMAGE_NAME: atikmpag.sys

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x116_IMAGE_atikmpag.sys

OS_VERSION: 10.0.10240.16393

BUILDLAB_STR: th1_st1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {e300aa8c-6915-3f37-7957-d2e4fc30a6fd}

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

[/CODE]
Kod:
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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

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

Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 9109

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 27297

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

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

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

    Key  : WER.OS.Branch
    Value: th1_st1

    Key  : WER.OS.Timestamp
    Value: 2015-07-17T17:19:00Z

    Key  : WER.OS.Version
    Value: 10.0.10240.16393


BUGCHECK_CODE:  116

BUGCHECK_P1: ffffe000c0d9a4c0

BUGCHECK_P2: fffff8017da2cc9c

BUGCHECK_P3: 0

BUGCHECK_P4: d

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

PROCESS_OBJECT: 000000000000000d

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
ffffd000`295b27c8 fffff801`7d592a7c     : 00000000`00000116 ffffe000`c0d9a4c0 fffff801`7da2cc9c 00000000`00000000 : nt!KeBugCheckEx
ffffd000`295b27d0 fffff801`7d592213     : fffff801`7da2cc9c ffffe000`c0d9a4c0 ffffd000`295b28a9 00000000`0000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
ffffd000`295b2810 fffff801`83f5e3b1     : ffffe000`c0d9a4c0 ffffd000`295b28a9 00000000`00000005 00000000`00000000 : dxgkrnl!TdrIsRecoveryRequired+0x193
ffffd000`295b2840 fffff801`83f8b0f8     : ffffe000`be798000 00000000`00000002 ffffe000`be798000 ffffe000`badba000 : dxgmms2!VidSchiReportHwHang+0x3fd
ffffd000`295b2910 fffff801`83f77855     : 00000000`00000002 00000000`003fdea5 00000000`00000010 fffff801`00000000 : dxgmms2!VidSchiCheckHwProgress+0x13888
ffffd000`295b2950 fffff801`83f45c2d     : 00000000`00000000 ffffe000`badba000 ffffd000`295b2b00 00000000`00000000 : dxgmms2!VidSchiWaitForSchedulerEvents+0x265
ffffd000`295b2a00 fffff801`83f83363     : ffffe000`badba000 ffffd000`295b2bc8 ffffe000`c2143900 ffffe000`00000000 : dxgmms2!VidSchiScheduleCommandToRun+0x32d
ffffd000`295b2b90 fffff801`83f83340     : ffffe000`badba000 ffffe000`badba000 ffffe000`bad41040 ffffd000`2ba4cbc0 : dxgmms2!VidSchiRun_PriorityTable+0x1f
ffffd000`295b2bc0 fffff802`642f9698     : ffffe000`bad41040 ffffd000`295b2c90 ffffd000`2ba40180 fffff802`64366230 : dxgmms2!VidSchiWorkerThread+0x80
ffffd000`295b2c00 fffff802`64366306     : ffffd000`2ba40180 ffffe000`badbb800 ffffd000`2ba4cbc0 0000f0a1`0000ef28 : nt!PspSystemThreadStartup+0x58
ffffd000`295b2c60 00000000`00000000     : ffffd000`295b3000 ffffd000`295ad000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


SYMBOL_NAME:  atikmpag+cc9c

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  0x116_IMAGE_atikmpag.sys

OS_VERSION:  10.0.10240.16393

BUILDLAB_STR:  th1_st1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {e300aa8c-6915-3f37-7957-d2e4fc30a6fd}

Followup:     MachineOwner
---------
Kod:
2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)
The device driver is spinning in an infinite loop, most likely waiting for
hardware to become idle. This usually indicates problem with the hardware
itself or with the device driver programming the hardware incorrectly.
If the kernel debugger is connected and running when watchdog detects a
timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
and detailed message including BugCheck arguments will be printed to the
debugger. This way we can identify an offending thread, set breakpoints in it,
and hit go to return to the spinning code to debug it further. Because
KeBugCheckEx() is not called the .BugCheck directive will not return BugCheck
information in this case. The arguments are already printed out to the kernel
debugger. You can also retrieve them from a global variable via
"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
On MP machines it is possible to hit a timeout when the spinning thread is
interrupted by hardware interrupt and ISR or DPC routine is running at the time
of the BugCheck (this is because the timeout's work item can be delivered and
handled on the second CPU and the same time). If this is the case you will have
to look deeper at the offending thread's stack (e.g. using dds) to determine
spinning code which caused the timeout to occur.
Arguments:
Arg1: ffffe0018bbf1380, Pointer to a stuck thread object.  Do .thread then kb on it to find
    the hung location.
Arg2: 0000000000000000, Pointer to a DEFERRED_WATCHDOG object.
Arg3: 0000000000000000, Pointer to offending driver name.
Arg4: 0000000000000000, Number of times "intercepted" BugCheck 0xEA was hit (see notes).

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

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 6937

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 20172

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

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

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

    Key  : WER.OS.Branch
    Value: th1_st1

    Key  : WER.OS.Timestamp
    Value: 2015-07-17T17:19:00Z

    Key  : WER.OS.Version
    Value: 10.0.10240.16393


BUGCHECK_CODE:  ea

BUGCHECK_P1: ffffe0018bbf1380

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FAULTING_THREAD:  ffffe0018bbf1380

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
ffffd000`e05a2d98 fffff801`a592e15c     : 00000000`000000ea ffffe001`8bbf1380 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffd000`e05a2da0 fffff801`a592e21e     : ffffd000`e05a2e78 fffff801`a96282c0 ffffd000`e05a2e78 ffffd000`e05a2f40 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x24
ffffd000`e05a2e10 fffff801`a95d4703     : ffffe001`88e00000 ffffd000`e05a2f71 ffffd000`e05a2f40 fffff801`a96282ac : dxgkrnl!TdrTimedOperationDelay+0xbe
ffffd000`e05a2e50 ffffe001`88e00000     : ffffd000`e05a2f71 ffffd000`e05a2f40 fffff801`a96282ac 00000000`01312d00 : atikmdag+0x44703
ffffd000`e05a2e58 ffffd000`e05a2f71     : ffffd000`e05a2f40 fffff801`a96282ac 00000000`01312d00 00000000`00000028 : 0xffffe001`88e00000
ffffd000`e05a2e60 ffffd000`e05a2f40     : fffff801`a96282ac 00000000`01312d00 00000000`00000028 fffff801`a95d46d7 : 0xffffd000`e05a2f71
ffffd000`e05a2e68 fffff801`a96282ac     : 00000000`01312d00 00000000`00000028 fffff801`a95d46d7 00000000`00000101 : 0xffffd000`e05a2f40
ffffd000`e05a2e70 00000000`01312d00     : 00000000`00000028 fffff801`a95d46d7 00000000`00000101 00000000`00000080 : atikmdag+0x982ac
ffffd000`e05a2e78 00000000`00000028     : fffff801`a95d46d7 00000000`00000101 00000000`00000080 00000000`030bdaea : 0x1312d00
ffffd000`e05a2e80 fffff801`a95d46d7     : 00000000`00000101 00000000`00000080 00000000`030bdaea ffff2141`f6e01e49 : 0x28
ffffd000`e05a2e88 00000000`00000101     : 00000000`00000080 00000000`030bdaea ffff2141`f6e01e49 00000000`00000000 : atikmdag+0x446d7
ffffd000`e05a2e90 00000000`00000080     : 00000000`030bdaea ffff2141`f6e01e49 00000000`00000000 00000000`00000001 : 0x101
ffffd000`e05a2e98 00000000`030bdaea     : ffff2141`f6e01e49 00000000`00000000 00000000`00000001 ffffe001`88e00000 : 0x80
ffffd000`e05a2ea0 ffff2141`f6e01e49     : 00000000`00000000 00000000`00000001 ffffe001`88e00000 ffffd000`e05a2f60 : 0x30bdaea
ffffd000`e05a2ea8 00000000`00000000     : 00000000`00000001 ffffe001`88e00000 ffffd000`e05a2f60 fffff801`a95ce05e : 0xffff2141`f6e01e49


STACK_COMMAND:  .thread 0xffffe0018bbf1380 ; kb

SYMBOL_NAME:  dxgkrnl!TdrTimedOperationBugcheckOnTimeout+24

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

IMAGE_VERSION:  10.0.10240.16397

FAILURE_BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys

OS_VERSION:  10.0.10240.16393

BUILDLAB_STR:  th1_st1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {ea458ad2-d5ab-aa6c-7a11-54653c70dfb8}

Followup:     MachineOwner
---------
Dediğiniz gibi pci.sys görülmemiş. Salt ekran kartı sürücüsü sorunu.
 
bugun sabahta farklı bir hata aldım ve yine mavi ekran verdi acaba onu da size iletsem ? artık bu sorundan kafayı yemek üzereyim çünkü sürücüler vs birşeyler denedım ve asla eskisi gibi olmadı :(
 
Bugün sabahta farklı bir hata aldım ve yine mavi ekran verdi acaba onu da size iletsem? Artık bu sorundan kafayı yemek üzereyim çünkü sürücüler vs bir şeyler denedım ve asla eskisi gibi olmadı :(

Cezanız bitince paylaşın.
 
Cezanız bitince paylaşın.
bu minidump sonucuna göre birseyler yaparız umarım :/
 
Son düzenleme:

Bu minidump sonucuna göre bir şeyler yaparız umarım :/

Farklı bir şey yok dosyada aynısı diğerlerinin. Dediğim işlemleri yapmıştınız değil mi?
 
Hata 184 tarzı bı sorun çıkıyor kurulmuyor ama :/
peki sorunun donanımsal olma ihtimali ne sizce eğer donanımsal olma ihtimali varsa sizi de yormayayım daha fazla..
 

Geri
Yukarı