Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD error


  • Please log in to reply
No replies to this topic

#1 blue02celi

blue02celi

  • Members
  • 23 posts
  • OFFLINE
  •  
  • Local time:11:29 PM

Posted 16 April 2009 - 07:45 PM

hello
lately I've been getting the BSOD as soon as I turn on my computer. it was put together by someone else I know, so Im guessing maybe he didnt put it together as well as we thought. I read through some posts, tried doing the online malware search but the link on the topic I was reading didnt work, so I Just kept going and got the dump analyzed. I didnt write down the full error last time it happened but I will get it and try to edit or add to this topic when i get the whole number, right now all I copied was: STOP 0X00000101


AMD Phenom™ 9600 Quad-Core Processor 2.30 GHz
4 GB Ram
64 bit OS
Windows Vista Home Premium SP1


analysis from debugger:



Microsoft ® Windows Debugger Version 6.11.0001.404 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\Mini041609-03.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18226.amd64fre.vistasp1_gdr.090302-1506
Machine Name:
Kernel base = 0xfffff800`0265f000 PsLoadedModuleList = 0xfffff800`02824db0
Debug session time: Thu Apr 16 17:46:16.543 2009 (GMT-6)
System Uptime: 0 days 0:19:15.810
Loading Kernel Symbols
...............................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {31, 0, fffffa6001963180, 2}

Unable to load image \SystemRoot\System32\Drivers\sptd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffffa6001963180, The PRCB address of the hung processor.
Arg4: 0000000000000002, 0.

Debugging Details:
------------------


BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_4_PROC

CUSTOMER_CRASH_COUNT: 3

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: d

STACK_TEXT:
fffff800`037c7358 fffff800`02703311 : 00000000`00000101 00000000`00000031 00000000`00000000 fffffa60`01963180 : nt!KeBugCheckEx
fffff800`037c7360 fffff800`026ad18a : fffff800`02646460 fffff800`037c7480 fffff800`037c74d0 fffff800`02646460 : nt! ?? ::FNODOBFM::`string'+0x34b4
fffff800`037c73a0 fffff800`02623d74 : 00000000`00000000 00000003`da85fe54 00000000`00000000 00000003`da8966de : nt!KeUpdateSystemTime+0xea
fffff800`037c73d0 fffff800`026b4ded : 00000000`69a8e2e3 fffffa80`06db0448 fffffa80`06569750 fffffa60`06d673ed : hal!HalpHpetClockInterrupt+0x8c
fffff800`037c7400 fffff800`0273e732 : fffff800`00000000 fffff800`037c75b0 00000000`00000000 00000000`00000008 : nt!KiInterruptDispatchNoLock+0x14d
fffff800`037c7590 fffffa60`00a47a94 : 00000000`00000002 00000000`00000002 00000000`0000000e 00000000`00000000 : nt!KeIpiGenericCall+0xd2
fffff800`037c75f0 00000000`00000002 : 00000000`00000002 00000000`0000000e 00000000`00000000 fffffa60`00a481ec : sptd+0x44a94
fffff800`037c75f8 00000000`00000002 : 00000000`0000000e 00000000`00000000 fffffa60`00a481ec fffff800`037c76c0 : 0x2
fffff800`037c7600 00000000`0000000e : 00000000`00000000 fffffa60`00a481ec fffff800`037c76c0 fffffa60`00a481a8 : 0x2
fffff800`037c7608 00000000`00000000 : fffffa60`00a481ec fffff800`037c76c0 fffffa60`00a481a8 fffff800`037c76c0 : 0xe


STACK_COMMAND: kb

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE

Followup: MachineOwner
---------

0: kd> !analyze -v

BC AdBot (Login to Remove)

 





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users