Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Tarik Uzerli\AppData\Local\Temp\WER1A53.tmp\WD-20131120-1925.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*c:\symbols*
http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\symbols*
http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`02e4e000 PsLoadedModuleList = 0xfffff800`030916d0
Debug session time: Wed Nov 20 19:25:07.439 2013 (UTC + 1:00)
System Uptime: 0 days 0:59:16.672
Loading Kernel Symbols
.
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
..............................................................
................................................................
...................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 117, {fffffa800da3b4e0, fffff8800f366e64, 0, 0}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+152e64 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_TIMEOUT_DETECTED (117)
The display driver failed to respond in timely fashion.
(This code can never be used for a real bugcheck.)
Arguments:
Arg1: fffffa800da3b4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800f366e64, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000000000, Optional internal context dependent data.
Debugging Details:
------------------
FAULTING_IP:
nvlddmkm+152e64
fffff880`0f366e64 ?? ???
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_TIMEOUT
TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b
BUGCHECK_STR: 0x117
PROCESS_NAME: System
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
STACK_TEXT:
fffff880`088874f0 fffff880`0feb0737 : fffffa80`0da3b4e0 fffff880`0fefd038 fffffa80`0da3b4e0 fffff880`0fe7e843 : watchdog!WdDbgReportRecreate+0xa3
fffff880`08887a10 fffff880`0feb13fc : fffff8a0`0e51dd70 fffff8a0`0e51dd70 00000000`00000080 fffffa80`0da3b4e0 : dxgkrnl!TdrUpdateDbgReport+0xcb
fffff880`08887a60 fffff880`0fe856b3 : 00000000`00000001 fffffa80`0a9ae000 00000000`00000000 fffff880`00000096 : dxgkrnl!TdrCollectDbgInfoStage2+0x220
fffff880`08887a90 fffff880`0feb1f4f : fffffa80`0a9ada58 ffffffff`fffe7960 fffffa80`0da3b4e0 fffff880`0ff80f3c : dxgkrnl!DXGADAPTER::Reset+0xef
fffff880`08887b40 fffff880`0ff8103d : fffffa80`0b479c90 00000000`00000080 00000000`00000000 fffffa80`0a9ad410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`08887bc0 fffff800`031602ea : 00000000`0188c5bd fffffa80`0a9d0060 fffffa80`066d7450 fffffa80`0a9d0060 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`08887c00 fffff800`02eb48e6 : fffff800`0303ee80 fffffa80`0a9d0060 fffff800`0304ccc0 fffffa80`06e8eb40 : nt!PspSystemThreadStartup+0x5a
fffff880`08887c40 00000000`00000000 : fffff880`08888000 fffff880`08882000 fffff880`08915d70 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nvlddmkm+152e64
fffff880`0f366e64 ?? ???
SYMBOL_NAME: nvlddmkm+152e64
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5280da75
FAILURE_BUCKET_ID: X64_0x117_IMAGE_nvlddmkm.sys
BUCKET_ID: X64_0x117_IMAGE_nvlddmkm.sys
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x117_image_nvlddmkm.sys
FAILURE_ID_HASH: {c306f7be-ced2-9b11-9b10-d0239a4fd800}
Followup: MachineOwner
---------
.
). Die RAM-Riegel immer nur einzeln einbauen.
) - dann hättest du nach der Testerei in jedem Fall dein jetziges System in Reserve, wenn du die Datensicherung zurückspielst.
Werde hier Posten wenn ich mehr weiss
