Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

watchdog.sys error


  • Please log in to reply

#1
wavjr

wavjr

    New Member

  • Member
  • Pip
  • 1 posts
Each time I try to access a video while on-line my computer locks and I get the screen error:

STOP: 0x0000008E (0xE0000001, 0xBA3D8925,0xAC3D7820, 0x00000000)

watchdog.sys - Address BA3D8925 base at BA3D8000, DateStamp 480254ab

I can restart the machine and it seems to run fine until I try to access a video function. I have no idea how to attack this problem and any help would be greatly appreciated!

I did some checking and saw the whocrashed suggestion. Here is that analysis:



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

computer name: D2C63QG1
windows version: Windows XP Service Pack 3, 5.1, build: 2600
windows dir: C:\WINDOWS
CPU: GenuineIntel Intel® Core™2 Duo CPU E8300 @ 2.83GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 2145492992 total
VM: 2147352576, free: 2034814976



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

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.


On Mon 2/28/2011 1:13:39 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini022711-03.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x925)
Bugcheck code: 0x1000008E (0xFFFFFFFFE0000001, 0xFFFFFFFFBA3D8925, 0xFFFFFFFFAC3D7820, 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 Mon 2/28/2011 12:50:46 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini022711-02.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x925)
Bugcheck code: 0x1000008E (0xFFFFFFFFE0000001, 0xFFFFFFFFBA430925, 0xFFFFFFFFAE014820, 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 Mon 2/28/2011 12:35:09 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini022711-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x925)
Bugcheck code: 0x1000008E (0xFFFFFFFFE0000001, 0xFFFFFFFFBA418925, 0xFFFFFFFFAC6EA820, 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 2/26/2011 8:53:09 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini022611-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x925)
Bugcheck code: 0x1000008E (0xFFFFFFFFE0000001, 0xFFFFFFFFBA430925, 0xFFFFFFFFACD57820, 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 Tue 12/29/2009 10:53:58 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini122909-01.dmp
This was probably caused by the following module: ati2cqag.dll (ati2cqag+0x141BF)
Bugcheck code: 0xEA (0xFFFFFFFF89D936E0, 0xFFFFFFFF89E2F308, 0xFFFFFFFF89DFCAB8, 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

Edited by wavjr, 27 February 2011 - 10:13 PM.

  • 0

Advertisements


#2
Spyderturbo007

Spyderturbo007

    Member

  • Member
  • PipPipPip
  • 760 posts
Take a look at this thread and see if it helps with your problem. Also, the 0x0000008E BSOD is typically related to a driver and I see the following in your last crash dump, so you might want to look at updating your device drivers.

This can typically be done either through Windows Update, or the PC manufacturers' website.

Edited by Spyderturbo007, 01 March 2011 - 08:36 AM.

  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP