problema: ogni 2 o 3 mesi dipende, un server in cluster si riavvia per blue screen..

architettura: cluster composto da 2 HP DL380G5 collegato ad uno storage MSA2000fc.. tutti e due Windows 2003 Server R2 Enterprise aggiornati, patchati e con antivirus McAfee Enterprise.. non ci sono task previsti per la data/ora che si riavvia.. non ci sono schede aggiuntive..

primo tentativo: è stato installato il Proliant Support Pack ma non è cambiato nulla..

prima analisi: dal bugcheck

DRIVER_CORRUPTED_MMPOOL (d0)
Arguments:
Arg1: 00000008, memory referenced
Arg2: d0000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 80891aaf, address which referenced memory
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is
caused by drivers that have corrupted the system pool. Run the driver
verifier against any new (or suspect) drivers, and if that doesn't turn up
the culprit, then use gflags to enable special pool. You can also set
HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\ProtectNonPagedPool
to a DWORD 1 value and reboot. Then the system will unmap freed nonpaged pool,
preventing drivers (although not DMA-hardware) from corrupting the pool.

Debugging Details:
------------------
READ_ADDRESS: 00000008
CURRENT_IRQL: 2
FAULTING_IP:
nt!KiDoubleFaultStack+1ff
80891aaf ?? ???
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP
BUGCHECK_STR: 0xD0
PROCESS_NAME: System
LAST_CONTROL_TRANSFER: from 00000000 to 8088c993
STACK_TEXT:
f78d27b4 00000000 f78d27c0 00000000 808a0000 nt!ExFreePoolWithTag+0x65d
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nt!KiDoubleFaultStack+1ff
80891aaf ?? ???
SYMBOL_NAME: nt!KiDoubleFaultStack+1ff
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlpa.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 48a2ac75
FAILURE_BUCKET_ID: 0xD0_nt!KiDoubleFaultStack+1ff
BUCKET_ID: 0xD0_nt!KiDoubleFaultStack+1ff
Followup: MachineOwner
---------

seconda analisi: sigverif non da segni di problemi di verifica driver
verifier non da problemi apparenti ma non so bene come usarlo e vi vorrei chiedere una mano su come interpretare il tutto.. Grazie davvero mille!