3 sayfa mesaj yazdık. Düşünmekle olmuyor minidumpları incelemiş olsa idin, düşünüyorum demezdin. Olayın ekran kartıyla bir alakası yok. RAM slotunda sorun olsaydı RAM'de 5093 hata çıkmazdı. Sistem boot etmezdi bile. Ben yönlendiriyorum zaten, benim dediklerimin aynısını söylediğini varsayalım ne olacak? Benim mesaj yazmamın ne anlamı kaldı? Ki zaten yanlış yönlendirmiş oldun. Mevzu bu.
Şahsen senin minidump dosyalarını tam olarak incelediğini düşünmüyorum. Ekran kartı ile bir alakası yok diyorsun ama en büyük boyutlu DMP dosyasının sebebi "nvlddmkm.sys" ve
[CODE title="nvlddmkm.sys"]7: 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: fffff805458fa320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp 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 ***
*** ***
*************************************************************************
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 9500
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 17603
Key : Analysis.Init.CPU.mSec
Value: 764
Key : Analysis.Init.Elapsed.mSec
Value: 3043
Key : Analysis.Memory.CommitPeak.Mb
Value: 74
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
FILE_IN_CAB: 020722-9531-01.dmp
BUGCHECK_CODE: 133
BUGCHECK_P1: 1
BUGCHECK_P2: 1e00
BUGCHECK_P3: fffff805458fa320
BUGCHECK_P4: 0
DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED
TRAP_FRAME: fffffb068388b4c0 -- (.trap 0xfffffb068388b4c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffa88b95b1a6c0 rbx=0000000000000000 rcx=ffffa88b95b19940
rdx=0000527aef1cafc8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8054d19590d rsp=fffffb068388b650 rbp=00000000fffe795e
r8=0000000000000000 r9=0000000000000000 r10=00000000454c764e
r11=fffffb068388b6d8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nvlddmkm+0x81590d:
fffff805`4d19590d 488bf1 mov rsi,rcx
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: LogonUI.exe
STACK_TEXT:
ffffe501`50ae2e18 fffff805`4501f77e : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff805`458fa320 : nt!KeBugCheckEx
ffffe501`50ae2e20 fffff805`44e16953 : 000000ac`277cded0 ffffe501`50ac9180 00000000`00000000 ffffe501`50ac9180 : nt!KeAccumulateTicks+0x2065ce
ffffe501`50ae2e80 fffff805`44e1643a : ffffa88b`8aeaeec0 fffffb06`8388b540 ffffa88b`8f58b100 00000000`00000000 : nt!KeClockInterruptNotify+0x453
ffffe501`50ae2f30 fffff805`44ede205 : ffffa88b`8aeaeec0 fffff805`44f525f7 00000000`00000000 00000000`00000000 : nt!HalpTimerClockIpiRoutine+0x1a
ffffe501`50ae2f60 fffff805`44ff8e5a : fffffb06`8388b540 ffffa88b`8aeaeec0 ffffa88b`92927b20 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffffe501`50ae2fb0 fffff805`44ff93c7 : ffffa88b`946c06c0 fffff805`44e8c7cf 00000000`00000002 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffffb06`8388b4c0 fffff805`4d19590d : 00000000`0000003c ffffa88b`946c06c0 00000000`00000000 00000000`00000002 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffffb06`8388b650 00000000`0000003c : ffffa88b`946c06c0 00000000`00000000 00000000`00000002 00000000`00000000 : nvlddmkm+0x81590d
fffffb06`8388b658 ffffa88b`946c06c0 : 00000000`00000000 00000000`00000002 00000000`00000000 ffffa88b`8f681000 : 0x3c
fffffb06`8388b660 00000000`00000000 : 00000000`00000002 00000000`00000000 ffffa88b`8f681000 fffffb06`8388b6d8 : 0xffffa88b`946c06c0
SYMBOL_NAME: nvlddmkm+81590d
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 81590d
FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm!unknown_function
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {f97493a5-ea2b-23ca-a808-8602773c2a86}
Followup: MachineOwner
---------[/CODE]
5 minidump dosyasının biri tam oluşmamış(neden diye düşünme). Memory_management ve hardware yazısını görünce direk RAM deyip geçmişsin. Ne diyeyim devam et hocam.
