Valutazione 4.87/ 5 (100.00%) 5838 voti

Condividi:        

pc spento durante aggiornamento

Hai problemi con i file Zip, vuoi formattare l'HD, non sai come funziona FireFox? O magari ti serve proprio quel programmino di cui non ricordi il nome! Ecco il forum dove poter risolvere i tuoi problemi.

Moderatori: Dylan666, hydra, gahan

pc spento durante aggiornamento

Postdi alessia84 » 16/10/13 23:03

Buonasera a tutti...ho un problemino...
Durante gli aggiornamenti di Windows si è staccata la corrente e si è spento il pc...Oggi l'ho riacceso credendo che fossero andati a buon fine invece mi sono trovata davanti un vero disastro =(...mi si apre la schermata blu che non permette il caricamento di Windows..ho provato a riavviare in modalità provvisoria e avviare un punto di ripristino ma non si conclude e si riavvia portandomi sempre alla stessa schermata...
L'unica soluzione è formattare?
Ho un portatile con win7.

Grazie mille in anticipo...
alessia84
Utente Senior
 
Post: 132
Iscritto il: 18/07/06 14:33

Sponsor
 

Re: pc spento durante aggiornamento

Postdi Dylan666 » 17/10/13 10:54

hai provato TUTTI i punti di ripristino?
Avatar utente
Dylan666
Moderatore
 
Post: 38040
Iscritto il: 18/11/03 16:46

Re: pc spento durante aggiornamento

Postdi alessia84 » 17/10/13 11:32

Ho provato a ripristinare ad una data precedente agli aggiornamenti ma non riesco a farlo, non mi permette di attivare nessun punto di ripristino.. pur avviando la procedura di ripristino al riavvio spunta quella schermata blu.. ho provato a farlo anche in modalità provvisoria ma non riesco. Forse si è spento durante l'installazione di aggiornamenti Windows fondamentali..
alessia84
Utente Senior
 
Post: 132
Iscritto il: 18/07/06 14:33

Re: pc spento durante aggiornamento

Postdi Dylan666 » 17/10/13 13:06

Sotto l'opzione della modalità provvisoria c'è "usa ultima configurazione funzionante" ma dubito funzioni dato che il ripristino è più "potente"
La formattazione la vedo l'unica opzione.
Intanto potrai portarti via i dati con un disco esterno e la modalità provvisoria
Avatar utente
Dylan666
Moderatore
 
Post: 38040
Iscritto il: 18/11/03 16:46

Re: pc spento durante aggiornamento

Postdi alessia84 » 17/10/13 19:08

ma dal prompt dei comandi, o in modalità provvisoria, non posso riscaricare gli aggiornamenti?
alessia84
Utente Senior
 
Post: 132
Iscritto il: 18/07/06 14:33

Re: pc spento durante aggiornamento

Postdi Dylan666 » 17/10/13 19:31

scaricarli pure pure, ma installarli non credo proprio...
Avatar utente
Dylan666
Moderatore
 
Post: 38040
Iscritto il: 18/11/03 16:46

Re: pc spento durante aggiornamento

Postdi nikita75 » 17/10/13 20:49

ciao alessia84
se l'hard disk drive era in fase di scrittura durante la mancanza di rete potrebbe averlo danneggiato :roll: :mmmh:
ma spero non sia il tuo caso !
buon formattone e fai sapere se è filato tutto per il verso giusto! :) ;)
Avatar utente
nikita75
Utente Senior
 
Post: 4387
Iscritto il: 31/07/09 13:36

Re: pc spento durante aggiornamento

Postdi nikita75 » 17/10/13 21:06

curiosando in rete
ne parlano su questo forum !è sempre una espperienza allucinante :(
http://www.tomshardware.co.uk/forum/336 ... dates-boot
Hanno tentato resettando il bios ma senza alcun risultato

formatta e fai sapere se è filato tutto per il verso giusto! :) ;)
Avatar utente
nikita75
Utente Senior
 
Post: 4387
Iscritto il: 31/07/09 13:36

Re: pc spento durante aggiornamento

Postdi Dylan666 » 17/10/13 21:39

nikita75 ha scritto:ciao alessia84
se l'hard disk drive era in fase di scrittura durante la mancanza di rete potrebbe averlo danneggiato :roll: :mmmh:

Non sarebbe partito nemmeno in modalità provvisoria allora...
Avatar utente
Dylan666
Moderatore
 
Post: 38040
Iscritto il: 18/11/03 16:46

Re: pc spento durante aggiornamento

Postdi alessia84 » 18/10/13 13:46

ma c'è qualche prova che posso fare prima di formattare? qualche tentativo oltre il ripristino?
alessia84
Utente Senior
 
Post: 132
Iscritto il: 18/07/06 14:33

Re: pc spento durante aggiornamento

Postdi alessia84 » 18/10/13 14:29

ho scaricato whocrashed e il
problema, a quanto pare, e' stato causato da un driver di avg. Sto provando a reinstallare avg e vediamo
che succede :(
alessia84
Utente Senior
 
Post: 132
Iscritto il: 18/07/06 14:33

Re: pc spento durante aggiornamento

Postdi alessia84 » 18/10/13 14:48

Allora ragazzi...
dopo aver scaricato whoCrashed il log che è venuto fuori era il seguente:


System Information (local)
--------------------------------------------------------------------------------

computer name: ACER-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Pentium(R) Dual-Core CPU T4300 @ 2.10GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 3215904768 total
VM: 2147352576, free: 1925050368



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Fri 18/10/2013 13:19:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101813-83101-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x19 (0x22, 0xFFFFF8A004200000, 0x1, 0x0)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Fri 18/10/2013 13:19:31 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: avgldx64.sys (avgldx64+0x7649)
Bugcheck code: 0x19 (0x22, 0xFFFFF8A004200000, 0x1, 0x0)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\avgldx64.sys
product: AVG Internet Security
company: AVG Technologies CZ, s.r.o.
description: AVG AVI Loader Driver
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: avgldx64.sys (AVG AVI Loader Driver, AVG Technologies CZ, s.r.o.).
Google query: avgldx64.sys AVG Technologies CZ, s.r.o. BAD_POOL_HEADER




On Thu 17/10/2013 18:18:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101813-82961-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x19 (0x22, 0xFFFFF8A004200000, 0x1, 0x0)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 17/10/2013 17:49:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101713-83023-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x19 (0x22, 0xFFFFF8A004200000, 0x1, 0x0)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 17/10/2013 17:36:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101713-83101-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x19 (0x22, 0xFFFFF8A004200000, 0x1, 0x0)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Wed 16/10/2013 21:28:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101613-87797-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x19 (0x22, 0xFFFFF8A004200000, 0x1, 0x0)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Wed 16/10/2013 21:13:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101613-87188-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x19 (0x22, 0xFFFFF8A004200000, 0x1, 0x0)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Wed 16/10/2013 20:33:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101613-90277-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x19 (0x22, 0xFFFFF8A004200000, 0x1, 0x0)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.



--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

8 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

avgldx64.sys (AVG AVI Loader Driver, AVG Technologies CZ, s.r.o.)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

Non sapendo cosa fare nello specifico, e capendo per grandi linee che il problema era dovuto ad un driver di AVG, ho riavviato in mod provv e l'ho reinstallato. Come per magia al riavvio il pc non mi ha dato problemi (anche se per accendersi c'è stato un bel po...); sono andata si Windows update e ho visto che sono presenti 4 aggiornamenti importanti che adesso installerò.

Il problema è risolto o mi consigliate di fare qualcos'altro? Ho letto di un programma che si chiama RefreshPC, mi consigliate si installarlo ed eseguirlo o no?
alessia84
Utente Senior
 
Post: 132
Iscritto il: 18/07/06 14:33

Re: pc spento durante aggiornamento

Postdi Dylan666 » 18/10/13 16:09

disattiva l'antivirus durante l'aggiornamento, solo a scopo precauzionale.
Comunque se riappare il problema sai dove mettere le mani
Avatar utente
Dylan666
Moderatore
 
Post: 38040
Iscritto il: 18/11/03 16:46

Re: pc spento durante aggiornamento

Postdi alessia84 » 18/10/13 16:27

Ok aggiornamenti.
Ma è sempre tutto molto lento...quando riavvio ci sta almeno 10 minuti prima di attivarsi.
E poi dal log che ho copiato prima c'è questo ntoskrnl.exe che compare spesso...che posso fare?
Consigli di utilizzare il prg RefreshPC? ho provato a ripristinare utilizzando un punto di ripristino di fine settembre, ma non va a buon fine.
alessia84
Utente Senior
 
Post: 132
Iscritto il: 18/07/06 14:33

Re: pc spento durante aggiornamento

Postdi Dylan666 » 18/10/13 17:19

anche un altro utente lamentava lentezza dopo l'upgrade a 8.1 non so se sia un caso.
RefreshPC non lo conosco.
Avatar utente
Dylan666
Moderatore
 
Post: 38040
Iscritto il: 18/11/03 16:46

Re: pc spento durante aggiornamento

Postdi nikita75 » 22/10/13 12:16

ciao Alessia84 , se leggi ancora questo post hai risolto il problema ?
Avatar utente
nikita75
Utente Senior
 
Post: 4387
Iscritto il: 31/07/09 13:36


Torna a Software Windows


Topic correlati a "pc spento durante aggiornamento":


Chi c’è in linea

Visitano il forum: Nessuno e 9 ospiti