Menu
Neler Yeni
Üye mesajlarında:
Filtreler

d.a sistem 2 mavi ekran

zerolite

zerolite

80+ Gold
Katılım
4 Nisan 2020
Mesajlar
7,972
Dahası  
Reaksiyon skoru
3,353
Yaş
25
İsim
Mertcan
İlgilendiği Kategoriler
Kripto
arkadaşlar bir video açtım ve birden mavi ekran verdi hata kodu

video tdr failure
 
FightForHonor

FightForHonor

80+ Platinum
Katılım
11 Ağustos 2020
Mesajlar
13,226
En İyi Cevap
33
mini dump dosyasını atsana
 
zerolite

zerolite

80+ Gold
Katılım
4 Nisan 2020
Mesajlar
7,972
Dahası  
Reaksiyon skoru
3,353
Yaş
25
İsim
Mertcan
İlgilendiği Kategoriler
Kripto
  • Konu Sahibi Konu Sahibi
  • #3
FightForHonor

FightForHonor

80+ Platinum
Katılım
11 Ağustos 2020
Mesajlar
13,226
En İyi Cevap
33
C:\Windows\minidump olması lazım
 
kandes22

kandes22

80+ Platinum
Katılım
25 Mart 2020
Mesajlar
18,106
En İyi Cevap
13
Video dediğine göre ekran kartıyla alakalı bir sorun olabilir.

Minidump Dosyalarını Paylaşın

Minidump dosyaları, bilgisayarınız mavi ekran verdiğinde belleğin ufak bir dökümünü barındıran dosyalardır. Bunları analiz ederek mavi ekran hatalarının nedenini öğrenebiliriz. Minidump dosyaları C:\Windows\Minidump klasöründe bulunur ve DMP uzantılıdır. Bu dosyaları sizden istediğimizde...
www.technopat.net www.technopat.net
 
zerolite

zerolite

80+ Gold
Katılım
4 Nisan 2020
Mesajlar
7,972
Dahası  
Reaksiyon skoru
3,353
Yaş
25
İsim
Mertcan
İlgilendiği Kategoriler
Kripto
  • Konu Sahibi Konu Sahibi
  • #6
EMİN Yıldız yazmış:
mini dump dosyasını atsana
Devamı için tıklayın...

Minidump.rar dosyasını indir - download

Minidump.rar dosyasını indir, download. Dosya.tc .Dosya Upload. Dosya Paylaş. Dosya Yükle
s7.dosya.tc s7.dosya.tc
Mesaj otomatik birleştirildi:

kandes22 yazmış:
Video dediğine göre ekran kartıyla alakalı bir sorun olabilir.

Minidump Dosyalarını Paylaşın

Minidump dosyaları, bilgisayarınız mavi ekran verdiğinde belleğin ufak bir dökümünü barındıran dosyalardır. Bunları analiz ederek mavi ekran hatalarının nedenini öğrenebiliriz. Minidump dosyaları C:\Windows\Minidump klasöründe bulunur ve DMP uzantılıdır. Bu dosyaları sizden istediğimizde...
www.technopat.net www.technopat.net
Devamı için tıklayın...
video açtığım gibi gitti
 
O

Orhunaltintas

80+
Katılım
25 Mart 2020
Mesajlar
28
Dahası  
Reaksiyon skoru
12
Yaş
34
İsim
Orhun ALTINTAŞ
Arkadaşlar bende dasistem 2 yi kullanıyorum 2 3 ay oluyor hic bir sorun ile karsılasmadım. Sürücülerinizin güncel oldugunu kontrol edin
 
kandes22

kandes22

80+ Platinum
Katılım
25 Mart 2020
Mesajlar
18,106
En İyi Cevap
13
Dosya TC'den kendi yüklediğim dosyayı bile indirmem :D

Google Drive'a falan yüklesene.
 
FightForHonor

FightForHonor

80+ Platinum
Katılım
11 Ağustos 2020
Mesajlar
13,226
En İyi Cevap
33
zerolite

zerolite

80+ Gold
Katılım
4 Nisan 2020
Mesajlar
7,972
Dahası  
Reaksiyon skoru
3,353
Yaş
25
İsim
Mertcan
İlgilendiği Kategoriler
Kripto
FightForHonor

FightForHonor

80+ Platinum
Katılım
11 Ağustos 2020
Mesajlar
13,226
En İyi Cevap
33
Hocam valla kusura bakmayın Windbg prewiew ile dosyayı analiz edemedim açmadı bir türlü sanırım 3 mb fazla geldi :D
 
kandes22

kandes22

80+ Platinum
Katılım
25 Mart 2020
Mesajlar
18,106
En İyi Cevap
13
zerolite yazmış:
yadi.sk

Minidump.rar

Görüntüle ve Yandex Disk'ten indir
yadi.sk yadi.sk
Devamı için tıklayın...

Sanırsam sorun ekran kartında. Hangi sürüm driver kullanıyorsunuz?

Aynı zamanda Memtest86 yapın derim.
Mesaj otomatik birleştirildi:

EMİN Yıldız yazmış:
Hocam valla kusura bakmayın Windbg prewiew ile dosyayı analiz edemedim açmadı bir türlü sanırım 3 mb fazla geldi :D
Devamı için tıklayın...

Bende açıldı. Kod şöyle:

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

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

Unable to load image \SystemRoot\System32\DriverStore\FileRepository\u0355311.inf_amd64_183b8d63847c90cf\B355199\atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 7186

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on BEYAZGULPC

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 29255

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

Key : Analysis.System
Value: CreateObject

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


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE: 116

BUGCHECK_P1: ffff990a5dced010

BUGCHECK_P2: fffff802353f0818

BUGCHECK_P3: ffffffffc0000001

BUGCHECK_P4: 3

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffff8283`cd9e29f8 fffff802`34ad129e : 00000000`00000116 ffff990a`5dced010 fffff802`353f0818 ffffffff`c0000001 : nt!KeBugCheckEx
ffff8283`cd9e2a00 fffff802`34a7961b : fffff802`353f0818 ffff990a`50f8d000 ffff990a`50f8d0f0 00000000`00000000 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
ffff8283`cd9e2a40 fffff802`34a7a3ee : ffff990a`00000101 00000000`00002000 ffff990a`50f8d000 00000000`01000000 : dxgkrnl!DXGADAPTER::prepareToReset+0x1a3
ffff8283`cd9e2a90 fffff802`34ad09c5 : 00000000`00000100 ffff990a`50f8da50 00000000`47a98530 00000000`00000300 : dxgkrnl!DXGADAPTER::Reset+0x28e
ffff8283`cd9e2b10 fffff802`34ad0b37 : fffff802`27d24440 00000000`00000000 00000000`00000000 00000000`00000300 : dxgkrnl!TdrResetFromTimeout+0x15
ffff8283`cd9e2b40 fffff802`27233f45 : ffff990a`5a0ad040 fffff802`34ad0b10 ffff990a`47a98530 00000000`00000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27
ffff8283`cd9e2b70 fffff802`27346745 : ffff990a`5a0ad040 00000000`00000080 ffff990a`47a7a040 00576575`00000001 : nt!ExpWorkerThread+0x105
ffff8283`cd9e2c10 fffff802`273e5598 : ffffae01`dc5e4180 ffff990a`5a0ad040 fffff802`273466f0 00726168`43656469 : nt!PspSystemThreadStartup+0x55
ffff8283`cd9e2c60 00000000`00000000 : ffff8283`cd9e3000 ffff8283`cd9dd000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: atikmpag+10818

MODULE_NAME: atikmpag

IMAGE_NAME: atikmpag.sys

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x116_IMAGE_atikmpag.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

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

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

3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

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

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 4655

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on BEYAZGULPC

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 10159

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

Key : Analysis.System
Value: CreateObject

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


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE: 116

BUGCHECK_P1: ffff990a5dced010

BUGCHECK_P2: fffff802353f0818

BUGCHECK_P3: ffffffffc0000001

BUGCHECK_P4: 3

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffff8283`cd9e29f8 fffff802`34ad129e : 00000000`00000116 ffff990a`5dced010 fffff802`353f0818 ffffffff`c0000001 : nt!KeBugCheckEx
ffff8283`cd9e2a00 fffff802`34a7961b : fffff802`353f0818 ffff990a`50f8d000 ffff990a`50f8d0f0 00000000`00000000 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
ffff8283`cd9e2a40 fffff802`34a7a3ee : ffff990a`00000101 00000000`00002000 ffff990a`50f8d000 00000000`01000000 : dxgkrnl!DXGADAPTER::prepareToReset+0x1a3
ffff8283`cd9e2a90 fffff802`34ad09c5 : 00000000`00000100 ffff990a`50f8da50 00000000`47a98530 00000000`00000300 : dxgkrnl!DXGADAPTER::Reset+0x28e
ffff8283`cd9e2b10 fffff802`34ad0b37 : fffff802`27d24440 00000000`00000000 00000000`00000000 00000000`00000300 : dxgkrnl!TdrResetFromTimeout+0x15
ffff8283`cd9e2b40 fffff802`27233f45 : ffff990a`5a0ad040 fffff802`34ad0b10 ffff990a`47a98530 00000000`00000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27
ffff8283`cd9e2b70 fffff802`27346745 : ffff990a`5a0ad040 00000000`00000080 ffff990a`47a7a040 00576575`00000001 : nt!ExpWorkerThread+0x105
ffff8283`cd9e2c10 fffff802`273e5598 : ffffae01`dc5e4180 ffff990a`5a0ad040 fffff802`273466f0 00726168`43656469 : nt!PspSystemThreadStartup+0x55
ffff8283`cd9e2c60 00000000`00000000 : ffff8283`cd9e3000 ffff8283`cd9dd000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: atikmpag+10818

MODULE_NAME: atikmpag

IMAGE_NAME: atikmpag.sys

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x116_IMAGE_atikmpag.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

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

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

3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

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

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 5483

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on BEYAZGULPC

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 11536

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

Key : Analysis.System
Value: CreateObject

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


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE: 116

BUGCHECK_P1: ffff990a5dced010

BUGCHECK_P2: fffff802353f0818

BUGCHECK_P3: ffffffffc0000001

BUGCHECK_P4: 3

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffff8283`cd9e29f8 fffff802`34ad129e : 00000000`00000116 ffff990a`5dced010 fffff802`353f0818 ffffffff`c0000001 : nt!KeBugCheckEx
ffff8283`cd9e2a00 fffff802`34a7961b : fffff802`353f0818 ffff990a`50f8d000 ffff990a`50f8d0f0 00000000`00000000 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
ffff8283`cd9e2a40 fffff802`34a7a3ee : ffff990a`00000101 00000000`00002000 ffff990a`50f8d000 00000000`01000000 : dxgkrnl!DXGADAPTER::prepareToReset+0x1a3
ffff8283`cd9e2a90 fffff802`34ad09c5 : 00000000`00000100 ffff990a`50f8da50 00000000`47a98530 00000000`00000300 : dxgkrnl!DXGADAPTER::Reset+0x28e
ffff8283`cd9e2b10 fffff802`34ad0b37 : fffff802`27d24440 00000000`00000000 00000000`00000000 00000000`00000300 : dxgkrnl!TdrResetFromTimeout+0x15
ffff8283`cd9e2b40 fffff802`27233f45 : ffff990a`5a0ad040 fffff802`34ad0b10 ffff990a`47a98530 00000000`00000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27
ffff8283`cd9e2b70 fffff802`27346745 : ffff990a`5a0ad040 00000000`00000080 ffff990a`47a7a040 00576575`00000001 : nt!ExpWorkerThread+0x105
ffff8283`cd9e2c10 fffff802`273e5598 : ffffae01`dc5e4180 ffff990a`5a0ad040 fffff802`273466f0 00726168`43656469 : nt!PspSystemThreadStartup+0x55
ffff8283`cd9e2c60 00000000`00000000 : ffff8283`cd9e3000 ffff8283`cd9dd000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: atikmpag+10818

MODULE_NAME: atikmpag

IMAGE_NAME: atikmpag.sys

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x116_IMAGE_atikmpag.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

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

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

3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

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

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 5562

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on BEYAZGULPC

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 11705

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

Key : Analysis.System
Value: CreateObject

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


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE: 116

BUGCHECK_P1: ffff990a5dced010

BUGCHECK_P2: fffff802353f0818

BUGCHECK_P3: ffffffffc0000001

BUGCHECK_P4: 3

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffff8283`cd9e29f8 fffff802`34ad129e : 00000000`00000116 ffff990a`5dced010 fffff802`353f0818 ffffffff`c0000001 : nt!KeBugCheckEx
ffff8283`cd9e2a00 fffff802`34a7961b : fffff802`353f0818 ffff990a`50f8d000 ffff990a`50f8d0f0 00000000`00000000 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
ffff8283`cd9e2a40 fffff802`34a7a3ee : ffff990a`00000101 00000000`00002000 ffff990a`50f8d000 00000000`01000000 : dxgkrnl!DXGADAPTER::prepareToReset+0x1a3
ffff8283`cd9e2a90 fffff802`34ad09c5 : 00000000`00000100 ffff990a`50f8da50 00000000`47a98530 00000000`00000300 : dxgkrnl!DXGADAPTER::Reset+0x28e
ffff8283`cd9e2b10 fffff802`34ad0b37 : fffff802`27d24440 00000000`00000000 00000000`00000000 00000000`00000300 : dxgkrnl!TdrResetFromTimeout+0x15
ffff8283`cd9e2b40 fffff802`27233f45 : ffff990a`5a0ad040 fffff802`34ad0b10 ffff990a`47a98530 00000000`00000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27
ffff8283`cd9e2b70 fffff802`27346745 : ffff990a`5a0ad040 00000000`00000080 ffff990a`47a7a040 00576575`00000001 : nt!ExpWorkerThread+0x105
ffff8283`cd9e2c10 fffff802`273e5598 : ffffae01`dc5e4180 ffff990a`5a0ad040 fffff802`273466f0 00726168`43656469 : nt!PspSystemThreadStartup+0x55
ffff8283`cd9e2c60 00000000`00000000 : ffff8283`cd9e3000 ffff8283`cd9dd000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: atikmpag+10818

MODULE_NAME: atikmpag

IMAGE_NAME: atikmpag.sys

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x116_IMAGE_atikmpag.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

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

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

3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

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

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 5593

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on BEYAZGULPC

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 11296

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

Key : Analysis.System
Value: CreateObject

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


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE: 116

BUGCHECK_P1: ffff990a5dced010

BUGCHECK_P2: fffff802353f0818

BUGCHECK_P3: ffffffffc0000001

BUGCHECK_P4: 3

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffff8283`cd9e29f8 fffff802`34ad129e : 00000000`00000116 ffff990a`5dced010 fffff802`353f0818 ffffffff`c0000001 : nt!KeBugCheckEx
ffff8283`cd9e2a00 fffff802`34a7961b : fffff802`353f0818 ffff990a`50f8d000 ffff990a`50f8d0f0 00000000`00000000 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
ffff8283`cd9e2a40 fffff802`34a7a3ee : ffff990a`00000101 00000000`00002000 ffff990a`50f8d000 00000000`01000000 : dxgkrnl!DXGADAPTER::prepareToReset+0x1a3
ffff8283`cd9e2a90 fffff802`34ad09c5 : 00000000`00000100 ffff990a`50f8da50 00000000`47a98530 00000000`00000300 : dxgkrnl!DXGADAPTER::Reset+0x28e
ffff8283`cd9e2b10 fffff802`34ad0b37 : fffff802`27d24440 00000000`00000000 00000000`00000000 00000000`00000300 : dxgkrnl!TdrResetFromTimeout+0x15
ffff8283`cd9e2b40 fffff802`27233f45 : ffff990a`5a0ad040 fffff802`34ad0b10 ffff990a`47a98530 00000000`00000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27
ffff8283`cd9e2b70 fffff802`27346745 : ffff990a`5a0ad040 00000000`00000080 ffff990a`47a7a040 00576575`00000001 : nt!ExpWorkerThread+0x105
ffff8283`cd9e2c10 fffff802`273e5598 : ffffae01`dc5e4180 ffff990a`5a0ad040 fffff802`273466f0 00726168`43656469 : nt!PspSystemThreadStartup+0x55
ffff8283`cd9e2c60 00000000`00000000 : ffff8283`cd9e3000 ffff8283`cd9dd000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: atikmpag+10818

MODULE_NAME: atikmpag

IMAGE_NAME: atikmpag.sys

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x116_IMAGE_atikmpag.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

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

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

FightForHonor

80+ Platinum
Katılım
11 Ağustos 2020
Mesajlar
13,226
En İyi Cevap
33
kandes22 yazmış:
Sanırsam sorun ekran kartında. Hangi sürüm driver kullanıyorsunuz?
Devamı için tıklayın...
Banada öyle geldi bence driver ini silip güncel WHQL driver i kurun ve birde memtest 86 veya memtest 64 ile belleklerinize test yapın
 
Buraya cevap vermek için giriş yapmalı veya kayıt olmalısınız.

BENZER KONULAR

P
Acil yardım lazım mavi ekran
Cevaplar
0
Hit
98
pandatr8
P
T
Bilgisayar mavi ekran hatası veriyor
Cevaplar
1
Hit
216
Einstein
Einstein
MooDT
Mavi Erkan sonrasında bilgisayar açılmıyor
Cevaplar
2
Hit
114
MooDT
MooDT
L
Windows 10 Mavi Ekran Hatası
Cevaplar
1
Hit
157
lordist
L
CHADE GİGAD
Mavi Ekran Hatasın'dan Sonra ne Yapmalıyım
Cevaplar
2
Hit
187
CHADE GİGAD
CHADE GİGAD
Yeni mesajlar Yeni Konu Aç      

SON KONULAR

En Son İçerikler

Çevrim içi üyeler

... ve 363 daha.
Toplam: 2,628 (üye: 388, ziyaretçi: 2,240)

Forum istatistikleri

Konular
1,063,605
Mesajlar
9,560,755
Üyeler
168,960
Son üye
Bartzabel
Top Bottom