problema schermata blu

[SHEKER..BLOW]

salve a tutti e da due giorni che quando vado a spegnere il computer dopo tutta la sua procedura di salvataggio e si sta per spegnere compare una schermata blu dicendomi di un errore e in basso un dump che parte do 0 ad arrivare al 100% e poi riaccendere il pc in automatico ( in pratica è impossibile spegnere il pc a meno che non spenga il tastino dietro per "metterlo ko definitivamente" )

e quando il pc viene autoriavviato mi ritrovo questo.

Windows è stato ripristinato in seguito ad un arresto imprevisto del sistema.
e visualizzando i dettagli esce scritto questo,

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

Ulteriori informazioni sul problema:
BCCode: 10d
BCP1: 0000000D
BCP2: 88C30688
BCP3: 878697B0
BCP4: 88BC31A0
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

File che contribuiscono alla descrizione del problema:
C:\Windows\Minidump\080611-27627-01.dmp
C:\Users\Ale\AppData\Local\Temp\WER-75504-0.sysdata.xml

Leggere l'informativa sulla privacy online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0410

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



cosa dovrei fare ??


grazie mille !

[Eress]

cosa dovrei fare ??
Seguire passo passo qui

http://www.hwupgrade.it/forum/showthread.php?t=1955371

servono i files dmp

[SHEKER..BLOW]

scusami davvero ma sono poco pratico e non ci cpaisco nulla ho installato
Windows_Win7SP1.7601.17514.101119-1850.X86FRE.Symbols
e anche
dbg_x86_6.11.1.404

ma quando arrivo che devo aprire i codici con il programma che devo dare il percorso esatto dei symbol non succede nulla do il percorso ma nulla, poi ho provato ad aprire i file dmp degli errori ma quando ne apro uno oltre ad uscire un pò di scritte non succede nient altro

[SHEKER..BLOW]

ho scaricato un programma in grado di capire da dove derivano questi errori si chiama, WhoCrashed.
mi ha trovato 10 errori adesso vi posto quello che mi è uscito dall'analisi



On Sat 06/08/2011 11:27:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080611-50450-01.dmp
This was probably caused by the following module: libusb0.sys (libusb0+0x428C)
Bugcheck code: 0x10D (0xD, 0xFFFFFFFF8889A4D8, 0xFFFFFFFF86527140, 0xFFFFFFFF8889A8F0)
Error: WDF_VIOLATION
file path: C:\Windows\system32\drivers\libusb0.sys
product: LibUSB-Win32 - Kernel Driver
company: http://libusb-win32.sourceforge.net
description: LibUSB-Win32 - Kernel Driver
Bug check description: This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.
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: libusb0.sys (LibUSB-Win32 - Kernel Driver, http://libusb-win32.sourceforge.net).
Google query: libusb0.sys http://libusb-win32.sourceforge.net WDF_VIOLATION




On Sat 06/08/2011 11:27:18 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: libusb0.sys (libusb0!DriverEntry+0x213C)
Bugcheck code: 0x10D (0xD, 0xFFFFFFFF8889A4D8, 0xFFFFFFFF86527140, 0xFFFFFFFF8889A8F0)
Error: WDF_VIOLATION
file path: C:\Windows\system32\drivers\libusb0.sys
product: LibUSB-Win32 - Kernel Driver
company: http://libusb-win32.sourceforge.net
description: LibUSB-Win32 - Kernel Driver
Bug check description: This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.
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: libusb0.sys (LibUSB-Win32 - Kernel Driver, http://libusb-win32.sourceforge.net).
Google query: libusb0.sys http://libusb-win32.sourceforge.net WDF_VIOLATION




On Sat 06/08/2011 10:22:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080611-29827-01.dmp
This was probably caused by the following module: libusb0.sys (libusb0+0x428C)
Bugcheck code: 0x10D (0xD, 0xFFFFFFFF889814D8, 0xFFFFFFFF8774F030, 0xFFFFFFFF889874D0)
Error: WDF_VIOLATION
file path: C:\Windows\system32\drivers\libusb0.sys
product: LibUSB-Win32 - Kernel Driver
company: http://libusb-win32.sourceforge.net
description: LibUSB-Win32 - Kernel Driver
Bug check description: This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.
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: libusb0.sys (LibUSB-Win32 - Kernel Driver, http://libusb-win32.sourceforge.net).
Google query: libusb0.sys http://libusb-win32.sourceforge.net WDF_VIOLATION




On Sat 06/08/2011 09:51:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080611-52868-01.dmp
This was probably caused by the following module: libusb0.sys (libusb0+0x428C)
Bugcheck code: 0x10D (0xD, 0xFFFFFFFF88C8C9D0, 0xFFFFFFFF878256A0, 0xFFFFFFFF88C915D8)
Error: WDF_VIOLATION
file path: C:\Windows\system32\drivers\libusb0.sys
product: LibUSB-Win32 - Kernel Driver
company: http://libusb-win32.sourceforge.net
description: LibUSB-Win32 - Kernel Driver
Bug check description: This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.
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: libusb0.sys (LibUSB-Win32 - Kernel Driver, http://libusb-win32.sourceforge.net).
Google query: libusb0.sys http://libusb-win32.sourceforge.net WDF_VIOLATION




On Sat 06/08/2011 01:06:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080611-27627-01.dmp
This was probably caused by the following module: libusb0.sys (libusb0+0x428C)
Bugcheck code: 0x10D (0xD, 0xFFFFFFFF88C30688, 0xFFFFFFFF878697B0, 0xFFFFFFFF88BC31A0)
Error: WDF_VIOLATION
file path: C:\Windows\system32\drivers\libusb0.sys
product: LibUSB-Win32 - Kernel Driver
company: http://libusb-win32.sourceforge.net
description: LibUSB-Win32 - Kernel Driver
Bug check description: This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.
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: libusb0.sys (LibUSB-Win32 - Kernel Driver, http://libusb-win32.sourceforge.net).
Google query: libusb0.sys http://libusb-win32.sourceforge.net WDF_VIOLATION




On Sat 06/08/2011 00:52:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080611-14554-01.dmp
This was probably caused by the following module: libusb0.sys (libusb0+0x428C)
Bugcheck code: 0x10D (0xD, 0xFFFFFFFF888FB5C0, 0xFFFFFFFF890F1470, 0xFFFFFFFF8784B740)
Error: WDF_VIOLATION
file path: C:\Windows\system32\drivers\libusb0.sys
product: LibUSB-Win32 - Kernel Driver
company: http://libusb-win32.sourceforge.net
description: LibUSB-Win32 - Kernel Driver
Bug check description: This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.
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: libusb0.sys (LibUSB-Win32 - Kernel Driver, http://libusb-win32.sourceforge.net).
Google query: libusb0.sys http://libusb-win32.sourceforge.net WDF_VIOLATION




On Sat 06/08/2011 00:32:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080611-17487-01.dmp
This was probably caused by the following module: libusb0.sys (libusb0+0x428C)
Bugcheck code: 0x10D (0xD, 0xFFFFFFFF864C6828, 0xFFFFFFFF893FC4D8, 0xFFFFFFFF86932468)
Error: WDF_VIOLATION
file path: C:\Windows\system32\drivers\libusb0.sys
product: LibUSB-Win32 - Kernel Driver
company: http://libusb-win32.sourceforge.net
description: LibUSB-Win32 - Kernel Driver
Bug check description: This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.
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: libusb0.sys (LibUSB-Win32 - Kernel Driver, http://libusb-win32.sourceforge.net).
Google query: libusb0.sys http://libusb-win32.sourceforge.net WDF_VIOLATION




On Fri 05/08/2011 01:35:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080511-16317-01.dmp
This was probably caused by the following module: libusb0.sys (libusb0+0x428C)
Bugcheck code: 0x10D (0xD, 0xFFFFFFFF887AC020, 0xFFFFFFFF89044908, 0xFFFFFFFF87875150)
Error: WDF_VIOLATION
file path: C:\Windows\system32\drivers\libusb0.sys
product: LibUSB-Win32 - Kernel Driver
company: http://libusb-win32.sourceforge.net
description: LibUSB-Win32 - Kernel Driver
Bug check description: This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.
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: libusb0.sys (LibUSB-Win32 - Kernel Driver, http://libusb-win32.sourceforge.net).
Google query: libusb0.sys http://libusb-win32.sourceforge.net WDF_VIOLATION




On Fri 05/08/2011 00:54:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080511-15225-01.dmp
This was probably caused by the following module: libusb0.sys (libusb0+0x428C)
Bugcheck code: 0x10D (0xD, 0xFFFFFFFF88C7A160, 0xFFFFFFFF88940230, 0xFFFFFFFF88C977D0)
Error: WDF_VIOLATION
file path: C:\Windows\system32\drivers\libusb0.sys
product: LibUSB-Win32 - Kernel Driver
company: http://libusb-win32.sourceforge.net
description: LibUSB-Win32 - Kernel Driver
Bug check description: This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.
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: libusb0.sys (LibUSB-Win32 - Kernel Driver, http://libusb-win32.sourceforge.net).
Google query: libusb0.sys http://libusb-win32.sourceforge.net WDF_VIOLATION




On Fri 05/08/2011 00:52:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080511-17487-01.dmp
This was probably caused by the following module: libusb0.sys (libusb0+0x428C)
Bugcheck code: 0x10D (0xD, 0xFFFFFFFF86424328, 0xFFFFFFFF89060408, 0xFFFFFFFF86D1D8A8)
Error: WDF_VIOLATION
file path: C:\Windows\system32\drivers\libusb0.sys
product: LibUSB-Win32 - Kernel Driver
company: http://libusb-win32.sourceforge.net
description: LibUSB-Win32 - Kernel Driver
Bug check description: This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.
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: libusb0.sys (LibUSB-Win32 - Kernel Driver, http://libusb-win32.sourceforge.net).
Google query: libusb0.sys http://libusb-win32.sourceforge.net WDF_VIOLATION





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

10 crash dumps have been found and analyzed. 10 third party drivers have 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:

libusb0.sys (LibUSB-Win32 - Kernel Driver, http://libusb-win32.sourceforge.net)

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.




Io ho seguito le istruzioni e ho scaricato dal link proposto, libusb-win32
un programma che mi ha fatto fare una specie di controllo di tutti i miei dispositivi fino ad ora installati all'interno del pc (uno per uno anche se non erano collegati e tutto è andato bene ) ma il problema persiste :(

[Il Bruco]

Libusb0.sys con descrizione libusb-Win32 - i driver del kernel è un file di driver da http://libusb-win32.sourceforge.net società appartenente al prodotto libusb-Win32 - driver del kernel.

C:\Program_Files\PSPdisp\libusb0.sys

http://www.removespywareguides.com/libusb0-sys-how-to-remove.html

[Eress]

Quello è un driver collegato alle porte usb come si capisce anche dal nome ed è un driver che appartiene a questo software

nel caso prova a disinstallarlo

[Il Bruco]

Quello è un driver collegato alle porte usb come si capisce anche dal nome ed è un driver che appartiene a questo software

http://www.file.net/it/processo/libusbd-nt.exe.html

nel caso prova a disinstallarlo

L'errore a lui glielo dà libusb0.sys e non libusbd-nt.exe o libusbdotnet.dll, gli ho postato le istruzioni e la tool per rimuovere l'errore di libusb0.sys

[Eress]

L'errore a lui glielo dà libusb0.sys e non libusbd-nt.exe o libusbdotnet.dll, gli ho postato le istruzioni e la tool per rimuovere l'errore di libusb0.sys
Vero c'era una d di troppo, allora sarà malware :D

[SHEKER..BLOW]

grazie a tutti voi per la vostre risposte e i vosri aiuti, non so ocme ma grazie a ilprogramma libUSB che mi ha fatto controllare i driver delle porte usb mi ha fatto capire che l'errore era dovuto ad una chiavetta usb staccata mentre il pc era in fase di spegnimento e quindi aveva causato questo problema, ora non so se il problema è stato risolto grazie a questo, oppure grazie al fatto che ho installato tutti gli aggiornamenti presenti insieme al service pack 1, l'importante è che tutto sia tornato alla normalità grazie a tutti sempre molto presenti !

qui si può chiudere