Bonjour,
 
J'ai des nombreux écran de la mort ainsi que innombrable freeze
 
Pas de virus ni autre  
ram testé 8 pass sans erreurs
 
cm asrock pro3 r2 - cpu fx 6300 - 8giga de kingston
 
win7 est à jour
ts les drivers sont à jour selon ma config.com
 
 
 
voici la copie whocrashed  
 
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: ASRock, 970 Pro3 R2.0
CPU: AuthenticAMD AMD FX(tm)-6300 Six-Core Processor AMD586, level: 21
6 logical processors, active mask: 63
RAM: 4249604096 total
VM: 2147352576, free: 1933684736
 
 
 
 
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
 
Crash dump directory: C:\Windows\Minidump
 
Crash dumps are enabled on your computer.
 
On Thu 27/02/2014 18:11:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022714-23337-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)  
Bugcheck code: 0xDE (0x2, 0xFFFFF8A00E361B00, 0xFFFFF8A00E161B01, 0x137C528C0)
Error: POOL_CORRUPTION_IN_FILE_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 a driver has corrupted pool memory that is used for holding pages destined for disk.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.  
 
 
 
On Thu 27/02/2014 18:11:35 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x7E4C3)  
Bugcheck code: 0xDE (0x2, 0xFFFFF8A00E361B00, 0xFFFFF8A00E161B01, 0x137C528C0)
Error: POOL_CORRUPTION_IN_FILE_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 a driver has corrupted pool memory that is used for holding pages destined for disk.
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 that cannot be identified at this time.  
 
 
 
On Thu 27/02/2014 15:30:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022714-28953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)  
Bugcheck code: 0x19 (0x3, 0xFFFFF8A011F4A380, 0xFFFFF8A011F4A380, 0xFFFFF8A02AD0BAC0)
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 Thu 27/02/2014 11:16:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022714-28610-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)  
Bugcheck code: 0xA (0xFFFFF7FFF96F5683, 0xD, 0x0, 0xFFFFF800032E2F09)
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.  
 
 
 
 
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
 
4 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.  
 
 
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.  
 
 
 
Si cela inspire qqu'un .....  
 
 

salut

fait un memtest, si tu as des erreurs c'est qu'une de tes barrettes de ram est bonne pour la poubelle

j'ai testé les 2 une par une  
 
après 8 pass elles sont sans aucune erreur

Salut,
 
Mon inspiration me dit de regarder coté disque: fait un scan complet de la santé de ton disque (table d'allocation ou secteurs corrompus).

Bonsoir,
C'est normal que whocrashed n'indique que 4go de RAM ?
 
Qu'as tu dans l'observateur d'évènements ?

bonjour,
 
désolé de ma réponse tardive ms mon ordi c'est encore planté et je l'ai pas rallumé.....
 
C'est normal pour la mémoire je n'ai qu'un barrette en ce moment je n'ai pas remis la seconde après le memtest

pour le DD j'ai rien trouvé.
j'ai fait une intall de win7 (officiel)sur 2 disques différent et les mm problème sont apparu
je commence a me demander si c'est pas la CM mais j'en ai pas d'autre et je ne sais pas comment la tester

Quelle alim ?

j'ai eu un pc qui n'arrêtait de crasher.J'ai fini par changer la CM et les problèmes ont disparu.

Peut être des options du bios à modifier, du genre mettre disable le memory caching.

l'alim est une antec de 620w neuve

je fait le test avec une "vieille" alim le problème est toujours la

Tu peux flasher ton BIOS à la dernière version ?

le bios est flashé avec la derniere version disponible sur asrock ....

D'après les msgs que tu as postés, tu as également des pbs de pilotes pci ..
As-tu tenté de trouver des drivers + récents pour ton chipset, par exemple chez AMD au lieu d'asrock ?
Et tenter d'utiliser l'utilitaire de résolution de pbs windows ?

chez AMD tout les drivers passe par catalyste, je n'ai pas de trouvé de drivers "individuel"
 
a l'installation j'ai d'abord utilisé les drivers asrock et ensuite j'ai installé catalyst
 
ps : merci a tous pour votre aide

voici encore qque rapport
 
 
On Fri 28/02/2014 14:07:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022814-33665-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)  
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800035A489D, 0xFFFFF8800A82AD30, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.  
 
 
 
On Fri 28/02/2014 14:07:51 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: 0x3B (0xC0000005, 0xFFFFF800035A489D, 0xFFFFF8800A82AD30, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.  

Catalyst c'est pour la CG, mais tu trouves aussi les drivers du chipset

je suis retourné sur amd
il a deux entré gpu et apu
mais on retombe des 2 coté sur catalyst même version - même taille - et même date  
qque chose m'échappe ?

Tout est là, pour le chipset et autres puces de ta mobo : http://www.asrock.com/mb/AMD/970%2 [...] t=Download

merci GrizzzlyBear c'est bien les drivers que j'ai installé
je vais faire une reinstall on ne sait jamais .....

Il y en a des plus récents sur le site AMD :
http://support.amd.com/en-us/downl [...] 7%20-%2064

merci vero_b77  
 
je vais les installer
je vous donne des news demain