Lost_but_Happy said:
Have you loaded the proper symbol file for your machine (either downloaded it or run it off the MS server)?
Also, are you getting the full dump, mini dump or the one in between?
Beyond that, the last one that I had was pretty clear at one point where it pointed directly at the problem .sys file (said something like, "likely problem is whatever.sys).
Yep I have loaded the symbol file for this machine and it is the mini dump.
Here is a small part ..and to the point i guess.
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+34b4 )
Hope this fits...but here is the report.
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: fffffa60019d2180, The PRCB address of the hung processor.
Arg4: 0000000000000003, 0.
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x101
PROCESS_NAME: svchost.exe
CURRENT_IRQL: d
LAST_CONTROL_TRANSFER: from fffff80001eb3331 to fffff80001e64390
STACK_TEXT:
fffffa60`0c6956d8 fffff800`01eb3331 : 00000000`00000101 00000000`00000031 00000000`00000000 fffffa60`019d2180 : nt!KeBugCheckEx
fffffa60`0c6956e0 fffff800`01e5deba : fffff800`023543c0 fffffa60`0c695800 fffffa60`0c695850 fffff800`023543c0 : nt! ?? ::FNODOBFM::`string'+0x34b4
fffffa60`0c695720 fffff800`02331d74 : 00000000`00000000 0000000b`47956c6f 00000000`00000000 0000000b`4795a45d : nt!KeUpdateSystemTime+0xea
fffffa60`0c695750 fffff800`01e65b2d : 00000000`45470a2e fffff800`01f83680 fffffa80`04268c10 fffffa80`092cc060 : hal!HalpHpetClockInterrupt+0x8c
fffffa60`0c695780 fffff800`01e32ec5 : fffff800`00000000 fffffa60`0c695930 00000000`00000000 00000000`00000008 : nt!KiInterruptDispatchNoLock+0x14d
fffffa60`0c695910 fffff800`020dc8ef : 00000000`00000000 fffffa60`0c695ca0 00000000`00000000 00000000`00000000 : nt!KeFlushProcessWriteBuffers+0xc9
fffffa60`0c695960 fffff800`01e63e33 : fffffa80`092cc060 00000000`00013880 ffffffff`fffe7960 00000000`00000000 : nt!NtQuerySystemInformation+0x117f
fffffa60`0c695c20 00000000`76f15dda : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00c2ef88 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76f15dda
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+34b4
fffff800`01eb3331 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+34b4
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 479192b7
FAILURE_BUCKET_ID: X64_0x101_nt!_??_::FNODOBFM::_string_+34b4
BUCKET_ID: X64_0x101_nt!_??_::FNODOBFM::_string_+34b4
Followup: MachineOwner