Esegui 
Con "Debugging tools for Windows" mi è stato consigliato, per capire da cosa fossero dipesi questi errori, di eseguire "Open Crash Dump" > per aprire i files contenuti nella cartella C\Win\Minidump [da quello che ho capito sono files creati a seguito degli errori di sistema] appunto per capirne le cause.
Nella cartella Minidump ci sono 5 files. L'ultimo creato in ordine di tempo l'ho appunto aperto, e qui sotto vedete il risultato dell'analisi:
Microsoft ® Windows Debugger Version 6.5.0003.7
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini121405-03.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Wed Dec 14 03:01:25.250 2005 (GMT+1)
System Uptime: 0 days 0:13:03.812
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
..................................................................................................................................
Loading unloaded module list
.........
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck F4, {3, 88722da0, 88722f14, 805c7478}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** WARNING: Unable to verify timestamp for wpsdrvnt.sys
*** ERROR: Module load completed but symbols could not be loaded for wpsdrvnt.sys
*** WARNING: Unable to verify timestamp for wg5n.sys
*** ERROR: Module load completed but symbols could not be loaded for wg5n.sys
Probably caused by : wpsdrvnt.sys ( wpsdrvnt+2984 )
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 00000003, Process
Arg2: 88722da0, Terminating object
Arg3: 88722f14, Process image file name
Arg4: 805c7478, Explanatory message (ascii)
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
FAULTING_MODULE: 00000000
DEBUG_FLR_IMAGE_TIMESTAMP: 41195fe9
PROCESS_OBJECT: 88722da0
IMAGE_NAME: wpsdrvnt.sys
CUSTOMER_CRASH_COUNT: 3
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xF4
LAST_CONTROL_TRANSFER: from 805c65a9 to 804f8925
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b789a4cc 805c65a9 000000f4 00000003 88722da0 nt+0x21925
b789a4f0 805c7523 805c7478 88722da0 88722f14 nt+0xef5a9
b789a520 b75bf984 88722fe8 c0000006 b789a584 nt+0xf0523
b789a584 804fe699 badb0d00 b789a5fc 000c0000 wpsdrvnt+0x2984
b789a9b0 804ff8ed b789a9d8 00000000 b789ad64 nt+0x27699
b789ad34 80540049 0052fbe8 0052fc08 00000000 nt+0x288ed
b789ad50 8053c808 0052fbe8 0052fc08 00000000 nt+0x69049
b789ad64 7c91eb94 badb0d00 0052fbdc bad7fd98 nt+0x65808
b789ad68 badb0d00 0052fbdc bad7fd98 bad7fdcc 0x7c91eb94
b789ad6c 0052fbdc bad7fd98 bad7fdcc 00000000 wg5n+0xd00
b789ad70 bad7fd98 bad7fdcc 00000000 00000000 0x52fbdc
b789ad74 bad7fdcc 00000000 00000000 00000000 0xbad7fd98
b789ad78 00000000 00000000 00000000 00000000 0xbad7fdcc
FOLLOWUP_IP:
wpsdrvnt+2984
b75bf984 ?? ???
SYMBOL_STACK_INDEX: 3
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: wpsdrvnt+2984
MODULE_NAME: wpsdrvnt
STACK_COMMAND: kb
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
_______________________________________________________________
Il driver che ho evidenziato in rosso apparteneva ad un Firewall (Sygate Pro), che ora ho disinstallato (e del driver ora nel sistema non è + traccia)
Che ne dite? Posso stare trnquillo? O il sistema è potenzialmente instabile/danneggiato? Se si, cosa fare? la formattazione vorrei proprio evitarla, non ho tempo in questi giorni (ho una mole ingente di programmi da install xchè lavoro spesso con la musica)
_______________________________________________________________
*HD LaCie difettoso: contenente un HD SeagateBarracuda 160 GB 7200 rpm: usando un tool scaricato dalla Seagate il risultato è stato questo:
File Structure Test Result:
Partition 1 (NTFS (160 GB) LACIE LOREN) Result: Failed with critical Errors
The following errors were found while scanning the volume: - One or more errors were found in metadata file records
quando ho letto questo risultato, ho eseguito una nuova formattazione del LaCie, sempre in NTFS (e non in modalità veloce) , dopodichè ho eseguito di nuovo l'utilty Seagate, ed il risultato è stato identico.
Per la cronaca ho già dovuto formattare una volta il mio sistema causa di un altro errore ("Scrittura interrotta non eseguita") verificatosi durante trasferimento di files (Mp3 ed archivi) da questo HD al mio pc.
