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