Windows 7 Ultimate crash

[mrk1988]

Salve a tutti

Da poco tempo ho installato sul mio PC Windows 7 Ultimate 64bit, però alcune volte mi si crascia improvvisamente.
Sono riuscito a recuperare il seguente messaggio di errore:

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

Ulteriori informazioni sul problema:
BCCode: 18
BCP1: 0000000000000000
BCP2: FFFFFA8005F6BB60
BCP3: 0000000000000002
BCP4: FFFFFFFFFFFFFFFF
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

File che contribuiscono alla descrizione del problema:
C:\Windows\Minidump\121209-24445-01.dmp
C:\Users\Marco\AppData\Local\Temp\WER-32027-0.sysdata.xml

Leggere l'informativa sulla privacy online:
http://go.microsoft.com/fwlink/?link...8&clcid=0x0410

Se l'informativa sulla privacy online non è disponibile, leggere quella offline:
C:\Windows\system32\it-IT\erofflps.txt


Da questo errore sono risalito al file minidump e tramite il tool di debug di windows l'ho aperto tirando fuori il seguente risulatato:

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\121209-24445-01.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 \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 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e0e000 PsLoadedModuleList = 0xfffff800`0304be50
Debug session time: Sat Dec 12 15:02:31.907 2009 (GMT+1)
System Uptime: 0 days 2:47:53.234
*********************************************************************
* 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 \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 18, {0, fffffa8005f6bb60, 2, ffffffffffffffff}

***** 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 ***
*** ***
*************************************************************************
*********************************************************************
* 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+ *
*********************************************************************
*********************************************************************
* 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+ *
*********************************************************************
Probably caused by : ntoskrnl.exe ( nt+71f00 )

Followup: MachineOwner

Le mie conoscenze però finiscono quì. E possibile, tramite le informazioni che sono riuscito ad ottenere, risalire al problema che mi fa crasciare il PC?
se si quali?
Altri menti, come faccio a sapere quale è il problema del mio PC?

[cajenna]

Ciao,innanzi tutto bisognerebbe sapere che hardware hai sul tuo computer e che programmi/driver hai installato,l'errore è troppo generico.

[mrk1988]

Il mio compiter è composto dal seguente hardware:

-Scheda Madre: Gigabait GA-MA790XT-UD4P
-Processore: AMD Phenom II X4 955 Black edition
- RAM: 4GB
-Scheda Video: ATI Radeon HD 4800
-Scheda Audio: Terratech DMX 6Fire 24/96
-2 HDD in raid 1

la scheda audio l'ho reciclata dal mio vecchio PC e sono riuscito a trovare su internet i driver per WIndows Vista e 7

Che sia questo il driver che da noia?

[cajenna]

Ma hai per caso disabilitato qualche servizio o è tutto a default?
Te lo chiedo perchè il ntoskrnl.exe riguarda un srvizio di sistema essenziale...

[Macinastoned]

anche io identico problema che nn ho mai avuto fino a due giorni fa!

computer mai overclocckato ho un e8400 cn 4 gb corsair pc 8500

[Macinastoned]

Originariamente inviato da Macinastoned

anche io identico problema che nn ho mai avuto fino a due giorni fa!

computer mai overclocckato ho un e8400 cn 4 gb corsair pc 8500

please qualuno ci aiuti