CRASH schermata BLU della Morte

[stefano.pomes]

ciao! da troppo tempo sto cercando di risolvere questo problema senza successo.

Il computer sotto-sforzo mi va in crash. Ho provato a formattare ma niente. Avevo windows Xp e andava in crash. Ora ho windows 7 e mi continua ad andare in crash. Le ho provate tutte. Ho provato ad installare i banchi di memoria singolarmente e a fare il controllo ma niente.

Come posso fare?
questo è il report di WhoCrash:

On Sat 25/05/2013 07:56:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052513-19110-01.dmp
This was probably caused by the following module: tascusb2.sys (tascusb2+0x1EE78)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF92B8BD66, 0xFFFFFFFF9F1B7B0C, 0xFFFFFFFF9F1B76F0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\tascusb2.sys
product: TASCAM USB 2.0 Driver
company: TASCAM
description: TASCAM USB 2.0 Audio Driver
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.
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: tascusb2.sys (TASCAM USB 2.0 Audio Driver, TASCAM).
Google query: TASCAM SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



On Sat 25/05/2013 07:56:30 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!KeBugCheckEx+0x1E)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFFFFF92B8BD66, 0xFFFFFFFF9F1B7B0C, 0xFFFFFFFF9F1B76F0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
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: ntkrpamp.exe .
Google query: ntkrpamp.exe SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
.
WhoCrash



mi dareste una mano???grazie mille....

Stefano

[piero.mac]

prova a leggere questa pagina:

http://support.microsoft.com/kb/983615/it

Avevo un problema del genere con la scheda grafica su un pc HP. Il problema mi e' comparso dopo avere aggiornato la scheda video (una NVIDIA) con una release successiva presa dal sito NVIDIA. Per chiudere questo errore ho dovuto riprendere il vecchio software legato al pc con la versione rilasciata da HP, dal sito di HP.

I PC di marca spesso e volentieri modificano il BIOS della scheda madre riducendo od impostanto di default delle opzioni non modificabili.

Dovresti comunque indicare se e' un desktop od un laptop e se di marca oppure uno generico.

[comas17]

Originariamente inviato da stefano.pomes

This was probably caused by the following module: tascusb2.sys (tascusb2+0x1EE78)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF92B8BD66, 0xFFFFFFFF9F1B7B0C, 0xFFFFFFFF9F1B76F0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\tascusb2.sys
product: TASCAM USB 2.0 Driver
company: TASCAM
description: TASCAM USB 2.0 Audio Driver

Cos'è questo TASCAM ... ? una scheda audio particolare ?
Hai provato a vedere qui se trovi driver aggiornati per il tuo sostema operativo ?
http://tascam.com/support/downloads/

[stefano.pomes]

VI ALLEGO l'ultimissimo CRASH DUMP:

"On Tue 28/05/2013 21:08:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052813-19188-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x3F3F)
Bugcheck code: 0x1000008E (0xFFFFFFFFC000001D, 0xFFFFFFFF93376F3F, 0xFFFFFFFF8078AE34, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\usbport.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver porta USB 1.1 & 2.0
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 Tue 28/05/2013 21:08:22 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.sys (hal!KeRaiseIrqlToSynchLevel+0x8F)
Bugcheck code: 0x8E (0xFFFFFFFFC000001D, 0xFFFFFFFF93376F3F, 0xFFFFFFFF8078AE34, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a kernel-mode application generated an exception that the error handler did not catch.
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: hal.sys .
Google query: hal.sys KERNEL_MODE_EXCEPTION_NOT_HANDLED



On Tue 28/05/2013 18:42:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052813-32479-01.dmp
This was probably caused by the following module: hidusb.sys (hidusb+0x1BCE)
Bugcheck code: 0x1000008E (0xFFFFFFFFC000001D, 0xFFFFFFFF81F42BCE, 0xFFFFFFFF807E4A6C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\hidusb.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB Miniport Driver for Input Devices
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 Sat 25/05/2013 07:56:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052513-19110-01.dmp
This was probably caused by the following module: tascusb2.sys (tascusb2+0x1EE78)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF92B8BD66, 0xFFFFFFFF9F1B7B0C, 0xFFFFFFFF9F1B76F0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\tascusb2.sys
product: TASCAM USB 2.0 Driver
company: TASCAM
description: TASCAM USB 2.0 Audio Driver
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.
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: tascusb2.sys (TASCAM USB 2.0 Audio Driver, TASCAM).
Google query: TASCAM SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M"


per COMAS: è una scheda audio esterna, i driver sono aggiornati.

per PIERO MAC: questo è il mio desktop: Core 2 Quad CPU q8300 2,5 GHZ
sistema operativo a 32bit. è un generico assemblato.

[stefano.pomes]

per PIERO.MAC.

ho scaricato l'aggiornamento che dalla descrizione sembra fare proprio al caso mio.
Quando provo ad installare il pacchetto mi dice: impossibile applicare l'aggiornamento al computer.

..
..
..

:-(

[comas17]

Il problema sembra essere quasi certamente legato alle porte USB (prima avevi errori solo relativi a questi dispositivo TASCAM, ora ne hai anche altri, tutti legati a USB)

Hai una scheda apposita con porte USB ? le porte sono sulla scheda madre ? io proverei ad aggiornare i driver delle porte USB; cerca tra i driver della tua scheda madre (se sono lì)

[stefano.pomes]

ho aggiornato le usb..

aspettiamo fiduciosi :-) ..

..

[stefano.pomes]

niente da fare..
la schermata BLU è più ostinata di noi..
vi posto il report:

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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 30/05/2013 08:19:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\053013-23166-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x8AF7F)
Bugcheck code: 0xD1 (0x2AC, 0x2, 0x1, 0xFFFFFFFF8B4ACF7F)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver TCP/IP
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 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 Thu 30/05/2013 08:19:33 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.sys (hal!KeRaiseIrqlToSynchLevel+0x8F)
Bugcheck code: 0xD1 (0x2AC, 0x2, 0x1, 0xFFFFFFFF8B4ACF7F)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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.
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: hal.sys .
Google query: hal.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Tue 28/05/2013 23:07:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052913-26738-01.dmp
This was probably caused by the following module: msrpc.sys (msrpc+0x11BC1)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0x7C141A36, 0xFFFFFFFF8D01BAA8, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\msrpc.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Remote Procedure Call Provider
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 Tue 28/05/2013 21:08:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052813-19188-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x3F3F)
Bugcheck code: 0x1000008E (0xFFFFFFFFC000001D, 0xFFFFFFFF93376F3F, 0xFFFFFFFF8078AE34, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\usbport.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver porta USB 1.1 & 2.0
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 Tue 28/05/2013 18:42:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052813-32479-01.dmp
This was probably caused by the following module: hidusb.sys (hidusb+0x1BCE)
Bugcheck code: 0x1000008E (0xFFFFFFFFC000001D, 0xFFFFFFFF81F42BCE, 0xFFFFFFFF807E4A6C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\hidusb.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB Miniport Driver for Input Devices
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 Sat 25/05/2013 07:56:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052513-19110-01.dmp
This was probably caused by the following module: tascusb2.sys (tascusb2+0x1EE78)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF92B8BD66, 0xFFFFFFFF9F1B7B0C, 0xFFFFFFFF9F1B76F0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\tascusb2.sys
product: TASCAM USB 2.0 Driver
company: TASCAM
description: TASCAM USB 2.0 Audio Driver
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.
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: tascusb2.sys (TASCAM USB 2.0 Audio Driver, TASCAM).
Google query: TASCAM SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



....

HEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEeeeeeeeeeeee eeeelpppppppppp

[piero.mac]

L'errore avviene su piu' driver. Quindi potrebbe essere la memoria fisica RAM o la memoria del kernel nel file di paging. Altro possibile guaio potrebbe averlo l'HD ma noteresti anche altri sintomi.
Chi piu' di tutti potrebbe influire sui precedenti nominati e' la scheda video con i suoi driver. Di solito non basta la semplice disinstallazione del driver ma occorre un tool appropriato che completi con la pulizia del registro.

Comincerei a "staccare" un po' di roba dal pc e provare partendo con su la sola memoria e HD. Fai un test approfondito della ram partendo da un disco live di linux tipo gparted che offrono l'opzione del test ram. Controlla la funzionalita' dell'HD (seagate e maxtor offrono vari tools. Occhio alla penna quando li usi). Una bella setacciata per virus e malware e' pure d'obbligo.

[stefano.pomes]

Ti devo dire la verità.. non sono così pratico.. nè di linux nè di disattivare/attivare hardware..
mi potresti spiegare passo passo???