Diagnostic de Plantage WhoCrashed (External Mirror 1) : http://www.filecluster.com/downloads/WhoCrashed.html System Information (local) -------------------------------------------------------------------------------- computer name: BRUNO-PC windows version: Windows 7 Service Pack 1, 6.1, build: 7601 windows dir: C:\Windows Hardware: Z68X-UD3P-B3, Gigabyte Technology Co., Ltd. CPU: GenuineIntel Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz Intel586, level: 6 4 logical processors, active mask: 15 RAM: 8572231680 total VM: 2147352576, free: 1903378432 -------------------------------------------------------------------------------- Crash Dump Analysis -------------------------------------------------------------------------------- Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Tue 29/04/2014 14:05:53 GMT your computer crashed crash dump file: C:\Windows\Minidump\042914-12604-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF8000365DD4E) 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 that cannot be identified at this time. On Fri 04/04/2014 15:02:37 GMT your computer crashed crash dump file: C:\Windows\Minidump\040414-14398-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) Bugcheck code: 0x19 (0x20, 0xFFFFFA800A6E0290, 0xFFFFFA800A6E0310, 0xC080003) Error: BAD_POOL_HEADER 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 pool header is corrupt. 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. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Wed 02/04/2014 17:15:52 GMT your computer crashed crash dump file: C:\Windows\Minidump\040314-16816-01.dmp This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x153034) Bugcheck code: 0x116 (0xFFFFFA800F60E230, 0xFFFFF8800F38A034, 0xFFFFFFFFC00000B5, 0xA) Error: VIDEO_TDR_ERROR file path: C:\Windows\system32\drivers\nvlddmkm.sys product: NVIDIA Windows Kernel Mode Driver, Version 335.23 company: NVIDIA Corporation description: NVIDIA Windows Kernel Mode Driver, Version 335.23 Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed. 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 335.23 , NVIDIA Corporation). Google query: NVIDIA Corporation VIDEO_TDR_ERROR -------------------------------------------------------------------------------- Conclusion -------------------------------------------------------------------------------- 3 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 335.23 , 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. Read the topic general suggestions for troubleshooting system crashes for more information. Note that it's not always possible to state with certainty whether a reported driver is actually 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.