Ecrans bleu à la chaine

Bonjour,

Depuis 2 semaines mon PC plante très souvent et complétement aléatoirement. Parfois aucuns problèmes pendant 24h et parfois 10 écrans bleu dans la journée...
- MemTest me dit que la RAM est ok.
- CrystalDiskInfo ne rapporte pas d'erreur sur le disque systeme.
- L'analyse SFC des fichiers systeme est OK.
- Windows est a jour.
- Pas de virus, ni de spywares.
- Avira est a jour

Ca se produit que j'utilise l'ordinateur ou pas... Je ne sais plus quoi faire... :(

Voici les rapports d'ecrans bleu analysés par WhoCrashed :

--------------------------------

On Tue 07/05/2013 15:27:11 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
uptime: 00:22:53
This was probably caused by the following module: Unknown ()
Bugcheck code: 0xA (0xFFFFFFFFF887E5E1, 0x2, 0x0, 0xFFFFFFFF8429AB80)
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.
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: Unknown .
Google query: Unknown IRQL_NOT_LESS_OR_EQUAL




On Tue 07/05/2013 15:02:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050713-26937-01.dmp
uptime: 00:06:29
This was probably caused by the following module: ntkrnlpa.exe (nt+0x40C9B)
Bugcheck code: 0xA (0x28, 0x2, 0x1, 0xFFFFFFFF842DE1BE)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 07/05/2013 14:54:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050713-28609-01.dmp
uptime: 00:16:27
This was probably caused by the following module: avkmgr.sys (avkmgr+0x2F05)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF990E9341, 0xFFFFFFFFA4CC7B48, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\avkmgr.sys
product: Avira Professional Security
company: Avira Operations GmbH & Co. KG
description: Avira Manager Driver
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: avkmgr.sys (Avira Manager Driver, Avira Operations GmbH & Co. KG).
Google query: avkmgr.sys Avira Operations GmbH & Co. KG KERNEL_MODE_EXCEPTION_NOT_HANDLED_M




On Tue 07/05/2013 13:38:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050713-46671-01.dmp
uptime: 00:01:00
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDEC2C)
Bugcheck code: 0x4E (0x99, 0x66ABB, 0x2, 0x6602E)
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/05/2013 10:24:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050613-28812-01.dmp
uptime: 00:00:31
This was probably caused by the following module: ntfs.sys (Ntfs+0x1AAC3)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFFFFF830378BC, 0xFFFFFFFF830374A0, 0xFFFFFFFF84064FD9)
Error: NTFS_FILE_SYSTEM
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 a problem occurred in the NTFS file system.
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 05/05/2013 17:32:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050513-31171-01.dmp
uptime: 00:00:46
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDEC2C)
Bugcheck code: 0x4E (0x8D, 0x832F, 0x410001, 0xFFFFFFFF94789523)
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 Sun 05/05/2013 17:30:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050513-28328-01.dmp
uptime: 05:38:45
This was probably caused by the following module: ntfs.sys (Ntfs+0x15D17)
Bugcheck code: 0xA (0x16, 0x2, 0x0, 0xFFFFFFFF8407B611)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 Fri 03/05/2013 20:50:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050313-30046-01.dmp
uptime: 00:01:48
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDEBDC)
Bugcheck code: 0x1A (0x8887, 0xFFFFFFFF8589F7A0, 0xFFFFFFFF854AF6A4, 0x502)
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 Fri 03/05/2013 20:47:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050313-28265-01.dmp
uptime: 03:41:55
This was probably caused by the following module: ntkrnlpa.exe (nt+0x40C7B)
Bugcheck code: 0xA (0x14, 0x2, 0x0, 0xFFFFFFFF840B42A0)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 03/05/2013 16:48:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050313-31125-01.dmp
uptime: 09:32:22
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDEBDC)
Bugcheck code: 0x1A (0x8884, 0xFFFFFFFF85C5C1E4, 0xFFFFFFFF85C63270, 0x405)
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.


The following dump files were found but could not be read. These files may be corrupt:
C:\Windows\Minidump\050613-29921-01.dmp




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

On your computer a total of 11 crash dumps have been found. Only 10 could be analyzed. 2 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:

avkmgr.sys (Avira Manager Driver, Avira Operations GmbH & Co. KG)

unknown

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.

-----------------------------------