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 Bluescreen of death!


  • Please log in to reply

#1
jjsimmons

jjsimmons

    New Member

  • Member
  • Pip
  • 1 posts
From WhoCrashed (which has only caught 1 of the 4 last crashes)

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

computer name: MR-A
windows version: Windows XP Service Pack 3, 5.1, build: 2600
windows dir: I:\WINDOWS
CPU: GenuineIntel Intel® Core™2 Duo CPU E6850 @ 3.00GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 3218989056 total
VM: 2147352576, free: 2050490368



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

Crash dump directory: I:\WINDOWS\Minidump

Crash dumps are enabled on your computer.


On Tue 6/14/2011 10:10:57 PM GMT your computer crashed
crash dump file: I:\WINDOWS\Minidump\Mini061411-01.dmp
uptime: 08:33:21
This was probably caused by the following module: watchdog.sys (watchdog+0x925)
Bugcheck code: 0x1000008E (0xFFFFFFFFE0000001, 0xFFFFFFFFF781F925, 0xFFFFFFFFACF78820, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: I:\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.



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

1 crash dumps have been found and analyzed.
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.


Thanks in advance!

Edited by jjsimmons, 14 June 2011 - 04:25 PM.

  • 0

Advertisements







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