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 Blue Screen


  • Please log in to reply

#61
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts

0x000000EA: THREAD_STUCK_IN_DEVICE_DRIVER
(Click to consult the online Win XP Resource Kit article.)
A device driver problem has caused the system to pause indefinitely (hang). Typically, this is caused by a display driver waiting for the video hardware to enter an idle state. This might indicate a hardware problem with the video adapter, or a faulty video driver.


Oh boy another issue pops up.
OK lets see if we can fix this.
Reboot and tap F8 to enter the Advance Boot Menu
Using your arrows highlight the line that says Use Last Known Good Configuration and then click Enter
See if the system will now boot up normally.
  • 0

Advertisements


#62
chantal7

chantal7

    Member

  • Topic Starter
  • Member
  • PipPip
  • 59 posts
It seems to boot up normally just fine. It didn't have any issues after I clicked restart when I got the blue screen. I know exactly how to make this blue screen appear. I just have to run these programs: Google Chrome, Windows Media Player, Microsoft Word, Diablo. Probably a lot for a computer to run with but still shouldn't give me that issue right?
  • 0

#63
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
The only one that would stress the system really is Diablo. The others are standard programs which really don't use much memory or stress the video card.
This happened on a reboot correct and not a crash from within windows?
  • 0

#64
chantal7

chantal7

    Member

  • Topic Starter
  • Member
  • PipPip
  • 59 posts
The blue screen appeared while I was on Diablo. It was a crash while I was doing things on the computer.

Edited by chantal7, 27 March 2011 - 11:25 PM.

  • 0

#65
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Hmm ok that might be a good thing then.
Can you run a new BlueScreen View report and use today's date for the to and from entries.
  • 0

#66
chantal7

chantal7

    Member

  • Topic Starter
  • Member
  • PipPip
  • 59 posts
I have BlueScreenView open (it appears blank), where do I enter the date?

I have read through this topic again and I can't even find where I did this the first time... I hope it's not because I am tired. :D

Edited by chantal7, 27 March 2011 - 11:42 PM.

  • 0

#67
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Sorry it's late here so I was thinking of the wrong program. :D Just run a new log and attach it in your next post.
  • 0

#68
chantal7

chantal7

    Member

  • Topic Starter
  • Member
  • PipPip
  • 59 posts
It's okay, it's late here too!

I don't see anything when I open the Bluescreenview. But with WhoCrashed it says this:


On Wed 3/16/2011 4:22:26 AM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x8E (0xFFFFFFFFC0000047, 0xFFFFFFFF804FCF44, 0xFFFFFFFFBA4D7A58, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a kernel-mode application generated an exception that the error handler did not catch.
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: Unknown .
Google query: Unknown KERNEL_MODE_EXCEPTION_NOT_HANDLED

Or did you mean this log?


Vino's Event Viewer v01c run on Windows XP in English
Report run at 27/03/2011 11:47:22 PM

Note: All dates below are in the format dd/mm/yyyy

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 27/03/2011 11:00:32 PM
Type: error Category: 0
Event: 7000 Source: Service Control Manager
The adfs service failed to start due to the following error: The system cannot find the file specified.

Log: 'System' Date/Time: 27/03/2011 11:00:32 PM
Type: error Category: 0
Event: 7000 Source: Service Control Manager
The Parallel port driver service failed to start due to the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

Log: 'System' Date/Time: 27/03/2011 11:00:14 PM
Type: error Category: 2
Event: 55 Source: Ntfs
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume J:.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - information Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 27/03/2011 11:01:53 PM
Type: information Category: 0
Event: 7035 Source: Service Control Manager
The MpKslb953f45b service was successfully sent a start control.

Log: 'System' Date/Time: 27/03/2011 11:00:50 PM
Type: information Category: 0
Event: 7036 Source: Service Control Manager
The Computer Browser service entered the stopped state.

Log: 'System' Date/Time: 27/03/2011 11:00:49 PM
Type: information Category: 0
Event: 7036 Source: Service Control Manager
The IMAPI CD-Burning COM Service service entered the stopped state.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 27/03/2011 11:46:18 PM
Type: warning Category: 0
Event: 51 Source: Disk
An error was detected on device \Device\Harddisk1\D during a paging operation.

Log: 'System' Date/Time: 27/03/2011 9:40:40 PM
Type: warning Category: 0
Event: 51 Source: Disk
An error was detected on device \Device\Harddisk1\D during a paging operation.

Log: 'System' Date/Time: 27/03/2011 8:45:33 PM
Type: warning Category: 0
Event: 51 Source: Disk
An error was detected on device \Device\Harddisk1\D during a paging operation.

Edited by chantal7, 27 March 2011 - 11:48 PM.

  • 0

#69
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Go to

Start and then to Run
Type in Chkdsk /r Note the space between k and /
Click Enter ...It will probably ask if you want to do this on the next reboot...click Y
If the window doesn't shutdown on its own then reboot the system manually. On reboot the system will start the chkdsk operation
This one will take longer then chkdsk /f

Note... there are 5 stages...
It may appear to hang at a certain percent for a hour or more or even back up and go over the same area...this is normal...
DO NOT SHUT YOUR COMPUTER DOWN WHILE CHKDSK IS RUNNING OR YOU CAN HAVE SEVERE PROBLEMS
This can take several hours to complete.
When completed it will boot the system back into windows.

Let me know if this fixes the problem
  • 0

#70
chantal7

chantal7

    Member

  • Topic Starter
  • Member
  • PipPip
  • 59 posts

Go to

Start and then to Run
Type in Chkdsk /r Note the space between k and /
Click Enter ...It will probably ask if you want to do this on the next reboot...click Y
If the window doesn't shutdown on its own then reboot the system manually. On reboot the system will start the chkdsk operation
This one will take longer then chkdsk /f

Note... there are 5 stages...
It may appear to hang at a certain percent for a hour or more or even back up and go over the same area...this is normal...
DO NOT SHUT YOUR COMPUTER DOWN WHILE CHKDSK IS RUNNING OR YOU CAN HAVE SEVERE PROBLEMS
This can take several hours to complete.
When completed it will boot the system back into windows.

Let me know if this fixes the problem


Done.

I'll find out tonight if it fixed the problem !

Edited by chantal7, 29 March 2011 - 08:29 AM.

  • 0

Advertisements


#71
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
OK sorry just got home. Thanks for the update :D
  • 0

#72
chantal7

chantal7

    Member

  • Topic Starter
  • Member
  • PipPip
  • 59 posts
Update: I still get the same blue screen. Haha. No need to apologize, I was waiting for a good time to let my comp do all that stuff. :D
  • 0

#73
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
OK at this point we have to consider it may be a faulty video card or faulty video memory.
Go to Start and then to Run and Type in dxdiag and then click Enter
At the bottom of the System page click on Save All Information
Save As a Text file and save to Desktop.Include this file with your next reply.
On the DirectX Files tab, check at the bottom of the window for any problem notes.
On the Display Tab click the
Test DirectDraw button and wait for the results.
Then click the Test Direct3D button and wait for the results.

In your next reply include results of each of the above steps.
  • 0

#74
chantal7

chantal7

    Member

  • Topic Starter
  • Member
  • PipPip
  • 59 posts
Bottom of DirectX Files: No problems found.

Non-3D Test:

No problems found.
DirectDraw test results: All tests were successful.
To test Direct3D functionality, click the "Test Direct3D" button above.

3D Test:

No problems found.
DirectDraw test results: All tests were successful.
Direct3D 7 test results: All tests were successful.
Direct3D 8 test results: All tests were successful.
Direct3D 9 test results: All tests were successful.

Attached Files


Edited by chantal7, 30 March 2011 - 01:24 PM.

  • 0

#75
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
OK are you over clocking your cpu or ram?
  • 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