Blue screen analyse WhoCrashed

[pepperlive]

Bonjour,

Depuis quelques jours les bleu screens deviennent intempestifs, j'ai vraiment besoin d'aide, voici le copier coller de who crashed:

System Information (local)
--------------------------------------------------------------------------------

computer name: MATHIEU-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: AuthenticAMD AMD Phenom(tm) II X6 1100T Processor AMD586, level: 16
6 logical processors, active mask: 63
RAM: 17139367936 total
VM: 2147352576, free: 1977790464



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Sun 15/01/2012 14:04:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011512-16083-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x50 (0xFFFFF80014CA7350, 0x0, 0xFFFFF88004D952EB, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 15/01/2012 14:04:25 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1!VidMmInterface+0xBA2B)
Bugcheck code: 0x50 (0xFFFFF80014CA7350, 0x0, 0xFFFFF88004D952EB, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 Fri 13/01/2012 23:43:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011412-12402-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0xD1 (0xFFFFF88009B1B7D8, 0x2, 0x0, 0xFFFFF880121A127F)
Error: DRIVER_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 a kernel-mode driver 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 12/01/2012 20:09:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011212-13540-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x50 (0xFFFFFA81C813D50B, 0x0, 0xFFFFF800050893AB, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Wed 11/01/2012 23:33:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011212-12776-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x50 (0xFFFFFA82F90339BB, 0x0, 0xFFFFF800050E546F, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 7/01/2012 19:11:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010712-13696-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x50 (0xFFFFFA0011738A8C, 0x0, 0xFFFFF880122A816C, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 18/12/2011 19:10:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121811-14492-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x19 (0x22, 0xA8000000, 0x0, 0x0)
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 which cannot be identified at this time.


On Thu 15/12/2011 11:39:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121511-15178-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x50 (0xFFFFF8A04A6248CC, 0x0, 0xFFFFF800053CE0B4, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 11/12/2011 21:30:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121111-29359-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x50 (0xFFFFF87C05255A80, 0x0, 0xFFFFF800050CB437, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 4/12/2011 22:05:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120411-15475-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0xA (0xA600000028, 0x2, 0x0, 0xFFFFF800050A230B)
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 25/11/2011 15:35:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112511-13228-01.dmp
This was probably caused by the following module: cdd.dll (cdd+0x1328D)
Bugcheck code: 0x3B (0x80000004, 0xFFFFF9600069328D, 0xFFFFF880083511C0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\cdd.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Canonical Display Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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.

Je deviens dingue a cause de ca sans compter que ma machine m'as couté un os.

Aidez moi ! :'(

EDIT Modération.
Merci de lire la charte du forum.
Tu peux continuer le fil de la discussion ici.
@+

[nardino]

Bonjour
Problème de pilote et/ou de mémoire vive défectueuse.
Pour tester la mémoire:
Avec Vista et Sept.
Dans le panneau de configuration, Outils d'administration, Diagnostic de mémoire Windows, choisis parmi les deux options proposées.
Cette opération se fera au redémarrage.

Avec Memtest
Voir sur ce site
Il faut graver un CD ou l'installer sur une clé USB bootable et démarrer sur ce médium pour lancer l'analyse.
Un cycle dure environ 15 à 25 minutes avec une machine assez récente.
Il ne faut pas d'erreur dans le cadre en bas à droite.

Pour les pilotes regarder dans le gestionnaire de périphériques en tapant devmgmt.msc dans la barre de recherche et en validant par Entrer.
@+