Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- Primary Analysis
- Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
- Online Crash Dump Analysis Service
- See http://www.osronline.com for more information
- Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
- Product: WinNt, suite: TerminalServer SingleUserTS
- Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
- Machine Name:
- Kernel base = 0xfffff800`02c04000 PsLoadedModuleList = 0xfffff800`02e476d0
- Debug session time: Sun May 11 08:59:33.900 2014 (UTC - 4:00)
- System Uptime: 0 days 0:12:24.837
- *******************************************************************************
- * *
- * Bugcheck Analysis *
- * *
- *******************************************************************************
- VIDEO_TDR_FAILURE (116)
- Attempt to reset the display driver and recover from timeout failed.
- Arguments:
- Arg1: fffffa80091084e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
- Arg2: fffff8800f9dd6f4, The pointer into responsible device driver module (e.g. owner tag).
- Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
- Arg4: 0000000000000004, Optional internal context dependent data.
- Debugging Details:
- ------------------
- TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
- FAULTING_IP:
- nvlddmkm+9cc6f4
- fffff880`0f9dd6f4 48ff2555b2edff jmp qword ptr [nvlddmkm+0x8a7950 (fffff880`0f8b8950)]
- DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
- BUGCHECK_STR: 0x116
- PROCESS_NAME: System
- CURRENT_IRQL: 0
- STACK_TEXT:
- fffff880`03ff7a48 fffff880`0fd44140 : 00000000`00000116 fffffa80`091084e0 fffff880`0f9dd6f4 ffffffff`c000009a : nt!KeBugCheckEx
- fffff880`03ff7a50 fffff880`0fd17867 : fffff880`0f9dd6f4 fffffa80`08cdb000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
- fffff880`03ff7a90 fffff880`0fd43f4f : fffffa80`ffffd84d 00000000`00000000 fffffa80`091084e0 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
- fffff880`03ff7b40 fffff880`06fd303d : fffffa80`071f3010 00000000`00000080 00000000`00000000 fffffa80`07e17410 : dxgkrnl!TdrResetFromTimeout+0x23
- fffff880`03ff7bc0 fffff800`02f162ea : 00000000`fffffc32 fffffa80`087a4b50 fffffa80`0667c890 fffffa80`087a4b50 : dxgmms1!VidSchiWorkerThread+0x101
- fffff880`03ff7c00 fffff800`02c6a8e6 : fffff800`02df4e80 fffffa80`087a4b50 fffff800`02e02cc0 fffffa80`06778b50 : nt!PspSystemThreadStartup+0x5a
- fffff880`03ff7c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
- STACK_COMMAND: .bugcheck ; kb
- FOLLOWUP_IP:
- nvlddmkm+9cc6f4
- fffff880`0f9dd6f4 48ff2555b2edff jmp qword ptr [nvlddmkm+0x8a7950 (fffff880`0f8b8950)]
- SYMBOL_NAME: nvlddmkm+9cc6f4
- FOLLOWUP_NAME: MachineOwner
- MODULE_NAME: nvlddmkm
- IMAGE_NAME: nvlddmkm.sys
- DEBUG_FLR_IMAGE_TIMESTAMP: 533349c9
- FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
- BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
- Followup: MachineOwner
- ---------
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement