--------------------------------------------------------------------------------
computer name: SAKIL-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: Intel, Intel Corporation, DG41WV
CPU: GenuineIntel Pentium® Dual-Core CPU E6600 @ 3.06GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 3418890240 total
VM: 2147352576, free: 1946140672
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 1/15/2014 12:08:10 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011514-39889-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x8D0FF)
Bugcheck code: 0x116 (0xFFFFFFFF8578F510, 0xFFFFFFFF918289B0, 0x0, 0xC)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Tue 1/14/2014 4:54:17 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011414-15085-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x8D0FF)
Bugcheck code: 0x116 (0xFFFFFFFF85D85510, 0xFFFFFFFF918239B0, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
