Ecran bleu
Fermé
mica65250
-
29 juil. 2013 à 14:18
g3n-h@ckm@n Messages postés 13238 Date d'inscription jeudi 31 janvier 2013 Statut Membre Dernière intervention 24 février 2022 - 1 août 2013 à 17:38
g3n-h@ckm@n Messages postés 13238 Date d'inscription jeudi 31 janvier 2013 Statut Membre Dernière intervention 24 février 2022 - 1 août 2013 à 17:38
A voir également:
- Ecran bleu
- Double ecran - Guide
- Écran bleu - Guide
- Capture d'écran samsung - Guide
- Ecran noir pc - Guide
- Capture d'écran whatsapp - Guide
67 réponses
Voici l'analyse de blue screen view:
http://image.noelshack.com/fichiers/2013/31/1375100624-analyse-blue-screen-view.jpg
http://image.noelshack.com/fichiers/2013/31/1375100624-analyse-blue-screen-view.jpg
lilidurhone
Messages postés
43343
Date d'inscription
lundi 25 avril 2011
Statut
Contributeur sécurité
Dernière intervention
19 juillet 2024
3 807
29 juil. 2013 à 16:26
29 juil. 2013 à 16:26
Hello mica
On va utiliser Whocrashed
https://www.commentcamarche.net/telecharger/utilitaires/23795-whocrashed-free-home-edition/
On va utiliser Whocrashed
https://www.commentcamarche.net/telecharger/utilitaires/23795-whocrashed-free-home-edition/
lilidurhone
Messages postés
43343
Date d'inscription
lundi 25 avril 2011
Statut
Contributeur sécurité
Dernière intervention
19 juillet 2024
3 807
29 juil. 2013 à 17:09
29 juil. 2013 à 17:09
Hello
Fort possible mais on verra ce qui cloche avec Whocrashed :)
Fort possible mais on verra ce qui cloche avec Whocrashed :)
Vous n’avez pas trouvé la réponse que vous recherchez ?
Posez votre question
lilidurhone
Messages postés
43343
Date d'inscription
lundi 25 avril 2011
Statut
Contributeur sécurité
Dernière intervention
19 juillet 2024
3 807
29 juil. 2013 à 17:20
29 juil. 2013 à 17:20
Hello
Si ça ne démarre pas en mode normal passe en mode sans échec
Si ça ne démarre pas en mode normal passe en mode sans échec
Tenez:
System Information (local)
--------------------------------------------------------------------------------
computer name: PC-DE-MICKAEL
windows version: Windows Vista Service Pack 1, 6.0, build: 6001
windows dir: C:\Windows
CPU: AuthenticAMD AMD Phenom(tm) 8600 Triple-Core Processor AMD586, level: 16
3 logical processors, active mask: 7
RAM: 3084660736 total
VM: 2147352576, free: 2008649728
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 29/07/2013 13:17:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini072913-02.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x5ADC4)
Bugcheck code: 0xA (0x0, 0x1B, 0x1, 0xFFFFFFFF82301E4A)
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 Mon 29/07/2013 13:17:31 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!Kei386EoiHelper+0x293C)
Bugcheck code: 0xA (0x0, 0x1B, 0x1, 0xFFFFFFFF82301E4A)
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: ntkrpamp.exe .
Google query: ntkrpamp.exe IRQL_NOT_LESS_OR_EQUAL
On Mon 29/07/2013 11:44:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini072913-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x5ADC4)
Bugcheck code: 0xC5 (0x4010004, 0x2, 0x1, 0xFFFFFFFF82332886)
Error: DRIVER_CORRUPTED_EXPOOL
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 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 Sun 28/07/2013 19:09:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini072813-03.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x1A316)
Bugcheck code: 0x24 (0x1904AA, 0xFFFFFFFF8B1879F0, 0xFFFFFFFF8B1876EC, 0xFFFFFFFF82303218)
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 Sun 28/07/2013 17:17:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini072813-02.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xCD1E3)
Bugcheck code: 0xF4 (0x3, 0xFFFFFFFF90227D90, 0xFFFFFFFF90227EDC, 0xFFFFFFFF82456430)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
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 28/07/2013 13:46:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini072813-01.dmp
This was probably caused by the following module: ps2.sys (PS2+0x203F)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF82307882, 0xFFFFFFFF8B18F698, 0xFFFFFFFF8B18F394)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\ps2.sys
product: Hewlett-Packard Company PS2 SYS
company: Hewlett-Packard Company
description: PS2 SYS
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.
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: ps2.sys (PS2 SYS, Hewlett-Packard Company).
Google query: Hewlett-Packard Company SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
6 crash dumps have been found and 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:
ps2.sys (PS2 SYS, Hewlett-Packard Company)
ntkrpamp.exe
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.
System Information (local)
--------------------------------------------------------------------------------
computer name: PC-DE-MICKAEL
windows version: Windows Vista Service Pack 1, 6.0, build: 6001
windows dir: C:\Windows
CPU: AuthenticAMD AMD Phenom(tm) 8600 Triple-Core Processor AMD586, level: 16
3 logical processors, active mask: 7
RAM: 3084660736 total
VM: 2147352576, free: 2008649728
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 29/07/2013 13:17:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini072913-02.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x5ADC4)
Bugcheck code: 0xA (0x0, 0x1B, 0x1, 0xFFFFFFFF82301E4A)
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 Mon 29/07/2013 13:17:31 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!Kei386EoiHelper+0x293C)
Bugcheck code: 0xA (0x0, 0x1B, 0x1, 0xFFFFFFFF82301E4A)
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: ntkrpamp.exe .
Google query: ntkrpamp.exe IRQL_NOT_LESS_OR_EQUAL
On Mon 29/07/2013 11:44:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini072913-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x5ADC4)
Bugcheck code: 0xC5 (0x4010004, 0x2, 0x1, 0xFFFFFFFF82332886)
Error: DRIVER_CORRUPTED_EXPOOL
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 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 Sun 28/07/2013 19:09:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini072813-03.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x1A316)
Bugcheck code: 0x24 (0x1904AA, 0xFFFFFFFF8B1879F0, 0xFFFFFFFF8B1876EC, 0xFFFFFFFF82303218)
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 Sun 28/07/2013 17:17:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini072813-02.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xCD1E3)
Bugcheck code: 0xF4 (0x3, 0xFFFFFFFF90227D90, 0xFFFFFFFF90227EDC, 0xFFFFFFFF82456430)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
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 28/07/2013 13:46:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini072813-01.dmp
This was probably caused by the following module: ps2.sys (PS2+0x203F)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF82307882, 0xFFFFFFFF8B18F698, 0xFFFFFFFF8B18F394)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\ps2.sys
product: Hewlett-Packard Company PS2 SYS
company: Hewlett-Packard Company
description: PS2 SYS
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.
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: ps2.sys (PS2 SYS, Hewlett-Packard Company).
Google query: Hewlett-Packard Company SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
6 crash dumps have been found and 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:
ps2.sys (PS2 SYS, Hewlett-Packard Company)
ntkrpamp.exe
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.
lilidurhone
Messages postés
43343
Date d'inscription
lundi 25 avril 2011
Statut
Contributeur sécurité
Dernière intervention
19 juillet 2024
3 807
29 juil. 2013 à 17:28
29 juil. 2013 à 17:28
Hello
Bon rien de bien méchant il faudrait que tu mettes à jour ce driver
=> ps2.sys (PS2 SYS, Hewlett-Packard Company)
Donne nous le modèle exact de ton pc?
Ensuite faudrait vérifier les erreurs sur le disque dur
Bon rien de bien méchant il faudrait que tu mettes à jour ce driver
=> ps2.sys (PS2 SYS, Hewlett-Packard Company)
Donne nous le modèle exact de ton pc?
Ensuite faudrait vérifier les erreurs sur le disque dur
Ou se trouve le Nom du modele?
C'est un HP ca c'est sur
et pour les erreurs comment je fais???
Et comment je le met a jour le driver
PS merci de ta précieuse aide
C'est un HP ca c'est sur
et pour les erreurs comment je fais???
Et comment je le met a jour le driver
PS merci de ta précieuse aide
lilidurhone
Messages postés
43343
Date d'inscription
lundi 25 avril 2011
Statut
Contributeur sécurité
Dernière intervention
19 juillet 2024
3 807
29 juil. 2013 à 17:33
29 juil. 2013 à 17:33
Mais non rassure toi tout va bien se passer
Ton rapport montre qu'un driver n'est pas compatible :)
Ton rapport montre qu'un driver n'est pas compatible :)
lilidurhone
Messages postés
43343
Date d'inscription
lundi 25 avril 2011
Statut
Contributeur sécurité
Dernière intervention
19 juillet 2024
3 807
29 juil. 2013 à 17:43
29 juil. 2013 à 17:43
Hello mica
En fait ton cas est un peu plus compliqué
Ton rapport whocrashed montre quelque chose d'anormal
"file path: C:\Windows\system32\drivers\ntfs.sys"
J'ai prévenu quelqu'un qui va regarder ton problème
En fait ton cas est un peu plus compliqué
Ton rapport whocrashed montre quelque chose d'anormal
"file path: C:\Windows\system32\drivers\ntfs.sys"
J'ai prévenu quelqu'un qui va regarder ton problème
Mais ca va être possible de le réparer?
lilidurhone
Messages postés
43343
Date d'inscription
lundi 25 avril 2011
Statut
Contributeur sécurité
Dernière intervention
19 juillet 2024
3 807
29 juil. 2013 à 17:45
29 juil. 2013 à 17:45
Oui bien sûr :)
Rassure toi :)
Rassure toi :)
lilidurhone
Messages postés
43343
Date d'inscription
lundi 25 avril 2011
Statut
Contributeur sécurité
Dernière intervention
19 juillet 2024
3 807
29 juil. 2013 à 17:49
29 juil. 2013 à 17:49
Il est déjà au courant (dès que je t'ai pris en charge)
Rassure toi patiente un peu :)
Rassure toi patiente un peu :)
J'ai peur que mon ordi s'éteigne et mette du temps a se rallumer
lilidurhone
Messages postés
43343
Date d'inscription
lundi 25 avril 2011
Statut
Contributeur sécurité
Dernière intervention
19 juillet 2024
3 807
29 juil. 2013 à 18:10
29 juil. 2013 à 18:10
Mais non rassure toi
Sois patient c'est tout
Sois patient c'est tout
g3n-h@ckm@n
Messages postés
13238
Date d'inscription
jeudi 31 janvier 2013
Statut
Membre
Dernière intervention
24 février 2022
948
29 juil. 2013 à 18:23
29 juil. 2013 à 18:23
salut moi j'aimerais contrôler quelque chose
Fais analyser le(s) fichier(s) suivants sur Virustotal :
Virus Total
clique sur "Parcourir" et trouve puis selectionne ce(s) fichier(s) :
C:\Windows\System32\Drivers\ntfs.sys
* Clique maintenant sur Envoyer le fichier. et laisse travailler tant que "Situation actuelle : en cours d'analyse" est affiché.
* Il est possible que le fichier soit mis en file d'attente en raison d'un grand nombre de demandes d'analyses. En ce cas, il te faudra patienter sans actualiser la page.
* Lorsque l'analyse est terminée colle le lien de(s)( la) page(s) dans ta prochaine réponse.
Fais analyser le(s) fichier(s) suivants sur Virustotal :
Virus Total
clique sur "Parcourir" et trouve puis selectionne ce(s) fichier(s) :
C:\Windows\System32\Drivers\ntfs.sys
* Clique maintenant sur Envoyer le fichier. et laisse travailler tant que "Situation actuelle : en cours d'analyse" est affiché.
* Il est possible que le fichier soit mis en file d'attente en raison d'un grand nombre de demandes d'analyses. En ce cas, il te faudra patienter sans actualiser la page.
* Lorsque l'analyse est terminée colle le lien de(s)( la) page(s) dans ta prochaine réponse.
c'est fait
Lien: https://www.virustotal.com/fr/file/12af3c19dd2de7d92ee4c03ad07bafd77eb8bff2333e6fbd9caaa0f654a35f46/analysis/
Lien: https://www.virustotal.com/fr/file/12af3c19dd2de7d92ee4c03ad07bafd77eb8bff2333e6fbd9caaa0f654a35f46/analysis/
g3n-h@ckm@n
Messages postés
13238
Date d'inscription
jeudi 31 janvier 2013
Statut
Membre
Dernière intervention
24 février 2022
948
29 juil. 2013 à 18:38
29 juil. 2013 à 18:38
va sur windows update dans ton menu demarrer , et prends toutes les mises à jour proposées
