Sign in with
Sign up | Sign in
Your question

BSOD ATI 6770 and crappy fps

Last response: in Graphics & Displays
Share
July 29, 2011 3:03:45 PM

I keep getting the BSOD on startup.
Used DriverSweeper to get rid of the old version of my video drivers. Installed newest drivers from ATI (version 11.7) and when it finished there's a yellow question mark at the top of the screen like something didn't install properly but when I looked at the log it provides there were no errors listed.

Played Rift last night at 30+ fps logged in today and stuck at 5 fps.


Crash dump logs from WhoCrashed:

System Information (local)
--------------------------------------------------------------------------------

computer name: AJ-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU E8500 @ 3.16GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 8588353536 total
VM: 2147352576, free: 1923670016



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Fri 7/29/2011 2:37:53 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072911-25942-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0x79C8)
Bugcheck code: 0x116 (0xFFFFFA800909D010, 0xFFFFF88002E079C8, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport Driver
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
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: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
Google query: atikmpag.sys Advanced Micro Devices, Inc. VIDEO_TDR_ERROR




On Fri 7/29/2011 2:37:53 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl!TdrResetFromTimeout+0x214)
Bugcheck code: 0x116 (0xFFFFFA800909D010, 0xFFFFF88002E079C8, 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 Fri 7/29/2011 2:36:10 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072911-25053-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x122F)
Bugcheck code: 0x119 (0x1, 0x2, 0x9, 0x8)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
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 Fri 7/29/2011 12:55:01 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072811-13462-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x122F)
Bugcheck code: 0x119 (0x1, 0x2, 0x9, 0x8)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
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 Thu 7/28/2011 3:07:13 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072811-13774-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x122F)
Bugcheck code: 0x119 (0x1, 0x2, 0x9, 0x8)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
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 Thu 7/28/2011 1:50:05 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072811-16707-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x122F)
Bugcheck code: 0x119 (0x1, 0x2, 0x9, 0x8)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
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.



--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

6 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
July 31, 2011 11:31:17 AM

Nothing?

I've tried multiple video drivers 11.7 11.6 11.5 nothing seems to work.
m
0
l
July 31, 2011 11:39:08 AM

try running program called memtest86. bad memory module also leads to BSOD
m
0
l
Related resources
August 1, 2011 2:53:14 PM

I'll run the mem test asap. Here's my logfile from Hijackthis.

Logfile of Trend Micro HijackThis v2.0.4
Scan saved at 10:51:27 AM, on 8/1/2011
Platform: Windows 7 SP1 (WinNT 6.00.3505)
MSIE: Internet Explorer v9.00 (9.00.8112.16421)
Boot mode: Normal

Running processes:
C:\Program Files (x86)\Lavasoft\Ad-Aware\AAWTray.exe
C:\Program Files (x86)\Ideazon\ZEngine\Zboard.exe
C:\Program Files (x86)\Trend Micro\HiJackThis\HiJackThis.exe

R1 - HKCU\Software\Microsoft\Internet Explorer\Main,Search Page = http://go.microsoft.com/fwlink/?LinkId=54896
R0 - HKCU\Software\Microsoft\Internet Explorer\Main,Start Page = http://go.microsoft.com/fwlink/?LinkId=69157
R1 - HKLM\Software\Microsoft\Internet Explorer\Main,Default_Page_URL = http://go.microsoft.com/fwlink/?LinkId=69157
R1 - HKLM\Software\Microsoft\Internet Explorer\Main,Default_Search_URL = http://go.microsoft.com/fwlink/?LinkId=54896
R1 - HKLM\Software\Microsoft\Internet Explorer\Main,Search Page = http://go.microsoft.com/fwlink/?LinkId=54896
R0 - HKLM\Software\Microsoft\Internet Explorer\Main,Start Page = http://go.microsoft.com/fwlink/?LinkId=69157
R0 - HKLM\Software\Microsoft\Internet Explorer\Search,SearchAssistant =
R0 - HKLM\Software\Microsoft\Internet Explorer\Search,CustomizeSearch =
R0 - HKLM\Software\Microsoft\Internet Explorer\Main,Local Page = C:\Windows\SysWOW64\blank.htm
R1 - HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings,ProxyOverride = *.local
R0 - HKCU\Software\Microsoft\Internet Explorer\Toolbar,LinksFolderName =
F2 - REG:system.ini: UserInit=userinit.exe
O1 - Hosts: ::1 localhost
O2 - BHO: (no name) - {0CDE258C-FCE7-4817-8910-46FF0170814d} - (no file)
O2 - BHO: AcroIEHelperStub - {18DF081C-E8AD-4283-A596-FA578C2EBDC3} - C:\Program Files (x86)\Common Files\Adobe\Acrobat\ActiveX\AcroIEHelperShim.dll
O2 - BHO: Spybot-S&D IE Protection - {53707962-6F74-2D53-2644-206D7942484F} - C:\PROGRA~2\SPYBOT~1\SDHelper.dll
O2 - BHO: Windows Live ID Sign-in Helper - {9030D464-4C02-4ABF-8ECC-5164760863C6} - C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live\WindowsLiveLogin.dll
O2 - BHO: Windows Live Messenger Companion Helper - {9FDDE16B-836F-4806-AB1F-1455CBEFF289} - C:\Program Files (x86)\Windows Live\Companion\companioncore.dll
O2 - BHO: Java(tm) Plug-In 2 SSV Helper - {DBC80044-A445-435b-BC74-9C25C1C588A9} - C:\Program Files (x86)\Java\jre6\bin\jp2ssv.dll
O4 - HKLM\..\Run: [Zboard] C:\Program Files (x86)\Ideazon\ZEngine\Zboard.exe
O4 - HKLM\..\Run: [StartCCC] "C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static\CLIStart.exe" MSRun
O4 - HKCU\..\Run: [SUPERAntiSpyware] C:\Program Files\SUPERAntiSpyware\SUPERAntiSpyware.exe
O4 - HKCU\..\Run: [uTorrent] "C:\Program Files (x86)\uTorrent\uTorrent.exe"
O4 - HKUS\S-1-5-19\..\Run: [Sidebar] %ProgramFiles%\Windows Sidebar\Sidebar.exe /autoRun (User 'LOCAL SERVICE')
O4 - HKUS\S-1-5-19\..\RunOnce: [mctadmin] C:\Windows\System32\mctadmin.exe (User 'LOCAL SERVICE')
O4 - HKUS\S-1-5-20\..\Run: [Sidebar] %ProgramFiles%\Windows Sidebar\Sidebar.exe /autoRun (User 'NETWORK SERVICE')
O4 - HKUS\S-1-5-20\..\RunOnce: [mctadmin] C:\Windows\System32\mctadmin.exe (User 'NETWORK SERVICE')
O9 - Extra button: @C:\Program Files (x86)\Windows Live\Companion\companionlang.dll,-600 - {0000036B-C524-4050-81A0-243669A86B9F} - C:\Program Files (x86)\Windows Live\Companion\companioncore.dll
O9 - Extra button: @C:\Program Files (x86)\Windows Live\Writer\WindowsLiveWriterShortcuts.dll,-1004 - {219C3416-8CB2-491a-A3C7-D9FCDDC9D600} - C:\Program Files (x86)\Windows Live\Writer\WriterBrowserExtension.dll
O9 - Extra 'Tools' menuitem: @C:\Program Files (x86)\Windows Live\Writer\WindowsLiveWriterShortcuts.dll,-1003 - {219C3416-8CB2-491a-A3C7-D9FCDDC9D600} - C:\Program Files (x86)\Windows Live\Writer\WriterBrowserExtension.dll
O9 - Extra button: (no name) - {DFB852A3-47F8-48C4-A200-58CAB36FD2A2} - C:\PROGRA~2\SPYBOT~1\SDHelper.dll
O9 - Extra 'Tools' menuitem: Spybot - Search & Destroy Configuration - {DFB852A3-47F8-48C4-A200-58CAB36FD2A2} - C:\PROGRA~2\SPYBOT~1\SDHelper.dll
O10 - Unknown file in Winsock LSP: c:\program files (x86)\common files\microsoft shared\windows live\wlidnsp.dll
O10 - Unknown file in Winsock LSP: c:\program files (x86)\common files\microsoft shared\windows live\wlidnsp.dll
O11 - Options group: [ACCELERATED_GRAPHICS] Accelerated graphics
O18 - Protocol: wlpg - {E43EF6CD-A37A-4A9B-9E6F-83F89B8E6324} - C:\Program Files (x86)\Windows Live\Photo Gallery\AlbumDownloadProtocolHandler.dll
O23 - Service: @%SystemRoot%\system32\Alg.exe,-112 (ALG) - Unknown owner - C:\Windows\System32\alg.exe (file missing)
O23 - Service: AMD External Events Utility - Unknown owner - C:\Windows\system32\atiesrxx.exe (file missing)
O23 - Service: @%SystemRoot%\system32\efssvc.dll,-100 (EFS) - Unknown owner - C:\Windows\System32\lsass.exe (file missing)
O23 - Service: @%systemroot%\system32\fxsresm.dll,-118 (Fax) - Unknown owner - C:\Windows\system32\fxssvc.exe (file missing)
O23 - Service: @keyiso.dll,-100 (KeyIso) - Unknown owner - C:\Windows\system32\lsass.exe (file missing)
O23 - Service: Lavasoft Ad-Aware Service - Lavasoft Limited - C:\Program Files (x86)\Lavasoft\Ad-Aware\AAWService.exe
O23 - Service: Logitech Bluetooth Service (LBTServ) - Logitech, Inc. - C:\Program Files\Common Files\LogiShrd\Bluetooth\lbtserv.exe
O23 - Service: @comres.dll,-2797 (MSDTC) - Unknown owner - C:\Windows\System32\msdtc.exe (file missing)
O23 - Service: @%SystemRoot%\System32\netlogon.dll,-102 (Netlogon) - Unknown owner - C:\Windows\system32\lsass.exe (file missing)
O23 - Service: @%systemroot%\system32\psbase.dll,-300 (ProtectedStorage) - Unknown owner - C:\Windows\system32\lsass.exe (file missing)
O23 - Service: @%systemroot%\system32\Locator.exe,-2 (RpcLocator) - Unknown owner - C:\Windows\system32\locator.exe (file missing)
O23 - Service: @%SystemRoot%\system32\samsrv.dll,-1 (SamSs) - Unknown owner - C:\Windows\system32\lsass.exe (file missing)
O23 - Service: SAS Core Service (SASCORE) - SUPERAntiSpyware.com - C:\Program Files\SUPERAntiSpyware\SASCORE64.EXE
O23 - Service: @%SystemRoot%\system32\snmptrap.exe,-3 (SNMPTRAP) - Unknown owner - C:\Windows\System32\snmptrap.exe (file missing)
O23 - Service: @%systemroot%\system32\spoolsv.exe,-1 (Spooler) - Unknown owner - C:\Windows\System32\spoolsv.exe (file missing)
O23 - Service: @%SystemRoot%\system32\sppsvc.exe,-101 (sppsvc) - Unknown owner - C:\Windows\system32\sppsvc.exe (file missing)
O23 - Service: Steam Client Service - Valve Corporation - C:\Program Files (x86)\Common Files\Steam\SteamService.exe
O23 - Service: @%SystemRoot%\system32\ui0detect.exe,-101 (UI0Detect) - Unknown owner - C:\Windows\system32\UI0Detect.exe (file missing)
O23 - Service: @%SystemRoot%\system32\vaultsvc.dll,-1003 (VaultSvc) - Unknown owner - C:\Windows\system32\lsass.exe (file missing)
O23 - Service: @%SystemRoot%\system32\vds.exe,-100 (vds) - Unknown owner - C:\Windows\System32\vds.exe (file missing)
O23 - Service: @%systemroot%\system32\vssvc.exe,-102 (VSS) - Unknown owner - C:\Windows\system32\vssvc.exe (file missing)
O23 - Service: @%SystemRoot%\system32\Wat\WatUX.exe,-601 (WatAdminSvc) - Unknown owner - C:\Windows\system32\Wat\WatAdminSvc.exe (file missing)
O23 - Service: @%systemroot%\system32\wbengine.exe,-104 (wbengine) - Unknown owner - C:\Windows\system32\wbengine.exe (file missing)
O23 - Service: @%Systemroot%\system32\wbem\wmiapsrv.exe,-110 (wmiApSrv) - Unknown owner - C:\Windows\system32\wbem\WmiApSrv.exe (file missing)
O23 - Service: @%PROGRAMFILES%\Windows Media Player\wmpnetwk.exe,-101 (WMPNetworkSvc) - Unknown owner - C:\Program Files (x86)\Windows Media Player\wmpnetwk.exe (file missing)

--
End of file - 7698 bytes
m
0
l
August 1, 2011 3:06:36 PM

Every time I install any version of the video driver for HD 6xxx series there are always warnings like something didn't install properly. It even happened when I used the drivers that were on the packaged CD.
m
0
l
August 1, 2011 11:16:15 PM

Ran memtest86 came back with zero errors after 5 passes.
m
0
l
August 2, 2011 7:01:42 AM

what power supply make/model are you running? maybe it is inadequate. Also, remove the video card from the slot, then re-seat it firmly in the slot. Sometimes the contacts dont make a good connection.
m
0
l
August 2, 2011 3:17:37 PM

CORSAIR Enthusiast Series CMPSU-550VX 550W ATX12V V2.2 SLI Ready CrossFire Ready 80 PLUS Certified Active PFC Compatible with Core i7 Power Supply

Fans: 1 x 120mm Double ball-bearing fan
Main Connector: 20+4Pin
+12V Rails: Single
PCI-Express Connector: 1 x 6-Pin, 1 x 6+2-Pin
Model #: CMPSU-550VX
Item #: N82E16817139004
Return Policy: Standard Return Policy
m
0
l
August 2, 2011 4:02:55 PM

iam2thecrowe said:
what power supply make/model are you running? maybe it is inadequate. Also, remove the video card from the slot, then re-seat it firmly in the slot. Sometimes the contacts dont make a good connection.


Removed the card from the slot and re-seated it. Still getting BSOD.


--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Tue 8/2/2011 3:57:03 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080211-20264-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x122F)
Bugcheck code: 0x119 (0x1, 0x2, 0x9, 0x8)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
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 Tue 8/2/2011 3:57:03 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0x50AA)
Bugcheck code: 0x119 (0x1, 0x2, 0x9, 0x8)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\Windows\system32\drivers\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport 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: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
Google query: atikmpag.sys Advanced Micro Devices, Inc. VIDEO_SCHEDULER_INTERNAL_ERROR




On Tue 8/2/2011 2:56:30 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080211-17097-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x122F)
Bugcheck code: 0x119 (0x1, 0x2, 0x9, 0x8)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
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 Tue 8/2/2011 5:42:08 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080211-28345-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x122F)
Bugcheck code: 0x119 (0x1, 0x2, 0x9, 0x8)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
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 Tue 8/2/2011 5:27:23 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080211-28314-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x122F)
Bugcheck code: 0x119 (0x1, 0x2, 0x9, 0x8)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
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 Mon 8/1/2011 3:10:29 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080111-29577-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x122F)
Bugcheck code: 0x119 (0x1, 0x2, 0x9, 0x8)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
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 Mon 8/1/2011 2:07:45 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080111-17799-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x122F)
Bugcheck code: 0x119 (0x1, 0x2, 0x9, 0x8)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
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 Sun 7/31/2011 11:22:14 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\073111-14164-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x122F)
Bugcheck code: 0x119 (0x1, 0x2, 0x9, 0x8)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
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 Sun 7/31/2011 2:34:23 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\073011-15397-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x122F)
Bugcheck code: 0x119 (0x1, 0x2, 0x9, 0x8)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
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 Fri 7/29/2011 2:37:53 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072911-25942-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0x79C8)
Bugcheck code: 0x116 (0xFFFFFA800909D010, 0xFFFFF88002E079C8, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport Driver
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
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: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
Google query: atikmpag.sys Advanced Micro Devices, Inc. VIDEO_TDR_ERROR




On Fri 7/29/2011 2:36:10 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072911-25053-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x122F)
Bugcheck code: 0x119 (0x1, 0x2, 0x9, 0x8)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
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 Fri 7/29/2011 12:55:01 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072811-13462-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x122F)
Bugcheck code: 0x119 (0x1, 0x2, 0x9, 0x8)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
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 Thu 7/28/2011 3:07:13 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072811-13774-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x122F)
Bugcheck code: 0x119 (0x1, 0x2, 0x9, 0x8)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
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 Thu 7/28/2011 1:50:05 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072811-16707-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x122F)
Bugcheck code: 0x119 (0x1, 0x2, 0x9, 0x8)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
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.


The following dump files were found but could not be read. These files may be corrupt:
C:\Windows\Minidump\073011-15444-01.dmp
C:\Windows\Minidump\073011-31356-01.dmp




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

On your computer a total of 16 crash dumps have been found. Only 14 could be analyzed. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.


m
0
l
August 2, 2011 5:05:21 PM

Sounds like a defective video card, I'd think about RMAing that card for a replacement asap, and if the issue persists with the new one then it maybe something with the motherboard. Have you done any OCing on this system in the past ? That can cause things to become unstable and your get some of the weirdest issues from a bad OC.
m
0
l
August 2, 2011 5:27:31 PM

kaitheus said:
Sounds like a defective video card, I'd think about RMAing that card for a replacement asap, and if the issue persists with the new one then it maybe something with the motherboard. Have you done any OCing on this system in the past ? That can cause things to become unstable and your get some of the weirdest issues from a bad OC.


Ok I'll do a RMA. I've never overclocked anything on my PC.
m
0
l
August 2, 2011 11:11:54 PM

first try using Driversweeper following all the instructions to use it properly, it removes all traces of any drivers and registry entries. Then only install the latest whql driver. give that a shot, then RMA the card.
m
0
l
August 3, 2011 6:13:11 AM

iam2thecrowe said:
first try using Driversweeper following all the instructions to use it properly, it removes all traces of any drivers and registry entries. Then only install the latest whql driver. give that a shot, then RMA the card.


I've used DriverCleaner.net and even SlimDrivers to update everything on my PC. The 11.4 drivers actually installed properly (got the green thumbs up symbol instead of the yellow question mark) and played RIFT at 30+ fps. Got home from the bar tonight and RIFT only runs a 1-7 fps. What the hell gives with this card and its drivers?
m
0
l
August 3, 2011 6:30:14 AM

did you notice the watchdog.sys in your crash dump file?
that is a windows system file having to do with display drivers
read this
http://msdn.microsoft.com/en-us/library/ff553890.aspx
you can disable this by using REGEDIT
then try running install again

be careful if you have never used regedit before
do some reading on it

EDIT- try doing the stuff on my next post FIRST
m
0
l
August 3, 2011 6:35:17 AM

this is drivers for win7 64-bit
http://sites.amd.com/us/game/downloads/Pages/radeon_win...
this is drivers for win 7 32bit
http://sites.amd.com/us/game/downloads/Pages/radeon_win...

also try uninstalling old drivers from SAFE mode
and running install package as administrator

also go into device manager and uninstall whatever display driver currently and then
reboot and let it install again
it should be a Microsoft WDM driver for your card
if not then use Microsoft update to get the MS WDM driver for the card
and then install the CCC driver
m
0
l
August 3, 2011 7:32:31 PM

king smp said:
this is drivers for win7 64-bit
http://sites.amd.com/us/game/downloads/Pages/radeon_win...
this is drivers for win 7 32bit
http://sites.amd.com/us/game/downloads/Pages/radeon_win...

also try uninstalling old drivers from SAFE mode
and running install package as administrator

also go into device manager and uninstall whatever display driver currently and then
reboot and let it install again
it should be a Microsoft WDM driver for your card
if not then use Microsoft update to get the MS WDM driver for the card
and then install the CCC driver


I can't boot it in safe mode. When that option comes up after a BSOD the keyboard doesn't work. I've restarted and hit F8 and nothing happens.

I haven't tried installing as an admin.

Temps are at 27 degrees Celsius at Idle. Temps were 30 after playing RIFT for 5-10 min at the crap 1-7 fps.
m
0
l
August 3, 2011 9:27:12 PM

hit the F8 over and over during post so that the tower is beeping
if mobo has speaker

every computer can boot into safe mode
just keep hitting f8 as computer is starting

also go into device manager and uninstall whatever display driver currently and then
reboot and let it install again
it should be a Microsoft WDM driver for your card
if not then use Microsoft update to get the MS WDM driver for the card
and then install the CCC driver
m
0
l
August 4, 2011 4:42:37 AM

king smp said:
hit the F8 over and over during post so that the tower is beeping
if mobo has speaker

every computer can boot into safe mode
just keep hitting f8 as computer is starting

also go into device manager and uninstall whatever display driver currently and then
reboot and let it install again
it should be a Microsoft WDM driver for your card
if not then use Microsoft update to get the MS WDM driver for the card
and then install the CCC driver



I can't boot into safe mode at all. I spam hit F8 as soon as the PC restarts until it totally boots up but I don't get any prompt for safe mode or anything. It's like the keyboard isn't there. My keyboard only lights up right when the Motherboard screen is there for a few seconds then the lights on the keyboard go out until the Windows logo appears. During the Motherboard screen there's the options to go into BIOS and Xpress Recovery etc, but F8 Safe Mode isn't one of them.
m
0
l
August 4, 2011 5:14:41 AM

also go into device manager and uninstall whatever display driver currently and then
reboot and let it install again
it should be a Microsoft WDM driver for your card
if not then use Microsoft update to get the MS WDM driver for the card
and then install the CCC driver


did you try that yet?
m
0
l
August 4, 2011 10:29:31 AM

king smp said:
also go into device manager and uninstall whatever display driver currently and then
reboot and let it install again
it should be a Microsoft WDM driver for your card
if not then use Microsoft update to get the MS WDM driver for the card
and then install the CCC driver


did you try that yet?


Yes I've done that multiple times. Every time but once the driver failed to install properly. It worked once using the 11.4 drivers and lasted until I restarted my computer then I was right back to BSOD.
m
0
l
August 4, 2011 10:40:42 AM

if you havn't tried driversweeper yet, then do that following all instructions. really dont car if you have tried DriverCleaner.net and even SlimDrivers, they are not driversweeper and dont do the same thing. If you are unwilling to take advice just RMA the card.
m
0
l
August 4, 2011 11:54:44 AM

iam2thecrowe said:
if you havn't tried driversweeper yet, then do that following all instructions. really dont car if you have tried DriverCleaner.net and even SlimDrivers, they are not driversweeper and dont do the same thing. If you are unwilling to take advice just RMA the card.


I have used driversweeper and tried installing as admin but nothing works. The drivers seem to always fail to install properly, or when it did install that one time correctly it gets corrupted and then fails.
m
0
l
August 4, 2011 12:10:25 PM

INF file was not found when I try to install the drivers.
m
0
l
August 4, 2011 7:22:20 PM

contact AMD support since I have been seeing issues other than you with AMD drivers with the HD 6xxx series
m
0
l
September 30, 2011 5:51:49 PM

FYI - Same sort of issues:

Win7
Radeon 6950 HD 2m crossfire
i5 2500k
GigaByte GA-Z68A-D3H-B3 Intel Z68
Corsair CMPSU-850TXV2

Basically going through your same motions...
m
0
l
!