Aiuto su analisi file minudump dopo crash Vista 32

[Mamukata]

E' da un pò che ho un pò di problemi di instabilità del mio Vista Ultimate 32 e, analizzando il file minidump ottengo questi risultati.
Io però non riesco a capirli fino in fondo.
Con l'utility di debug ottengo questi risultati, qualcuno di voi riesce a dirmi qualcosa di più?
Da quel poco che ho capito cmq deduco la la riga principale da analizzare sia questa:

WARNING: Unable to verify timestamp for sptd.sys

Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [c:\windows\minidump\Mini080908-01.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: c:\windows\i386
Windows Server 2008 Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18063.x86fre.vistasp1_gdr.080425-1930
Kernel base = 0x82039000 PsLoadedModuleList = 0x82146930
Debug session time: Sat Aug  9 00:55:34.444 2008 (GMT+2)
System Uptime: 2 days 4:33:03.349
Loading Kernel Symbols
..............................................................................................................................................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {31, 0, 806d1120, 1}

*** 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: 00000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 00000000, 0.
Arg3: 806d1120, The PRCB address of the hung processor.
Arg4: 00000001, 0.

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


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  1c

STACK_TEXT:  
821258bc 820a5f7a 00000101 00000031 00000000 nt!KeBugCheckEx+0x1e
821258f0 820a769d 0000001b 000000d1 821259b0 nt!KeUpdateRunTime+0xd5
821258f0 820a5240 0000001b 000000d1 821259b0 nt!KeUpdateSystemTime+0xed
8212597c 8204099b 0000000e 82040a3c 87e4b982 nt!KiIpiSendPacket+0xac
821259b0 87e4bb3e 87e4b982 821259c8 00040000 nt!KeIpiGenericCall+0x6e
WARNING: Stack unwind information not available. Following frames may be wrong.
82125a00 87e4c26a 0000001f 87e4b84e 82125a24 sptd+0x14b3e
82125a30 87e465e3 01000001 859d8420 859f5460 sptd+0x1526a
82125a48 87e47f6d 00000103 859d7330 866df008 sptd+0xf5e3
82125a74 87e4a8c4 859d8368 82125acc 87e478ec sptd+0x10f6d
82125ae4 8207f1ad 85a73030 859d8368 859d8368 sptd+0x138c4
82125afc 8864d264 85a59b70 859d7310 85a59ab8 nt!IofCallDriver+0x63
82125b10 8864d45d 85a59b70 859d7328 00000000 CLASSPNP!ClasspSendMediaStateIrp+0x2ec
82125b28 8864d2af 85a59b70 859bd2bc 82163700 CLASSPNP!ClassCheckMediaState+0x54
82125b48 820a8553 85a59ab8 00000000 82125bac CLASSPNP!ClasspTimerTick+0x41
82125b68 820a42a0 821636e0 02163684 dbadd17c nt!IopTimerDispatch+0x49
82125c88 820a3e60 82125cd0 85567902 82125cd8 nt!KiTimerListExpire+0x367
82125ce8 820a3a23 00000000 00000000 00b90a7a nt!KiTimerExpiration+0x22a
82125d50 820a254d 00000000 0000000e 00000000 nt!KiRetireDpcList+0xba
82125d54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x49


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:  CLOCK_WATCHDOG_TIMEOUT_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_ANALYSIS_INCONCLUSIVE

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

0: kd> lmvm Unknown_Module
start    end        module name

[stefanothebest]

"sptd.sys" è un driver utilizzato da daemon tools o alcohol 120%.
Se hai uno di questi programmi installati prova a disinstallarli o aggiornarli a una versione più recente.