VIDEO_TDR_FAILURE Mavi Ekran Hatası

alidogan58

alidogan58

Femtopat
Katılım
14 Eylül 2020
Mesajlar
12
BCCode: 116

BCP1: FFFFFA80047454E0

BCP2: FFFFF8800F184400

BCP3: 0000000000000000

BCP4: 0000000000000002

OS Version: 6_1_7601

Service Pack: 1_0

Product: 768_1

Nasıl kurtulabilirim bu hatadan?
 
Tarihe göre sırala Puana göre sırala
Son düzenleyen: Moderatör:
Artı 0 Eksi
Ekran kartı sorun çıkarmış. DDU ile silip güncelini yükleyiniz. Valorant anti-cheat kaldırın. DDU ile Sürücü Kaldırma Rehberi - Technopat Sosyal
Kod: 
MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
    contains the address of the PFN for the corrupted page table page.
    On a 32 bit OS, parameter 2 contains a pointer to the number of used
    PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa80003635d0
Arg3: 000000000000ffff
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  Update.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre

LAST_CONTROL_TRANSFER:  from fffff80002d65dfd to fffff80002ca1ba0

STACK_TEXT: 
fffff880`062c67e8 fffff800`02d65dfd : 00000000`0000001a 00000000`00041790 fffffa80`003635d0 00000000`0000ffff : nt!KeBugCheckEx
fffff880`062c67f0 fffff800`02d833e5 : 00000000`00000000 00000000`7729ffff 00000000`00000000 00000000`00000001 : nt!MiDeleteVirtualAddresses+0x93d
fffff880`062c6960 fffff800`02c3d904 : fffffa80`028b39b0 fffffa80`00000000 00000000`00000000 00000000`7729ffff : nt!MiRemoveMappedView+0x485
fffff880`062c6aa0 fffff800`0303e454 : fffff8a0`00a159f0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmCleanProcessAddressSpace+0x284
fffff880`062c6af0 fffff800`0309b6d5 : 00000000`c0000005 00000000`00000001 00000000`7efdb000 00000000`00000000 : nt!PspExitThread+0x944
fffff880`062c6bb0 fffff800`02cafbd3 : ffffffff`ffffffff fffffa80`0458cb50 fffffa80`028b39b0 00000000`00000be4 : nt!NtTerminateProcess+0x2d5
fffff880`062c6c20 00000000`775c9b4a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`000ddf68 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x775c9b4a


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt!MiDeleteVirtualAddresses+93d
fffff800`02d65dfd cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiDeleteVirtualAddresses+93d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  5c6e1cbd

IMAGE_VERSION:  6.1.7601.24384

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!MiDeleteVirtualAddresses+93d

BUCKET_ID:  X64_0x1a_41790_nt!MiDeleteVirtualAddresses+93d

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x1a_41790_nt!mideletevirtualaddresses+93d

FAILURE_ID_HASH:  {f4a94a0f-7c3c-4cbd-b72c-ee4a493af7de}

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

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


FAULTING_IP:
nvlddmkm+153400
fffff880`0f209400 48ff2539ce7200  jmp     qword ptr [nvlddmkm+0x880240 (fffff880`0f936240)]

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre

STACK_TEXT: 
fffff880`035ff9c8 fffff880`02c8b388 : 00000000`00000116 fffffa80`04923010 fffff880`0f209400 00000000`00000000 : nt!KeBugCheckEx
fffff880`035ff9d0 fffff880`02c8b092 : fffff880`0f209400 fffffa80`04923010 fffffa80`04a73c10 fffffa80`04aa6410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`035ffa10 fffff880`02d32fcb : fffffa80`04923010 00000000`00000000 fffffa80`04a73c10 fffffa80`04aa6410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`035ffa40 fffff880`02d5cd45 : 00000000`ffffffff 00000000`00000a43 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`035ffb20 fffff880`02d5b48b : 00000000`00000102 00000000`00000000 00000000`00000a43 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`035ffb50 fffff880`02d2e2f2 : ffffffff`ff676980 fffffa80`04aa6410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`035ffbf0 fffff880`02d5b04a : 00000000`00000000 fffffa80`04abbbb0 00000000`00000080 fffffa80`04aa6410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`035ffd00 fffff800`02f571a0 : 00000000`fffffc32 fffff880`009ea180 00000000`00000001 fffffa80`04aa1a00 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`035ffd40 fffff800`02cafba6 : fffff880`009ea180 fffffa80`04aa1a00 fffff880`009f9140 00000000`00000000 : nt!PspSystemThreadStartup+0x194
fffff880`035ffd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP:
nvlddmkm+153400
fffff880`0f209400 48ff2539ce7200  jmp     qword ptr [nvlddmkm+0x880240 (fffff880`0f936240)]

SYMBOL_NAME:  nvlddmkm+153400

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5829870b

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x116_image_nvlddmkm.sys

FAILURE_ID_HASH:  {1f9e0448-3238-5868-3678-c8e526bb1edc}

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

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


FAULTING_IP:
nvlddmkm+153400
fffff880`0f184400 48ff2539ce7200  jmp     qword ptr [nvlddmkm+0x880240 (fffff880`0f8b1240)]

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre

STACK_TEXT: 
fffff880`02b3a9c8 fffff880`0fd2b388 : 00000000`00000116 fffffa80`047454e0 fffff880`0f184400 00000000`00000000 : nt!KeBugCheckEx
fffff880`02b3a9d0 fffff880`0fd2b092 : fffff880`0f184400 fffffa80`047454e0 fffffa80`04b46ab0 fffffa80`04b3f410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`02b3aa10 fffff880`0430efcb : fffffa80`047454e0 00000000`00000000 fffffa80`04b46ab0 fffffa80`04b3f410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`02b3aa40 fffff880`04338d45 : 00000000`ffffffff 00000000`000007e2 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`02b3ab20 fffff880`0433748b : 00000000`00000102 00000000`00000000 00000000`000007e2 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`02b3ab50 fffff880`0430a2f2 : ffffffff`ff676980 fffffa80`04b3f410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`02b3abf0 fffff880`0433704a : 00000000`00000000 fffffa80`05dded50 00000000`00000080 fffffa80`04b3f410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`02b3ad00 fffff800`02fa21a0 : 00000000`fffffc32 fffff880`009ea180 00000000`00000001 fffffa80`04b6b4c0 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`02b3ad40 fffff800`02cfaba6 : fffff880`009ea180 fffffa80`04b6b4c0 fffff880`009f9140 00000000`00000000 : nt!PspSystemThreadStartup+0x194
fffff880`02b3ad80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP:
nvlddmkm+153400
fffff880`0f184400 48ff2539ce7200  jmp     qword ptr [nvlddmkm+0x880240 (fffff880`0f8b1240)]

SYMBOL_NAME:  nvlddmkm+153400

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5829870b

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x116_image_nvlddmkm.sys

FAILURE_ID_HASH:  {1f9e0448-3238-5868-3678-c8e526bb1edc}

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

2: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f031000 fffff880`0fcce000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Mon Nov 14 09:42:35 2016 (5829870B)
    CheckSum:         00C5E4C4
    ImageSize:        00C9D000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Devam ederse bellek testi yapınız.
Bu içeriği görüntülemek için üçüncü taraf çerezlerini yerleştirmek için izninize ihtiyacımız olacak.
Daha detaylı bilgi için, çerezler sayfamıza bakınız.
 
Artı 0 Eksi
Şu an çözüldü gibi duruyor teşekkürler.

Assecreed dedi:
Ekran kartı sorun çıkarmış. DDU ile silip güncelini yükleyiniz. Valorant anti-cheat kaldırın. DDU ile Sürücü Kaldırma Rehberi - Technopat Sosyal
Kod: 
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
contains the address of the PFN for the corrupted page table page.
On a 32 bit OS, parameter 2 contains a pointer to the number of used
PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa80003635d0
Arg3: 000000000000ffff
Arg4: 0000000000000000

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

BUGCHECK_STR: 0x1a_41790

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: Update.exe

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre

LAST_CONTROL_TRANSFER: from fffff80002d65dfd to fffff80002ca1ba0

STACK_TEXT:
fffff880`062c67e8 fffff800`02d65dfd : 00000000`0000001a 00000000`00041790 fffffa80`003635d0 00000000`0000ffff : nt!KeBugCheckEx
fffff880`062c67f0 fffff800`02d833e5 : 00000000`00000000 00000000`7729ffff 00000000`00000000 00000000`00000001 : nt!MiDeleteVirtualAddresses+0x93d
fffff880`062c6960 fffff800`02c3d904 : fffffa80`028b39b0 fffffa80`00000000 00000000`00000000 00000000`7729ffff : nt!MiRemoveMappedView+0x485
fffff880`062c6aa0 fffff800`0303e454 : fffff8a0`00a159f0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmCleanProcessAddressSpace+0x284
fffff880`062c6af0 fffff800`0309b6d5 : 00000000`c0000005 00000000`00000001 00000000`7efdb000 00000000`00000000 : nt!PspExitThread+0x944
fffff880`062c6bb0 fffff800`02cafbd3 : ffffffff`ffffffff fffffa80`0458cb50 fffffa80`028b39b0 00000000`00000be4 : nt!NtTerminateProcess+0x2d5
fffff880`062c6c20 00000000`775c9b4a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`000ddf68 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x775c9b4a

STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiDeleteVirtualAddresses+93d
fffff800`02d65dfd cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MiDeleteVirtualAddresses+93d

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 5c6e1cbd

IMAGE_VERSION: 6.1.7601.24384

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: X64_0x1a_41790_nt!MiDeleteVirtualAddresses+93d

BUCKET_ID: X64_0x1a_41790_nt!MiDeleteVirtualAddresses+93d

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x1a_41790_nt!mideletevirtualaddresses+93d

FAILURE_ID_HASH: {f4a94a0f-7c3c-4cbd-b72c-ee4a493af7de}

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

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

FAULTING_IP:
nvlddmkm+153400
fffff880`0f209400 48ff2539ce7200 jmp qword ptr [nvlddmkm+0x880240 (fffff880`0f936240)]

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0x116

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre

STACK_TEXT:
fffff880`035ff9c8 fffff880`02c8b388 : 00000000`00000116 fffffa80`04923010 fffff880`0f209400 00000000`00000000 : nt!KeBugCheckEx
fffff880`035ff9d0 fffff880`02c8b092 : fffff880`0f209400 fffffa80`04923010 fffffa80`04a73c10 fffffa80`04aa6410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`035ffa10 fffff880`02d32fcb : fffffa80`04923010 00000000`00000000 fffffa80`04a73c10 fffffa80`04aa6410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`035ffa40 fffff880`02d5cd45 : 00000000`ffffffff 00000000`00000a43 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`035ffb20 fffff880`02d5b48b : 00000000`00000102 00000000`00000000 00000000`00000a43 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`035ffb50 fffff880`02d2e2f2 : ffffffff`ff676980 fffffa80`04aa6410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`035ffbf0 fffff880`02d5b04a : 00000000`00000000 fffffa80`04abbbb0 00000000`00000080 fffffa80`04aa6410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`035ffd00 fffff800`02f571a0 : 00000000`fffffc32 fffff880`009ea180 00000000`00000001 fffffa80`04aa1a00 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`035ffd40 fffff800`02cafba6 : fffff880`009ea180 fffffa80`04aa1a00 fffff880`009f9140 00000000`00000000 : nt!PspSystemThreadStartup+0x194
fffff880`035ffd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nvlddmkm+153400
fffff880`0f209400 48ff2539ce7200 jmp qword ptr [nvlddmkm+0x880240 (fffff880`0f936240)]

SYMBOL_NAME: nvlddmkm+153400

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5829870b

FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x116_image_nvlddmkm.sys

FAILURE_ID_HASH: {1f9e0448-3238-5868-3678-c8e526bb1edc}

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

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

FAULTING_IP:
nvlddmkm+153400
fffff880`0f184400 48ff2539ce7200 jmp qword ptr [nvlddmkm+0x880240 (fffff880`0f8b1240)]

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0x116

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre

STACK_TEXT:
fffff880`02b3a9c8 fffff880`0fd2b388 : 00000000`00000116 fffffa80`047454e0 fffff880`0f184400 00000000`00000000 : nt!KeBugCheckEx
fffff880`02b3a9d0 fffff880`0fd2b092 : fffff880`0f184400 fffffa80`047454e0 fffffa80`04b46ab0 fffffa80`04b3f410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`02b3aa10 fffff880`0430efcb : fffffa80`047454e0 00000000`00000000 fffffa80`04b46ab0 fffffa80`04b3f410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`02b3aa40 fffff880`04338d45 : 00000000`ffffffff 00000000`000007e2 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`02b3ab20 fffff880`0433748b : 00000000`00000102 00000000`00000000 00000000`000007e2 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`02b3ab50 fffff880`0430a2f2 : ffffffff`ff676980 fffffa80`04b3f410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`02b3abf0 fffff880`0433704a : 00000000`00000000 fffffa80`05dded50 00000000`00000080 fffffa80`04b3f410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`02b3ad00 fffff800`02fa21a0 : 00000000`fffffc32 fffff880`009ea180 00000000`00000001 fffffa80`04b6b4c0 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`02b3ad40 fffff800`02cfaba6 : fffff880`009ea180 fffffa80`04b6b4c0 fffff880`009f9140 00000000`00000000 : nt!PspSystemThreadStartup+0x194
fffff880`02b3ad80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nvlddmkm+153400
fffff880`0f184400 48ff2539ce7200 jmp qword ptr [nvlddmkm+0x880240 (fffff880`0f8b1240)]

SYMBOL_NAME: nvlddmkm+153400

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5829870b

FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x116_image_nvlddmkm.sys

FAILURE_ID_HASH: {1f9e0448-3238-5868-3678-c8e526bb1edc}

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

2: kd> lmvm nvlddmkm
start end module name
fffff880`0f031000 fffff880`0fcce000 nvlddmkm T (no symbols)
Loaded symbol image file: nvlddmkm.sys
Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
Image name: nvlddmkm.sys
Timestamp: Mon Nov 14 09:42:35 2016 (5829870B)
CheckSum: 00C5E4C4
ImageSize: 00C9D000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Devam ederse bellek testi yapınız.
Bu içeriği görüntülemek için üçüncü taraf çerezlerini yerleştirmek için izninize ihtiyacımız olacak.
Daha detaylı bilgi için, çerezler sayfamıza bakınız.
Genişletmek için tıkla...


Sorun şöyle devam ediyor. Ekran birden gitti ve kod 43 hatasını verdi. Birkaç gün önce PSU değiştirmiştim ondan kaynaklı olabilir mi?
 
Son düzenleyen: Moderatör:
Artı 0 Eksi
Uyarı! Bu konu 6 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.

Benzer konular

frezyona
  • Soru
"VIDEO_TDR_FAILURE" mavi ekran hatası
Mesaj
5
Görüntüleme
247
claus
claus
WildCharm
  • Soru
VIDEO_TDR_FAILURE mavi ekran hatası
Mesaj
3
Görüntüleme
162
turko35408
turko35408
Xorto
  • Soru
VIDEO_TDR_FAILURE mavi ekran hatası
Mesaj
5
Görüntüleme
273
claus
claus
Lewis44
  • Soru
VIDEO_TDR_FAILURE mavi ekran hatası
Mesaj
0
Görüntüleme
190
Lewis44
Lewis44
vilgaxq
  • Soru
VIDEO_TDR_FAILURE mavi ekran hatası
Mesaj
2
Görüntüleme
243
vilgaxq
vilgaxq

Technopat Haberler

Yeni konular

Yeni mesajlar

Geri
Yukarı