Windows 7 - Toshiba P305-S8820 BSOD VIDEO_TDR_ERROR

I just upgraded from Vista to Windows 7 32 bit (clean install) and I receive the following error message. Any idea how I can fix this issue?


System Information (local) computer name: TTWRK1
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU T5550 @ 1.83GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 3219578880 total
VM: 2147352576, free: 1972510720


Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Wed 7/27/2011 5:37:14 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072611-39671-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x8CC26)
Bugcheck code: 0x116 (0xFFFFFFFF85DAA510, 0xFFFFFFFF90810B86, 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 which cannot be identified at this time.


On Wed 7/27/2011 5:37:14 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl!TdrCreateRecoveryContext+0x1F2)
Bugcheck code: 0x116 (0xFFFFFFFF85DAA510, 0xFFFFFFFF90810B86, 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 which cannot be identified at this time.


On Wed 7/27/2011 5:34:25 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072611-41137-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x8CC26)
Bugcheck code: 0x116 (0xFFFFFFFF859CC510, 0xFFFFFFFF9020FB86, 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 which cannot be identified at this time.

Thanks.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.



To ensure minidumps are enabled:

Go to Start, in the Search Box type: sysdm.cpl, press Enter.
Under the Advanced tab, click on the Startup and Recovery Settings... button.
Ensure that Automatically restart is unchecked.
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
OK your way out.
Reboot if changes have been made.

I just attached two mini dump files for research.

Thanks.

Attachment 167181

Attachment 167182

"It's not a true crash, in the sense that the bluescreen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception.

Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OSs like XP to crash.

As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds.

If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.

If playing with video driver versions hasn't helped, make sure the box is not overheating.

Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU.

Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference.

If so, it might be as simple as dust buildup and subsequently inadequate cooling.

I would download cpu-z and gpu-z (both free) and keep an eye on the video temps Let us know if you need help STOP 0x116: VIDEO_TDR_ERROR troubleshooting

When I ran GPU, it immediately BSOD. This is now showing up after I don't run anything. I just boot up, login, and don't do anything it will BSOD.

I now get the following error.
On Thu 7/28/2011 2:06:23 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072811-46581-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x17F89)
Bugcheck code: 0x119 (0x1, 0x1F3E, 0x1F40, 0x1F3F)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: ATI Technologies Inc.
description: ATI Radeon Kernel Mode Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.).
Google query: atikmdag.sys ATI Technologies Inc. VIDEO_SCHEDULER_INTERNAL_ERROR

Attachment 167348

This one probably this.

STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg