blue screen in istallazione vista - acer 4810 tg

[mikele]

ciao a tutti!

ho da poco regalato a mia moglie un aspire 4810tg ed alla prima accensione mi è andato in bscreen
in pratica alla terza schermata di impostazione data e ora.

Ci sono stati decine di riavvii spontanei - non sapevo che fare - della macchina e la scrittura di tre utenti di cui uno è amministratore (in pratica ogni volta mi ripartiva l'installazione di vista...).

Se accendo il pc, dopo pochi secondi dalla comparsa del desktop va di nuovo in crash, si riavvia, riaccedo normalmente ed ho la schermata di errore con descrizione del bscreen. a questo punto sembra stabile.

Non so se riportarlo indietro e chiedere una sostistuzione del pc, dato che mercoledi scade la settimana dall'acquisto. non so neanche se me lo sostituiscono...oppure smanettare... o mandarlo indietro in garanzia...help!

riporto dati e dump. grazie mille!


Windows NT Version 6.0 Build: 6001 Service Pack 1
Product (0x3): Windows Vista (TM) Home Premium
Edition: HomePremium
BuildString: 6001.18226.x86fre.vistasp1_gdr.090302-1506
Flavor: Multiprocessor Free
Architecture: X86
LCID: 1040

[TheMic]

riportalo indietro.... secondo me è la cosa più giusta!

[Masamune_Date]

entro un tot di tempo non mi ricordo se 7 giorni, son obligatia sostituirti la macchina , riporta indietro il portatile e falla cambiare

[mikele]

grazie per il consiglio. ci proverò ma temo che trattandosi di una grande catena di elettronica mi rifiuteranno il cambio, o almeno ci proveranno.

vi terrò aggiornati sulla vicenda.
mik

[mikele]

...non riesco a stare fermo... così ho deciso di installare il debugger di windows e provare a capirci qualcosa...
riporto l'output. il problema sembra ntkrnlpa.exe, ma non riesco a trovare nulla di esplicativo su internet.

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


Loading Dump File [C:\Users\michele\Desktop\Mini120109-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\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0x82040000 PsLoadedModuleList = 0x82157c70
Debug session time: Tue Dec 1 19:18:41.821 2009 (GMT+1)
System Uptime: 0 days 0:44:17.436
*********************************************************************
* 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\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {7, 3c517, 8, 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 ***
*** ***
*************************************************************************
*********************************************************************
* 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 : ntkrnlpa.exe ( nt+41277 )

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

[italian soldier]

Potrebbe essere che un banco di RAM non sia insertito correttamente e dia BSOD.
Il mio consiglio spassionato è, portalo assolutamente indietro e fattelo cambiare!!!

[TheMic]

Come dice Italian e come ti ho scritto qualche post fa: riportalo indietro se non vuoi ulteriori problemi futuri.


Potrebbe essere tutto o nulla... e visto che il prodotto è nuovissimo, non è il tuo compito scoprirlo.

[Masamune_Date]

grazie per il consiglio. ci proverò ma temo che trattandosi di una grande catena di elettronica mi rifiuteranno il cambio, o almeno ci proveranno.

vi terrò aggiornati sulla vicenda.
mik

sono obbligati a farlo c'e' poco da dire

[mikele]

ho seguito il vs consiglio.
non avendo piu' un acer in magazzino me lo hanno sostituito con un toshiba satellite t13011u che mi sembra anche meglio attrezzato dell'acer precedente.

nel punto vendita hanno voluto avviare il vecchio pc per controllare ciò che riportavo loro. devo dire che aver letto i 3d di questo forum mi ha aiutato a sostenere meglio il mio punto di vista.

grazie a tutti!
mik

[italian soldier]

Bene i toshiba sono ottimi PC Speriamo comunque tu non debba mai ver bisogno dell'assistenza

Marco