Ecran bleu depuis nouvelle config
yo2263
-
yo2263 -
yo2263 -
Bonjour à tous,
J'espère etre dans la bonne section pour mon problème.
Depuis environ 15 jours maintenant j'ai changé mon pc. J'ai réinstallé mon Windows 7 mais j'ai remarqué que quelques fois mon pc ne s'éteignait pas complètement. Enfin le ventirad continue de trouner apres avoir eteint l'ordi et seul un appui long sur le bouton lui permet de s'éteindre totalement et de redémarrer.
En plus il me signale un soucis au redémarrage et me dirige vers le bios, mais aucun paramètre n'a changé.
Enfin hier j'(ai eu 2 écrans bleu. N'en connaissant pas la cause et n'ayant jamais eu à faire à ce genre de problème j'ai analyser avec Whocrashed. En voilà le rapport :
Donc apparemment c'est un soucis de directX et Avast.
J'aurais voulu avoir votre avis. Merci à vous
J'espère etre dans la bonne section pour mon problème.
Depuis environ 15 jours maintenant j'ai changé mon pc. J'ai réinstallé mon Windows 7 mais j'ai remarqué que quelques fois mon pc ne s'éteignait pas complètement. Enfin le ventirad continue de trouner apres avoir eteint l'ordi et seul un appui long sur le bouton lui permet de s'éteindre totalement et de redémarrer.
En plus il me signale un soucis au redémarrage et me dirige vers le bios, mais aucun paramètre n'a changé.
Enfin hier j'(ai eu 2 écrans bleu. N'en connaissant pas la cause et n'ayant jamais eu à faire à ce genre de problème j'ai analyser avec Whocrashed. En voilà le rapport :
System Information (local) -------------------------------------------------------------------------------- computer name: LIONEL-PC windows version: Windows 7 , 6.1, build: 7600 windows dir: C:\Windows CPU: AuthenticAMD AMD Phenom(tm) II X4 965 Processor AMD586, level: 16 4 logical processors, active mask: 15 RAM: 3487748096 total VM: 2147352576, free: 1990303744 -------------------------------------------------------------------------------- Crash Dump Analysis -------------------------------------------------------------------------------- Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Thu 26/05/2011 21:39:50 GMT your computer crashed crash dump file: C:\Windows\Minidump\052611-18064-01.dmp This was probably caused by the following module: aswsp.sys (aswSP+0x2CB1F) Bugcheck code: 0x50 (0xFFFFFFFFDAD6FD1A, 0x0, 0xFFFFFFFF91E38203, 0x2) Error: PAGE_FAULT_IN_NONPAGED_AREA file path: C:\Windows\system32\drivers\aswsp.sys product: avast! Antivirus System company: AVAST Software description: avast! self protection module 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. 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: aswsp.sys (avast! self protection module, AVAST Software). Google query: aswsp.sys AVAST Software PAGE_FAULT_IN_NONPAGED_AREA On Thu 26/05/2011 21:39:50 GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: aswsp.sys (aswSP+0xDDB8) Bugcheck code: 0x50 (0xFFFFFFFFDAD6FD1A, 0x0, 0xFFFFFFFF91E38203, 0x2) Error: PAGE_FAULT_IN_NONPAGED_AREA file path: C:\Windows\system32\drivers\aswsp.sys product: avast! Antivirus System company: AVAST Software description: avast! self protection module 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. 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: aswsp.sys (avast! self protection module, AVAST Software). Google query: aswsp.sys AVAST Software PAGE_FAULT_IN_NONPAGED_AREA On Thu 26/05/2011 15:49:40 GMT your computer crashed crash dump file: C:\Windows\Minidump\052611-19141-01.dmp This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x1DF02) Bugcheck code: 0x50 (0xFFFFFFFFB3433D88, 0x0, 0xFFFFFFFF92F35F02, 0x0) Error: PAGE_FAULT_IN_NONPAGED_AREA file path: C:\Windows\system32\drivers\dxgmms1.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: DirectX Graphics MMS 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. -------------------------------------------------------------------------------- Conclusion -------------------------------------------------------------------------------- 3 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: aswsp.sys (avast! self protection module, 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.
Donc apparemment c'est un soucis de directX et Avast.
J'aurais voulu avoir votre avis. Merci à vous
A voir également:
- Ecran bleu depuis nouvelle config
- Supprimer rond bleu whatsapp - Guide
- Double ecran - Guide
- Darkino nouvelle adresse - Guide
- Écran bleu - Guide
- Capture d'écran whatsapp - Accueil - Messagerie instantanée