Ecran bleu aléatoire

le memtest86 vous l'avez laissé tourner pendant combien de temps ?
si vous disposez de plus de 2 barrettes mémoire, il serait judicieux de les tester une à une.
car effectivement, ces erreurs me font penser à une mémoire défectueuse.

peut-être tester l'intégrité du système de fichier avec un chkdsk également.

quelle carte graphique est utilisée ?

Oh le memtest86 il a du tourner une nuit entière ;)

A l'instant un nouveau motif que j'avais encore jamais vu:
SYSTEM_SERVICE_EXCEPTION
Et un peu plus bas dans l'écran juste apres le code erreur: fltmgr.sys

Carte graphique ATI Radeon HS 5700 Series
Processeur AMD Athlon II X4 620 2,6ghz si ça peut aider.

Merci

bonjour,

pouvez vous télécharger whocrashed et nous copier son rapport ?

pareil, dans l'observateur d'évènements windows, dans les erreurs système, les codes erreurs.

Attention c'est long ;)


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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 26/11/2012 18:03:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112612-32339-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x4FA9)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88001074FA9, 0xFFFFF880060E09B0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
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 that cannot be identified at this time.



On Mon 26/11/2012 18:03:08 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr!FltGetStreamHandleContext+0xAB9)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88001074FA9, 0xFFFFF880060E09B0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
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 that cannot be identified at this time.



On Mon 26/11/2012 14:11:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112612-29000-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x50 (0xFFFFF8A014BE7000, 0x1, 0xFFFFF800032C7832, 0x0)
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 that cannot be identified at this time.



On Mon 12/11/2012 16:04:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111212-54506-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800032D0437, 0xFFFFF88007332030, 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 09/11/2012 10:36:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\110912-28641-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70590)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 that cannot be identified at this time.



On Mon 29/10/2012 19:05:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102912-56909-01.dmp
This was probably caused by the following module: ndis.sys (0xFFFFF8800149735D)
Bugcheck code: 0xD1 (0xFFFFF8804D1E8916, 0x2, 0x0, 0xFFFFF8800149735D)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ndis.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote NDIS 6.20
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 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 Sun 14/10/2012 02:23:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101412-30326-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70590)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 that cannot be identified at this time.



On Fri 12/10/2012 13:38:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101212-38532-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5F68)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88003193258, 0xFFFFF88003192AC0, 0xFFFFF800032D124C)
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 that cannot be identified at this time.



On Thu 11/10/2012 16:37:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101112-32385-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x50 (0xFFFFF88017F7EB07, 0x0, 0xFFFFF8000354341F, 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 that cannot be identified at this time.



On Tue 12/06/2012 06:02:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061212-44943-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x3B (0xC0000096, 0xFFFFF800032856C6, 0xFFFFF88008969EC0, 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 Sat 19/05/2012 22:34:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052012-26270-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7E0CA)
Bugcheck code: 0xA (0x8, 0x2, 0x0, 0xFFFFF8000325FC69)
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 Tue 08/05/2012 13:35:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050812-22822-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70590)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 that cannot be identified at this time.



On Sun 06/05/2012 20:37:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050612-21793-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0x87E59)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88001493E59, 0xFFFFF8800828F1F8, 0xFFFFF8800828EA60)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\ndis.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote NDIS 6.20
Bug check description: This indicates that a system thread 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 that cannot be identified at this time.



On Sun 06/05/2012 20:01:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050612-46082-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70590)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 that cannot be identified at this time.



On Fri 04/05/2012 16:08:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050412-23337-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8000354796B, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 that cannot be identified at this time.




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

51 crash dumps have been found and analyzed. Only 15 are included in this report. 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:

rt64win7.sys (Realtek 8101E/8168/8169 NDIS 6.20 64-bit Driver , Realtek Corporation )
atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.)

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.

______________________________________________________________

Pour l'observateur d'elements WIndows il y a 75 evenements dans le rapport sous Windows, que des "Arret non planifié"

Je vous mets les deux derniers:
Signature du problème
Nom d'événement du problème : BlueScreen
Version du système: 6.1.7600.2.0.0.256.48
Identificateur de paramètres régionaux: 1036

Informations complémentaires sur le problème
BCCode: 3b
BCP1: 00000000C0000005
BCP2: FFFFF88001074FA9
BCP3: FFFFF880060E09B0
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1


Signature du problème
Nom d'événement du problème : BlueScreen
Version du système: 6.1.7600.2.0.0.256.48
Identificateur de paramètres régionaux: 1036

Informations complémentaires sur le problème
BCCode: 50
BCP1: FFFFF8A014BE7000
BCP2: 0000000000000001
BCP3: FFFFF800032C7832
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

vérifiez donc la mise à jour pour:
votre carte réseau "Realtek 8101E/8168/8169 NDIS 6.20 64-bit Driver , Realtek Corporation"
votre carte graphique "ATI Radeon Kernel Mode Driver, ATI Technologies Inc."

il y a sûrement un pilote incompatible ou un doublon que Windows gère mal. le pb étant que les codes se multiplient sans lien direct, y aurait-il une fuite de "données" depuis la carte mère directement ? difficile à convenir, il faut creuser encore une peu. à ce stade je n'ai pas la réponse pour vous, des pistes seulement.

cependant, en attendant, vous pouvez désactiver le redémarrage automatique en cas de "crash" en faisant un clic droit sur "ordinateur" > propriétés > colonne de gauche "paramètres système avancés" > Section démarrage et récupération "Paramètres" > décocher la case "redémarrer automatiquement"

Bonjour,
J'ai deux disques et aucun n'a "Verifier le volume".
Ils ont tout deux: General, Outils, Materiel, Partage, Sécurité, Quotas, Personnaliser, Versions Précédentes

oups, propriétés
outils
vérifier le volume

Bonjour, tests réalisés et rien de nouveau...

bonjour,

combien vous avez vous de barrettes mémoire ?
je pense à une mémoire défectueuse. si vous avez 2 barrettes, enlevez-en une, et faite lui subir le test de memtest86 (laisser tourner au moins 3h..)