Crash con Nod32+Azureus

[egidio82]

Salve a tutti, da un po' di giorni ho installato NOD32 su Vista, ma purtroppo ho dei problemi quando avvio Azureus, dopo qualche minuto schermata blu e riavvio. Vi posto il log del file di dump con relativa analisi, spero qualcuno mi sappia dare una mano per risolvere il problema.

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


Loading Dump File [c:\windows\minidump\minidump.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/Windows Vista SP1 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18145.x86fre.vistasp1_gdr.080917-1612
Machine Name:
Kernel base = 0x81e0b000 PsLoadedModuleList = 0x81f22c70
Debug session time: Tue Feb  3 16:37:46.432 2009 (GMT+1)
System Uptime: 0 days 0:22:05.172
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {bca2d001, 0, 81ec06d2, 0}

*** WARNING: Unable to verify timestamp for eamon.sys
*** ERROR: Module load completed but symbols could not be loaded for eamon.sys
Probably caused by : hardware ( eamon+379f )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: bca2d001, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 81ec06d2, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 00000000, (reserved)

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 81f42868
Unable to read MiSystemVaType memory at 81f22420
 bca2d001 

FAULTING_IP: 
nt!memcpy+72
81ec06d2 8a06            mov     al,byte ptr [esi]

MM_INTERNAL_CODE:  0

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  Azureus.exe

CURRENT_IRQL:  0

TRAP_FRAME:  acfcd248 -- (.trap 0xffffffffacfcd248)
ErrCode = 00000000
eax=00000001 ebx=ffffffff ecx=fffffffc edx=00000000 esi=bca2d001 edi=8577c001
eip=81ec06d2 esp=acfcd2bc ebp=acfcd2c4 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
nt!memcpy+0x72:
81ec06d2 8a06            mov     al,byte ptr [esi]          ds:0023:bca2d001=??
Resetting default scope

MISALIGNED_IP: 
nt!memcpy+72
81ec06d2 8a06            mov     al,byte ptr [esi]

LAST_CONTROL_TRANSFER:  from 81e65b54 to 81eb00f5

STACK_TEXT:  
acfcd230 81e65b54 00000000 bca2d001 00000000 nt!MmAccessFault+0x10a
acfcd230 81ec06d2 00000000 bca2d001 00000000 nt!KiTrap0E+0xdc
acfcd2c4 87e24e94 8577c001 bca2d001 ffffffff nt!memcpy+0x72
acfcd33c 87e24d2d acfcd6b0 845399f8 ffffffff Ntfs!NtfsCopyFromMdl+0x131
acfcd364 87e13be3 acfcd6b0 00000001 ffffffff Ntfs!NtfsPrepareSparseWriteBuffer+0x5b
acfcd3f4 87e1a198 acfcd6b0 8435eb20 00010000 Ntfs!NtfsPrepareComplexBuffers+0x17e
acfcd428 87e1a496 acfcd6b0 00000000 b8e9b930 Ntfs!NtfsPrepareBuffers+0xf3
acfcd570 87e1d5e5 acfcd6b0 8435eb20 b8e9b930 Ntfs!NtfsNonCachedIo+0x233
acfcd6a0 87e1b914 acfcd6b0 8435eb20 0118070a Ntfs!NtfsCommonWrite+0x1c13
acfcd830 81ec6fd3 874c5020 8435eb20 8435eb20 Ntfs!NtfsFsdWrite+0x2dc
acfcd848 87ba2ba7 874bede0 8435eb20 00000000 nt!IofCallDriver+0x63
acfcd86c 87ba2d64 acfcd88c 874bede0 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x251
acfcd8a4 81ec6fd3 874bede0 8435eb20 a73177ac fltmgr!FltpDispatch+0xc2
acfcd8bc a72e279f 8154baa8 acfcd8e0 81ec6fd3 nt!IofCallDriver+0x63
WARNING: Stack unwind information not available. Following frames may be wrong.
acfcd8c8 81ec6fd3 8154baa8 8435eb20 003fa000 eamon+0x379f
acfcd8e0 81e4b9fa 00006000 845399f8 00000000 nt!IofCallDriver+0x63
acfcd8f4 81ec9689 842bfab8 8154baa8 acfcd930 nt!IoSynchronousPageWrite+0x10b
acfcd978 81fb7ffa 84598a90 00001000 b8e9b930 nt!CcZeroDataOnDisk+0x1d3
acfcd9b0 87e77a07 84598a90 acfcd9f8 acfcd9f0 nt!CcZeroData+0x1b9
acfcda2c 87e1d8fe 873bbbd8 b8e9b930 84598a90 Ntfs!NtfsZeroData+0x192
acfcdb5c 87e1b914 873bbbd8 a53fbe00 2b18b2fc Ntfs!NtfsCommonWrite+0x1f22
acfcdbd4 81ec6fd3 874c5020 a53fbe00 a53fbe00 Ntfs!NtfsFsdWrite+0x2dc
acfcdbec 87ba2ba7 874bede0 a53fbe00 00000000 nt!IofCallDriver+0x63
acfcdc10 87ba2d64 acfcdc30 874bede0 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x251
acfcdc48 81ec6fd3 874bede0 a53fbe00 a73177ac fltmgr!FltpDispatch+0xc2
acfcdc60 a72e279f 8154baa8 acfcdc84 81ec6fd3 nt!IofCallDriver+0x63
acfcdc6c 81ec6fd3 8154baa8 a53fbe00 a53fbe00 eamon+0x379f
acfcdc84 82057615 84598abc a53fbe00 a53fbfd8 nt!IofCallDriver+0x63
acfcdca4 8203291d 8154baa8 84598a90 00000001 nt!IopSynchronousServiceTail+0x1d9
acfcdd38 81e62a1a 8154baa8 00000000 00000000 nt!NtWriteFile+0x6fc
acfcdd38 775a9a94 8154baa8 00000000 00000000 nt!KiFastCallEntry+0x12a
065af3c4 00000000 00000000 00000000 00000000 0x775a9a94


STACK_COMMAND:  kb

FOLLOWUP_IP: 
eamon+379f
a72e279f ??              ???

SYMBOL_STACK_INDEX:  e

SYMBOL_NAME:  eamon+379f

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  IP_MISALIGNED

BUCKET_ID:  IP_MISALIGNED

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

[egidio82]

nessuno ha idee?