[SeaGoddess3240]

Hello;

I have been having BSOD issues with my computer for approximately the last month or so. I would get a Blue Screen whenever I would try to watch an online video. Watching videos off-line on my Media Player was not a problem. The error message I would get was a watchdog.sys. I tried running virus scans, fixing the registry - everything I could think of. Yet, the Blue Screen returned whenever I tried to watch a video.

Earlier this afternoon, I found some advice on this wonderful Geeks to Go forum that the watchdog.sys could be caused by an outdated driver. I downloaded PC Pitstop, which told me that my ATI Radeon HD 2400 was out of date and needed updating. I found the website, downloaded the update, and VOILA! I could watch videos again.

My joy was short lived, however, as not even an hour later I'm getting another Blue Screen - this one at random websites, not related to video. This BS tells me that ATI2DVAG = "The device driver got stuck in an infinite loop. This usually indicates a problem with the device itself or with device driven programming hardware incorrectly..."

UPDATE: Since no one is responding to my request, and there had been some changes since I originally posted this, I created another topic this morning (I'm pretty desperate). So, apparently someone at Geeks to Go didn't like that and they locked that topic (Thanks alot, guys).

Here is what it said:

I was getting a Watchdog.sys error message; I then upgraded to the most current version of ATI, which made it even worse (ATI2DVAG infinite loop error message). Now, I'm back to the original ATI version that came with my computer and I'm still getting a BSOD frequently. Is there a version that may be a year or so old that may work? My computer keeps crashing and it's driving me crazy.

Does anyone have any advice on which update version has the least problems, and where I can find it? And is ATI Catalyst the same thing as what I'm trying to upgrade?

Any advice would be greatly appreciated.

Oh, by the way, I am running Windows XP, with an AMD Phenom Quad 4 Processor

Thank you!

Edited by SeaGoddess3240, 27 March 2011 - 08:55 AM.

[Advertisements]

Firstly

So, apparently someone at Geeks to Go didn't like that and they locked that topic (Thanks alot, guys).]

It was explained to you by a Moderator why the other post was closed.
To put the issue in prespective for you:
We're all volunteers here, even the owner of the site does this for fun and because he likes helping people out. We all have other things to do other than work here, but we choose to offer as much help as possible when we do have spare time. and we do it for free.

If you haven't noticed this forum has close to 2,000,000 posts and almost 330,000 members. That's a lot to keep up with. Sometimes something/someone will slip through the cracks.

Add to the sheer volume of posts, the fact that not everyone is a specialist in every aspect of computer support and the number of things that might go a few days without an answer grows.


AND you did not wait, very long, before the duplicate post.




That all said, to attempt to assist -


Download this please
http://www.resplendence.com/whocrashed

Run the program, click the analyse tab and scroll down as indicated for the results.

Please then copy and paste just the crash dump analysis to your reply

Edited by Macboatmaster, 27 March 2011 - 04:30 PM.

[Macboatmaster]

Firstly

So, apparently someone at Geeks to Go didn't like that and they locked that topic (Thanks alot, guys).]

It was explained to you by a Moderator why the other post was closed.
To put the issue in prespective for you:
We're all volunteers here, even the owner of the site does this for fun and because he likes helping people out. We all have other things to do other than work here, but we choose to offer as much help as possible when we do have spare time. and we do it for free.

If you haven't noticed this forum has close to 2,000,000 posts and almost 330,000 members. That's a lot to keep up with. Sometimes something/someone will slip through the cracks.

Add to the sheer volume of posts, the fact that not everyone is a specialist in every aspect of computer support and the number of things that might go a few days without an answer grows.


AND you did not wait, very long, before the duplicate post.




That all said, to attempt to assist -


Download this please
http://www.resplendence.com/whocrashed

Run the program, click the analyse tab and scroll down as indicated for the results.

Please then copy and paste just the crash dump analysis to your reply

Edited by Macboatmaster, 27 March 2011 - 04:30 PM.

[SeaGoddess3240]

First of all, I apologize if I came across upset. I'm not upset at anyone, just frustrated with my situation because I do a lot of work off of this computer. That being said, this is my first time at the forums and I didn't realize how it worked. I thought if I posted more than once, I'd get a response sooner. That's how it is at other forums I frequent, so I'm sorry I seemed impatient.

Now, back to the matter at hand... I am back to my orignial problem, which is "Watchdog.sys" error message and an inability to play video online. Here are my WhoCrashed results:

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

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.


On Sun 3/27/2011 12:44:02 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini032711-02.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x925)
Bugcheck code: 0x1000008E (0xFFFFFFFFE0000001, 0xFFFFFFFFBA3C8925, 0xFFFFFFFFA90F6820, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 3/27/2011 3:16:06 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini032711-01.dmp
This was probably caused by the following module: ati2cqag.dll (ati2cqag+0x191AF)
Bugcheck code: 0xEA (0xFFFFFFFF88442BA0, 0xFFFFFFFF8AD14BE0, 0xFFFFFFFF8AD04EC0, 0x1)
Error: THREAD_STUCK_IN_DEVICE_DRIVER
file path: C:\WINDOWS\system32\ati2cqag.dll
product: ATI Radeon Family
company: ATI Technologies Inc.
description: Central Memory Manager / Queue Server Module
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: ati2cqag.dll (Central Memory Manager / Queue Server Module, ATI Technologies Inc.).
Google query: ati2cqag.dll ATI Technologies Inc. THREAD_STUCK_IN_DEVICE_DRIVER




On Sun 3/27/2011 1:35:18 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini032611-04.dmp
This was probably caused by the following module: ati2cqag.dll (ati2cqag+0x191BD)
Bugcheck code: 0xEA (0xFFFFFFFF899CFDA8, 0xFFFFFFFF8AA16008, 0xFFFFFFFF8AD12EE0, 0x1)
Error: THREAD_STUCK_IN_DEVICE_DRIVER
file path: C:\WINDOWS\system32\ati2cqag.dll
product: ATI Radeon Family
company: ATI Technologies Inc.
description: Central Memory Manager / Queue Server Module
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: ati2cqag.dll (Central Memory Manager / Queue Server Module, ATI Technologies Inc.).
Google query: ati2cqag.dll ATI Technologies Inc. THREAD_STUCK_IN_DEVICE_DRIVER




On Sat 3/26/2011 8:06:13 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini032611-03.dmp
This was probably caused by the following module: ati2cqag.dll (ati2cqag+0x1926F)
Bugcheck code: 0xEA (0xFFFFFFFF876BA920, 0xFFFFFFFF896A5568, 0xFFFFFFFF89696738, 0x1)
Error: THREAD_STUCK_IN_DEVICE_DRIVER
file path: C:\WINDOWS\system32\ati2cqag.dll
product: ATI Radeon Family
company: ATI Technologies Inc.
description: Central Memory Manager / Queue Server Module
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: ati2cqag.dll (Central Memory Manager / Queue Server Module, ATI Technologies Inc.).
Google query: ati2cqag.dll ATI Technologies Inc. THREAD_STUCK_IN_DEVICE_DRIVER




On Sat 3/26/2011 3:59:07 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini032611-02.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x925)
Bugcheck code: 0x1000008E (0xFFFFFFFFE0000001, 0xFFFFFFFFBA3D8925, 0xFFFFFFFFA9A87820, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 Sat 3/26/2011 1:25:19 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini032611-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x925)
Bugcheck code: 0x1000008E (0xFFFFFFFFE0000001, 0xFFFFFFFFBA460925, 0xFFFFFFFFAA044820, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 3/25/2011 10:06:27 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini032511-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x925)
Bugcheck code: 0x1000008E (0xFFFFFFFFE0000001, 0xFFFFFFFFBA350925, 0xFFFFFFFFAA03E820, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 3/25/2011 1:43:39 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini032411-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x925)
Bugcheck code: 0x1000008E (0xFFFFFFFFE0000001, 0xFFFFFFFFBA468925, 0xFFFFFFFFA8B66820, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 3/23/2011 10:51:07 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini032311-02.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x925)
Bugcheck code: 0x1000008E (0xFFFFFFFFE0000001, 0xFFFFFFFFBA400925, 0xFFFFFFFFA95B7820, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 3/23/2011 12:25:50 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini032311-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x925)
Bugcheck code: 0x1000008E (0xFFFFFFFFE0000001, 0xFFFFFFFFBA468925, 0xFFFFFFFFA9EE0820, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 3/23/2011 1:53:15 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini032211-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x925)
Bugcheck code: 0x1000008E (0xFFFFFFFFE0000001, 0xFFFFFFFFBA438925, 0xFFFFFFFFA8AB4820, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 3/20/2011 9:10:31 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini032011-03.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x925)
Bugcheck code: 0x1000008E (0xFFFFFFFFE0000001, 0xFFFFFFFFBA410925, 0xFFFFFFFFA96F4820, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 3/20/2011 8:52:00 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini032011-02.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x925)
Bugcheck code: 0x1000008E (0xFFFFFFFFE0000001, 0xFFFFFFFFBA3F0925, 0xFFFFFFFFA8F0C820, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 3/20/2011 3:21:19 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini032011-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x925)
Bugcheck code: 0x1000008E (0xFFFFFFFFE0000001, 0xFFFFFFFFBA468925, 0xFFFFFFFFA8E58820, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 3/20/2011 12:37:01 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini031911-03.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x925)
Bugcheck code: 0x1000008E (0xFFFFFFFFE0000001, 0xFFFFFFFFBA418925, 0xFFFFFFFFA9F79820, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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.


Thank you kindly for your help!

[Macboatmaster]

Firstly please see this and reinstall that driver for the ATi Radeon HD2400
These are the instructions.
When downloading and installing, please disable your anti-virus.
PLEASE REMEMBER to reactivate it afterwards
http://support.amd.c...teDriverXP.aspx

and here is the driver
http://support.amd.c...Home&rev=11.1#1
either the complete package or you can select the link indivdual downloads.

NOTE if this is a branded computer please do not use this link I have given you UNLESS you know it is an added ATI Radeon HD2400.
The reason being that many branded computers use a version of the ATI made especially for the OEM.
If that is the case go to your computer manufacturers site and obtain the driver from there.

If you have Adobe Flash Player installed see this link and download the latest version
That is 10.2.153.1
http://get.adobe.com/flashplayer/
Again note the caution re the anti-virus
The download can be apparently successful but is affected by the AV

Here is the procedure for resolving difficulties in the installation of flash player
http://kb2.adobe.com...1/tn_19166.html


IF THESE suggestions do not solve the issue run a full chkdsk - that is on start, run type "cmd" at the prompt type "chkdsk C: /r"
agree to run on restart. Do so please.
Then go Control Panel, Administrative Tools, Event Viewer, Application on left pane and scroll to the first Winlogon entry from the top.
Double click that entry and that will be the chkdsk results.
If you are in any doubt about what they show - below the up and down arrow is the copy symbol - left click and then right click to paste on your reply.

Also pls go Start, right click My Computer , click properties and on the system properties that open , click the hardware tab, then the device manager button, then on the view tab click to show hidden devices and examine any warning indicators - yellow or red.

Edited by Macboatmaster, 28 March 2011 - 07:41 PM.

[SeaGoddess3240]

Hi there!

Thank you for the information.

I do actually have a branded Computer. I have a Gateway GM5664. To further complicate matters, when I purchased the computer almost 3 years ago, due to Vista's numerous issues, I had Vista removed and XP put on it (from my previous computer).

I did go to the Gateway site to look at the drivers. I found the ATI/AMD driver, but it appears to be for Vista (since it was preloaded on the computer). I'm assuming that I can't use those drivers for XP?

I will download the new flash player and report the status once that's done.

Thanks!

[Macboatmaster]

I suggest you try this one
http://support.amd.c...x?&lang=English

driver only

Edited by Macboatmaster, 29 March 2011 - 05:18 PM.

[SeaGoddess3240]

Hi, Mac;

I installed the driver... and so far, so good. VIDEO! NO BLUE SCREEN! Keeping my fingers crossed, I will keep an eye on it for a few days and update you as it goes.

Thanks so much!

[Macboatmaster]

Pleased it appears to have worked.
So that if you do get another crash we are not then looking at old crash reports could you please go Windows, open Minidump folder and delete the dumps in there.
Then anything new will make it so much easier to follow - for you.
In case it does not blue screen but you receive error messages, here is event viewer which will make it easy for you to see those

Change the dates please to as required to cover the problem

• Please download the Event Viewer Tool by Vino Rosso VEW and save it to your Desktop:
• Double-click VEW.exe
• Under 'Select log to query', select (as appropriate):
  • Application
  • System
• Under 'Select type to list', select (as appropriate):
  • Error PLEASE SELECT ONLY THE ERROR type for event log at first. It makes it so much easier to interpret. I will ask for the others if needed.
    
  • Information
  • Warning

Then use the 'Date of events' or 'Number of events' as follows:

Either:

• Click the radio button for 'Number of events'
  Type 3 in the 1 to 20 box (or any number from 1 to 20)
  Then click the Run button.
  Notepad will open with the output log.
• Click the radio button for 'Date of events'
  In the From: boxes type today's date (presuming the crash happened today) say a week ago pls.
  In the To: boxes type today's date (presuming the crash happened today) 01.04..2011 - changing the date of course as appropriate
  Then click the Run button.
  Notepad will open with the output log.

Edited by Macboatmaster, 01 April 2011 - 12:54 PM.