Watchdog folder found in the Windows/logfile folder

[SkyBum]

I was preparing to do a fresh windows install and while I was backing up pertinent files and folders I came across a folder named Watchdog in my C:\WINDOWS\LogFiles\Watchdog.

The files in the folder are labeled in the format: "041230_0613_01.wdl" etc. Anyone care to speculate on what app these files are specific to?

Thanks....

SkyBum

 

[SkyBum]

Well a bit more searching showed me how to open the logfile in notepad and I get this message (which is very interesting because ive been experiencing frequent system hangs) can anyone make some sense of this?


//
// Watchdog Event Log File
//

LogType: Watchdog
Created: 2004-12-30 06:13:21
TimeZone: 480 - Pacific Standard Time
WindowsVersion: XP
EventType: 0xEA - Thread Stuck in Device Driver

//
// The driver for the display device got stuck in an infinite loop. This
// usually indicates a problem with the device itself or with the device
// driver programming the hardware incorrectly. Please check with your
// display device vendor for any driver updates.
//

EaRecovery: 1
ShutdownCount: 12
Shutdown: 0
EventFlag: 1
EventCount: 1
BreakCount: 1
BugcheckTriggered: 1
DebuggerNotPresent: 1
DriverName: ati2dvag
DeviceClass: Display
DeviceDescription: RADEON X800 XT (Omega 2.5.97a)
HardwareID: PCI\VEN_1002&DEV_5D57&SUBSYS_00441043&REV_00
Manufacturer: ATI Technologies Inc. (Omega 2.5.97a)
DriverFixedFileInfo: FEEF04BD 00010000 0006000E 000A1961 0006000E 000A1961 0000003F 00000008 00040004 00000003 00000004 00000000 00000000
DriverCompanyName: ATI Technologies Inc.
DriverFileDescription: ATI Radeon WindowsNT Display Driver
DriverFileVersion: 6.14.10.6497
DriverInternalName: ati2dvag.dll
DriverLegalCopyright: Copyright (C) 1998-2004 ATI Technologies Inc.
DriverOriginalFilename: ati2dvag.dll
DriverProductName: ATI Radeon WindowsNT Display Driver
DriverProductVersion: 6.14.10.6497

 

[n0cmonkey]

watchdog is typically a term for a process that monitors other processes, or in this case the ATI driver. If something goes wrong, a lot of times a watchdog may reset the machine or perform other actions...