esc.exe
07-12-2010, 23:17
Ciao a tutti. Ho urgente bisogno d'aiuto perché la situazione è veramente insostenibile. Brevemente cercherò di spiegarvi il mio problema mentre come vedete in basso riporto parzialmente il report fornito dal software WHOCRASHED home edition.
Sostanzialmente questo crash (continuo ma a intervalli irregolari) si verifica solo ed esclusivamente durante la visione di video (film) sia in streaming che da disco (uso vlc come player). Con vlc a volte compare la schermata blu altre invece si blocca tutto ma nn riesco a muovere neanche il cursore del mouse. In streaming invece esce sempre la schermata blu, ma cosa abbastanza curiosa è che l'audio è disturbato. In pratica all'inizio della visione il disturbo è assente o impercettibile poi, con il passare del tempo, cresce sempre di più. Per darvi una idea di questo disturbo lo paragonerei a quello "scoppiettio" classico di quando si aumenta troppo il volume ma le casse nn reggono...non so se ho reso l'idea. Grazie
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Pentium(R) 4 CPU 3.00GHz Intel586, level: 15
2 logical processors, active mask: 3
RAM: 2146754560 total
VM: 2147352576, free: 2001915904
On Tue 07/12/2010 19:38:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120710-14828-01.dmp
This was probably caused by the following module: Unknown (0x00000000)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0x0, 0xFFFFFFFF949BFF64, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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: Unknown . Google query: Unknown KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Tue 07/12/2010 19:38:50 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x1E)
Bugcheck code: 0x8E (0xFFFFFFFFC0000005, 0x0, 0xFFFFFFFF949BFF64, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a kernel-mode application generated an exception that the error handler did not catch.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Tue 07/12/2010 19:35:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120710-15765-01.dmp
This was probably caused by the following module: Unknown (0x00000000)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0x0, 0xFFFFFFFF9A41FF64, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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: Unknown . Google query: Unknown KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Tue 07/12/2010 11:59:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120710-12750-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x30775)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF9153A775, 0xFFFFFFFF8E326BC4, 0xFFFFFFFF8E3267A0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Sun 05/12/2010 21:35:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120510-14046-01.dmp
This was probably caused by the following module: vsdatant.sys (vsdatant+0x26098)
Bugcheck code: 0xC5 (0x4, 0x2, 0x1, 0xFFFFFFFF829534A3)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\drivers\vsdatant.sys
product: ZoneAlarm Firewalling Driver
company: Check Point Software Technologies LTD
description: ZoneAlarm Firewalling Driver
Bug check description: This indicates that the system attempted to access invalid 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. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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: vsdatant.sys (ZoneAlarm Firewalling Driver, Check Point Software Technologies LTD).
Google query: vsdatant.sys Check Point Software Technologies LTD DRIVER_CORRUPTED_EXPOOL
On Sun 05/12/2010 12:53:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120510-12843-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x316F63)
Bugcheck code: 0x124 (0x0, 0xFFFFFFFF85744594, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
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 a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time
Sostanzialmente questo crash (continuo ma a intervalli irregolari) si verifica solo ed esclusivamente durante la visione di video (film) sia in streaming che da disco (uso vlc come player). Con vlc a volte compare la schermata blu altre invece si blocca tutto ma nn riesco a muovere neanche il cursore del mouse. In streaming invece esce sempre la schermata blu, ma cosa abbastanza curiosa è che l'audio è disturbato. In pratica all'inizio della visione il disturbo è assente o impercettibile poi, con il passare del tempo, cresce sempre di più. Per darvi una idea di questo disturbo lo paragonerei a quello "scoppiettio" classico di quando si aumenta troppo il volume ma le casse nn reggono...non so se ho reso l'idea. Grazie
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Pentium(R) 4 CPU 3.00GHz Intel586, level: 15
2 logical processors, active mask: 3
RAM: 2146754560 total
VM: 2147352576, free: 2001915904
On Tue 07/12/2010 19:38:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120710-14828-01.dmp
This was probably caused by the following module: Unknown (0x00000000)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0x0, 0xFFFFFFFF949BFF64, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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: Unknown . Google query: Unknown KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Tue 07/12/2010 19:38:50 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x1E)
Bugcheck code: 0x8E (0xFFFFFFFFC0000005, 0x0, 0xFFFFFFFF949BFF64, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a kernel-mode application generated an exception that the error handler did not catch.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Tue 07/12/2010 19:35:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120710-15765-01.dmp
This was probably caused by the following module: Unknown (0x00000000)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0x0, 0xFFFFFFFF9A41FF64, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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: Unknown . Google query: Unknown KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Tue 07/12/2010 11:59:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120710-12750-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x30775)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF9153A775, 0xFFFFFFFF8E326BC4, 0xFFFFFFFF8E3267A0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Sun 05/12/2010 21:35:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120510-14046-01.dmp
This was probably caused by the following module: vsdatant.sys (vsdatant+0x26098)
Bugcheck code: 0xC5 (0x4, 0x2, 0x1, 0xFFFFFFFF829534A3)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\drivers\vsdatant.sys
product: ZoneAlarm Firewalling Driver
company: Check Point Software Technologies LTD
description: ZoneAlarm Firewalling Driver
Bug check description: This indicates that the system attempted to access invalid 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. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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: vsdatant.sys (ZoneAlarm Firewalling Driver, Check Point Software Technologies LTD).
Google query: vsdatant.sys Check Point Software Technologies LTD DRIVER_CORRUPTED_EXPOOL
On Sun 05/12/2010 12:53:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120510-12843-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x316F63)
Bugcheck code: 0x124 (0x0, 0xFFFFFFFF85744594, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
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 a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time