Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- 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 (8 procs) Free x64
- Product: WinNt, suite: TerminalServer SingleUserTS
- Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
- Machine Name:
- Kernel base = 0xfffff800`03002000 PsLoadedModuleList = 0xfffff800`032456d0
- Debug session time: Mon Apr 7 21:51:43.418 2014 (UTC - 4:00)
- System Uptime: 0 days 3:31:39.604
- *******************************************************************************
- * *
- * Bugcheck Analysis *
- * *
- *******************************************************************************
- VIDEO_TDR_FAILURE (116)
- Attempt to reset the display driver and recover from timeout failed.
- Arguments:
- Arg1: fffffa800b04a010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
- Arg2: fffff88011e09e2c, 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+9bbe2c
- fffff880`11e09e2c 803db68aeeff00 cmp byte ptr [nvlddmkm+0x8a48e9 (fffff880`11cf28e9)],0
- DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
- BUGCHECK_STR: 0x116
- PROCESS_NAME: System
- CURRENT_IRQL: 0
- STACK_TEXT:
- fffff880`041e6a48 fffff880`12103140 : 00000000`00000116 fffffa80`0b04a010 fffff880`11e09e2c ffffffff`c000009a : nt!KeBugCheckEx
- fffff880`041e6a50 fffff880`120d6867 : fffff880`11e09e2c fffffa80`09fe1000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
- fffff880`041e6a90 fffff880`12102f4f : fffffa80`ffffd84d ffffffff`fffe7960 fffffa80`0b04a010 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
- fffff880`041e6b40 fffff880`121d203d : fffffa80`0b155360 00000000`00000080 00000000`00000000 fffffa80`09fe0410 : dxgkrnl!TdrResetFromTimeout+0x23
- fffff880`041e6bc0 fffff800`033142ea : 00000000`02c9867e fffffa80`0a00e060 fffffa80`06ce4230 fffffa80`0a00e060 : dxgmms1!VidSchiWorkerThread+0x101
- fffff880`041e6c00 fffff800`030688e6 : fffff800`031f2e80 fffffa80`0a00e060 fffff800`03200cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
- fffff880`041e6c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
- STACK_COMMAND: .bugcheck ; kb
- FOLLOWUP_IP:
- nvlddmkm+9bbe2c
- fffff880`11e09e2c 803db68aeeff00 cmp byte ptr [nvlddmkm+0x8a48e9 (fffff880`11cf28e9)],0
- SYMBOL_NAME: nvlddmkm+9bbe2c
- FOLLOWUP_NAME: MachineOwner
- MODULE_NAME: nvlddmkm
- IMAGE_NAME: nvlddmkm.sys
- DEBUG_FLR_IMAGE_TIMESTAMP: 5315b408
- 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