XP SP3 BSOD Watchdog.sys error

Dell INSPIRON 1520
October 2, 2011 at 20:11:41
Specs: Windows XP, 3GB
I am currently getting a B.S.O.D. on my Windows XP SP3 machine. It happens quite randomly....the computer will lockup then suddenly display the BSOD with a 'Watchdog.sys' error.

I've updated Windows and updated the Video Driver (from memory I think its a nVidia) to the latest.

Any suggestions before I do a complete wipe and reinstall?

caso1992


See More: XP SP3 BSOD Watchdog.sys error

Report •

#1
October 3, 2011 at 12:51:32
It's usually driver-related but not necessarily the video driver.
Any third-party driver could be responsible so re-install or update each one in turn, testing between each driver update to see if the problem re-occurs.


Report •

#2
October 4, 2011 at 05:52:38
Hi,

Download, and install WhoCrashed: http://www.resplende...rashedSetup.exe
Open it, click Analyze button.
WhoCrashed will create report.
Copy, and paste it into your next reply.


Report •

#3
October 5, 2011 at 14:57:29
I'm going into work today, so I will be able to get the report for you then

caso1992


Report •

Related Solutions

#4
October 5, 2011 at 21:30:49
This is from one of our computers, that has been crashing....this is not the watchdog.sys one but....I will post that one later.

****OFFICE2*****
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.


On Wed 2/03/2011 3:47:41 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini030211-01.dmp
This was probably caused by the following module: ati2cqag.dll (ati2cqag+0xABF0)
Bugcheck code: 0xEA (0xFFFFFFFF88E63A08, 0xFFFFFFFF8A97C290, 0xFFFFFFFF8A660C10, 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 Tue 15/02/2011 3:54:41 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini021511-01.dmp
This was probably caused by the following module: ati2cqag.dll (ati2cqag+0x16D24)
Bugcheck code: 0xEA (0xFFFFFFFF86ACB020, 0xFFFFFFFF894DDEC8, 0xFFFFFFFF893A73F8, 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

caso1992


Report •

#5
October 5, 2011 at 21:45:44
This is the watchdog.sys BSOD

*****POS2******
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.


On Thu 15/09/2011 8:52:20 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini091511-01.dmp
This was probably caused by the following module: vserial.sys (vserial+0x2ABF)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFA9B3DABF, 0xFFFFFFFFA8AA0454, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\vserial.sys
product: ELTIMA Virtual Serial Ports
company: ELTIMA Software
description: Virtual Serial Port 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.
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: vserial.sys (Virtual Serial Port Driver, ELTIMA Software).
Google query: vserial.sys ELTIMA Software KERNEL_MODE_EXCEPTION_NOT_HANDLED_M


On Sun 21/08/2011 3:49:00 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini082111-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x925)
Bugcheck code: 0x1000008E (0xFFFFFFFFE0000001, 0xFFFFFFFFBA3C0925, 0xFFFFFFFFA9326820, 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 Thu 11/08/2011 7:39:42 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini081111-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x925)
Bugcheck code: 0x1000008E (0xFFFFFFFFE0000001, 0xFFFFFFFFBA3B8925, 0xFFFFFFFFAA1D8820, 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 23/07/2011 3:28:52 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini072311-01.dmp
This was probably caused by the following module: vserial.sys (vserial+0x9A2C)
Bugcheck code: 0x100000D1 (0x60, 0x2, 0x0, 0xFFFFFFFFAA83BA2C)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\vserial.sys
product: ELTIMA Virtual Serial Ports
company: ELTIMA Software
description: Virtual Serial Port Driver
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: vserial.sys (Virtual Serial Port Driver, ELTIMA Software).
Google query: vserial.sys ELTIMA Software CUSTOM_ERROR

caso1992


Report •

Ask Question