Bluescreen x116

W

weezy7

Kabelverknoter(in)
Guten Tag,

ich habe nun zum 2. Mal in kürzester Zeit den Bluescreen x116 während eines Spiel bekommen. Computer hatte wohl hohe Belastung, da er kurz vorher sehr laut wurde.

Mein System sieht folgendermaßen aus: Windows 7 Home Edition 64 bit, Intel i5-4570 CPU @ 3,2 GHz, 8 Gb RAM, Sapphire R9 280x OC, Gigabyte H87-HD3

Ich habe das Bluescreen How To befolgt, die Windows Debug tools benutzt und die 2 Bluescreens die ich bekam ausgelesen:

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


Loading Dump File [C:\Windows\Minidump\112914-5990-01.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.18526.amd64fre.win7sp1_gdr.140706-1506
Machine Name:
Kernel base = 0xfffff800`03257000 PsLoadedModuleList = 0xfffff800`0349a890
Debug session time: Sat Nov 29 14:18:19.521 2014 (UTC + 1:00)
System Uptime: 0 days 14:20:15.692
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
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800db2c010, fffff88004ea8038, 0, 2}

*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+b038 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800db2c010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004ea8038, 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:
atikmpag+b038
fffff880`04ea8038 4883ec28 sub rsp,28h

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.17298 (debuggers(dbg).141024-1500) amd64fre

STACK_TEXT:
fffff880`05dff928 fffff880`10b38134 : 00000000`00000116 fffffa80`0db2c010 fffff880`04ea8038 00000000`00000000 : nt!KeBugCheckEx
fffff880`05dff930 fffff880`10b37e3e : fffff880`04ea8038 fffffa80`0db2c010 fffffa80`0dd92970 fffffa80`0ad9e010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`05dff970 fffff880`0fa0ff13 : fffffa80`0db2c010 00000000`00000000 fffffa80`0dd92970 fffffa80`0ad9e010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`05dff9a0 fffff880`0fa39cf1 : 00000000`ffffffff 00000000`00327bd8 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`05dffa80 fffff880`0fa0b2e1 : fffffa80`0ad9e010 ffffffff`00000008 00000000`00327bd8 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`05dffab0 fffff880`0fa37ff6 : 00000000`00000000 fffffa80`074a6010 00000000`00000080 fffffa80`0ad9e010 : dxgmms1!VidSchiScheduleCommandToRun+0x1e9
fffff880`05dffbc0 fffff800`0356873a : 00000000`fffffc32 fffffa80`0ad97b50 fffffa80`06fc1040 fffffa80`0ad97b50 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`05dffc00 fffff800`032bd8e6 : fffff800`03447e80 fffffa80`0ad97b50 fffff800`03455cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`05dffc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
atikmpag+b038
fffff880`04ea8038 4883ec28 sub rsp,28h

SYMBOL_NAME: atikmpag+b038

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME: atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5417612a

FAILURE_BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x116_image_atikmpag.sys

FAILURE_ID_HASH: {83e844bc-fe68-2042-4230-7f5d3e90b48a}

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

Loading Dump File [C:\Windows\Minidump\112514-6910-01.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.18526.amd64fre.win7sp1_gdr.140706-1506
Machine Name:
Kernel base = 0xfffff800`0320b000 PsLoadedModuleList = 0xfffff800`0344e890
Debug session time: Tue Nov 25 18:33:10.368 2014 (UTC + 1:00)
System Uptime: 0 days 5:12:00.523
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
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800ba2d4e0, fffff880054c5038, 0, 2}

Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+b038 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800ba2d4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880054c5038, 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:
atikmpag+b038
fffff880`054c5038 4883ec28 sub rsp,28h

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.17298 (debuggers(dbg).141024-1500) amd64fre

STACK_TEXT:
fffff880`05ba4718 fffff880`04ef7134 : 00000000`00000116 fffffa80`0ba2d4e0 fffff880`054c5038 00000000`00000000 : nt!KeBugCheckEx
fffff880`05ba4720 fffff880`04ef6e3e : fffff880`054c5038 fffffa80`0ba2d4e0 fffffa80`0a97a110 fffffa80`0b2b2010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`05ba4760 fffff880`04f9ef13 : fffffa80`0ba2d4e0 00000000`00000000 fffffa80`0a97a110 fffffa80`0b2b2010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`05ba4790 fffff880`04fcced6 : fffffa80`ffffffff 00000000`00124ee7 fffff880`05ba48f0 fffffa80`0b2b2010 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`05ba4870 fffff880`04fc8a6c : 00000000`00000000 ffffffff`feced300 fffffa80`0e238310 fffff880`04f9b0a1 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`05ba48b0 fffff880`04fc7679 : fffffa80`0b2b2140 00000000`0003b44c fffffa80`0b2b2010 fffff880`05ba4bc0 : dxgmms1!VidSchiWaitForFence+0xf4
fffff880`05ba49a0 fffff880`04fc7514 : fffff800`00b94080 fffff880`04fc6f3c fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0xe1
fffff880`05ba4b90 fffff880`04fc7012 : 00000000`00000000 fffffa80`07286920 00000000`00000080 fffffa80`0b2b2010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`05ba4bc0 fffff800`0351c73a : 00000000`fffffc32 fffffa80`0b317b50 fffffa80`06fc1040 fffffa80`0b317b50 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`05ba4c00 fffff800`032718e6 : fffff800`033fbe80 fffffa80`0b317b50 fffff800`03409cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`05ba4c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
atikmpag+b038
fffff880`054c5038 4883ec28 sub rsp,28h

SYMBOL_NAME: atikmpag+b038

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME: atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5417612a

FAILURE_BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x116_image_atikmpag.sys

FAILURE_ID_HASH: {83e844bc-fe68-2042-4230-7f5d3e90b48a}

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

Als nächstes habe ich versucht Windows Verifier laufen zu lassen, jedoch fror der Bildschirm sofort nach dem Hochfahren ein.

Nach dem ersten Bluescreen habe ich den Grafikkartentreiber schon aktualisiert.

Ich hoffe ich habe alle Informationen gepostet die ihr braucht und danke im vorraus,

mfg!
 
Wie sehen die Temperaturen aus?
Vielleicht sind die Kühler verschmutzt und die Lautstärke kommt von hohen Lüftergeschwindigkeiten, mit den sich der PC versucht frische Luft zuzuführen.
 
Ich habe mir nun ein Programm geladen welches die Temperatur aufzeichnet und werde es austesten! Verschmutzt sollte der Lüfter aber eigentlich nicht sein, da ich ihn regelmäßig sauge!

mfg
 
die Höchsttemperatur lag nun bei 68 °C, durchschnittlich jedoch bei 63-64°C. Jedoch ist beim Spielstart nun direkt der Amd Anzeigetreiber ausgefallen. Spielabsturz + Browserfenster weiß.

Gibt es irgendeine Hoffnung, dass nicht die Grafikkarte kaputt ist? :(

mfg
 
Stell im CCC das powertarget auf 20+ und in windows die energieeinstellung auf höchstleistung.

Dann teste noch mal.
Welches Netzteil verwendest du?

Mfg
 
wo finde ich denn die powertarget einstellung? ist das beim overdrive die "Leistungsgrenzeinstellung"? Mein Netzteil ist das be quiet! E9-400W 80+ Gold

mfg
 
So mit overclocking hat die graka nun 69-72°C bei belastung. die cpu liegt bei maximal 68 °C. Bisher läuft alles mit overclocking . ich teste es so dann mal weiter!

mfg
 
So heute der nächste x116 Bluescreen.

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


Loading Dump File [C:\Windows\Minidump\113014-6146-01.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.18526.amd64fre.win7sp1_gdr.140706-1506
Machine Name:
Kernel base = 0xfffff800`0321c000 PsLoadedModuleList = 0xfffff800`0345f890
Debug session time: Sun Nov 30 23:16:26.936 2014 (UTC + 1:00)
System Uptime: 0 days 7:31:35.800
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
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800f0894e0, fffff88005340038, 0, 2}

Unable to load image atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+b038 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800f0894e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88005340038, 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:
atikmpag+b038
fffff880`05340038 4883ec28 sub rsp,28h

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.17298 (debuggers(dbg).141024-1500) amd64fre

STACK_TEXT:
fffff880`06382758 fffff880`10af6134 : 00000000`00000116 fffffa80`0f0894e0 fffff880`05340038 00000000`00000000 : nt!KeBugCheckEx
fffff880`06382760 fffff880`10af5e3e : fffff880`05340038 fffffa80`0f0894e0 fffffa80`0da6dd50 fffffa80`07072010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`063827a0 fffff880`10b9df13 : fffffa80`0f0894e0 00000000`00000000 fffffa80`0da6dd50 fffffa80`07072010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`063827d0 fffff880`10bcbed6 : 00000000`ffffffff 00000000`001a8015 fffff880`06382930 fffffa80`07072010 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`063828b0 fffff880`10bc782b : fffffa80`07072010 ffffffff`feced300 00000000`00000000 fffff880`10b9a2fe : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`063828f0 fffff880`10bc619f : fffffa80`07072010 00000000`00000002 fffff880`10bc5f3c 00000000`00000000 : dxgmms1!VidSchiWaitForEmptyHwQueue+0x8f
fffff880`063829e0 fffff880`10bc647a : 00000000`00000000 00000000`00000002 00000000`00000002 fffff880`10bc7bb9 : dxgmms1!VidSchiHandleControlEvent+0x3b
fffff880`06382a10 fffff880`10b992d2 : ffffffff`ff676980 fffffa80`07072010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x23e
fffff880`06382ab0 fffff880`10bc5ff6 : 00000000`00000000 fffffa80`0d977530 00000000`00000080 fffffa80`07072010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`06382bc0 fffff800`0352d73a : 00000000`fffffc32 fffffa80`0abc6b50 fffffa80`06fc1040 fffffa80`0abc6b50 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`06382c00 fffff800`032828e6 : fffff800`0340ce80 fffffa80`0abc6b50 fffff800`0341acc0 fffffa80`099fcda0 : nt!PspSystemThreadStartup+0x5a
fffff880`06382c40 00000000`00000000 : fffff880`06383000 fffff880`0637d000 fffff880`0d73dd40 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
atikmpag+b038
fffff880`05340038 4883ec28 sub rsp,28h

SYMBOL_NAME: atikmpag+b038

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME: atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5417612a

FAILURE_BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x116_image_atikmpag.sys

FAILURE_ID_HASH: {83e844bc-fe68-2042-4230-7f5d3e90b48a}

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800f0894e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88005340038, 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:
atikmpag+b038
fffff880`05340038 4883ec28 sub rsp,28h

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.17298 (debuggers(dbg).141024-1500) amd64fre

STACK_TEXT:
fffff880`06382758 fffff880`10af6134 : 00000000`00000116 fffffa80`0f0894e0 fffff880`05340038 00000000`00000000 : nt!KeBugCheckEx
fffff880`06382760 fffff880`10af5e3e : fffff880`05340038 fffffa80`0f0894e0 fffffa80`0da6dd50 fffffa80`07072010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`063827a0 fffff880`10b9df13 : fffffa80`0f0894e0 00000000`00000000 fffffa80`0da6dd50 fffffa80`07072010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`063827d0 fffff880`10bcbed6 : 00000000`ffffffff 00000000`001a8015 fffff880`06382930 fffffa80`07072010 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`063828b0 fffff880`10bc782b : fffffa80`07072010 ffffffff`feced300 00000000`00000000 fffff880`10b9a2fe : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`063828f0 fffff880`10bc619f : fffffa80`07072010 00000000`00000002 fffff880`10bc5f3c 00000000`00000000 : dxgmms1!VidSchiWaitForEmptyHwQueue+0x8f
fffff880`063829e0 fffff880`10bc647a : 00000000`00000000 00000000`00000002 00000000`00000002 fffff880`10bc7bb9 : dxgmms1!VidSchiHandleControlEvent+0x3b
fffff880`06382a10 fffff880`10b992d2 : ffffffff`ff676980 fffffa80`07072010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x23e
fffff880`06382ab0 fffff880`10bc5ff6 : 00000000`00000000 fffffa80`0d977530 00000000`00000080 fffffa80`07072010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`06382bc0 fffff800`0352d73a : 00000000`fffffc32 fffffa80`0abc6b50 fffffa80`06fc1040 fffffa80`0abc6b50 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`06382c00 fffff800`032828e6 : fffff800`0340ce80 fffffa80`0abc6b50 fffff800`0341acc0 fffffa80`099fcda0 : nt!PspSystemThreadStartup+0x5a
fffff880`06382c40 00000000`00000000 : fffff880`06383000 fffff880`0637d000 fffff880`0d73dd40 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
atikmpag+b038
fffff880`05340038 4883ec28 sub rsp,28h

SYMBOL_NAME: atikmpag+b038

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME: atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5417612a

FAILURE_BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x116_image_atikmpag.sys

FAILURE_ID_HASH: {83e844bc-fe68-2042-4230-7f5d3e90b48a}

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800f0894e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88005340038, 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:
atikmpag+b038
fffff880`05340038 4883ec28 sub rsp,28h

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.17298 (debuggers(dbg).141024-1500) amd64fre

STACK_TEXT:
fffff880`06382758 fffff880`10af6134 : 00000000`00000116 fffffa80`0f0894e0 fffff880`05340038 00000000`00000000 : nt!KeBugCheckEx
fffff880`06382760 fffff880`10af5e3e : fffff880`05340038 fffffa80`0f0894e0 fffffa80`0da6dd50 fffffa80`07072010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`063827a0 fffff880`10b9df13 : fffffa80`0f0894e0 00000000`00000000 fffffa80`0da6dd50 fffffa80`07072010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`063827d0 fffff880`10bcbed6 : 00000000`ffffffff 00000000`001a8015 fffff880`06382930 fffffa80`07072010 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`063828b0 fffff880`10bc782b : fffffa80`07072010 ffffffff`feced300 00000000`00000000 fffff880`10b9a2fe : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`063828f0 fffff880`10bc619f : fffffa80`07072010 00000000`00000002 fffff880`10bc5f3c 00000000`00000000 : dxgmms1!VidSchiWaitForEmptyHwQueue+0x8f
fffff880`063829e0 fffff880`10bc647a : 00000000`00000000 00000000`00000002 00000000`00000002 fffff880`10bc7bb9 : dxgmms1!VidSchiHandleControlEvent+0x3b
fffff880`06382a10 fffff880`10b992d2 : ffffffff`ff676980 fffffa80`07072010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x23e
fffff880`06382ab0 fffff880`10bc5ff6 : 00000000`00000000 fffffa80`0d977530 00000000`00000080 fffffa80`07072010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`06382bc0 fffff800`0352d73a : 00000000`fffffc32 fffffa80`0abc6b50 fffffa80`06fc1040 fffffa80`0abc6b50 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`06382c00 fffff800`032828e6 : fffff800`0340ce80 fffffa80`0abc6b50 fffff800`0341acc0 fffffa80`099fcda0 : nt!PspSystemThreadStartup+0x5a
fffff880`06382c40 00000000`00000000 : fffff880`06383000 fffff880`0637d000 fffff880`0d73dd40 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
atikmpag+b038
fffff880`05340038 4883ec28 sub rsp,28h

SYMBOL_NAME: atikmpag+b038

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME: atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5417612a

FAILURE_BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x116_image_atikmpag.sys

FAILURE_ID_HASH: {83e844bc-fe68-2042-4230-7f5d3e90b48a}

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

Soweit ich weiß kam der Bluescreen nun immer im gleichen Moment. Spiel gespielt (in diesem Fall guildwars2) - Spiel abgestürzt ( x.exe funktioniert nicht mehr) - Spiel erneut gestartet -> Bluescreen
Nach Neustart kann man das jeweilige Spiel dann wieder starten.
 
directX ist auf dem neusten Stand.
Hotfix installiert.

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


Loading Dump File [C:\Windows\Minidump\120114-7020-01.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.18526.amd64fre.win7sp1_gdr.140706-1506
Machine Name:
Kernel base = 0xfffff800`0325e000 PsLoadedModuleList = 0xfffff800`034a1890
Debug session time: Mon Dec 1 16:46:42.813 2014 (UTC + 1:00)
System Uptime: 0 days 2:09:32.526
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
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800e2954e0, fffff880054d2038, 0, 2}

Unable to load image atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+b038 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800e2954e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880054d2038, 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:
atikmpag+b038
fffff880`054d2038 4883ec28 sub rsp,28h

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.17298 (debuggers(dbg).141024-1500) amd64fre

STACK_TEXT:
fffff880`05df8758 fffff880`05324144 : 00000000`00000116 fffffa80`0e2954e0 fffff880`054d2038 00000000`00000000 : nt!KeBugCheckEx
fffff880`05df8760 fffff880`05323e4e : fffff880`054d2038 fffffa80`0e2954e0 fffffa80`0e8492c0 fffffa80`070e2010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`05df87a0 fffff880`0520ffbf : fffffa80`0e2954e0 00000000`00000000 fffffa80`0e8492c0 fffffa80`070e2010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`05df87d0 fffff880`0523deee : 00000000`ffffffff 00000000`0007998e fffff880`05df8930 fffffa80`070e2010 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`05df88b0 fffff880`05239843 : fffffa80`070e2010 ffffffff`feced300 00000000`00000000 0001d43b`0000000a : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`05df88f0 fffff880`052381b7 : fffffa80`070e2010 00000000`00000002 fffff880`05df8a50 fffff880`05df8a40 : dxgmms1!VidSchiWaitForEmptyHwQueue+0x8f
fffff880`05df89e0 fffff880`05238492 : 00000000`00000000 00000000`00000002 0000000a`000005dc fffff880`05239bd1 : dxgmms1!VidSchiHandleControlEvent+0x3b
fffff880`05df8a10 fffff880`0520b2e6 : ffffffff`ff676980 fffffa80`070e2010 00000000`00000080 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x23e
fffff880`05df8ab0 fffff880`0523800e : fffffa80`0e8492c0 fffffa80`0e8492c0 00000000`00000080 fffffa80`070e2010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`05df8bc0 fffff800`0356f73a : 00000000`fffffc32 fffffa80`0b06bb50 fffffa80`06fc1040 fffffa80`0b06bb50 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`05df8c00 fffff800`032c48e6 : fffff880`03965180 fffffa80`0b06bb50 fffff880`0396ffc0 fffffa80`0a8c8c60 : nt!PspSystemThreadStartup+0x5a
fffff880`05df8c40 00000000`00000000 : fffff880`05df9000 fffff880`05df3000 fffff880`0bd7bd40 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
atikmpag+b038
fffff880`054d2038 4883ec28 sub rsp,28h

SYMBOL_NAME: atikmpag+b038

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME: atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5417612a

FAILURE_BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x116_image_atikmpag.sys

FAILURE_ID_HASH: {83e844bc-fe68-2042-4230-7f5d3e90b48a}

Followup: MachineOwner
---------
kam im selben Schema wie vorher. Diesmal bin ich mir sicher dass es aufkeinen Fall an Überhitzung/Überlastung gelegen hat.

Werde dann jetzt den Treiber nochmal löschen und neu drauf packen.

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


Loading Dump File [C:\Windows\Minidump\120214-7675-01.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.18526.amd64fre.win7sp1_gdr.140706-1506
Machine Name:
Kernel base = 0xfffff800`03268000 PsLoadedModuleList = 0xfffff800`034ab890
Debug session time: Tue Dec 2 17:28:58.120 2014 (UTC + 1:00)
System Uptime: 0 days 14:09:45.900
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
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800e0d04e0, fffff88004cbf038, 0, 2}

*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+b038 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800e0d04e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004cbf038, 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:
atikmpag+b038
fffff880`04cbf038 4883ec28 sub rsp,28h

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.17298 (debuggers(dbg).141024-1500) amd64fre

STACK_TEXT:
fffff880`0423e758 fffff880`10343144 : 00000000`00000116 fffffa80`0e0d04e0 fffff880`04cbf038 00000000`00000000 : nt!KeBugCheckEx
fffff880`0423e760 fffff880`10342e4e : fffff880`04cbf038 fffffa80`0e0d04e0 fffffa80`0c33b010 fffffa80`0b32c410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`0423e7a0 fffff880`0f20ffbf : fffffa80`0e0d04e0 00000000`00000000 fffffa80`0c33b010 fffffa80`0b32c410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`0423e7d0 fffff880`0f23deee : 00000000`ffffffff 00000000`0031de1e fffff880`0423e930 fffffa80`0b32c410 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`0423e8b0 fffff880`0f239843 : fffffa80`0b32c410 ffffffff`feced300 00000000`00000000 0000b821`0000000a : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`0423e8f0 fffff880`0f2381b7 : fffffa80`0b32c410 00000000`00000002 fffff880`0423ea50 fffff880`0423ea40 : dxgmms1!VidSchiWaitForEmptyHwQueue+0x8f
fffff880`0423e9e0 fffff880`0f238492 : 00000000`00000000 00000000`00000002 0000000a`000005dc fffff880`0f239bd1 : dxgmms1!VidSchiHandleControlEvent+0x3b
fffff880`0423ea10 fffff880`0f20b2e6 : ffffffff`ff676980 fffffa80`0b32c410 00000000`00000080 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x23e
fffff880`0423eab0 fffff880`0f23800e : fffffa80`0c33b010 fffffa80`0c33b010 00000000`00000080 fffffa80`0b32c410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`0423ebc0 fffff800`0357973a : 00000000`fffffc32 fffffa80`0b343b50 fffffa80`06f58890 fffffa80`0b343b50 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`0423ec00 fffff800`032ce8e6 : fffff800`03458e80 fffffa80`0b343b50 fffff800`03466cc0 fffffa80`0a474840 : nt!PspSystemThreadStartup+0x5a
fffff880`0423ec40 00000000`00000000 : fffff880`0423f000 fffff880`04239000 fffff880`0a519d40 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
atikmpag+b038
fffff880`04cbf038 4883ec28 sub rsp,28h

SYMBOL_NAME: atikmpag+b038

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME: atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5417612a

FAILURE_BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x116_image_atikmpag.sys

FAILURE_ID_HASH: {83e844bc-fe68-2042-4230-7f5d3e90b48a}

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

Selbes Schema Browser Fenster nach dem Spielabsturz weiß. :/

mfg
 
Tritt das Problem nur bei Browser Spielen auf?

Wenn ja, deaktiviere im Browser (zumindest testweise) die Hardwarebeschleunigung.

Wenn das Problem auch bei nicht-Browser-Spielen auftritt, ändere im Bios folgende Einstellung:
Menü "M.I.T" -> "Miscellaneous Settings" -> PEG Gen3 Slot Configuration" -> von [AUTO] auf [Gen2] ändern.
Änderungen im Bios abspeichern (F10 Taste). Testen, ob Probleme bleiben.

Poste außerdem noch ein paar Screenshots von CPU-Z (Reiter Mainboard, CPU, Memory und SPD), sowie einen Screenshot von GPU-Z.
 
Du musst dich einloggen oder registrieren, um hier zu antworten.

Ähnliche Themen

D
Probleme mit Bluescreen 0x00000116
Antworten
18
Aufrufe
2K
Misanthrop68
Misanthrop68
J
PC startet nicht nach Bluescreen
Antworten
9
Aufrufe
2K
Janulo95
J
M
PC fährt nicht mehr hoch
Antworten
10
Aufrufe
1K
Misanthrop68
Misanthrop68
R
Bluescreen-Fehlermeldung "PAGE_FAULT_IN_NONPAGED_AREA" Fehler: nvlddmkm.sys
Antworten
7
Aufrufe
1K
Misanthrop68
Misanthrop68
V
Spiele stürzen ab, was ist die Ursache ?
2
Antworten
26
Aufrufe
7K
Hellhammer
Hellhammer
Oben Unten
Zurück