PROBLEMA Windows crasha!

Pubblicità

Boars

Nuovo Utente
Messaggi
47
Reazioni
1
Punteggio
26
Salve a tutti, ultimamente sto riscontrando problemi con windows, cioe' quando vedo i video dopo una mezz'oretta crasha con errore'' kmode exception not handled'' (schermata blu e si riavvia) invece quando gioco non mi e' mai capitato. Ho letto alcuni topic dove dicevano di cancellare l'antivirus e di metterne un altro ma questo problema persiste. Cosa devo fare? Perche' sinceramente portarlo in assistenza dopo neanche un mese che lo posseggo non mi va proprio.
Grazie in anticipo.:retard:
 
Whocrashed scaricalo e posta il log qui.
On Wed 11/06/2014 23:00:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061214-5046-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0x7F (0x8, 0xFFFFF8025A9CFE70, 0xFFF7D000228FDFC0, 0xFFFFF802591C833C)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 11/06/2014 23:00:50 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x7F (0x8, 0xFFFFF8025A9CFE70, 0xFFF7D000228FDFC0, 0xFFFFF802591C833C)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 11/06/2014 12:23:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061114-5718-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80211C62B2D, 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 Fri 06/06/2014 15:41:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060614-6984-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0x7F (0x8, 0xFFFFF802208BBE70, 0x64, 0xFFFFF8021EEE9533)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 04/06/2014 19:46:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060414-6968-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0xC2 (0x7, 0x1200, 0x5030224, 0xFFFFC0011CCE96D0)
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
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 Tue 03/06/2014 09:15:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060314-6375-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x103056)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8031DD85056, 0xFFFFD00145A46838, 0xFFFFD00145A46040)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread 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 02/06/2014 16:12:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060214-6765-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x14B1ED)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960001721ED, 0xFFFFD00149F45040, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver Win32 multiutente
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Mon 02/06/2014 15:01:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060214-7125-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF80273D3259C, 0xFFFFE00185083880, 0x0)
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 Sat 31/05/2014 10:08:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\053114-6265-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80284108AAD, 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 Sat 31/05/2014 08:51:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\053114-6281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF801BDC6BC63, 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.




Conclusion

16 crash dumps have been found and analyzed. Only 10 are included in this report. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.


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.


(ah! e' un'altra cosa quando si riavvia il computer dopo il crash, avendo una chiavetta w-fi, mi dice che non e' collegata O.o)
 
Ciao ma hai installato di recente qualche dispositivo hardware USB, memory ecc ecc ?

Se si rimuovili per provare se il PC funziona benissimo senza di essa, L'hardware potrebbe essere difettoso.

Prova ad aggiornare tutti i driver del PC all'ultima versione.

Hai per caso overcloccato il PC ?

Purtroppo in alcuni PC, non sono in grado di gestire l'overclock.
 
Ciao ma hai installato di recente qualche dispositivo hardware USB, memory ecc ecc ?

Se si rimuovili per provare se il PC funziona benissimo senza di essa, L'hardware potrebbe essere difettoso.

Prova ad aggiornare tutti i driver del PC all'ultima versione.

Hai per caso overcloccato il PC ?

Purtroppo in alcuni PC, non sono in grado di gestire l'overclock.
no non ho fatto overclock, penso piu all'ipotesi del dispositivo usb, cioe' la chiavetta wi-fi perche' quando si riavvia il sistema e' come se si scollegasse automaticamente (la chiavetta wi fi l'ho collegata con il supporto USB).Pero' se fosse quello il problema cosa posso fare? Senza la chiavetta non mi posso collegare a internet.... comunque si ho aggiornato tutti i driver tramite driver booster

- - - Updated - - -

Ok proprio ora ho aggiornato il software della chiavetta n300. Potrebbe essere quello il problema che faceva riavviare il pc? (Ora provo e ti diro').
 
Ultima modifica:
no non ho fatto overclock, penso piu all'ipotesi del dispositivo usb, cioe' la chiavetta wi-fi perche' quando si riavvia il sistema e' come se si scollegasse automaticamente (la chiavetta wi fi l'ho collegata con il supporto USB).Pero' se fosse quello il problema cosa posso fare? Senza la chiavetta non mi posso collegare a internet.... comunque si ho aggiornato tutti i driver tramite driver booster

- - - Updated - - -

Ok proprio ora ho aggiornato il software della chiavetta n300. Potrebbe essere quello il problema che faceva riavviare il pc? (Ora provo e ti diro').

Se il dispositivo wifi USB è la causa del problema e togliendolo il computer funziona e non ti da schermata blu, allora dovresti sostituirlo infatti il dispositivo potrebbe essere difettoso o al massimo aggiornarlo attendo tue notizie.
 
Ultima modifica:
Se il dispositivo wifi USB è la causa del problema e togliendolo il computer funziona e non ti da schermata blu, allora dovresti sostituirlo infatti il dispositivo potrebbe essere difettoso o al massimo aggiornarlo attendo tue notizie.
[FONT=Segoe UI, Arial]On Sat 14/06/2014 16:12:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061414-5671-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x153FA0)
Bugcheck code: 0xDE (0x2, 0xFFFFC00102A158B8, 0xFFEFC00102A158B9, 0x35303C8C0)
Error: [FONT=Segoe UI, Arial]POOL_CORRUPTION_IN_FILE_AREA[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a driver has corrupted pool memory that is used for holding pages destined for disk.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


Continua a crashare ....
[/FONT]:retard:
 
On Sat 14/06/2014 16:12:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061414-5671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0xDE (0x2, 0xFFFFC00102A158B8, 0xFFEFC00102A158B9, 0x35303C8C0)
Error: POOL_CORRUPTION_IN_FILE_AREA
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 driver has corrupted pool memory that is used for holding pages destined for disk.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


Continua a crashare ....
:retard:

Ciao sembra essere il driver della scheda video a dare dei problemi, ma hai ATI o Nvidia ? hai già aggiornato tutti i driver compresso quella della scheda video ?
 
Ultima modifica:
Ciao sembra essere il driver della scheda video a dare dei problemi, ma hai ATI o Nvidia ? hai già aggiornato tutti i driver compresso quella della scheda video ?
si l'ho aggiornato... non so che fare (scusa il ritardo della risposta ma un fulmine ha preso l'antenna e ha bruciato il mio monitor e modem...)
 
Ultima modifica:
Pubblicità
Pubblicità
Indietro
Top