3: 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: ffff838d74451830
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
DBGHELP: Timeout to store: https://msdl.microsoft.com/download/symbols
DBGHELP: Timeout to store: https://msdl.microsoft.com/download/symbols
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 3515
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 117703
Key : Analysis.Init.CPU.mSec
Value: 499
Key : Analysis.Init.Elapsed.mSec
Value: 10776
Key : Analysis.Memory.CommitPeak.Mb
Value: 81
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
BUGCHECK_CODE: 10e
BUGCHECK_P1: 33
BUGCHECK_P2: ffff838d74451830
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:
ffff960b`8becef98 fffff804`63e93ad0 : 00000000`0000010e 00000000`00000033 ffff838d`74451830 00000000`00000000 : nt!KeBugCheckEx
ffff960b`8becefa0 fffff804`6777d30d : 00000000`00000000 ffff838d`74451930 ffffda88`b6f03000 00000000`00000001 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffff960b`8becefe0 fffff804`676f0eca : ffff838d`74451830 00000000`00000000 ffff838d`8b67a1f0 00000000`00000001 : dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::~VIDMM_PROCESS_ADAPTER_INFO+0x33179
ffff960b`8becf020 fffff804`6774a14d : ffff838d`74451830 00000000`00000000 ffff838d`8b67a1f0 ffffda88`b6dc2010 : dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::`scalar deleting destructor'+0xe
ffff960b`8becf050 fffff804`6774a81d : 00000000`00000000 ffff838d`8b67a1f0 ffff838d`74451830 ffffda88`bd43f080 : dxgmms2!VIDMM_PROCESS::DestroyAdapterInfo+0xe5
ffff960b`8becf080 fffff804`676f0eae : ffff838d`8d2ae1f0 ffff960b`8becf239 ffffda88`b6dc2010 01000000`00100000 : dxgmms2!VIDMM_PROCESS::CloseAdapter+0xb9
ffff960b`8becf140 fffff804`63c4674a : ffff960b`8becf1f8 00000000`00000004 00000000`80008540 00000000`00000000 : dxgmms2!VidMmCloseAdapter+0x1e
ffff960b`8becf170 fffff804`63bf3c6f : ffffda88`b1468000 00000000`00000000 ffffda88`b7039310 fffff804`4b408633 : dxgkrnl!DXGPROCESS_ADAPTER_INFO::CloseVidMmAdapter+0x2e
ffff960b`8becf1a0 fffff804`63bc4c9d : ffff838d`8d2ae1f0 ffff838d`00000002 ffff838d`8d2ae1f0 ffffda88`b6dc2010 : dxgkrnl!DXGPROCESS::DestroyAdapterInfo+0x143
ffff960b`8becf2a0 fffff804`63bc30f1 : ffffda88`b6dba000 fffff804`00000001 ffffda88`b6dba000 ffff838d`95724360 : dxgkrnl!DXGPROCESS::CloseAdapter+0xf9
ffff960b`8becf330 fffff804`63bf4785 : ffffda88`ba6a5e00 ffff960b`8becf480 00000000`000002f0 ffff838d`95724270 : dxgkrnl!DXGADAPTER::DestroyHandle+0x11d
ffff960b`8becf380 fffff804`63bf5709 : ffff838d`95724270 00000000`00040282 ffff838d`95724270 ffff960b`8becf788 : dxgkrnl!DXGPROCESS::Destroy+0x341
ffff960b`8becf5f0 fffff804`63ae67b1 : 00000000`00000000 ffffda88`b5afdc50 00000000`00000000 00000000`00000000 : dxgkrnl!DXGPROCESS::DestroyDxgProcess+0x105
ffff960b`8becf740 fffff804`4b802a4f : 00000000`00000000 ffffda88`aeddcf80 ffffda88`bf184080 fffff804`01046000 : dxgkrnl!DxgkProcessNotify+0x1a1
ffff960b`8becf790 fffff804`4b81d664 : ffffda88`bf184000 ffffda88`bf184080 00000000`00000000 00000000`00000000 : nt!PspCallProcessNotifyRoutines+0x213
ffff960b`8becf860 fffff804`4b8b0a72 : ffffda88`bd43f4b8 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PspExitProcess+0x70
ffff960b`8becf890 fffff804`4b8b401e : ffffda88`d00002fe 00000000`00000001 00000000`00000000 0000005c`7a775000 : nt!PspExitThread+0x5b2
ffff960b`8becf990 fffff804`4b608bb5 : ffffda88`bf184080 ffffda88`bd43f080 ffff960b`8becfa80 ffffda88`bf184080 : nt!NtTerminateProcess+0xde
ffff960b`8becfa00 00007ffd`ff06d2f4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
0000005c`7a56f718 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`ff06d2f4
SYMBOL_NAME: dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::~VIDMM_PROCESS_ADAPTER_INFO+33179
MODULE_NAME: dxgmms2
IMAGE_NAME: dxgmms2.sys
IMAGE_VERSION: 10.0.19041.1288
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 33179
FAILURE_BUCKET_ID: 0x10e_33_dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::_VIDMM_PROCESS_ADAPTER_INFO
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {590e82e4-fa32-3e14-0943-e6b01c6637c4}
Followup: MachineOwner
Hocam BIOSTAR BIOS'unu bilmiyorum maalesef. Fakat kurcalayarak bulabilirsiniz kolayca.Ohh hocam bende sizi arıyordum
Ekran kartı driverını güncelledim, Oc/Uv yok.
Bios sıfırlamayı nerden ve nasıl yapayım?
www.technopat.net
Şuan bi tır kodluyorum o bitsin deneyeceğim hocam teşekkürler.Hocam BIOSTAR BIOS'unu bilmiyorum maalesef. Fakat kurcalayarak bulabilirsiniz kolayca.
Ayrıca bunu uygularmısın?
DISM Aracıyla Windows Onarma Rehberi
Windows 10'da karÅılaÅtıÄınız sorunları SFC komutu ile çözemiyorsanız, DISM aracını kullanarak Windows imajını onarıp, SFC'nin iÅini yapmasını
Uyguladım hocam.Hocam BIOSTAR BIOS'unu bilmiyorum maalesef. Fakat kurcalayarak bulabilirsiniz kolayca.
Ayrıca bunu uygularmısın?
DISM Aracıyla Windows Onarma Rehberi
Windows 10'da karÅılaÅtıÄınız sorunları SFC komutu ile çözemiyorsanız, DISM aracını kullanarak Windows imajını onarıp, SFC'nin iÅini yapmasını
Tekrar mavi ekran verirse yazarsınız.
Ileride lazim olur
Hocam ekran kartı drierıda kaynaklı olabilir başka bir şeyde. Dediklerimi uyguladıktan sonra tekrar verirse başka bir çözüme bakarız.
bu arada bende ets 2 de takılırken pc kendini resetliyor bi anda
