A Ovest Di Paperino

condizione:  versione = 5.4.4.0

Uhm, ho la 5.4.3.2 su 7 x64 (per fortuna fin'ora nessuna bsod)

@ Snake

Anche io ho quella versione... nessun problema su 7 x86

Beeeeeeello, allora esistono ancora quelle schermate blu!

Io è da aprile 2008 che non ne vedo più una

(Niente VirtualCloneDrive, era un commento giusto per cazzeggio )

io l ultimo Bsod l ho avuto con Vista (non c era manco SP1)  installando uno stravecchissimo titolo Jap .

E grattaondomi , spero di andare  avanti per questa strada

Io con Vista SP1, a causa di ZoneAlarm che ancora non era compatibile.

Mi ricordo le bestemmie rivolte verso il povero Vista, che dopo una ricerca su Internet ho trovato incolpevole (da lì ho smesso di prendermela subito con l'OS, ma di cercare se sono altre le cause dei problemi )

Tolto ZoneAlarm, messo Comodo e sono tornato tranquillo

Da 7, invece, uso Windows Firewall e mi trovo piuttosto bene

Appena verificata

5.4.3.2

Io ho ancora la 5.4.3.5

blue screen fresco di stamane.. chi me lo spiega? stavo navigando normalmente con IE 8 ...

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

Ulteriori informazioni sul problema:
  BCCode: 124
  BCP1: 0000000000000000
  BCP2: FFFFFA8005112038
  BCP3: 0000000000000000
  BCP4: 0000000000000000
  OS Version: 6_1_7600
  Service Pack: 0_0
  Product: 768_1

File che contribuiscono alla descrizione del problema:
  C:\Windows\Minidump\012110-15553-01.dmp
  C:\Users\lzk87\AppData\Local\Temp\WER-22526-0.sysdata.xml

Leggere l'informativa sulla privacy online:
  http://go.microsoft.com/fwlink/?...

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

  C:\Windows\Minidump\012110-15553-01.dmp

Servirebbe analizzare il suddetto con WinDBG per risalire alla causa.

vedo se riesco ad aprirlo con qualcosa... suggerimenti??

suggerimenti

WinDBG

Blue screen view mi riporta questo ora provo WinDBG

un gran bel casino col copia incolla.. scusa paperino rimuovi pure

Donald, we have a bug

winDBG mi da una serie di caratteri incomprensibili, sicuri che serva anche per i dump del bluescreen?  voglio capire se è un crash dei beta driver di ATI, Creative, o qualcosa d'altro

Sì, assolutamente. Caricalo da qualche parte (skydrive, mediafire etc) che gli si da un'occhiata

@lzk87

certo che WinDbg serve per aprire i minidump, vai sul menu' File e seleziona "Open Crash Dump..." ma devi prima settare il path per i simboli se vuoi una diagnosi precisa.

ciao raga grazie per gli aiuti, intanto ho visto questo:

(abbiate pazienza, non capisco dove pescare i simboli)

(quel Probably caused by : hardware che vedo in fondo è la diagnosi per noi umani?)

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

Loading Dump File [C:\Users\Levi\Desktop\012110-15553-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 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 Personal
Machine Name:
Kernel base = 0xfffff800`02c06000 PsLoadedModuleList = 0xfffff800`02e43e50
Debug session time: Thu Jan 21 07:36:59.286 2010 (GMT+1)
System Uptime: 0 days 0:00:08.377
*********************************************************************
* 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 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
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8005112038, 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!_WHEA_ERROR_RECORD_HEADER                  ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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!_WHEA_ERROR_RECORD_HEADER                  ***
***                                                                   ***
*************************************************************************
Unable to load image PSHED.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for PSHED.dll
*** ERROR: Module load completed but symbols could not be loaded for PSHED.dll
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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 : hardware

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

@snake: se proprio vuoi vederlo
Grazie di tutto a tutti ovviamente

http://www.megaupload.com/?d=5939SXAW

no, overcloccato tipo 7 mesi fa ma roba leggerissima.. poi ho lasciato tutto a default .... mmmmm saranno i driver beta che sto provando può essere??

andiamo bene l'altro giorno ho fatto un memtest ed era perfetto, dovro vedere gli altri componenti come stanno, grazie mille!!

dissipatore ko? (pasta termica secca/di scarsa qualità/insufficiente oppure pessimo ricircolo dell'aria/ostruzione delle laminature e della ventola che causano surriscaldamento)

in effetti son 3 mesi che non apro il PC per fare manutenzione domani ci do un occhiatina

@ lzk87:

L'alimentatore e' di buona qualita' (leggi: niente cineserie da 20 euro o "regalate" assieme al case)?

Edward

@Edward, Snake

La cosa più probabile (postai in off-Topo un po' di tempo fa) è la polvere... a me si era incrostata letteralmente nei dissipatori della CPU: ho un sistema di raffreddamento che è fatto dal processore su cui è poggiato una specie di "stella metallica a 100 punte e sopra di essa una ventola, ebbene la polvere era incrostata tra le "punte" del dissipatore metallico una roba allucinante... se hai il "Folletto" ti consiglio una pulizia con quello lì, ovviamente dotato di "estensione computer" (un riduttore di flusso fatto apposta x i componenti elettronici) oppure con fazzoletti, phon e tanta buona volontà (in un paio d'ore dovresti risolvere...

@ snake

mi rendo conto che

ostruzione delle laminature e della ventola che causano surriscaldamento

è il modo "figo" (nonchè esatto) di dire quello che ho detto io

@Giuseppe, lol, deformazione professionale

ho pulito ben bene circa 200 grammi di polvere erano 4 mesi che non aprivo il case per ora  è tutto fresco (ci credo in questa stagione) e ok