6.3k Aufrufe
Gefragt in Windows 7 von
Bekomme unerwartet Bluescreens, an welcher Anwendung es liegen könnte weiß ich leider nicht.
Was könnt ihr mit dem folgenden Dump-File-Infos anfangen? abt Ihr einen Tipp?

Mein System:
Windows 7 Home Premium 64bit
Intel i7-860
2x2Gb GeIL Ultra CL6-6-6-20 DDR3 1333
GA-P55-UD3R
Asus GTX 275
2 x 500Gb Seagate
Corsair TX650 Watt Netzteil

______________________________________


Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Animator\Desktop\032310-22214-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: a
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e63000 PsLoadedModuleList = 0xfffff800`030a0e50
Debug session time: Tue Mar 23 22:58:19.573 2010 (GMT+1)
System Uptime: 0 days 4:43:17.588
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
......
Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80055e54e0, fffff880048e8220, 0, 2}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** 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+e7220 )

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

6: kd>
6: kd>
6: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80055e54e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880048e8220, 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+e7220
fffff880`048e8220 803d31c0960000 cmp byte ptr [nvlddmkm+0xa53258 (fffff880`05254258)],0

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0x116

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`03bf59c8 fffff880`05323ef8 : 00000000`00000116 fffffa80`055e54e0 fffff880`048e8220 00000000`00000000 : nt!KeBugCheckEx
fffff880`03bf59d0 00000000`00000116 : fffffa80`055e54e0 fffff880`048e8220 00000000`00000000 00000000`00000002 : dxgkrnl+0x5cef8
fffff880`03bf59d8 fffffa80`055e54e0 : fffff880`048e8220 00000000`00000000 00000000`00000002 00000000`00000000 : 0x116
fffff880`03bf59e0 fffff880`048e8220 : 00000000`00000000 00000000`00000002 00000000`00000000 00000000`00000000 : 0xfffffa80`055e54e0
fffff880`03bf59e8 00000000`00000000 : 00000000`00000002 00000000`00000000 00000000`00000000 fffff880`05323c02 : nvlddmkm+0xe7220


STACK_COMMAND: kb

FOLLOWUP_IP:
nvlddmkm+e7220
fffff880`048e8220 803d31c0960000 cmp byte ptr [nvlddmkm+0xa53258 (fffff880`05254258)],0

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: nvlddmkm+e7220

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4abfff56

FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys

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

6: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80055e54e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880048e8220, 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+e7220
fffff880`048e8220 803d31c0960000 cmp byte ptr [nvlddmkm+0xa53258 (fffff880`05254258)],0

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0x116

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`03bf59c8 fffff880`05323ef8 : 00000000`00000116 fffffa80`055e54e0 fffff880`048e8220 00000000`00000000 : nt!KeBugCheckEx
fffff880`03bf59d0 00000000`00000116 : fffffa80`055e54e0 fffff880`048e8220 00000000`00000000 00000000`00000002 : dxgkrnl+0x5cef8
fffff880`03bf59d8 fffffa80`055e54e0 : fffff880`048e8220 00000000`00000000 00000000`00000002 00000000`00000000 : 0x116
fffff880`03bf59e0 fffff880`048e8220 : 00000000`00000000 00000000`00000002 00000000`00000000 00000000`00000000 : 0xfffffa80`055e54e0
fffff880`03bf59e8 00000000`00000000 : 00000000`00000002 00000000`00000000 00000000`00000000 fffff880`05323c02 : nvlddmkm+0xe7220


STACK_COMMAND: kb

FOLLOWUP_IP:
nvlddmkm+e7220
fffff880`048e8220 803d31c0960000 cmp byte ptr [nvlddmkm+0xa53258 (fffff880`05254258)],0

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: nvlddmkm+e7220

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4abfff56

FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys

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

14 Antworten

0 Punkte
Beantwortet von
Danke nochmal für die Hilfe. Darf ich fragen was du @friday beruflich so machst. Hast mir gut weitergeholfen.
Werd dann mal den Rechner gut beobachten sollten weitere Bluescreens kommen.
0 Punkte
Beantwortet von
Ich bin Maschinenführer in einem Glaswerk.
PC ist nur mein Hobby. ;)
0 Punkte
Beantwortet von Blitzhilfe Experte (1.4k Punkte)
Hallo,

mit Windows XP (Verifier.exe) kann man Treiberprobleme ermitteln, ob das für Windows 7 geht weiß ich leider nicht?

Grüße
0 Punkte
Beantwortet von Blitzhilfe Experte (1.4k Punkte)
Nachtrag,

Verifier.exe

viel Glück...
...