schermata blu, che palle!!!
vi posto direttalemente il log che mi ha dato il programma :
se ho capito bene la causa sarebbero dei driver non aggiornati, capito bene?
Attendo gli esperti :)
System Information (local)
--------------------------------------------------------------------------------
computer name: PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Pentium(R) Dual-Core CPU T4400 @ 2.20GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 4260286464 total
VM: 2147352576, free: 1925595136
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Fri 09/03/2012 13:22:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030912-18174-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0xB9D01)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFFFED, 0x8, 0xFFFFFFED)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 260.99
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 260.99
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 260.99 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation KMODE_EXCEPTION_NOT_HANDLED
On Fri 09/03/2012 13:22:22 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: 0x1E (0xFFFFFFFFC0000005, 0xFFFFFFED, 0x8, 0xFFFFFFED)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 which cannot be identified at this time.
On Thu 08/03/2012 20:54:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030812-17097-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0xFFFFF7FFA51F82F0, 0xD, 0x1, 0xFFFFF8000307418C)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 which cannot be identified at this time.
On Thu 08/03/2012 19:18:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030812-20623-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0xFFFFF7FF8C2BF028, 0xD, 0x0, 0xFFFFF80003083180)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 which cannot be identified at this time.
On Thu 08/03/2012 13:51:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030812-17222-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x3D (0xFFFFF80000B9C010, 0x0, 0x0, 0xFFFFF80003083139)
Error: INTERRUPT_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 bug check appears very infrequently.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sat 11/02/2012 21:48:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021112-23041-01.dmp
This was probably caused by the following module: ataport.sys (ataport+0x17EF)
Bugcheck code: 0x50 (0xFFFFFFFFFA8B48E1, 0x1, 0xFFFFF80003086104, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\ataport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ATAPI Driver Extension
Bug check description: This indicates that invalid system memory has been referenced.
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 Tue 31/01/2012 20:26:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\013112-17830-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x97DA)
Bugcheck code: 0x50 (0xFFFFFFFFFA8B48E1, 0x1, 0xFFFFF80003085104, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 Mon 23/01/2012 20:47:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012312-16692-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0xFFFFF7FF8C2C3028, 0xD, 0x0, 0xFFFFF80003087180)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 which cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
8 crash dumps have been found and analyzed. A third party driver has 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:
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 260.99 , NVIDIA Corporation)
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.