Ecran bleu

[iaowuh]

Bonjour,

depuis quelque temps, un écran bleu apparaît intempestivement en cours de session.
D'après le rapport de Whocrashed (ci-dessous), la mémoire semble en cause ; plus précisément sa gestion, non le matériel.
Que me conseillez-vous de faire ?

Merci.

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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 05/06/2013 06:11:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060513-41387-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xC5 (0x20, 0x2, 0x0, 0xFFFFF80002FB09BC)
Error: DRIVER_CORRUPTED_EXPOOL
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 the system attempted to access invalid 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. 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 Wed 05/06/2013 06:11:49 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: 0xC5 (0x20, 0x2, 0x0, 0xFFFFF80002FB09BC)
Error: DRIVER_CORRUPTED_EXPOOL
Bug check description: This indicates that the system attempted to access invalid 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. 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 Tue 04/06/2013 06:07:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060413-38532-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1A (0x5100, 0xFFFFF6FC40038F88, 0xD, 0x20)
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 that cannot be identified at this time.




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

3 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.


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.

[grimpeur]

Bonjour,

Error: DRIVER_CORRUPTED_EXPOOL = Je pense plutôt à un driver corrompu, il faut vérifier si tes pilotes sont bien tous à jour.

Le noyau a tenté d'accéder à la mémoire paginable (ou peut-être la mémoire complètement invalide) lorsque l'IRQL était trop élevé. La cause ultime de ce problème est presque certainement un pilote qui a corrompu la piscine du système.

Si vous avez récemment installé un nouveau logiciel, vérifier pour voir si elle est correctement installé. Vérifiez les pilotes mis à jour sur le site Web du fabricant.