New
#1
BSOD BBCode 116 - DMP file result
Hi,
I started to have problems with BlueScreen last night. It's happen everytime than I use a CG Software or play some game.
Im attaching the 3 DMP results to help th diagnotic:
On Thu 09/02/2012 23:56:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020912-11247-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x116 (0xFFFFFA800ADD44E0, 0xFFFFF88011274AE4, 0xFFFFFFFFC000009A, 0x4)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Thu 09/02/2012 23:56:30 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x116 (0xFFFFFA800ADD44E0, 0xFFFFF88011274AE4, 0xFFFFFFFFC000009A, 0x4)
Error: VIDEO_TDR_ERROR
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Thu 09/02/2012 23:51:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020912-11668-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FA3A)
Bugcheck code: 0x116 (0xFFFFFA800AFE0010, 0xFFFFF8801124CAE4, 0xFFFFFFFFC000009A, 0x4)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.