PROBLEMA Windows 8, evento critico improvviso e bluescreen

Pubblicità
Stato
Discussione chiusa ad ulteriori risposte.
B

Bullseye

Nuovo Utente
Messaggi
8
Reazioni
0
Punteggio
24
Come da titolo ho avuto il seguente problema col mio nuovo computer (comprato 4 giorni fa, asus pc desktop preassemblato)

nelle ultime 24 ore ho avuto ben 6 errori di livello critico, controllando nel registro eventi c'è scritto:

Origine:Kernel Power
ID evento:41
Categoria attività: (63)
Parola chiave: (2)

Le prime quattro volte che mi è capitato questo errore non ero al computer, ma era ugualmente acceso perchè era aperto Torrent..dopo qualche ora (non più di due ore) torno al pc accendo il monitor e mi si apre il meno start di win 8 con scritto il messaggio che c'è stato un errore di sistema e il pc è stato riavviato (con inclusa la dicitura "kmode exception not handled" per ulteriori dettagli sull'errore)

Le ultime due volte ero al pc e avevo aperto sia Torrent sia il browser, il computer non era per niente in sovraccarico ma nonostante ciò si è riavviato da solo dopo circa tre-quattri ore dall'accensione ed è comparsa la schermata del blue screen...

Ora mi chiedo...è possibile che il problema sia torrent? da quando mi capita questo problema ho avuto sempre quel programma aperto, ora sto provando a non avviarlo più e a lasciare il computer acceso per diverse ore per vedere cosa succede
mi sembra davvero difficle che sia un problema di sovraccarico, avevo davvero poche applicazioni aperte quando è successo

Quale potrebbe essere quindi la causa di questo problema? Grazie in anticipo per i consigli :ok:
 
ciao scarica whocrashed e posta il risultato della lettura del file dmp
 
Crash Dump Analysis:

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 18/02/2013 14.50.49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021813-18843-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7A040)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFFA801EF4D090, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 18/02/2013 14.50.49 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: aswnet.sys (aswnet+0x310EB)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFFA801EF4D090, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\aswnet.sys
product: Avast Firewall
company: AVAST Software
description: AVAST Firewall Core Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: aswnet.sys (AVAST Firewall Core Driver, AVAST Software).
Google query: AVAST Software KMODE_EXCEPTION_NOT_HANDLED



On Sun 17/02/2013 22.29.28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021713-26218-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0x37F21)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFFA801FEB1476, 0xFFFFFA801DA7DB00, 0x2)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sun 17/02/2013 20.45.23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021713-34718-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7A040)
Bugcheck code: 0xD1 (0x56, 0x2, 0x0, 0xFFFFFA801E9BE2D3)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 17/02/2013 16.58.24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021713-265828-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7A040)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFFA80192749E8, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 17/02/2013 14.39.57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021713-639515-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0x37F21)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFFA8020CBE561, 0xFFFFFA801E70CB00, 0x2)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sun 17/02/2013 11.15.42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021713-19812-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0x3836D)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFFA800E72C771, 0xFFFFFA800CC1AB00, 0x2)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



Conclusion
7 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:

aswnet.sys (AVAST Firewall Core Driver, AVAST Software)

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.


questi sono i dettagli sul report dei crash
 
disattiva temporaneamente avast e vedi se continua a darti noie
 
ok ho disattivato avast e in circa 24 ore per il momento non ha dato più problemi...a questo punto spero che il problema sia risolto, grazie per le istruzioni ;)
tuttavia rimane pur sempre il fatto che il computer ha crashato sei volte in due giorni, putroppo non mi intendo parecchio di computer, e mi chiedevo se il pc è stato danneggiato in qualche modo dopo quello che è successo..
 
no tranquillo non si è danneggiato al posto di avast ti consiglio di mettere avira
 
Stato
Discussione chiusa ad ulteriori risposte.
Pubblicità
Pubblicità
Indietro
Top