plusieurs ecrans bleu

[Teddy59]

Bonjour a tous,

Voila ce midi en allumant mon PC ,j'ai eu la surprise d'avoir un ecran bleu ...
Je n'ai jamais eu aucun probleme auparavant ...C'est la premiere fois,encore hier soir il fonctionné normalement ....

Voici les différents ecrans :






Voila ...L'overlock date d'un an voir + et jamais eu de probleme ...
En attendant je me dépanne avec mon pc portable ....

J'ai effectué une mise a jour drivers CG mais il a redémarré en plein milieu ...
Un dépoussiérage de la tour ,CCcleaner en mode sans echec,Glary utilities en mode sans echec...
La je procede au CHKDSK du disque dur ...

Si vous avez des pistes a me donné ,n'hesiter pas ...

J'ai lu que ca pouvait venir d'un composant de la carte mére,or j'ai regarder et ne vois rien d'anormal (pas de condo gonglé,brulé ou autre ....)

Merci

[Teddy59]

Re bonsoir,

Bon apparemment aprés le CHKDSK du disque dur ,celui ci n'affiche plus d'ecran bleu ...
En esperant ne pas parler trop vite

[EinsteinZero]

Bonsoir,

au cas ou...télécharge whocrashed >>ici<<

ce logiciel lit les rapport des écrans bleus

installe le, lance le et poste son rapport...comme ça on en saura plus sur les écrans bleus

[Skynet]

Bonsoir,

Merci de la réponse.
Pour l'instant toujours aucun Bug

Voici le rapport,j'espere que c'est bien ca !!

Code: Tout sélectionner

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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Thu 14/04/2011 15:17:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041411-26582-02.dmp
This was probably caused by the following module: classpnp.sys (CLASSPNP+0x4498)
Bugcheck code: 0xA (0x5EB5014, 0x2, 0x0, 0xFFFFFFFF82A52A55)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\classpnp.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: SCSI Class System Dll
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 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 14/04/2011 11:26:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041411-27534-01.dmp
This was probably caused by the following module: hal.sys (hal+0x3829)
Bugcheck code: 0xA (0x3AC378, 0x2, 0x1, 0xFFFFFFFF82A03829)
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hal.sys .
Google query: hal.sys IRQL_NOT_LESS_OR_EQUAL




On Thu 14/04/2011 11:22:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041411-32307-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x24 (0x1904FB, 0xFFFFFFFF957FB6C0, 0xFFFFFFFF957FB2A0, 0xFFFFFFFF8A8CC7DF)
Error: NTFS_FILE_SYSTEM
Bug check description: This indicates a problem occurred in the NTFS file system.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: Unknown .
Google query: Unknown NTFS_FILE_SYSTEM




On Thu 14/04/2011 10:48:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041411-26582-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x20033)
Bugcheck code: 0x50 (0xFFFFFFFFBEC3649C, 0x8, 0xFFFFFFFFBEC3649C, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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.


The following dump files were found but could not be read. These files may be corrupt:
C:\Windows\Minidump\041411-17238-01.dmp




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

On your computer a total of 5 crash dumps have been found. Only 4 could be analyzed. 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:

hal.sys

unknown

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.

[EinsteinZero]

bonsoir,

la majorité des rapports semble tourner autour de fichier intervenant ou pouvant intervenir sur la gestion des disques

le disque dur est probablement bien en cause. Ceci dit, la grande variété de cause pourrait aussi être lié à un pb au niveau de la Ram car quand un module mémoire est défaillant, il fait partir en vrille tout et n'importe quoi. Alors différent pilotes du système peuvent planter tour à tour et provoquer des BSOD

pour le disque dur, comme tout les disques depuis déjà quelque années embarque le système smart, tu peux le tester aisément avec un utilitaire gratuit de chez acronis >>ici<< simplement, après le test désinstalle le logiciel car il charge des trucs, inutiles en routine, au démarrage du PC

si ton disque est en fin de vie, ce logiciel devrait te renseigner

[Skynet]

Bonsoir,

sujet déplacé dans la bonne section .