Ecran noir
gregdj
Messages postés
7
Statut
Membre
-
gregdj Messages postés 7 Statut Membre -
gregdj Messages postés 7 Statut Membre -
Bonjour,
J'ai actuellement un problème avec mon ordinateur (Windows XP Service Pack 3). Il lui arrive d'avoir un écran noir et l'ordinateur cesse de fonctionner. A chaque fois que je le redémarre, il envoie un rapport d'erreur à Windows de la forme :
BCCode : 100000d1 BCP1 : 00000024 BCP2 : 00000002 BCP3 : 00000000 BCP4 : F739FD8F OSVer : 5_1_2600 SP : 3_0 Product : 768_1
J'ai installé WhoCrashed et Hijackthis pour avoir deux rapports. Il s'avère que c'est scsiport.sys et aswmon2.sys en cause. Que dois je faire?
Merci d'avance
J'ai actuellement un problème avec mon ordinateur (Windows XP Service Pack 3). Il lui arrive d'avoir un écran noir et l'ordinateur cesse de fonctionner. A chaque fois que je le redémarre, il envoie un rapport d'erreur à Windows de la forme :
BCCode : 100000d1 BCP1 : 00000024 BCP2 : 00000002 BCP3 : 00000000 BCP4 : F739FD8F OSVer : 5_1_2600 SP : 3_0 Product : 768_1
J'ai installé WhoCrashed et Hijackthis pour avoir deux rapports. Il s'avère que c'est scsiport.sys et aswmon2.sys en cause. Que dois je faire?
Merci d'avance
A voir également:
- Ecran noir
- Ecran noir - Guide
- Double ecran - Guide
- Capture d'écran ipad - Guide
- Capture d'écran whatsapp - Accueil - Messagerie instantanée
- Retourner ecran pc - Guide
3 réponses
cherche a quel perif corresponde ses deux fichier puis telechanger les pilote les plus récent.si c est des fichier officel de windows" il y a un problème materiel.
Rapport de WhoCrashed :
--------------------------------------------------------------------------------
Welcome to WhoCrashed (HOME EDITION) v 3.06
--------------------------------------------------------------------------------
This program checks for drivers which have been crashing your computer. If your computer has displayed a blue screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.
Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.
This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. If will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.
To obtain technical support visit www.resplendence.com/support
Click here to check if you have the latest version or if an update is available.
Just click the Analyze button for a comprehensible report ...
--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------
This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which also allows analysis of crashdumps on remote drives and computers on the network and offers a range of additional features.
Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
computer name: SN117870630319
windows version: Windows XP Service Pack 3, 5.1, build: 2600
windows dir: C:\WINDOWS
CPU: GenuineIntel Intel(R) Celeron(R) D CPU 3.20GHz Intel586, level: 15
1 logical processors, active mask: 1
RAM: 1005895680 total
VM: 2147352576, free: 2034774016
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Mon 13/08/2012 14:35:29 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini081312-01.dmp
This was probably caused by the following module: scsiport.sys (SCSIPORT+0x1D8F)
Bugcheck code: 0x100000D1 (0x24, 0x2, 0x0, 0xFFFFFFFFF739FD8F)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\scsiport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: SCSI Port Driver
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 17/07/2012 14:48:32 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini071712-01.dmp
This was probably caused by the following module: aswmon2.sys (aswMon2+0x7362)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF805446B2, 0xFFFFFFFFB59CE804, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\aswmon2.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! File System Filter Driver for Windows XP
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.
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: aswmon2.sys (avast! File System Filter Driver for Windows XP, AVAST Software).
Google query: aswmon2.sys AVAST Software KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
2 crash dumps have been found and analyzed. A third party driver has 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:
aswmon2.sys (avast! File System Filter Driver for Windows XP, AVAST Software)
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.
--------------------------------------------------------------------------------
Welcome to WhoCrashed (HOME EDITION) v 3.06
--------------------------------------------------------------------------------
This program checks for drivers which have been crashing your computer. If your computer has displayed a blue screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.
Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.
This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. If will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.
To obtain technical support visit www.resplendence.com/support
Click here to check if you have the latest version or if an update is available.
Just click the Analyze button for a comprehensible report ...
--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------
This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which also allows analysis of crashdumps on remote drives and computers on the network and offers a range of additional features.
Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
computer name: SN117870630319
windows version: Windows XP Service Pack 3, 5.1, build: 2600
windows dir: C:\WINDOWS
CPU: GenuineIntel Intel(R) Celeron(R) D CPU 3.20GHz Intel586, level: 15
1 logical processors, active mask: 1
RAM: 1005895680 total
VM: 2147352576, free: 2034774016
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Mon 13/08/2012 14:35:29 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini081312-01.dmp
This was probably caused by the following module: scsiport.sys (SCSIPORT+0x1D8F)
Bugcheck code: 0x100000D1 (0x24, 0x2, 0x0, 0xFFFFFFFFF739FD8F)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\scsiport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: SCSI Port Driver
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 17/07/2012 14:48:32 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini071712-01.dmp
This was probably caused by the following module: aswmon2.sys (aswMon2+0x7362)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF805446B2, 0xFFFFFFFFB59CE804, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\aswmon2.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! File System Filter Driver for Windows XP
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.
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: aswmon2.sys (avast! File System Filter Driver for Windows XP, AVAST Software).
Google query: aswmon2.sys AVAST Software KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
2 crash dumps have been found and analyzed. A third party driver has 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:
aswmon2.sys (avast! File System Filter Driver for Windows XP, AVAST Software)
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.
bof, le rapport ne donne que la meme choses de l observateur devennement de windows ...
ppour :
le fichiers scsiport.sys voir la :
https://support.microsoft.com/fr-fr/help/839635
pour l autre a tu avast comme antivirus ?
ppour :
le fichiers scsiport.sys voir la :
https://support.microsoft.com/fr-fr/help/839635
pour l autre a tu avast comme antivirus ?
