blue screen

[mattia.pascal]

Ho un problema con un desktop Pavillon a6380 appena acquistato. Il classico bluescreen. Ho testato la ram con memtest, ma non risultano errori. Quante volte conviene eseguire il test per aver una certa sicurezza sull'esito? Il pc non ha alcuna periferica installata e non ho installato nessun software. E' praticamente come esce di fabbrica. Ho solo fatto gli aggiornamenti di Windows. Prima di mandarlo in assistenza vorrei essere sicuro che sia un problema hardware. Il crash non avviene spesso una volta al giorno circa.
Allego il dump del crash.

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols 
Executable search path is: 
Windows Server 2008 Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18000.x86fre.longhorn_rtm.080118-1840
Kernel base = 0x81a4a000 PsLoadedModuleList = 0x81b61c70
Debug session time: Wed May 21 12:02:47.239 2008 (GMT+2)
System Uptime: 0 days 2:44:53.756
Loading Kernel Symbols
...........................................................................................................................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {bb5cf4a9, 2, 1, 81a1aff9}

Probably caused by : ntkrpamp.exe ( nt!KiTrap0E+2ac )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: bb5cf4a9, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 81a1aff9, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 81b81868
Unable to read MiSystemVaType memory at 81b61420
 bb5cf4a9 

CURRENT_IRQL:  2

FAULTING_IP: 
hal!KeAcquireInStackQueuedSpinLockRaiseToSynch+29
81a1aff9 8902            mov     dword ptr [edx],eax

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  iexplore.exe

TRAP_FRAME:  8ad7ba68 -- (.trap 0xffffffff8ad7ba68)
ErrCode = 00000002
eax=8ad7baec ebx=c00000d8 ecx=87106964 edx=bb5cf4a9 esi=84c2ec68 edi=87106930
eip=81a1aff9 esp=8ad7badc ebp=8ad7bafc iopl=0         nv up ei ng nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010286
hal!KeAcquireInStackQueuedSpinLockRaiseToSynch+0x29:
81a1aff9 8902            mov     dword ptr [edx],eax  ds:0023:bb5cf4a9=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 81a1aff9 to 81aa4d84

STACK_TEXT:  
8ad7ba68 81a1aff9 badb0d00 bb5cf4a9 81a1e5b0 nt!KiTrap0E+0x2ac
8ad7bad8 81a9bc36 00000002 8d6bac18 c00000d8 hal!KeAcquireInStackQueuedSpinLockRaiseToSynch+0x29
8ad7bafc 8a2143bb 87106930 00000000 8ad7bb30 nt!ExAcquireResourceExclusiveLite+0x25
8ad7bb0c 8a21427c 85ab35a8 8d6bac18 00000000 Ntfs!NtfsAcquireResourceExclusive+0x1e
8ad7bb30 8a219203 85ab35a8 8d6bac18 00000000 Ntfs!NtfsAcquireExclusiveFcb+0x42
8ad7bb5c 8a295f2f 85ab3500 8d6bac18 00000002 Ntfs!NtfsAcquireFcbWithPaging+0x8b
8ad7bbb4 8a294c20 85ab35a8 86451b88 00000008 Ntfs!NtfsFindPrefixHashEntry+0x3b8
8ad7bc10 8a29367f 85ab35a8 84d14250 8abd66b0 Ntfs!NtfsFindStartingNode+0x73b
8ad7bcec 8a2192aa 85ab35a8 84d14250 99376984 Ntfs!NtfsCommonCreate+0x620
8ad7bd2c 81b03318 9937691c 00000000 ffffffff Ntfs!NtfsCommonCreateCallout+0x20
8ad7bd2c 81b03411 9937691c 00000000 ffffffff nt!KiSwapKernelStackAndExit+0x118
993768ac 00000000 00000000 00000000 00000000 nt!KiSwitchKernelStackAndCallout+0x31


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiTrap0E+2ac
81aa4d84 833d648cb78100  cmp     dword ptr [nt!KiFreezeFlag (81b78c64)],0

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!KiTrap0E+2ac

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  47918b12

FAILURE_BUCKET_ID:  0xA_W_nt!KiTrap0E+2ac

BUCKET_ID:  0xA_W_nt!KiTrap0E+2ac

Followup: MachineOwner

[bgpop]

Quanto tempo ha girato memtest?
Fallo andare almeno 24h, prima di dire che la RAM è OK!
Mi è capitato un problema di BSOD occasionali, e memtest mi ha restituito un'area di RAM fallata solo dopo 12h di test continuo

[claudio21]

Anche a me capita la stessa cosa da qualche giorno, ma ho vista ultimate sp1con 4 GB di RAM....proverò anch'io a fare il test della memoria, anche se non credo sia la RAM....


Facendo il mem test mi sono accorto che il bios mi vede 3 giga soli di ram...mentre vista 4.
che sia questo che lo fa sbarellare?

[sirus]

Un più banale problema di driver?! Sul log del crash si accenna a possibili problemi causati da driver.