Ecran bleu Windows 7 seven

[rostalae]

Bonjour
Je suis nouveau sur ce forum; je suis à la retraite et vis dans le sud de la France.
J'ai par moment un crash Windows. J'ai lancé Whocrashed et voici le rapport. Je compte sur vous car pour moi ce n'est pas très parlant.
Merci à l'avance.
Robert
System Information (local)
--------------------------------------------------------------------------------

computer name: ROBERT-VAIO
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 4226998272 total
VM: 2147352576, free: 1930735616



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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Sun 08/01/2012 18:29:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010812-54116-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF8000349F4E0)
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 Sun 08/01/2012 18:29:56 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: 0xA (0x0, 0x2, 0x1, 0xFFFFF8000349F4E0)
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.
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 27/12/2011 21:37:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122711-40076-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x1A (0x41287, 0x30, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
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 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 Wed 07/12/2011 07:39:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120711-24726-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0xD589)
Bugcheck code: 0x10D (0x6, 0x3, 0x57FF92257C8, 0xFFFFFA80064CD830)
Error: WDF_VIOLATION
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Runtime de l’infrastructure de pilotes en mode noyau
Bug check description: This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.
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 Tue 06/12/2011 23:22:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120711-28782-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0xD589)
Bugcheck code: 0x10D (0x6, 0x3, 0x57FF91E5718, 0xFFFFFA800625C950)
Error: WDF_VIOLATION
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Runtime de l’infrastructure de pilotes en mode noyau
Bug check description: This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.
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 Thu 01/12/2011 08:37:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120111-29811-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0xD589)
Bugcheck code: 0x10D (0x6, 0x3, 0x57FF91684F8, 0xFFFFFA8006E63C50)
Error: WDF_VIOLATION
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Runtime de l’infrastructure de pilotes en mode noyau
Bug check description: This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.
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 28/11/2011 14:01:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112811-26488-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0x533F00002, 0x2, 0x0, 0xFFFFF800034F39B4)
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 Sun 13/11/2011 22:29:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111311-30544-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0xD589)
Bugcheck code: 0x10D (0x6, 0x3, 0x57FF95B7FD8, 0xFFFFFA800644A2C0)
Error: WDF_VIOLATION
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Runtime de l’infrastructure de pilotes en mode noyau
Bug check description: This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.
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 06/11/2011 16:14:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\110611-27456-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0xD589)
Bugcheck code: 0x10D (0x6, 0x3, 0x57FF9294FD8, 0xFFFFFA8006CE83D0)
Error: WDF_VIOLATION
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Runtime de l’infrastructure de pilotes en mode noyau
Bug check description: This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.
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.



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

9 crash dumps have been found and analyzed.
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 o

[hacbao]

As tu tapé la commande CHKDSK C: /f pour cherché les erreurs. on écrit cela dans l'invite de commande.
C'est une premières étape.

[rostalae]

Bonjour
Oui je l'ai fait tout est OK.
En analysant le journal des événements j'ai remarqué un problème avec un disque externe. J'ai changé le câble USB et il y a eu un effet immédiat.
Mais j'ai eu un nouvel écran bleu avec ce coup-ci un problème d'adressage de la mémoire.
-34429-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x1A (0x41287, 0x30, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
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 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 30/01/2012 13:56:45 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: 0x1A (0x41287, 0x30, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
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.
Si tu as une idée.
Merci à l’avance

[nardino]

Bonjour,
Il faut faire un test de la mémoire vive.
Soit avec la fonction de Windows : Panneau de configuration > Outils d'administration > Diagnostic de mémoire Windows
Soit avec Memtest
@+