Si je peux me permettre, voilà l'analyse de Whocrashed. Je sais, c'est long et j'ai hésité à la copier ici, j'espère que ça ne pose pas de problème 
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 13/06/11 07:06:01 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!ExFreePoolWithTag+0xEDC)
Bugcheck code: 0x19 (0x3, 0xFFFFFFFF9505C4C0, 0x61C602DC, 0xFFFFFFFFDC1BD860)
Error: BAD_POOL_HEADER
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.
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: ntkrpamp.exe .
Google query: ntkrpamp.exe BAD_POOL_HEADER
On Mon 13/06/11 06:59:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061311-19905-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x12068C)
Bugcheck code: 0x19 (0x3, 0xFFFFFFFF84E332E8, 0xFFFFFFFF84E332E8, 0xFFFFFFFF84E312E8)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntkrnlpa.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 which cannot be identified at this time.
On Mon 13/06/11 06:58:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061311-19718-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDEF2C)
Bugcheck code: 0x4E (0x99, 0x4B505, 0x0, 0x4B485)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
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 which cannot be identified at this time.
On Mon 13/06/11 06:56:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061311-25552-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x29C41)
Bugcheck code: 0x50 (0xFFFFFFFFFFFF8068, 0x0, 0xFFFFFFFF88E54C41, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
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 13/06/11 06:55:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061311-11668-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xCE0F9)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82F647FF, 0xFFFFFFFF9BC0793C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\win32k.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 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 13/06/11 06:53:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061311-12963-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x1217FF)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82F687FF, 0xFFFFFFFF8AEF77E4, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntkrnlpa.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 Mon 13/06/11 06:47:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061311-11091-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x121996)
Bugcheck code: 0x19 (0x3, 0xFFFFFFFF96C95C10, 0xFFFFFFFF88FE62A4, 0xFFFFFFFF96C95C10)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntkrnlpa.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 which cannot be identified at this time.
On Mon 13/06/11 06:46:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061311-13228-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xCC83B)
Bugcheck code: 0xC2 (0x99, 0xFFFFFFFFFE9B8EB0, 0x0, 0x0)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\win32k.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
Bug check description: This indicates that the current thread is making a bad pool request.
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 12/06/11 08:53:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061211-11450-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x94717)
Bugcheck code: 0x50 (0xFFFFFFFFB04734E3, 0x0, 0xFFFFFFFF82E9AB33, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
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 Sat 11/06/11 13:56:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061111-12620-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xA10AE)
Bugcheck code: 0x1A (0x403, 0xFFFFFFFFC0390FB0, 0x47F55025, 0xFFFFFFFFC03925E0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
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 which cannot be identified at this time.
On Sat 11/06/11 13:40:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061111-11450-01.dmp
This was probably caused by the following module: fileinfo.sys (fileinfo+0x5F78)
Bugcheck code: 0x7F (0x0, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\drivers\fileinfo.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: FileInfo Filter Driver
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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.
Google query: fileinfo.sys Microsoft Corporation UNEXPECTED_KERNEL_MODE_TRAP
On Sat 11/06/11 13:38:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061111-10998-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x1217FF)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82F677FF, 0xFFFFFFFF81F6F7E4, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntkrnlpa.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 11/06/11 13:36:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061111-31871-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xBB3A9)
Bugcheck code: 0x1A (0x41201, 0xFFFFFFFFC03A02B0, 0x1FC78025, 0xFFFFFFFF86E30C10)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
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 which cannot be identified at this time.
On Mon 06/06/11 14:05:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060611-12168-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDEF2C)
Bugcheck code: 0x4E (0x99, 0x288C8, 0x2, 0x28853)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
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 which cannot be identified at this time.
On Mon 06/06/11 14:04:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060611-11778-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xBB3A9)
Bugcheck code: 0x1A (0x41201, 0xFFFFFFFFC00250B0, 0x6DE95867, 0xFFFFFFFF86FAD648)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
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 which cannot be identified at this time.
Conclusion
51 crash dumps have been found and analyzed. Only 15 are included in this report. 4 third party drivers have 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:
fileinfo.sys (FileInfo Filter Driver, Microsoft Corporation)
ntkrpamp.exe
hal.sys
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.
