jo hab das einige seiten hier vorher von dir gelesen und gleich neu installt.
zusammengefast:
+seit dem graka treiber 8.10 keine atikmpag.sys bluescreens mehr.
+dafür aber crash to desktop nur beim spielen.
+pc läßt sich viel besser nach crash wieder booten.
+pc läuft auf 3,6 mhz und ram1066 mhz und fsb 1600mhz im normal betrieb reibungslos
sowie auf 3,0 mhz und ram 800mhz ohne probs.
+zocken geht nicht, freez nach einigen sekunden im spiel bfbc2
hier mal den letzten crashdump von gestern (mal was anderes)
nur verstehen tu ichs nicht was das heist.
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)
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 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: fffffa80056c5b60, 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 "intercepted" bugcheck 0xEA was hit (see notes).
Debugging Details:
------------------
FAULTING_THREAD: fffffa80056c5b60
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0xEA
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff8800450ff63 to fffff80002a8f740
STACK_TEXT:
fffff880`03ddb688 fffff880`0450ff63 : 00000000`000000ea fffffa80`056c5b60 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`03ddb690 fffff880`04510112 : fffff880`03ddb760 fffff880`04087cf7 fffff880`03ddb760 00000000`00000001 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x37
fffff880`03ddb700 fffff880`03eb9bca : 00000000`00000000 fffff880`04087cdc fffff880`03ddb880 00000000`004c4b40 : dxgkrnl!TdrTimedOperationDelay+0xbe
fffff880`03ddb740 00000000`00000000 : fffff880`04087cdc fffff880`03ddb880 00000000`004c4b40 00000000`00000028 : atikmdag+0x29bca
STACK_COMMAND: .thread 0xfffffa80056c5b60 ; kb
FOLLOWUP_IP:
dxgkrnl!TdrTimedOperationBugcheckOnTimeout+37
fffff880`0450ff63 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: 4ac5509e
FAILURE_BUCKET_ID: X64_0xEA_IMAGE_dxgkrnl.sys
BUCKET_ID: X64_0xEA_IMAGE_dxgkrnl.sys
Followup: MachineOwner
---------
