Windows 7 Problem - Frage zur Auswertung des Debugger Textes

[KA3AXCTAH]

Da mein PC sich seit ca. 2 Wochen nur mit größten Schwierigkeiten starten lässt, und wenn er gestartet ist, verabschiedet er sich auch nach 2 Minuten wieder. Kurz gesagt es ist eine Tortur ihn mal zum Laufen zu bekommen. Nun jetzt läuft er und ich habe nach dieser Anleitung https://www.computerbase.de/forum/threads/bluescreen.715519/#post-7575054 den Debugger laufen lassen.

Folgender Text kam dabei raus:

Use !analyze -v to get detailed debugging information.

BugCheck EA, {fffffa8007dc64d0, 0, 0, 0}

Probably caused by : dxgkrnl.sys ( dxgkrnl!TdrTimedOperationBugcheckOnTimeout+37 )

Followup: MachineOwner


THREAD_STUCK_IN_DEVICE_DRIVER (ea)
The device driver is spinning in an infinite loop, most likely waiting for
hardware to become idle. This usually indicates problem with the hardware
itself or with the device driver programming the hardware incorrectly.
If the kernel debugger is connected and running when watchdog detects a
timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
and detailed message including bugcheck arguments will be printed to the
debugger. This way we can identify an offending thread, set breakpoints in it,
and hit go to return to the spinning code to debug it further. Because
KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
information in this case. The arguments are already printed out to the kernel
debugger. You can also retrieve them from a global variable via
"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
On MP machines (OS builds <= 3790) it is possible to hit a timeout when the spinning thread is
interrupted by hardware interrupt and ISR or DPC routine is running at the time
of the bugcheck (this is because the timeout's work item can be delivered and
handled on the second CPU and the same time). If this is the case you will have
to look deeper at the offending thread's stack (e.g. using dds) to determine
spinning code which caused the timeout to occur.
Arguments:
Arg1: fffffa8007dc64d0, Pointer to a stuck thread object.  Do .thread then kb on it to find
	the hung location.
Arg2: 0000000000000000, Pointer to a DEFERRED_WATCHDOG object.
Arg3: 0000000000000000, Pointer to offending driver name.
Arg4: 0000000000000000, Number of times this error occurred.  If a debugger is attached,
	this error is not always fatal -- see DESCRIPTION below.  On the
	blue screen, this will always equal 1.

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


FAULTING_THREAD:  fffffa8007dc64d0

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT

BUGCHECK_STR:  0xEA

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff88006e44f63 to fffff80002e8ff00

STACK_TEXT:  
fffff880`081ee5c8 fffff880`06e44f63 : 00000000`000000ea fffffa80`07dc64d0 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`081ee5d0 fffff880`06e45112 : fffff880`081ee6a0 fffff880`06aaca2b fffff880`081ee6a0 00000000`00003f00 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x37
fffff880`081ee640 fffff880`068c3f72 : 00000000`00000000 fffff880`06aaca10 fffff880`081ee7c0 00000000`01c9c380 : dxgkrnl!TdrTimedOperationDelay+0xbe
fffff880`081ee680 fffff880`068c06f4 : 00000000`01c9c380 fffffa80`07ea4010 fffff880`081ee7c0 00000000`00000bb8 : atikmdag!OsServices::Wait+0x92
fffff880`081ee6f0 fffff880`06ab7c6e : 00000000`00000001 fffff880`06aaca10 fffff880`068c06a4 fffff880`068c06f4 : atikmdag!MCIL_WaitFor+0x50
fffff880`081ee720 fffff880`06aacdea : 00000000`00000000 00000000`00000001 fffffa80`06d3e230 fffffa80`06d3e230 : atikmdag!Cail_MCILWaitFor+0x72
fffff880`081ee7a0 fffff880`06ac1113 : 00000000`00030003 00000000`00001a20 00000000`00001a20 fffffa80`06d3e230 : atikmdag!Cail_WaitForMCIdle_Internal+0x116
fffff880`081ee7f0 fffff880`06ac21aa : 00000000`00007fff fffffa80`06d3e230 00000000`00000000 fffff880`068b7937 : atikmdag!Cail_RV770_SetXspPeerApertureDefault+0x68b
fffff880`081ee850 fffff880`06ac2681 : fffffa80`06d3e230 00000000`00000000 00000000`00000000 00000000`00000000 : atikmdag!Cail_RV770_SetXspPeerApertureDefault+0x1722
fffff880`081ee890 fffff880`06ab6dee : 00000000`ffffffff 00000000`00000000 00000000`00000000 fffffa80`06d3e230 : atikmdag!Cail_RV770_VPURecoveryBegin+0x2a5
fffff880`081ee8d0 fffff880`06aa9ca9 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`08879020 : atikmdag!CAIL_VPURecoveryBegin+0x56
fffff880`081ee900 fffff880`0689d84a : fffffa80`06d5a660 00000000`00000000 00000000`00000001 00000000`00000000 : atikmdag!CAILVPURecoveryBegin+0x19
fffff880`081ee930 fffff880`068a8d01 : fffffa80`07f8a240 00000000`00000001 00000000`00000000 00000000`00000000 : atikmdag!AsicInit::ResetTheAsic+0x4a
fffff880`081ee960 fffff880`068a8ef7 : fffffa80`07f8a240 00000000`00000001 fffffa80`093e7010 fffff880`06e3f038 : atikmdag!DISPATCHER::HeavyWeightReset+0x65
fffff880`081ee990 fffff880`068a9fe3 : 00000000`00000000 fffffa80`07f8a240 00000000`00000000 00000000`00000010 : atikmdag!DISPATCHER::ResetFromTimeoutWorker+0x16b
fffff880`081ee9c0 fffff880`06e72cf1 : fffffa80`08951000 00000000`00000000 00000000`00000000 fffffa80`0976a010 : atikmdag!Dispatch_ResetFromTimeout+0x67
fffff880`081ee9f0 fffff880`06e6e54a : 00000000`00000001 fffffa80`08951000 fffffa80`07dbc010 fffffa80`07dbc928 : dxgkrnl!DXGADAPTER::DdiResetFromTimeout+0x45
fffff880`081eea20 fffff880`06e9aa69 : fffffa80`0976a010 fffffa80`0976a010 fffffa80`0976a010 fffffa80`07dbc010 : dxgkrnl!DXGADAPTER::PrepareToReset+0xea
fffff880`081eea60 fffff880`06f41f07 : fffffa80`0976a010 00000000`00000000 fffffa80`08d35010 fffffa80`07dbc010 : dxgkrnl!TdrIsRecoveryRequired+0x245
fffff880`081eea90 fffff880`06f6fd7e : fffffa80`ffffffff 00000000`000015f7 fffff880`081eebf0 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`081eeb70 fffff880`06f3d29e : fffffa80`07dbc010 ffffffff`feced300 fffffa80`089e9950 00000000`00000000 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`081eebb0 fffff880`06f69e7a : 00000000`00000000 fffffa80`089e9950 00000000`00000080 fffffa80`07dbc010 : dxgmms1!VidSchiScheduleCommandToRun+0x1b2
fffff880`081eecc0 fffff800`03133166 : 00000000`00f1500b fffffa80`07dc64d0 fffffa80`06d0c040 fffffa80`07dc64d0 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`081eed00 fffff800`02e6e486 : fffff800`03008e80 fffffa80`07dc64d0 fffff800`03016c40 011f5570`00000002 : nt!PspSystemThreadStartup+0x5a
fffff880`081eed40 00000000`00000000 : fffff880`081ef000 fffff880`081e9000 fffff880`081ee290 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .thread 0xfffffa8007dc64d0 ; kb

FOLLOWUP_IP: 
dxgkrnl!TdrTimedOperationBugcheckOnTimeout+37
fffff880`06e44f63 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  dxgkrnl!TdrTimedOperationBugcheckOnTimeout+37

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc590

FAILURE_BUCKET_ID:  X64_0xEA_IMAGE_dxgkrnl.sys

BUCKET_ID:  X64_0xEA_IMAGE_dxgkrnl.sys

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

Bisher vermutete ich, dass das Problem an der SSD liegt. Aber im Text sehe ich irgendetwas mit Grafik Treiber?

Jedenfalls wäre ich für jede Hilfe dankbar!

 

[Inzersdorfer]

Das wär dann ein Hardwareproblem der Grafikkarte, denn was siehst du im Parameter3 (Arg3) ? Eben, nix, kein Pointer zum verursachenden Treiber.

1) Als Erstes kannst du den ATI Videotreiber einmal vollständig entfernen und dannach neu installieren, um einen korrumpierten Grafiktreiber ausschließen zu können.
2) Ändert das nichts an den Abstürzen, muß die Grafikkarte testweise getauscht werden.
3) Sollten auch dann Abstürze auftreten, läge es an der SSD.

 

[KA3AXCTAH]

Okay, Treiber der GraKa war aus dem Jahre 2009 (!) aktuellster ist nun drauf, Neustarten klappte ohne Problem (kleiner Lichtblick) bis jetzt kein Absturz, werde es beobachten und berichten. Großen Dank für deine Analyse!!!

Ergänzung (8. November 2012)

PC rennt wieder, startet ohne Probleme und stürzt nicht mehr ab.

Ich möchte mich noch einmal für deine Hilfe bedanken Inzersdorfer, wie ich auch in anderen Threads las, ist auf deine Tips stets Verlass!