Proszę o opis problemu. Poniżej wklejam dane z programu WinDbg.
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\012712-23353-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0340f000 PsLoadedModuleList = 0xfffff800`03654670
Debug session time: Fri Jan 27 18:38:13.077 2012 (GMT+1)
System Uptime: 0 days 8:45:48.623
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa800513d010, fffff88005329c80, 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+6c80 )
Followup: MachineOwner
---------
5: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800513d010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88005329c80, 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+6c80
fffff880`05329c80 4883ec28 sub rsp,28h
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`02557308 fffff880`03068000 : 00000000`00000116 fffffa80`0513d010 fffff880`05329c80 00000000`00000000 : nt!KeBugCheckEx
fffff880`02557310 fffff880`03067d0a : fffff880`05329c80 fffffa80`0513d010 fffffa80`04ea0d50 fffffa80`083ef410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`02557350 fffff880`0310ef07 : fffffa80`0513d010 00000000`00000000 fffffa80`04ea0d50 fffffa80`083ef410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`02557380 fffff880`0313cd5a : fffffa80`ffffffff 00000000`001edb31 fffff880`025574d0 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`02557460 fffff880`03122bb1 : fffffa80`084cf000 ffffffff`feced300 00000000`00000002 fffff880`025577d8 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`025574a0 fffff880`03125aaf : 00000000`0001fa80 00000000`00000000 fffffa80`07322020 fffff8a0`0bd5de50 : dxgmms1!VIDMM_GLOBAL::xWaitForAllEngines+0x1e9
fffff880`025575a0 fffff880`031241a0 : fffff8a0`0bd5de50 00000000`00000000 fffffa80`084cf000 fffff880`02557690 : dxgmms1!VIDMM_GLOBAL::SetupForBuildPagingBuffer+0xd7
fffff880`025575e0 fffff880`031240f6 : 00000000`00000000 00000000`00000001 fffffa80`084cf000 fffff880`03122a1e : dxgmms1!VIDMM_GLOBAL::UnmapVideoApertureSegmentInternal+0x34
fffff880`02557770 fffff880`0312d642 : fffffa80`07fc0910 00000000`00000001 00000000`00000001 fffff800`03490f32 : dxgmms1!VIDMM_GLOBAL::UnmapVideoApertureSegment+0x13e
fffff880`025577e0 fffff880`0312d3eb : fffff8a0`0bd5de50 00000000`00001000 fffffa80`07fc0910 fffff8a0`0bd5de50 : dxgmms1!VIDMM_APERTURE_SEGMENT::UnmapApertureRange+0x7a
fffff880`02557830 fffff880`0312cd8f : fffff8a0`0bd5de50 fffffa80`084cfc80 00000000`00000000 fffffa80`084cfc80 : dxgmms1!VIDMM_APERTURE_SEGMENT::UnmapTemporaryResource+0x9b
fffff880`02557890 fffff880`0312076c : fffffa80`084cf000 fffffa80`084cf000 fffffa80`084cfc80 fffffa80`084cf000 : dxgmms1!VIDMM_APERTURE_SEGMENT::ReleaseTemporaryResource+0xcf
fffff880`025578d0 fffff880`0311d133 : 00000000`00000000 00000000`00000000 00000000`0000000d fffffa80`084cf000 : dxgmms1!VIDMM_GLOBAL::EvictTemporaryAllocations+0xbc
fffff880`02557910 fffff880`0313765d : 00000000`00000000 fffff8a0`03738ab0 fffffa80`00000000 fffffa80`0503a650 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x69f
fffff880`02557ae0 fffff880`03137398 : fffff880`009ed040 fffff880`03136d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`02557cd0 fffff880`03136e96 : 00000000`00000000 fffffa80`084ccc70 00000000`00000080 fffffa80`083ef410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`02557d00 fffff800`03726fee : 00000000`fffffc32 fffffa80`07fa5a10 fffffa80`03c6e9e0 fffffa80`07fa5a10 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`02557d40 fffff800`0347d5e6 : fffff880`009e8180 fffffa80`07fa5a10 fffff880`009f30c0 fffff880`0160fcb0 : nt!PspSystemThreadStartup+0x5a
fffff880`02557d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
atikmpag+6c80
fffff880`05329c80 4883ec28 sub rsp,28h
SYMBOL_NAME: atikmpag+6c80
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: atikmpag
IMAGE_NAME: atikmpag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4c2aa271
FAILURE_BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys
BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys
Followup: MachineOwner
---------
5: kd>
Błąd BlueScreen VIDEO_TDR_FAILURE (116)
-
- Posty: 1
- Rejestracja: 28 sty 2012, 11:37
Błąd BlueScreen VIDEO_TDR_FAILURE (116)
Ostatnio zmieniony 28 sty 2012, 12:22 przez cosik_ktosik, łącznie zmieniany 1 raz.
Powód: Zmiana tytułu
Powód: Zmiana tytułu
- djkamil09061991
- Posty: 8250
- Rejestracja: 18 lut 2009, 11:54
- Lokalizacja: Wrocław
- Kontaktowanie:
Błąd BlueScreen
Problemem jest sterownik do grafiki ATI, odinstaluj aktualny i zainstaluj inną wersję, nie koniecznie najnowszy musi być najlepszy.
Mój kanał YouTube - Dostępne tylko dla zarejestrowanych użytkowników
Przyjmuje skiny Cs Go: Dostępne tylko dla zarejestrowanych użytkowników
Przyjmuje skiny Cs Go: Dostępne tylko dla zarejestrowanych użytkowników
-
- Reklama
Kto jest online
Użytkownicy przeglądający to forum: Obecnie na forum nie ma żadnego zarejestrowanego użytkownika i 4 gości