Jump to content

Welcome to Geeks to Go - Register now for FREE

Need help with your computer or device? Want to learn new tech skills? You're in the right place!
Geeks to Go is a friendly community of tech experts who can solve any problem you have. Just create a free account and post your question. Our volunteers will reply quickly and guide you through the steps. Don't let tech troubles stop you. Join Geeks to Go now and get the support you need!

How it Works Create Account
Photo

Blue Screen of Death


  • Please log in to reply

#106
biff74

biff74

    Member

  • Topic Starter
  • Member
  • PipPip
  • 61 posts
I can provide mnore crashes if you need but felt the last few would be good. Here you go:

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Mon 12/21/2009 5:14:33 PM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0x101 (0x60, 0x0, 0x803D1120, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
Dump file: C:\Windows\Minidump\Mini122109-02.dmp
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



On Mon 12/21/2009 5:01:16 PM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0x101 (0x60, 0x0, 0x803D1120, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
Dump file: C:\Windows\Minidump\Mini122109-01.dmp
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



On Sun 12/20/2009 11:07:31 PM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0x101 (0x60, 0x0, 0x803D1120, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
Dump file: C:\Windows\Minidump\Mini122009-02.dmp
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



On Sun 12/20/2009 10:02:02 PM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0x101 (0x60, 0x0, 0x803D1120, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
Dump file: C:\Windows\Minidump\Mini122009-01.dmp
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



On Fri 12/18/2009 4:13:11 PM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0x101 (0x60, 0x0, 0x803D1120, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
Dump file: C:\Windows\Minidump\Mini121809-01.dmp
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.
  • 0

Advertisements


#107
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Grrr that watchdog stuff is back again.
  • 0

#108
biff74

biff74

    Member

  • Topic Starter
  • Member
  • PipPip
  • 61 posts
rshaffer61

Do you think this link would help in any way. Appears Microsoft has a hotfix but not sure if I should move in that direction. Let me know what you think.

http://support.micro...?...&spid=11734
  • 0

#109
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Go ahead and try it but please follow the instructions exactly. Let me know what happens as I really would like to see you resolve this now. :) :)
  • 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