Ecran bleu avec message d'erreur

Résolu/Fermé
Signaler
Messages postés
5
Date d'inscription
jeudi 5 février 2015
Statut
Membre
Dernière intervention
4 septembre 2015
-
Messages postés
34458
Date d'inscription
vendredi 24 août 2007
Statut
Membre
Dernière intervention
6 décembre 2021
-
Bonjour, comme vous l'avez vu dans mon titre. J'ai un problème avec mon ordinateur. Qui s'éteint brusquement et devient bleu. Il m'affiche un message d'erreur dont je ne comprend pas.
J'ai cherché sur de nombreux site. Et comme je ne m'y connais pas vraiment alors j'ai télécharger "Whocrashed".

J'ai fait une analyse a chaque fois que mon ordi a craché. Et j'ai obtenu cela :
System Information (local)
--------------------------------------------------------------------------------
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: X55U, ASUSTeK COMPUTER INC.
CPU: AuthenticAMD AMD E2-1800 APU with Radeon(tm) HD Graphics AMD586, level: 20
2 logical processors, active mask: 3
RAM: 3851726848 total

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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 05/02/2015 11:57:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020515-23462-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF8800189456B)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF8800189456B)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote TCP/IP
Bug check description: This indicates that a kernel-mode driver attempted to access pageable 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.
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 05/02/2015 11:57:58 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: appexdrv.sys (appexDrv+0x9A65)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF8800189456B)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\appexdrv.sys
product: AppEx Accelerator L.E.
company: AppEx Networks Corporation
description: AppEx Accelerator LWF/WFP Driver L.E.
Bug check description: This indicates that a kernel-mode driver attempted to access pageable 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.
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: appexdrv.sys (AppEx Accelerator LWF/WFP Driver L.E., AppEx Networks Corporation).
Google query: AppEx Networks Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Thu 29/01/2015 07:45:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012915-27206-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF8800189556B)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF8800189556B)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote TCP/IP
Bug check description: This indicates that a kernel-mode driver attempted to access pageable 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.
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 29/01/2015 07:41:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012915-43212-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF8800169456B)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF8800169456B)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote TCP/IP
Bug check description: This indicates that a kernel-mode driver attempted to access pageable 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.
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 29/01/2015 07:08:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012915-25584-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF8800189556B)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF8800189556B)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote TCP/IP
Bug check description: This indicates that a kernel-mode driver attempted to access pageable 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.
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 22/01/2015 07:29:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012215-20685-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF8800189556B)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF8800189556B)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote TCP/IP
Bug check description: This indicates that a kernel-mode driver attempted to access pageable 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.
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 12/01/2015 09:41:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011215-17846-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF8800169456B)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF8800169456B)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote TCP/IP
Bug check description: This indicates that a kernel-mode driver attempted to access pageable 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.
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.

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

7 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:

appexdrv.sys (AppEx Accelerator LWF/WFP Driver L.E., AppEx Networks Corporation)

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 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.

Je fais régulièrement mes mises à jours sur windows update. Ex qu'il serait possible de m'aider et de trouver une solution à tous cela. J'espère que je vous ait donné suffisamment de détail sur mon problème.
merci de vos réponses
Cordialement FeeMoiiRiire

2 réponses

Messages postés
4336
Date d'inscription
vendredi 20 avril 2012
Statut
Membre
Dernière intervention
13 février 2016
831
Bjr,

lancez une détection de vos drivers ici :

https://www.touslesdrivers.com/?v_page=29

faites les MAJ si résultats dispos.

Crdlt.
1
Merci

Quelques mots de remerciements seront grandement appréciés. Ajouter un commentaire

CCM 41989 internautes nous ont dit merci ce mois-ci

Messages postés
34458
Date d'inscription
vendredi 24 août 2007
Statut
Membre
Dernière intervention
6 décembre 2021
3 924
Il aurait fallu, au moins, nous indiquer le message d'erreur qui s'affiche.