Crash windows vista home premium 64 bit

[andreadc]

Salve a tutti, da qualche giorno windows mi crasha in continuazione, ecco qui uno dei tanti

Firma del problema
Nome evento problema: BlueScreen
Versione SO: 6.0.6002.2.2.0.768.3
ID impostazioni locali: 1040

File che consentono di descrivere il problema (alcuni file potrebbero non essere più disponibili)
Mini080109-04.dmp
sysdata.xml
Version.txt


Ulteriori informazioni sul problema
BCCode: 1a
BCP1: 0000000000041287
BCP2: 0000000000000030
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_0_6002
Service Pack: 2_0
Product: 768_1
Informazioni sul server: 264ac0e0-6859-4cae-87a7-96fe314c3b49

a questo punto ho scaricato win dbg e i symbol nel tentativo di capire dov'è il problema, ma quando tento di aprire il file mi appare una finestra dove c'è scritto che non ho le autorizzazioni per aprire il file. Non essendo un utente esperto vi chiedo gentilmente assistenza.
P.S. se avete bisogno di altre info chiedete pure

[andreadc]

sono riuscito ad aprire il file DMP ma forse ho sbagliato qualcosa

Symbol search path is: C:\Windows\Symbols
Executable search path is:
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff800`01e5c000 PsLoadedModuleList = 0xfffff800`02020dd0
Debug session time: Sat Aug 1 14:56:41.826 2009 (GMT+2)
System Uptime: 0 days 1:37:15.202
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** 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 User Symbols
Loading unloaded module list
.....
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41287, 30, 0, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
Probably caused by : ntoskrnl.exe ( nt+5a450 )

Followup: MachineOwner

[molixii]

devi rendere il programma accessibile dal tuo account come in molti casi di vista
devi fare tasto destro mouse ed esegui come amministratore

per il resto aspett le risposte

ciao
davide

[andreadc]

Intanto grazie della risposta, ho fatto come consigliato da te ma mi dice che non uso i symbol giusti anche se sono sicuro che sono giusti. Comunque cercando sul sito della microsoft ho trovato questo http://support.microsoft.com/kb/929777/it, IRQL_NOT_LESS_OR_EQUAL è l' errore che mi dava nella maggior parte dei casi nella schermata blu. Ma i problemi non sono finiti.... ho scaricato come scritto nel link sopra l' aggiornamento ma quando provo a installarlo mi dice che non è possibile ho quindi proveduto a rimuovere un banco da 2 gb di ram e dalle 8 e30 di ieri sera sera non ci sono stati più crash. E' possibile che l aggiornamento sia già contenuto nel SP2 di vista? Se non è già presente come posso installarlo? E comunque secondo voi il problema era solo causa dei 4 GB di ram o è solo un caso che non si siano più verificati problemi?

[andreadc]

Niente altri due crash....