[Résolu] Plusieurs BlueScreen à la fois

[aramis74]

bonjour a tous, mon pc redémarre 5 a 6 fois avec un écra nbleu, j'ai lancé zhp diag mais il s'arrete a 4 % et me met un message d'erreur, sur un autre post il dsait de lancer OTL , donc je poste les rapport OTL.txt et extras.txt

 

si quelquses bonnes ames pouvaient m'aider car j'a ireformaté 2 fois et rien. Merci a vous.

 

Rapport OTL.txt

 

aramis74

Modifié le 9 avril 2013 par aramis74
Hébergement rapport volumineux ;o)

[bernard53]

Bonsoir

Dans un premier temps surtout ne pas mettre un rapport comme ceci mais plutôt l'héberger sur un site et mettre le lien. comme ici par exemple.

Accueil de Cjoint.com

ou.

Envoyez et partagez vos fichiers

 

Ensuite ton soucis est surement matériels donc ceci suite a ton rapport.

* Fait un double-clic sur l'icône d'OTL pour le lancer

/!\ pour Vista/Seven fais un clic-droit sur l'icône d'OTL et choisis "Exécuter en tant qu'administrateur"

 

* Assure-toi d'avoir fermé toutes les applications en court de fonctionnement.

 

* Quand la fenêtre d'OTL apparaît, assure toi que dans la section "Rapport" (en haut à droite) la case " Rapport minimal" soit cochée.

 

* Copies et colles le contenue de cette citation dans la partie inférieure d'OTL "Personnalisation"

:OTL

O4 - HKLM..\Run: [Eraser] "C:\PROGRA~1\Eraser\Eraser.exe" --atRestart File not found

O4 - HKU\S-1-5-21-2043426542-4194892725-3357011421-1000..\Run: [捁牥吠畯r] File not found

O4 - HKU\S-1-5-21-2043426542-4194892725-3357011421-1000..\Run: [捁牥吠畯⁲敒業摮牥] 㩃䅜散屲捁牥潔牵剜浥湩敤⹲硥e File not found

[2013/04/06 10:29:16 | 000,000,312 | ---- | M] () -- C:\Windows\tasks\GlaryInitialize.job

:reg

[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Security Center\Monitoring\SymantecAntiVirus]

[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Security Center\Monitoring\SymantecFirewall]

:Files

:Commands

[emptytemp]

[createrestorepoint]

[reboot]

* Cliques sur l'icône Correction (en haut à gauche) .

* Laisse le scan aller à son terme sans te servir du PC

* A la fin du scan un rapport s'ouvrir "OTL.log"

* Copie et colle le ou les rapports dans ta réponse stp...

* Au cas où, tu peux les retrouver dans le dossier C:\OTL ou sur ton bureau en fonction des cas rencontrés

Mets le rapport ici car il prend bien de la place.

Accueil de Cjoint.com

ou.

Envoyez et partagez vos fichiers

 

Puis;

 

Télécharger whocrashedSetup

 

Installer le logiciel et une fois installé cliquez sur Analyse

. Si tu as une anomalie mets-le rapport ici.

[Dylav]

Bonsoir Aramis, Bernard,

 

J'ai hébergé ton rapport OTL chez cjoint.

Son poids risquait en effet de provoquer, plus tard, le plantage de l'affichage de ce topic...

[bernard53]

Bonjour

 

Merci Dylav

[aramis74]

Merci Dylav et aussi a toi bernard 53 pour ton aide j'ai suivi tes instructions et voici le nouveau rapport OTL

 

© CJoint.com, 2012

 

 

par contre OTL est paramétré par défaut dois je cocher des choses ou autre par hasard ?

 

aramis 74

[bernard53]

aramis fait mes 2 demandes citées s.t.p.

[aramis74]

Excuse j'ai fait les 2 demandes mais j'ai oublié un rapport en route voici le rapport whocrashed, par contre j'a ipas su le mettre sur cjoint

 

System Information (local)

--------------------------------------------------------------------------------

 

computer name: YAZIDETKARIMA

windows version: Windows Vista Service Pack 2, 6.0, build: 6002

windows dir: C:\Windows

CPU: GenuineIntel Intel® Core2 CPU 6300 @ 1.86GHz Intel586, level: 6

2 logical processors, active mask: 3

RAM: 2146058240 total

VM: 2147352576, free: 1981149184

 

 

 

 

--------------------------------------------------------------------------------

Crash Dump Analysis

--------------------------------------------------------------------------------

 

Crash dump directory: C:\Windows\Minidump

 

Crash dumps are enabled on your computer.

 

On Sun 07/04/2013 07:42:29 GMT your computer crashed

crash dump file: C:\Windows\Minidump\Mini040713-01.dmp

This was probably caused by the following module: win32k.sys (win32k+0xA0761)

Bugcheck code: 0x1000008E (0xFFFFFFFFC0000006, 0xFFFFFFFFA70D8B25, 0xFFFFFFFF9A7CAB8C, 0x0)

Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

file path: C:\Windows\system32\win32k.sys

product: Système d'exploitation Microsoft® Windows®

company: Microsoft Corporation

description: Pilote Win32 multi-utilisateurs

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 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 07/04/2013 07:42:29 GMT your computer crashed

crash dump file: C:\Windows\memory.dmp

This was probably caused by the following module: win32k.sys (win32k!EngMulDiv+0xA5D5)

Bugcheck code: 0x8E (0xFFFFFFFFC0000006, 0xFFFFFFFFA70D8B25, 0xFFFFFFFF9A7CAB8C, 0x0)

Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED

file path: C:\Windows\system32\win32k.sys

product: Système d'exploitation Microsoft® Windows®

company: Microsoft Corporation

description: Pilote Win32 multi-utilisateurs

Bug check description: This bug check indicates that a kernel-mode application generated an exception that the error handler did not catch.

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 Fri 05/04/2013 15:10:14 GMT your computer crashed

crash dump file: C:\Windows\Minidump\Mini040513-01.dmp

This was probably caused by the following module: ataport.sys (ataport+0x8081)

Bugcheck code: 0x1000008E (0xFFFFFFFF80000003, 0xFFFFFFFF823B1080, 0xFFFFFFFF81D2FC78, 0x0)

Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

file path: C:\Windows\system32\drivers\ataport.sys

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: ATAPI Driver Extension

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 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 04/04/2013 17:20:15 GMT your computer crashed

crash dump file: C:\Windows\Minidump\Mini040413-03.dmp

This was probably caused by the following module: win32k.sys (win32k+0x74426)

Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF92164426, 0xFFFFFFFF8C419A94, 0x0)

Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

file path: C:\Windows\system32\win32k.sys

product: Système d'exploitation Microsoft® Windows®

company: Microsoft Corporation

description: Pilote Win32 multi-utilisateurs

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 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 04/04/2013 17:17:36 GMT your computer crashed

crash dump file: C:\Windows\Minidump\Mini040413-02.dmp

This was probably caused by the following module: classpnp.sys (CLASSPNP+0x5D5F)

Bugcheck code: 0x44 (0xFFFFFFFF84ED0CB0, 0xE7A, 0x0, 0x0)

Error: MULTIPLE_IRP_COMPLETE_REQUESTS

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 a driver has tried to requested an IRP be completed that is already complete.

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 Thu 04/04/2013 17:13:28 GMT your computer crashed

crash dump file: C:\Windows\Minidump\Mini040413-01.dmp

This was probably caused by the following module: ntfs.sys (Ntfs+0x91D4A)

Bugcheck code: 0x7F (0xD, 0x0, 0x0, 0x0)

Error: UNEXPECTED_KERNEL_MODE_TRAP

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 bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.

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 Wed 03/04/2013 15:00:42 GMT your computer crashed

crash dump file: C:\Windows\Minidump\Mini040313-01.dmp

This was probably caused by the following module: npfs.sys (Npfs+0x6587)

Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8ECAB587, 0xFFFFFFFF8C79491C, 0x0)

Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

file path: C:\Windows\system32\drivers\npfs.sys

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NPFS Driver

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 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 Tue 02/04/2013 16:54:01 GMT your computer crashed

crash dump file: C:\Windows\Minidump\Mini040213-01.dmp

This was probably caused by the following module: ntkrnlpa.exe (nt+0x4AC3A)

Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF96D67070, 0xFFFFFFFF9A5C6C6C, 0x0)

Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

file path: C:\Windows\system32\ntkrnlpa.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 Sat 30/03/2013 08:49:27 GMT your computer crashed

crash dump file: C:\Windows\Minidump\Mini033013-01.dmp

This was probably caused by the following module: ntfs.sys (Ntfs+0x8FBF0)

Bugcheck code: 0x1000008E (0xFFFFFFFFC000001D, 0xFFFFFFFF87E97BF0, 0xFFFFFFFF8E23CA75, 0x0)

Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

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 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 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 Fri 29/03/2013 16:11:55 GMT your computer crashed

crash dump file: C:\Windows\Minidump\Mini032913-02.dmp

This was probably caused by the following module: ntkrnlpa.exe (nt+0xCDABF)

Bugcheck code: 0x19 (0x20, 0xFFFFFFFF94D96E90, 0xFFFFFFFF94D96EE0, 0xA0A0208)

Error: BAD_POOL_HEADER

file path: C:\Windows\system32\ntkrnlpa.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 Fri 29/03/2013 16:11:51 GMT your computer crashed

crash dump file: C:\Windows\Minidump\Mini032913-01.dmp

This was probably caused by the following module: Unknown ()

Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)

Error: CUSTOM_ERROR

A third party driver was identified as the probable root cause of this system error.

Google query: CUSTOM_ERROR

 

 

 

On Tue 26/03/2013 17:38:35 GMT your computer crashed

crash dump file: C:\Windows\Minidump\Mini032613-01.dmp

This was probably caused by the following module: classpnp.sys (CLASSPNP+0x958E)

Bugcheck code: 0xC5 (0x4C7881D5, 0x2, 0x1, 0xFFFFFFFF81D01010)

Error: DRIVER_CORRUPTED_EXPOOL

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 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 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 25/03/2013 18:05:02 GMT your computer crashed

crash dump file: C:\Windows\Minidump\Mini032513-02.dmp

This was probably caused by the following module: ecache.sys (ecache+0xA852)

Bugcheck code: 0xC5 (0x4, 0x2, 0x1, 0xFFFFFFFF81CF282C)

Error: DRIVER_CORRUPTED_EXPOOL

file path: C:\Windows\system32\drivers\ecache.sys

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: Special Memory Device Cache

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 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 25/03/2013 18:03:20 GMT your computer crashed

crash dump file: C:\Windows\Minidump\Mini032513-01.dmp

This was probably caused by the following module: ntkrnlpa.exe (nt+0x4DF99)

Bugcheck code: 0xA (0x0, 0x1B, 0x1, 0xFFFFFFFF81CE31A4)

Error: IRQL_NOT_LESS_OR_EQUAL

file path: C:\Windows\system32\ntkrnlpa.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 Sun 24/03/2013 08:01:51 GMT your computer crashed

crash dump file: C:\Windows\Minidump\Mini032413-01.dmp

This was probably caused by the following module: ntkrnlpa.exe (nt+0x4DF99)

Bugcheck code: 0xA (0x15474C, 0x2, 0x0, 0xFFFFFFFF81C94769)

Error: IRQL_NOT_LESS_OR_EQUAL

file path: C:\Windows\system32\ntkrnlpa.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

--------------------------------------------------------------------------------

 

20 crash dumps have been found and analyzed. Only 15 are included in this report.

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.

 

 

 

 

par contre j'ai voulu réessayer ZHPDIAG et la il est allé a 100 %.

 

ARAMIS74

[bernard53]

He bien j'ai peur que le système soit endommagé donc ceci.

Si tu as Vista ou Seven

tapes cmd dans la recherche de Vista<ensuite clique droit sur la petite fenêtre noire nommée cmd.exe et choisis "Exécuter en tant qu'administrateur".

 

 

puis chkdsk X: /f /r

 

 

X étant la lettre de ton DD qui doit être surement C.

 

mets bien un espace entre chkdsk et X: puis entre X: et /f puis entre /f et /r

 

Si ta lettre est le C tu as donc ceci chkdsk C: /f /r

 

- Windows affiche : type fichier NTFS : impossible de verrouiller le lecteur en cours

CHKDSK ne peut s'exécuter parce que le volume est utilisé par un autre processus.

Voulez vous que ce volume soit vérifier au prochain démarrage : Oui ou Non

Valider O et Redémarrer le pc.

 

Puis si cela ne résous pas le soucis.

tapes cmd dans la recherche de Vista<ensuite clique droit sur la petite fenêtre noire nommée cmd.exe et choisis "Exécuter en tant qu'administrateur".

 

 

Puis dans la fenêtre qui s’affiche.

 

SFC*/SCANNOW * indique un espace entre SFC et /scannow

 

Puis si une erreur est détectée.

 

tapes cmd dans la recherche de Vista<ensuite clique droit sur la petite fenêtre noire nommée cmd.exe et choisis "Exécuter en tant qu'administrateur".

Tu y fais un copier-coller de :

findstr /C:"[sR] Cannot repair" %windir%\logs\cbs\cbs.log >sfcdetails2.txt

Valides par Entrer

Ensuite tu vas dans ce dossier :

C:\Windows\System32\ et tu postes par copier-coller le rapport sfcdetails2.txt

[aramis74]

Merci voila j'ai suivi tes instructions et le rapport suivant :

 

Le lien a été créé: © CJoint.com, 2012

Modifié le 7 avril 2013 par Dylav
Suppression citation inutile ;o)

[bernard53]

désolé mais rien n’apparaît sur le rapport.