Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 27/12/2009 12:31:34 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x50 (0xFFFFF9008B5EDB41, 0x0, 0xFFFFF960001EE507, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_A REA
Dump file: C:\Windows\Minidump\122709-29764-01.dmp
file path: C:\Windows\system32\win32k.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Controlador Win32 multiusuario
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.
On Sat 26/12/2009 11:15:16 your computer crashed
This was likely caused by the following module: p0870evx.sys
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80001A79517, 0xFFFFF88008353FC0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\122609-29406-01.dmp
file path: C:\Windows\system32\drivers\p0870evx.sys
company: Creative Technology Ltd.
description: Creative Evx Driver (64-bit)
On Fri 25/12/2009 6:10:08 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80001E962C4, 0xFFFFF8800BBB2680, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\122509-17440-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.
On Sun 20/12/2009 8:29:48 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HAND LED
Dump file: C:\Windows\Minidump\122009-16863-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.
On Fri 18/12/2009 20:08:30 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0x1, 0x2, 0x1, 0xFFFFF80001A8C502)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\121809-29296-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.
On Fri 11/12/2009 19:16:05 your computer crashed
This was likely caused by the following module: hardware
Bugcheck code: 0x3B (0x80000003, 0xFFFFF80001D7553D, 0xFFFFF88007E3ECA0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\121109-29577-01.dmp
On Fri 11/12/2009 19:00:41 your computer crashed
This was likely caused by the following module: nvlddmkm.sys
Bugcheck code: 0x1A (0x41287, 0x1EC86BB, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\121109-19780-01.dmp
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 195.62
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 195.62
On Fri 11/12/2009 0:35:46 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80001AC022B, 0xFFFFF8800211D908, 0xFFFFF8800211D160)
Error: SYSTEM_THREAD_EXCEPTION_ NOT_HANDLED_M
Dump file: C:\Windows\Minidump\121109-27206-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.
On Tue 08/12/2009 21:54:31 your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880012578AB, 0xFFFFF88001F8F978, 0xFFFFF88001F8F1D0)
Error: SYSTEM_THREAD_EXCEPTION_ NOT_HANDLED_M
Dump file: C:\Windows\Minidump\120809-30217-01.dmp
file path: C:\Windows\system32\drivers\ntfs.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Controlador del sistema de archivos NTFS
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.
On Mon 07/12/2009 20:08:22 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0x0, 0xC, 0x0, 0xFFFFF80001A80FB4)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\120709-19141-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
10 crash dumps have been found and analyzed. Note that it's not always possible to state with certainty whether a reported driver is really 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.
