R5 1600 AF sistemde mavi ekran hatası

İşletim sistemi
Windows 10

DOGSHIVERING

Hectopat
Katılım
13 Ocak 2021
Mesajlar
404
Arkadaşlar bugün 16:35 gibi minidump dosyalarına girdim. Bilgisiyarı açalı 2-3dk olmuştu ve hiçbir sorun yoktu. Girdiğim zaman yeni bir dosya açılmıştı aynı günde 16:32 diye ama zaten o sıra ben PC'deydim ve hiçbir şey yoktu. Bu dosya nasıl oldu inceleyebilir misiniz?

Sistem:
1650.
Ryzen 5 1600 AF.
16 GB RAM.

Minidump dosyası: minidump
 
DDU ile ekran kartı sürücüsünü kaldırıp, güncel sürümü kurar mısınız?
 
DDU ile ekran kartı sürücüsünü kaldırıp, güncel sürümü kurar mısınız?

Minidump'da ekran kartı sürücüsü ile ilgili bir problem mi çıktı? Ayrıca bir sorun gözükmüyor az önce GeForce NOW'dan yeni sürümü kurdum hiçbir sorun çıkmadı.
 
Minidump'da ekran kartı sürücüsü ile ilgili bir problem mi çıktı?
Ben bunu çıkardım, umarım sizi de yanlış yönlendirmemişimdir ama yanlış yönlendirdiğimi düşünmüyorum.
Ayrıca bir sorun gözükmüyor az önce GeForce NOW'dan yeni sürümü kurdum hiçbir sorun çıkmadı.
Denediyseniz yeni bir öneride bulunacağım. Aşağıdaki rehberi uygular mısınız?
 
Sorunun sebebi ekran kartı, DDU ile sürücüsünü silip tekrar yükleyin.
[CODE title="Dump dosyasının içeriği:"]4: kd> !analyze -v
*******************************************************************************
* *
* 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: 0000000000000033, The subtype of the BugCheck:
Arg2: ffffb58816505950
Arg3: 0000000000000000
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2436

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 9680

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

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

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


DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_CODE: 10e

BUGCHECK_P1: 33

BUGCHECK_P2: ffffb58816505950

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: dwm.exe

STACK_TEXT:
ffffeb00`ca7fc098 fffff805`44c43ad0 : 00000000`0000010e 00000000`00000033 ffffb588`16505950 00000000`00000000 : nt!KeBugCheckEx
ffffeb00`ca7fc0a0 fffff805`4514d30d : 00000000`00000000 ffffb588`16505a50 ffff9d88`65736000 00000000`00000001 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffffeb00`ca7fc0e0 fffff805`450c0eca : ffffb588`16505950 00000000`00000000 ffffb588`6cf068d0 00000000`00000001 : dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::~VIDMM_PROCESS_ADAPTER_INFO+0x33179
ffffeb00`ca7fc120 fffff805`4511a14d : ffffb588`16505950 00000000`00000000 ffffb588`6cf068d0 ffff9d88`639e36e0 : dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::`scalar deleting destructor'+0xe
ffffeb00`ca7fc150 fffff805`4511a81d : 00000000`00000000 ffffb588`6cf068d0 ffffb588`16505950 ffff9d88`63f66080 : dxgmms2!VIDMM_PROCESS::DestroyAdapterInfo+0xe5
ffffeb00`ca7fc180 fffff805`450c0eae : ffffb588`783ab650 ffffeb00`ca7fc339 ffff9d88`639e36e0 01000000`00100000 : dxgmms2!VIDMM_PROCESS::CloseAdapter+0xb9
ffffeb00`ca7fc240 fffff805`449f6749 : 00000000`00000030 00000000`00000799 ffffb588`1ebb7ef8 00000000`00000000 : dxgmms2!VidMmCloseAdapter+0x1e
ffffeb00`ca7fc270 fffff805`449a3c6f : ffff9d88`59e4a000 00000000`00000000 ffff9d88`63251090 fffff805`33808633 : dxgkrnl!DXGPROCESS_ADAPTER_INFO::CloseVidMmAdapter+0x2d
ffffeb00`ca7fc2a0 fffff805`44974c9d : ffffb588`783ab650 ffffb588`00000002 ffffb588`783ab650 ffff9d88`639e36e0 : dxgkrnl!DXGPROCESS::DestroyAdapterInfo+0x143
ffffeb00`ca7fc3a0 fffff805`449730f1 : ffff9d88`639e1000 fffff805`00000001 ffff9d88`639e1000 fffff805`00000001 : dxgkrnl!DXGPROCESS::CloseAdapter+0xf9
ffffeb00`ca7fc430 fffff805`449a4785 : ffffb588`1ebb7f10 ffffeb00`ca7fc580 00000000`0000028c ffffb588`1ebb7de0 : dxgkrnl!DXGADAPTER::DestroyHandle+0x11d
ffffeb00`ca7fc480 fffff805`449a5709 : ffffb588`1ebb7de0 00000000`00006144 ffffb588`1ebb7de0 ffffeb00`ca7fc888 : dxgkrnl!DXGPROCESS::Destroy+0x341
ffffeb00`ca7fc6f0 fffff805`448967b1 : 00000000`00000000 ffff9d88`67576e20 00000000`00000000 00000000`00000008 : dxgkrnl!DXGPROCESS::DestroyDxgProcess+0x105
ffffeb00`ca7fc840 fffff805`33c0246f : 00000000`00000000 ffff9d88`597bec10 ffff9d88`60f56080 fffff805`01046000 : dxgkrnl!DxgkProcessNotify+0x1a1
ffffeb00`ca7fc890 fffff805`33c1d0a4 : ffff9d88`60f56000 ffff9d88`60f56080 00000000`00000000 00000000`00000000 : nt!PspCallProcessNotifyRoutines+0x213
ffffeb00`ca7fc960 fffff805`33cb0432 : ffff9d88`63f664b8 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PspExitProcess+0x70
ffffeb00`ca7fc990 fffff805`33cb39de : ffff9d88`d00002fe 00000000`00000001 00000000`00000000 00000032`7d27e000 : nt!PspExitThread+0x5b2
ffffeb00`ca7fca90 fffff805`33a08bb8 : ffff9d88`60f56080 ffff9d88`63f66080 ffffeb00`ca7fcb80 ffff9d88`60f56080 : nt!NtTerminateProcess+0xde
ffffeb00`ca7fcb00 00007ffd`adc4d2f4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000032`7d17f878 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`adc4d2f4


SYMBOL_NAME: dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::~VIDMM_PROCESS_ADAPTER_INFO+33179

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

IMAGE_VERSION: 10.0.19041.1261

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 33179

FAILURE_BUCKET_ID: 0x10e_33_dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::_VIDMM_PROCESS_ADAPTER_INFO

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {590e82e4-fa32-3e14-0943-e6b01c6637c4}

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

[/CODE]
 
Sorunun sebebi ekran kartı, DDU ile sürücüsünü silip tekrar yükleyin.
[CODE title="Dump dosyasının içeriği:"]4: kd> !analyze -v
*******************************************************************************
* *
* 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: 0000000000000033, The subtype of the BugCheck:
Arg2: ffffb58816505950.
Arg3: 0000000000000000.
Arg4: 0000000000000000.

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2436.

Key : Analysis.DebugAnalysisManager
Value: Create.

Key : Analysis.Elapsed.mSec
Value: 9680.

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

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

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

DUMP_FILE_ATTRIBUTES: 0x8.
Kernel Generated Triage Dump.

BUGCHECK_CODE: 10e.

BUGCHECK_P1: 33.

BUGCHECK_P2: ffffb58816505950.

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: dwm.exe

STACK_TEXT:
ffffeb00`ca7fc098 fffff805`44c43ad0 : 00000000`0000010e 00000000`00000033 ffffb588`16505950 00000000`00000000 : nt!KeBugCheckEx
ffffeb00`ca7fc0a0 fffff805`4514d30d : 00000000`00000000 ffffb588`16505a50 ffff9d88`65736000 00000000`00000001 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffffeb00`ca7fc0e0 fffff805`450c0eca : ffffb588`16505950 00000000`00000000 ffffb588`6cf068d0 00000000`00000001 : dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::~VIDMM_PROCESS_ADAPTER_INFO+0x33179
ffffeb00`ca7fc120 fffff805`4511a14d : ffffb588`16505950 00000000`00000000 ffffb588`6cf068d0 ffff9d88`639e36e0 : dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::`scalar deleting destructor'+0xe
ffffeb00`ca7fc150 fffff805`4511a81d : 00000000`00000000 ffffb588`6cf068d0 ffffb588`16505950 ffff9d88`63f66080 : dxgmms2!VIDMM_PROCESS::DestroyAdapterInfo+0xe5
ffffeb00`ca7fc180 fffff805`450c0eae : ffffb588`783ab650 ffffeb00`ca7fc339 ffff9d88`639e36e0 01000000`00100000 : dxgmms2!VIDMM_PROCESS::CloseAdapter+0xb9
ffffeb00`ca7fc240 fffff805`449f6749 : 00000000`00000030 00000000`00000799 ffffb588`1ebb7ef8 00000000`00000000 : dxgmms2!VidMmCloseAdapter+0x1e
ffffeb00`ca7fc270 fffff805`449a3c6f : ffff9d88`59e4a000 00000000`00000000 ffff9d88`63251090 fffff805`33808633 : dxgkrnl!DXGPROCESS_ADAPTER_INFO::CloseVidMmAdapter+0x2d
ffffeb00`ca7fc2a0 fffff805`44974c9d : ffffb588`783ab650 ffffb588`00000002 ffffb588`783ab650 ffff9d88`639e36e0 : dxgkrnl!DXGPROCESS::DestroyAdapterInfo+0x143
ffffeb00`ca7fc3a0 fffff805`449730f1 : ffff9d88`639e1000 fffff805`00000001 ffff9d88`639e1000 fffff805`00000001 : dxgkrnl!DXGPROCESS::CloseAdapter+0xf9
ffffeb00`ca7fc430 fffff805`449a4785 : ffffb588`1ebb7f10 ffffeb00`ca7fc580 00000000`0000028c ffffb588`1ebb7de0 : dxgkrnl!DXGADAPTER::DestroyHandle+0x11d
ffffeb00`ca7fc480 fffff805`449a5709 : ffffb588`1ebb7de0 00000000`00006144 ffffb588`1ebb7de0 ffffeb00`ca7fc888 : dxgkrnl!DXGPROCESS::Destroy+0x341
ffffeb00`ca7fc6f0 fffff805`448967b1 : 00000000`00000000 ffff9d88`67576e20 00000000`00000000 00000000`00000008 : dxgkrnl!DXGPROCESS::DestroyDxgProcess+0x105
ffffeb00`ca7fc840 fffff805`33c0246f : 00000000`00000000 ffff9d88`597bec10 ffff9d88`60f56080 fffff805`01046000 : dxgkrnl!DxgkProcessNotify+0x1a1
ffffeb00`ca7fc890 fffff805`33c1d0a4 : ffff9d88`60f56000 ffff9d88`60f56080 00000000`00000000 00000000`00000000 : nt!PspCallProcessNotifyRoutines+0x213
ffffeb00`ca7fc960 fffff805`33cb0432 : ffff9d88`63f664b8 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PspExitProcess+0x70
ffffeb00`ca7fc990 fffff805`33cb39de : ffff9d88`d00002fe 00000000`00000001 00000000`00000000 00000032`7d27e000 : nt!PspExitThread+0x5b2
ffffeb00`ca7fca90 fffff805`33a08bb8 : ffff9d88`60f56080 ffff9d88`63f66080 ffffeb00`ca7fcb80 ffff9d88`60f56080 : nt!NtTerminateProcess+0xde
ffffeb00`ca7fcb00 00007ffd`adc4d2f4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000032`7d17f878 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`adc4d2f4

SYMBOL_NAME: dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::~VIDMM_PROCESS_ADAPTER_INFO+33179

MODULE_NAME: dxgmms2.

IMAGE_NAME: dxgmms2.sys

IMAGE_VERSION: 10.0.19041.1261

STACK_COMMAND: .thread ; .cxr ; kb.

BUCKET_ID_FUNC_OFFSET: 33179.

FAILURE_BUCKET_ID: 0x10e_33_dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::_VIDMM_PROCESS_ADAPTER_INFO

OSPLATFORM_TYPE: x64.

OSNAME: Windows 10.

FAILURE_ID_HASH: {590e82e4-fa32-3e14-0943-e6b01c6637c4}

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

[/CODE]

Teşekkürler peki bu mavi ekran nasıl kendi kendiliğine oldu? Çünkü ben bilgisayar başındayken olmuş ve o sıra bilgisiyarda hiçbir sorun yoktu. Mavi ekran ekranı gelmedi.
 
Uyarı! Bu konu 5 yıl önce açıldı.
Muhtemelen daha fazla tartışma gerekli değildir ki bu durumda yeni bir konu başlatmayı öneririz. Eğer yine de cevabınızın gerekli olduğunu düşünüyorsanız buna rağmen cevap verebilirsiniz.

Bu konuyu görüntüleyen kullanıcılar

Technopat Haberler

Yeni konular

Geri
Yukarı