Le rapport de Who Crashed :
On Mon 02/04/2012 00:37:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040212-23509-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x8901)
Bugcheck code: 0xA (0xFFFFF7D0039A4060, 0x2, 0x1, 0xFFFFF8000309AAE2)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 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 02/04/2012 00:37:55 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: 0xA (0xFFFFF7D0039A4060, 0x2, 0x1, 0xFFFFF8000309AAE2)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Sun 01/04/2012 16:08:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040112-23446-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
Bugcheck code: 0xA (0xFFFFF78080000320, 0xD, 0x0, 0xFFFFF80003091367)
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 Sun 01/04/2012 15:01:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040112-23244-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x8901)
Bugcheck code: 0xA (0xFFFFF7D003CB8E80, 0x2, 0x1, 0xFFFFF8000308FAE2)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 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 Thu 29/03/2012 00:54:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032912-22120-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
Bugcheck code: 0xA (0x60, 0x2, 0x1, 0xFFFFF800030E11B3)
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 Wed 28/03/2012 21:29:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032812-23446-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF8000309669D)
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 Wed 28/03/2012 16:31:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032812-26972-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
Bugcheck code: 0xA (0xFFFFF88003766354, 0xD, 0x1, 0xFFFFF80003076278)
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 Tue 27/03/2012 19:34:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032712-25740-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
Bugcheck code: 0xA (0x1F1BF, 0x2, 0x1, 0xFFFFF800030861AD)
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 Tue 27/03/2012 17:51:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032712-31605-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF800030E31B3)
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 Mon 26/03/2012 19:20:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032612-23961-01.dmp
This was probably caused by the following module: termdd.sys (termdd+0x128C0)
Bugcheck code: 0xD3 (0xFFFFF88003FD78C0, 0xD, 0x1, 0xFFFFF8000308C11F)
Error: DRIVER_PORTION_MUST_BE_NONPAGED
file path: C:\Windows\system32\drivers\termdd.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Remote Desktop Server Driver
Bug check description: This indicates that the system 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 which cannot be identified at this time.
On Sun 25/03/2012 01:57:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032512-31933-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
Bugcheck code: 0xA (0xFFFFF78080000320, 0xD, 0x0, 0xFFFFF800030E2367)
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 Sat 24/03/2012 13:40:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032412-33477-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD10)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_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 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 Sat 24/03/2012 01:33:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032412-16723-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD10)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_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 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 Fri 23/03/2012 01:29:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032312-16972-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
Bugcheck code: 0xA (0xFFFFF88002FCEBEE, 0x2, 0x1, 0xFFFFF80002E8A94C)
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 Fri 23/03/2012 00:56:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032312-28470-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x38570)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88002DB6570, 0xFFFFF88003D1B8A8, 0xFFFFF88003D1B100)
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
22 crash dumps have been found and analyzed. Only 15 are included in this report. 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:
unknown_module_00000000`00044040.sys