Running a i5-3570k with 8 gb of ram, Samsung 830 SSD. Windows 7 ult x64.
No particular activity seems to be the trigger, if someone could take a look of the dump, I'd appreciate it greatly.
Please let me know if any additional information is required.
Everything on the hardware side is up to date as of last week, i'll check for updates
Your dump shows problem with your graphic cards driver.
Code:2: kd> lmvm atikmpag start end module name fffff880`03a00000 fffff880`03a55000 atikmpag T (no symbols) Loaded symbol image file: atikmpag.sys Image path: atikmpag.sys Image name: atikmpag.sys Timestamp: Wed Feb 15 08:13:12 2012 (4F3B14B8) CheckSum: 00051BFD ImageSize: 00055000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 Mini Kernel Dump does not contain unloaded driver list
- Download and install Driver Sweeper:
|MG| Driver Fusion (Driver Sweeper) 1.2.0 Download
- Download the auto-detect tool for AMD.
- Boot into Safe Mode from Advanced Boot Options:
- Type in Driver Fusion in Search
- Remove all components of your ATI drivers
- Boot normally now, and install the latest drivers from the
auto-detect program you downloaded.
Now you have the latest drivers installed for your
graphic card.
Time for a test with Furmark:
Monitor the temp during the test using speccy:
For more information and similar to your case:
BSOD Index
Code:Microsoft (R) Windows Debugger Version 6.12.0002.633 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Yusra\Downloads\SF_excal\SF_23-09-2012\092212-5709-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*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 Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850 Machine Name: Kernel base = 0xfffff800`02c66000 PsLoadedModuleList = 0xfffff800`02eabe90 Debug session time: Sat Sep 22 05:05:54.267 2012 (UTC + 6:00) System Uptime: 0 days 0:23:12.454 Loading Kernel Symbols ............................................................... ................................................................ ............................. Loading User Symbols Mini Kernel Dump does not contain unloaded driver list ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 117, {fffffa80090ab010, fffff88003a079e0, 0, 0} *** 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+79e0 ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* VIDEO_TDR_TIMEOUT_DETECTED (117) The display driver failed to respond in timely fashion. (This code can never be used for real bugcheck). Arguments: Arg1: fffffa80090ab010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff88003a079e0, The pointer into responsible device driver module (e.g owner tag). Arg3: 0000000000000000, The secondary driver specific bucketing key. Arg4: 0000000000000000, Optional internal context dependent data. Debugging Details: ------------------ FAULTING_IP: atikmpag+79e0 fffff880`03a079e0 ?? ??? DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_TIMEOUT TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b CUSTOMER_CRASH_COUNT: 1 BUGCHECK_STR: 0x117 PROCESS_NAME: System CURRENT_IRQL: 0 STACK_TEXT: fffff880`021c74f0 fffff880`041065f7 : fffffa80`090ab010 fffff880`04152ec4 fffffa80`090ab010 fffff880`040d4843 : watchdog!WdDbgReportRecreate+0xa3 fffff880`021c7a10 fffff880`041072bc : fffff8a0`049bb220 fffff8a0`049bb220 00000000`00000080 fffffa80`090ab010 : dxgkrnl!TdrUpdateDbgReport+0xcb fffff880`021c7a60 fffff880`040db6b3 : 00000000`00000001 fffffa80`07dcc000 00000000`00000000 fffff880`000000a9 : dxgkrnl!TdrCollectDbgInfoStage2+0x220 fffff880`021c7a90 fffff880`04107e0f : 00000000`0000000f ffffffff`fffe7960 fffffa80`090ab010 00000000`0000000f : dxgkrnl!DXGADAPTER::Reset+0xef fffff880`021c7b40 fffff880`041d6ec1 : fffffa80`081ead50 00000000`00000080 00000000`00000000 fffffa80`067fb010 : dxgkrnl!TdrResetFromTimeout+0x23 fffff880`021c7bc0 fffff800`02f83cce : 00000000`00ebc809 fffffa80`067f9210 fffffa80`066d5b30 fffffa80`067f9210 : dxgmms1!VidSchiWorkerThread+0x101 fffff880`021c7c00 fffff800`02cd7fe6 : fffff800`02e58e80 fffffa80`067f9210 fffff800`02e66cc0 fffff880`01245384 : nt!PspSystemThreadStartup+0x5a fffff880`021c7c40 00000000`00000000 : fffff880`021c8000 fffff880`021c2000 fffff880`0bf20790 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: .bugcheck ; kb FOLLOWUP_IP: atikmpag+79e0 fffff880`03a079e0 ?? ??? SYMBOL_NAME: atikmpag+79e0 FOLLOWUP_NAME: MachineOwner MODULE_NAME: atikmpag IMAGE_NAME: atikmpag.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4f3b14b8 FAILURE_BUCKET_ID: X64_0x117_IMAGE_atikmpag.sys BUCKET_ID: X64_0x117_IMAGE_atikmpag.sys Followup: MachineOwner ---------
Quote