Dominic Decoco
Megapat
- Katılım
- 18 Eylül 2017
- Mesajlar
- 127
Minidump dosyalarını paylaşın.
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
sfc /scannow
Probably caused by : hardware_ram ( PAGE_NOT_ZERO )
Followup: MachineOwner
---------
FAULTING_MODULE: fffff8016e495000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAULTING_IP:
nvlddmkm+b4ca3c
fffff80f`4cc5ca3c 48ff253da6e1ff jmp qword ptr [nvlddmkm+0x967080 (fffff80f`4ca77080)]
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
CURRENT_IRQL: 0
BAD_PAGES_DETECTED: 10cb4
STACK_TEXT:
STACK_COMMAND: kb
SYMBOL_NAME: PAGE_NOT_ZERO
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware_ram
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
*** Memory manager detected 68788 instance(s) of page corruption, target is likely to have memory corruption.
Ekran kartı sürücünü DDU ile kaldır ve tekrar güncelini kur. DirectX güncelle. Bunun haricinde bellekler de sorunlu gibi gözüküyor MemTest ile bellekleri de test edin. Bu işte uzman hocalarımızı da etiketleyelim eksiğimiz varsa onlar tamamlar. @claus @Murat5038
DDU ile AMD ve NVIDIA Sürücü Kaldırma Rehberi
https://support.microsoft.com/tr-tr/help/179113/how-to-install-the-latest-version-of-directx
Memtest86 USB'den Çalışan RAM Test Programı
Komut istemini yönetici olarak çalıştırıp aşağıdakini girin.
Kod:sfc /scannow
Kod:Probably caused by : hardware_ram ( PAGE_NOT_ZERO ) Followup: MachineOwner ---------
Kod:FAULTING_MODULE: fffff8016e495000 nt DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAULTING_IP: nvlddmkm+b4ca3c fffff80f`4cc5ca3c 48ff253da6e1ff jmp qword ptr [nvlddmkm+0x967080 (fffff80f`4ca77080)] DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT CUSTOMER_CRASH_COUNT: 1 BUGCHECK_STR: 0x116 CURRENT_IRQL: 0 BAD_PAGES_DETECTED: 10cb4 STACK_TEXT: STACK_COMMAND: kb SYMBOL_NAME: PAGE_NOT_ZERO FOLLOWUP_NAME: MachineOwner MODULE_NAME: hardware IMAGE_NAME: hardware_ram BUCKET_ID: WRONG_SYMBOLS Followup: MachineOwner --------- *** Memory manager detected 68788 instance(s) of page corruption, target is likely to have memory corruption.
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffa60cddefc4a0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff80f4cc5ca3c, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.
Debugging Details:
------------------
Unable to load image nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 1
Key : Analysis.Elapsed.Sec
Value: 3
Key : Analysis.Memory.CommitPeak.Mb
Value: 73
PROCESSES_ANALYSIS: 1
SERVICE_ANALYSIS: 1
STACKHASH_ANALYSIS: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10.0.17134.765 (WinBuild.160101.0800)
SYSTEM_MANUFACTURER: LENOVO
SYSTEM_PRODUCT_NAME: 20354
SYSTEM_SKU: LENOVO_MT_20354_BU_idea_FM_Lenovo Z50-70
SYSTEM_VERSION: Lenovo Z50-70
BIOS_VENDOR: LENOVO
BIOS_VERSION: 9BCN29WW
BIOS_DATE: 10/20/2014
BASEBOARD_MANUFACTURER: LENOVO
BASEBOARD_PRODUCT: Lancer 5A5
BASEBOARD_VERSION: 31900059WIN
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
DUMP_TYPE: 2
BUGCHECK_P1: ffffa60cddefc4a0
BUGCHECK_P2: fffff80f4cc5ca3c
BUGCHECK_P3: ffffffffc000009a
BUGCHECK_P4: 4
FAULTING_IP:
nvlddmkm+b4ca3c
fffff80f`4cc5ca3c 48ff253da6e1ff jmp qword ptr [nvlddmkm+0x967080 (fffff80f`4ca77080)]
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
CPU_COUNT: 4
CPU_MHZ: 95a
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 45
CPU_STEPPING: 1
CPU_MICROCODE: 6,45,1,0 (F,M,S,R) SIG: 23'00000000 (cache) 23'00000000 (init)
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXPNP: 1 (!blackboxpnp)
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
PROCESS_NAME: System
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: DESKTOP-HH6FM2D
ANALYSIS_SESSION_TIME: 07-07-2019 15:49:11.0823
ANALYSIS_VERSION: 10.0.18914.1001 amd64fre
STACK_TEXT:
fffff300`a6637a28 fffff80f`4772acf8 : 00000000`00000116 ffffa60c`ddefc4a0 fffff80f`4cc5ca3c ffffffff`c000009a : nt!KeBugCheckEx
fffff300`a6637a30 fffff80f`476ebc04 : fffff80f`4cc5ca3c ffffa60c`da7a9a00 00000000`10000000 ffffa60c`da7a9a98 : dxgkrnl!TdrBugcheckOnTimeout+0xe4
fffff300`a6637a70 fffff80f`476df7a5 : ffffa60c`da65b000 ffffa60c`da65b980 00000000`00000001 00000000`00000001 : dxgkrnl!ADAPTER_RENDER::Reset+0x150
fffff300`a6637aa0 fffff80f`4772a495 : 00000000`00000100 fffff80f`45d47150 00000000`d26cfba0 ffffa60c`f1a8c300 : dxgkrnl!DXGADAPTER::Reset+0x451
fffff300`a6637b20 fffff80f`4772a5e7 : 00000000`00000000 ffffa60c`d99fae10 ffffa60c`d26cfba0 fffff80f`4766c240 : dxgkrnl!TdrResetFromTimeout+0x15
fffff300`a6637b50 fffff801`6e547155 : ffffa60c`f1a8c300 fffff80f`4772a5c0 ffffa60c`d26cfba0 fffff80f`45d47150 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27
fffff300`a6637b80 fffff801`6e4b9e27 : ffffa60c`f1a8c300 00000000`00000080 ffffa60c`d26d0440 ffffa60c`f1a8c300 : nt!ExpWorkerThread+0xf5
fffff300`a6637c10 fffff801`6e646f26 : ffff8401`98040180 ffffa60c`f1a8c300 fffff801`6e4b9de0 ffffa60c`e90c4080 : nt!PspSystemThreadStartup+0x47
fffff300`a6637c60 00000000`00000000 : fffff300`a6638000 fffff300`a6632000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
THREAD_SHA1_HASH_MOD_FUNC: 56a150c818aff348d17e35fc9e822916b6c0190b
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: e9996e8ce120731be0c6c9a46c50102468134ddc
THREAD_SHA1_HASH_MOD: 3225689ea8bf23dca00cdfd517975e0703e07271
FOLLOWUP_IP:
nvlddmkm+b4ca3c
fffff80f`4cc5ca3c 48ff253da6e1ff jmp qword ptr [nvlddmkm+0x967080 (fffff80f`4ca77080)]
FAULT_INSTR_CODE: 3d25ff48
SYMBOL_NAME: nvlddmkm+b4ca3c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5bee0308
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys
BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys
PRIMARY_PROBLEM_CLASS: 0x116_IMAGE_nvlddmkm.sys
TARGET_TIME: 2019-07-02T21:05:26.000Z
OSBUILD: 17134
OSSERVICEPACK: 765
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 784
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2019-05-03 08:57:58
BUILDDATESTAMP_STR: 160101.0800
BUILDLAB_STR: WinBuild
BUILDOSVER_STR: 10.0.17134.765
ANALYSIS_SESSION_ELAPSED_TIME: d43
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x116_image_nvlddmkm.sys
FAILURE_ID_HASH: {c89bfe8c-ed39-f658-ef27-f2898997fdbd}
Followup: MachineOwner
---------
VIDEO_SCHEDULER_INTERNAL_ERROR (119)
The video scheduler has detected that fatal violation has occurred. This resulted
in a condition that video scheduler can no longer progress. Any other values after
parameter 1 must be individually examined according to the subtype.
Arguments:
Arg1: 0000000000000002, The driver failed upon the submission of a command.
Arg2: ffffffffc000000d
Arg3: ffffd18cdac7d960
Arg4: ffffd60fd4509970
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 2
Key : Analysis.Elapsed.Sec
Value: 3
Key : Analysis.Memory.CommitPeak.Mb
Value: 70
PROCESSES_ANALYSIS: 1
SERVICE_ANALYSIS: 1
STACKHASH_ANALYSIS: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10.0.17134.829 (WinBuild.160101.0800)
SYSTEM_MANUFACTURER: LENOVO
SYSTEM_PRODUCT_NAME: 20354
SYSTEM_SKU: LENOVO_MT_20354_BU_idea_FM_Lenovo Z50-70
SYSTEM_VERSION: Lenovo Z50-70
BIOS_VENDOR: LENOVO
BIOS_VERSION: 9BCN29WW
BIOS_DATE: 10/20/2014
BASEBOARD_MANUFACTURER: LENOVO
BASEBOARD_PRODUCT: Lancer 5A5
BASEBOARD_VERSION: 31900059WIN
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
DUMP_TYPE: 2
BUGCHECK_P1: 2
BUGCHECK_P2: ffffffffc000000d
BUGCHECK_P3: ffffd18cdac7d960
BUGCHECK_P4: ffffd60fd4509970
CPU_COUNT: 4
CPU_MHZ: 95a
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 45
CPU_STEPPING: 1
CPU_MICROCODE: 6,45,1,0 (F,M,S,R) SIG: 24'00000000 (cache) 24'00000000 (init)
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXPNP: 1 (!blackboxpnp)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x119
PROCESS_NAME: System
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: DESKTOP-HH6FM2D
ANALYSIS_SESSION_TIME: 07-07-2019 15:49:15.0013
ANALYSIS_VERSION: 10.0.18914.1001 amd64fre
LAST_CONTROL_TRANSFER: from fffff80381a0331e to fffff8007624cab0
STACK_TEXT:
ffffd18c`dac7d888 fffff803`81a0331e : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffffd18c`dac7d960 : nt!KeBugCheckEx
ffffd18c`dac7d890 fffff803`8a0ab55b : 00000000`00000000 ffffd60f`d4508000 ffffd60f`d4508000 ffffd60f`d4509970 : watchdog!WdLogEvent5_WdCriticalError+0xce
ffffd18c`dac7d8d0 fffff803`8a10497e : ffffd60f`00000000 ffffd60f`d4509970 ffffd60f`d4508000 ffffd60f`d2ab3930 : dxgmms2!VidSchiSendToExecutionQueue+0x1333b
ffffd18c`dac7da00 fffff803`8a111014 : ffffd60f`d2ab3930 ffffd60f`d4241001 00000000`00000000 ffffd60f`d4241010 : dxgmms2!VidSchiSubmitPagingCommand+0x2ae
ffffd18c`dac7db80 fffff803`8a110e8e : ffffd60f`d43e6500 fffff803`8a110e00 ffffd60f`d43e6000 00000000`00000000 : dxgmms2!VidSchiRun_PriorityTable+0x174
ffffd18c`dac7dbd0 fffff800`760c6e27 : ffffd60f`d0375040 fffff803`8a110e00 00000000`77824620 fffff739`800052d8 : dxgmms2!VidSchiWorkerThread+0x8e
ffffd18c`dac7dc10 fffff800`76253f26 : ffffc080`78c17180 ffffd60f`d0375040 fffff800`760c6de0 fffff720`e183a5a3 : nt!PspSystemThreadStartup+0x47
ffffd18c`dac7dc60 00000000`00000000 : ffffd18c`dac7e000 ffffd18c`dac78000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
THREAD_SHA1_HASH_MOD_FUNC: 3c3aefa711a40e43478598e53abd6873e0c9ed57
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 24eeee6dae9fc8d01a89baeabee68a265b95314c
THREAD_SHA1_HASH_MOD: 8bc3a1490ebecb3d757d5cd2041e6cd7da5819c4
FOLLOWUP_IP:
dxgmms2!VidSchiSendToExecutionQueue+1333b
fffff803`8a0ab55b cc int 3
FAULT_INSTR_CODE: b60f41cc
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: dxgmms2!VidSchiSendToExecutionQueue+1333b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms2
IMAGE_NAME: dxgmms2.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 0
IMAGE_VERSION: 10.0.17134.829
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 1333b
FAILURE_BUCKET_ID: 0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue
BUCKET_ID: 0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue
PRIMARY_PROBLEM_CLASS: 0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue
TARGET_TIME: 2019-07-03T16:17:35.000Z
OSBUILD: 17134
OSSERVICEPACK: 829
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 784
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2019-06-07 08:21:36
BUILDDATESTAMP_STR: 160101.0800
BUILDLAB_STR: WinBuild
BUILDOSVER_STR: 10.0.17134.829
ANALYSIS_SESSION_ELAPSED_TIME: f0b
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x119_2_driver_failed_submit_command_dxgmms2!vidschisendtoexecutionqueue
FAILURE_ID_HASH: {9a11bf9c-270e-962e-7a82-3efdab93c10e}
Followup: MachineOwner
---------
Teşekkürler cevabınız için. Ancak solidworks programını zaten GT840M ile kullanmıyordum. Onun yerine "built-in" grafik kartını kullanıyordum. Intel'ın grafik işlemcisiyle yani.840M olan cihazın soğutması kullandığınız yazılıma uygun değildir. Bu bağlamda aşırı ısınan sistemde büyük ihtimalle GPU lehimleri atmıştır. Yazılımsal çözümler bana göre ancak vakit kaybı olur böyle bir sistemde.
Reablling ile sorun çözülebilir ama bu sistemde Solidworks kullanmaya devam ederseniz kısa sürede sorun yine nüksedeecektir.
Eğer render alacaksanız buna uygun bir cihaz almanız gerekiyor.
Kod:VIDEO_TDR_FAILURE (116) Attempt to reset the display driver and recover from timeout failed. Arguments: Arg1: ffffa60cddefc4a0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff80f4cc5ca3c, The pointer into responsible device driver module (e.g. owner tag). Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation. Arg4: 0000000000000004, Optional internal context dependent data. Debugging Details: ------------------ Unable to load image nvlddmkm.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for nvlddmkm.sys KEY_VALUES_STRING: 1 Key : Analysis.CPU.Sec Value: 1 Key : Analysis.Elapsed.Sec Value: 3 Key : Analysis.Memory.CommitPeak.Mb Value: 73 PROCESSES_ANALYSIS: 1 SERVICE_ANALYSIS: 1 STACKHASH_ANALYSIS: 1 TIMELINE_ANALYSIS: 1 DUMP_CLASS: 1 DUMP_QUALIFIER: 400 BUILD_VERSION_STRING: 10.0.17134.765 (WinBuild.160101.0800) SYSTEM_MANUFACTURER: LENOVO SYSTEM_PRODUCT_NAME: 20354 SYSTEM_SKU: LENOVO_MT_20354_BU_idea_FM_Lenovo Z50-70 SYSTEM_VERSION: Lenovo Z50-70 BIOS_VENDOR: LENOVO BIOS_VERSION: 9BCN29WW BIOS_DATE: 10/20/2014 BASEBOARD_MANUFACTURER: LENOVO BASEBOARD_PRODUCT: Lancer 5A5 BASEBOARD_VERSION: 31900059WIN DUMP_FILE_ATTRIBUTES: 0x8 Kernel Generated Triage Dump DUMP_TYPE: 2 BUGCHECK_P1: ffffa60cddefc4a0 BUGCHECK_P2: fffff80f4cc5ca3c BUGCHECK_P3: ffffffffc000009a BUGCHECK_P4: 4 FAULTING_IP: nvlddmkm+b4ca3c fffff80f`4cc5ca3c 48ff253da6e1ff jmp qword ptr [nvlddmkm+0x967080 (fffff80f`4ca77080)] DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT CPU_COUNT: 4 CPU_MHZ: 95a CPU_VENDOR: GenuineIntel CPU_FAMILY: 6 CPU_MODEL: 45 CPU_STEPPING: 1 CPU_MICROCODE: 6,45,1,0 (F,M,S,R) SIG: 23'00000000 (cache) 23'00000000 (init) BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXPNP: 1 (!blackboxpnp) CUSTOMER_CRASH_COUNT: 1 BUGCHECK_STR: 0x116 PROCESS_NAME: System CURRENT_IRQL: 0 ANALYSIS_SESSION_HOST: DESKTOP-HH6FM2D ANALYSIS_SESSION_TIME: 07-07-2019 15:49:11.0823 ANALYSIS_VERSION: 10.0.18914.1001 amd64fre STACK_TEXT: fffff300`a6637a28 fffff80f`4772acf8 : 00000000`00000116 ffffa60c`ddefc4a0 fffff80f`4cc5ca3c ffffffff`c000009a : nt!KeBugCheckEx fffff300`a6637a30 fffff80f`476ebc04 : fffff80f`4cc5ca3c ffffa60c`da7a9a00 00000000`10000000 ffffa60c`da7a9a98 : dxgkrnl!TdrBugcheckOnTimeout+0xe4 fffff300`a6637a70 fffff80f`476df7a5 : ffffa60c`da65b000 ffffa60c`da65b980 00000000`00000001 00000000`00000001 : dxgkrnl!ADAPTER_RENDER::Reset+0x150 fffff300`a6637aa0 fffff80f`4772a495 : 00000000`00000100 fffff80f`45d47150 00000000`d26cfba0 ffffa60c`f1a8c300 : dxgkrnl!DXGADAPTER::Reset+0x451 fffff300`a6637b20 fffff80f`4772a5e7 : 00000000`00000000 ffffa60c`d99fae10 ffffa60c`d26cfba0 fffff80f`4766c240 : dxgkrnl!TdrResetFromTimeout+0x15 fffff300`a6637b50 fffff801`6e547155 : ffffa60c`f1a8c300 fffff80f`4772a5c0 ffffa60c`d26cfba0 fffff80f`45d47150 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27 fffff300`a6637b80 fffff801`6e4b9e27 : ffffa60c`f1a8c300 00000000`00000080 ffffa60c`d26d0440 ffffa60c`f1a8c300 : nt!ExpWorkerThread+0xf5 fffff300`a6637c10 fffff801`6e646f26 : ffff8401`98040180 ffffa60c`f1a8c300 fffff801`6e4b9de0 ffffa60c`e90c4080 : nt!PspSystemThreadStartup+0x47 fffff300`a6637c60 00000000`00000000 : fffff300`a6638000 fffff300`a6632000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16 THREAD_SHA1_HASH_MOD_FUNC: 56a150c818aff348d17e35fc9e822916b6c0190b THREAD_SHA1_HASH_MOD_FUNC_OFFSET: e9996e8ce120731be0c6c9a46c50102468134ddc THREAD_SHA1_HASH_MOD: 3225689ea8bf23dca00cdfd517975e0703e07271 FOLLOWUP_IP: nvlddmkm+b4ca3c fffff80f`4cc5ca3c 48ff253da6e1ff jmp qword ptr [nvlddmkm+0x967080 (fffff80f`4ca77080)] FAULT_INSTR_CODE: 3d25ff48 SYMBOL_NAME: nvlddmkm+b4ca3c FOLLOWUP_NAME: MachineOwner MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys DEBUG_FLR_IMAGE_TIMESTAMP: 5bee0308 STACK_COMMAND: .thread ; .cxr ; kb FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys PRIMARY_PROBLEM_CLASS: 0x116_IMAGE_nvlddmkm.sys TARGET_TIME: 2019-07-02T21:05:26.000Z OSBUILD: 17134 OSSERVICEPACK: 765 SERVICEPACK_NUMBER: 0 OS_REVISION: 0 SUITE_MASK: 784 PRODUCT_TYPE: 1 OSPLATFORM_TYPE: x64 OSNAME: Windows 10 OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal OS_LOCALE: USER_LCID: 0 OSBUILD_TIMESTAMP: 2019-05-03 08:57:58 BUILDDATESTAMP_STR: 160101.0800 BUILDLAB_STR: WinBuild BUILDOSVER_STR: 10.0.17134.765 ANALYSIS_SESSION_ELAPSED_TIME: d43 ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0x116_image_nvlddmkm.sys FAILURE_ID_HASH: {c89bfe8c-ed39-f658-ef27-f2898997fdbd} Followup: MachineOwner --------- VIDEO_SCHEDULER_INTERNAL_ERROR (119) The video scheduler has detected that fatal violation has occurred. This resulted in a condition that video scheduler can no longer progress. Any other values after parameter 1 must be individually examined according to the subtype. Arguments: Arg1: 0000000000000002, The driver failed upon the submission of a command. Arg2: ffffffffc000000d Arg3: ffffd18cdac7d960 Arg4: ffffd60fd4509970 Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.Sec Value: 2 Key : Analysis.Elapsed.Sec Value: 3 Key : Analysis.Memory.CommitPeak.Mb Value: 70 PROCESSES_ANALYSIS: 1 SERVICE_ANALYSIS: 1 STACKHASH_ANALYSIS: 1 TIMELINE_ANALYSIS: 1 DUMP_CLASS: 1 DUMP_QUALIFIER: 400 BUILD_VERSION_STRING: 10.0.17134.829 (WinBuild.160101.0800) SYSTEM_MANUFACTURER: LENOVO SYSTEM_PRODUCT_NAME: 20354 SYSTEM_SKU: LENOVO_MT_20354_BU_idea_FM_Lenovo Z50-70 SYSTEM_VERSION: Lenovo Z50-70 BIOS_VENDOR: LENOVO BIOS_VERSION: 9BCN29WW BIOS_DATE: 10/20/2014 BASEBOARD_MANUFACTURER: LENOVO BASEBOARD_PRODUCT: Lancer 5A5 BASEBOARD_VERSION: 31900059WIN DUMP_FILE_ATTRIBUTES: 0x8 Kernel Generated Triage Dump DUMP_TYPE: 2 BUGCHECK_P1: 2 BUGCHECK_P2: ffffffffc000000d BUGCHECK_P3: ffffd18cdac7d960 BUGCHECK_P4: ffffd60fd4509970 CPU_COUNT: 4 CPU_MHZ: 95a CPU_VENDOR: GenuineIntel CPU_FAMILY: 6 CPU_MODEL: 45 CPU_STEPPING: 1 CPU_MICROCODE: 6,45,1,0 (F,M,S,R) SIG: 24'00000000 (cache) 24'00000000 (init) BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXPNP: 1 (!blackboxpnp) CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT BUGCHECK_STR: 0x119 PROCESS_NAME: System CURRENT_IRQL: 0 ANALYSIS_SESSION_HOST: DESKTOP-HH6FM2D ANALYSIS_SESSION_TIME: 07-07-2019 15:49:15.0013 ANALYSIS_VERSION: 10.0.18914.1001 amd64fre LAST_CONTROL_TRANSFER: from fffff80381a0331e to fffff8007624cab0 STACK_TEXT: ffffd18c`dac7d888 fffff803`81a0331e : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffffd18c`dac7d960 : nt!KeBugCheckEx ffffd18c`dac7d890 fffff803`8a0ab55b : 00000000`00000000 ffffd60f`d4508000 ffffd60f`d4508000 ffffd60f`d4509970 : watchdog!WdLogEvent5_WdCriticalError+0xce ffffd18c`dac7d8d0 fffff803`8a10497e : ffffd60f`00000000 ffffd60f`d4509970 ffffd60f`d4508000 ffffd60f`d2ab3930 : dxgmms2!VidSchiSendToExecutionQueue+0x1333b ffffd18c`dac7da00 fffff803`8a111014 : ffffd60f`d2ab3930 ffffd60f`d4241001 00000000`00000000 ffffd60f`d4241010 : dxgmms2!VidSchiSubmitPagingCommand+0x2ae ffffd18c`dac7db80 fffff803`8a110e8e : ffffd60f`d43e6500 fffff803`8a110e00 ffffd60f`d43e6000 00000000`00000000 : dxgmms2!VidSchiRun_PriorityTable+0x174 ffffd18c`dac7dbd0 fffff800`760c6e27 : ffffd60f`d0375040 fffff803`8a110e00 00000000`77824620 fffff739`800052d8 : dxgmms2!VidSchiWorkerThread+0x8e ffffd18c`dac7dc10 fffff800`76253f26 : ffffc080`78c17180 ffffd60f`d0375040 fffff800`760c6de0 fffff720`e183a5a3 : nt!PspSystemThreadStartup+0x47 ffffd18c`dac7dc60 00000000`00000000 : ffffd18c`dac7e000 ffffd18c`dac78000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16 THREAD_SHA1_HASH_MOD_FUNC: 3c3aefa711a40e43478598e53abd6873e0c9ed57 THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 24eeee6dae9fc8d01a89baeabee68a265b95314c THREAD_SHA1_HASH_MOD: 8bc3a1490ebecb3d757d5cd2041e6cd7da5819c4 FOLLOWUP_IP: dxgmms2!VidSchiSendToExecutionQueue+1333b fffff803`8a0ab55b cc int 3 FAULT_INSTR_CODE: b60f41cc SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: dxgmms2!VidSchiSendToExecutionQueue+1333b FOLLOWUP_NAME: MachineOwner MODULE_NAME: dxgmms2 IMAGE_NAME: dxgmms2.sys DEBUG_FLR_IMAGE_TIMESTAMP: 0 IMAGE_VERSION: 10.0.17134.829 STACK_COMMAND: .thread ; .cxr ; kb BUCKET_ID_FUNC_OFFSET: 1333b FAILURE_BUCKET_ID: 0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue BUCKET_ID: 0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue PRIMARY_PROBLEM_CLASS: 0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue TARGET_TIME: 2019-07-03T16:17:35.000Z OSBUILD: 17134 OSSERVICEPACK: 829 SERVICEPACK_NUMBER: 0 OS_REVISION: 0 SUITE_MASK: 784 PRODUCT_TYPE: 1 OSPLATFORM_TYPE: x64 OSNAME: Windows 10 OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal OS_LOCALE: USER_LCID: 0 OSBUILD_TIMESTAMP: 2019-06-07 08:21:36 BUILDDATESTAMP_STR: 160101.0800 BUILDLAB_STR: WinBuild BUILDOSVER_STR: 10.0.17134.829 ANALYSIS_SESSION_ELAPSED_TIME: f0b ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0x119_2_driver_failed_submit_command_dxgmms2!vidschisendtoexecutionqueue FAILURE_ID_HASH: {9a11bf9c-270e-962e-7a82-3efdab93c10e} Followup: MachineOwner ---------
Hocam ben ntpasswd ile sıfırladım bir kullanıcının şifresini. Şimdi parola soruyor ama parola girmeden enter a basınca girebiliyorum sıkıntı yok. Bir tane "Guest" diye hesapta "dis/lock" yazıyordu onu sıfırlamadım. Bu sıfırladığım hesabım da admin. Acaba ben şimdi DDU'yu kullansam bir sıkıntı çıkar mı? Bir sıkıntı falan çıksa çözümü yok mudur güvenli modda? Kaç gündür korkudan DDU çalıştıramadım.Aynen parolanızı öğrenmenizde yarar var. Aşağıdaki rehberden faydalanabilirsiniz.
Windows Åifrenizi NTpasswd İle Sıfırlayın
Windows Åifresini unuttuysanız,  bu ufak araç sayesinde dakikalar içinde Åifrenizi sıfırlayabilirsiniz. Kullanıcıların Windows oturumlarına aitwww.technopat.net
Hocam bu arada az önce düzelmedi diye aygıt yöneticisinden cihazı devre dışı bırakıp etkinleştirdim. 10 saniyeliğine üstündeki ünlem kalktı ve sonra windows, "kişisel bilgisayarınız bir sorunla karşılaştı" şeklinde bir mavi ekran verdi ve kendini kapattı. Kesin olarak donanımsal diyebiliriz herhalde? Şunu da sorayım sorun önceden de dediğiniz gibi lehimle mi ilgilidir? Teşekkürler cevabınız için.Maalesef sorunun donanımsal olduğunu düşünüyorum.