Driver IRQL not less or egual

Fermé
calimthar Messages postés 6 Date d'inscription jeudi 3 avril 2014 Statut Membre Dernière intervention 4 avril 2014 - 3 avril 2014 à 14:34
Miodo Messages postés 57 Date d'inscription vendredi 7 décembre 2012 Statut Membre Dernière intervention 11 avril 2014 - 4 avril 2014 à 21:54
Bonjour,
J'ai acheté un medion erazer 7825 en janvier. Au premier demarrage il a blue screen mais depuis plus aucun probleme. Depuis une semaine il plante 5/6 fois par jour avec la meme erreur: Driver IRQL not less or egual... J'ai cherché une solution mais je n'ai toujours pas trouvé. Merci de m'aider....
A voir également:

10 réponses

Miodo Messages postés 57 Date d'inscription vendredi 7 décembre 2012 Statut Membre Dernière intervention 11 avril 2014 6
3 avril 2014 à 14:42
Bonjour a toi ,
Tout d'abord je suohaite expliquer que ce probleme est du a des problemes de driver , et j'ai deja eu le meme probleme !
Donc je te conseil de verifier d'ou vien le probleme aec ce programme
" https://www.commentcamarche.net/telecharger/utilitaires/23795-whocrashed-free-home-edition/ "
Donc tu l'install normalement et tu le lance tu trouveras "Analyze" en haut , click deçu et descend en bat de la page tu trouveras le resultat et la cause du crash copie colle ici :D
a+
*Miodo
0
calimthar Messages postés 6 Date d'inscription jeudi 3 avril 2014 Statut Membre Dernière intervention 4 avril 2014
3 avril 2014 à 14:50
e22w8x64.sys (Killer e2200 PCI-E Gigabit Ethernet Controller, Qualcomm Atheros, Inc.)


voila
0
calimthar Messages postés 6 Date d'inscription jeudi 3 avril 2014 Statut Membre Dernière intervention 4 avril 2014
3 avril 2014 à 15:33
je met tout


--------------------------------------------------------------------------------
Welcome to WhoCrashed (HOME EDITION) v 5.01
--------------------------------------------------------------------------------

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. It 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 allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.


--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

computer name: PAUL
windows version: Windows 8 , 6.2, build: 9200
windows dir: C:\Windows
Hardware: X782X, MEDION
CPU: GenuineIntel Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 8468811776 total
VM: 2147352576, free: 1852129280




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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 03/04/2014 08:59:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040314-15171-01.dmp
This was probably caused by the following module: e22w8x64.sys (0xFFFFF8800881C353)
Bugcheck code: 0xD1 (0xFFFFF8801F1F5000, 0x2, 0x0, 0xFFFFF8800881C353)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\e22w8x64.sys
product: Killer e2200 PCI-E Gigabit Ethernet Controller
company: Qualcomm Atheros, Inc.
description: Killer e2200 PCI-E Gigabit Ethernet Controller
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: e22w8x64.sys (Killer e2200 PCI-E Gigabit Ethernet Controller, Qualcomm Atheros, Inc.).
Google query: Qualcomm Atheros, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Thu 03/04/2014 08:59:59 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: e22w8x64.sys (e22w8x64+0x1C353)
Bugcheck code: 0xD1 (0xFFFFF8801F1F5000, 0x2, 0x0, 0xFFFFF8800881C353)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\e22w8x64.sys
product: Killer e2200 PCI-E Gigabit Ethernet Controller
company: Qualcomm Atheros, Inc.
description: Killer e2200 PCI-E Gigabit Ethernet Controller
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: e22w8x64.sys (Killer e2200 PCI-E Gigabit Ethernet Controller, Qualcomm Atheros, Inc.).
Google query: Qualcomm Atheros, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Tue 01/04/2014 10:53:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040114-22359-01.dmp
This was probably caused by the following module: e22w8x64.sys (0xFFFFF88008032353)
Bugcheck code: 0xD1 (0xFFFFF88020664000, 0x2, 0x0, 0xFFFFF88008032353)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\e22w8x64.sys
product: Killer e2200 PCI-E Gigabit Ethernet Controller
company: Qualcomm Atheros, Inc.
description: Killer e2200 PCI-E Gigabit Ethernet Controller
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: e22w8x64.sys (Killer e2200 PCI-E Gigabit Ethernet Controller, Qualcomm Atheros, Inc.).
Google query: Qualcomm Atheros, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Mon 31/03/2014 11:35:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\033114-16593-01.dmp
This was probably caused by the following module: e22w8x64.sys (0xFFFFF88007032353)
Bugcheck code: 0xD1 (0xFFFFF880229D0000, 0x2, 0x0, 0xFFFFF88007032353)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\e22w8x64.sys
product: Killer e2200 PCI-E Gigabit Ethernet Controller
company: Qualcomm Atheros, Inc.
description: Killer e2200 PCI-E Gigabit Ethernet Controller
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: e22w8x64.sys (Killer e2200 PCI-E Gigabit Ethernet Controller, Qualcomm Atheros, Inc.).
Google query: Qualcomm Atheros, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Sat 29/03/2014 23:02:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\033014-23500-01.dmp
This was probably caused by the following module: e22w8x64.sys (0xFFFFF880087B5353)
Bugcheck code: 0xD1 (0xFFFFF88009B78000, 0x2, 0x0, 0xFFFFF880087B5353)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\e22w8x64.sys
product: Killer e2200 PCI-E Gigabit Ethernet Controller
company: Qualcomm Atheros, Inc.
description: Killer e2200 PCI-E Gigabit Ethernet Controller
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: e22w8x64.sys (Killer e2200 PCI-E Gigabit Ethernet Controller, Qualcomm Atheros, Inc.).
Google query: Qualcomm Atheros, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Sat 29/03/2014 14:41:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032914-19031-01.dmp
This was probably caused by the following module: e22w8x64.sys (0xFFFFF8800741C353)
Bugcheck code: 0xD1 (0xFFFFF88023BC3000, 0x2, 0x0, 0xFFFFF8800741C353)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\e22w8x64.sys
product: Killer e2200 PCI-E Gigabit Ethernet Controller
company: Qualcomm Atheros, Inc.
description: Killer e2200 PCI-E Gigabit Ethernet Controller
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: e22w8x64.sys (Killer e2200 PCI-E Gigabit Ethernet Controller, Qualcomm Atheros, Inc.).
Google query: Qualcomm Atheros, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Fri 28/03/2014 14:41:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032814-17781-01.dmp
This was probably caused by the following module: e22w8x64.sys (0xFFFFF880088AF353)
Bugcheck code: 0xD1 (0xFFFFF880040A7000, 0x2, 0x0, 0xFFFFF880088AF353)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\e22w8x64.sys
product: Killer e2200 PCI-E Gigabit Ethernet Controller
company: Qualcomm Atheros, Inc.
description: Killer e2200 PCI-E Gigabit Ethernet Controller
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: e22w8x64.sys (Killer e2200 PCI-E Gigabit Ethernet Controller, Qualcomm Atheros, Inc.).
Google query: Qualcomm Atheros, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Thu 27/03/2014 16:52:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032714-16203-01.dmp
This was probably caused by the following module: e22w8x64.sys (0xFFFFF88007BA7353)
Bugcheck code: 0xD1 (0xFFFFF880041F4000, 0x2, 0x0, 0xFFFFF88007BA7353)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\e22w8x64.sys
product: Killer e2200 PCI-E Gigabit Ethernet Controller
company: Qualcomm Atheros, Inc.
description: Killer e2200 PCI-E Gigabit Ethernet Controller
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: e22w8x64.sys (Killer e2200 PCI-E Gigabit Ethernet Controller, Qualcomm Atheros, Inc.).
Google query: Qualcomm Atheros, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Wed 26/03/2014 15:03:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032614-15421-01.dmp
This was probably caused by the following module: e22w8x64.sys (0xFFFFF880086AF353)
Bugcheck code: 0xD1 (0xFFFFF880019EF000, 0x2, 0x0, 0xFFFFF880086AF353)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\e22w8x64.sys
product: Killer e2200 PCI-E Gigabit Ethernet Controller
company: Qualcomm Atheros, Inc.
description: Killer e2200 PCI-E Gigabit Ethernet Controller
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: e22w8x64.sys (Killer e2200 PCI-E Gigabit Ethernet Controller, Qualcomm Atheros, Inc.).
Google query: Qualcomm Atheros, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Wed 05/02/2014 13:28:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020514-19281-01.dmp
This was probably caused by the following module: e22w8x64.sys (0xFFFFF88008C1C353)
Bugcheck code: 0xD1 (0xFFFFF8801D266000, 0x2, 0x0, 0xFFFFF88008C1C353)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\e22w8x64.sys
product: Killer e2200 PCI-E Gigabit Ethernet Controller
company: Qualcomm Atheros, Inc.
description: Killer e2200 PCI-E Gigabit Ethernet Controller
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: e22w8x64.sys (Killer e2200 PCI-E Gigabit Ethernet Controller, Qualcomm Atheros, Inc.).
Google query: Qualcomm Atheros, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL




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

13 crash dumps have been found and analyzed. Only 10 are included in this report. 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:

e22w8x64.sys (Killer e2200 PCI-E Gigabit Ethernet Controller, Qualcomm Atheros, Inc.)

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.
0
Miodo Messages postés 57 Date d'inscription vendredi 7 décembre 2012 Statut Membre Dernière intervention 11 avril 2014 6
4 avril 2014 à 00:41
Bon a ce que je vois c'est ce chere
"e22w8x64.sys (Killer e2200 PCI-E Gigabit Ethernet Controller, Qualcomm Atheros, Inc.) "
qui cause un probleme , je voudrais savoir si cela vien du reseau ou pas !
click droit sur post de travail > propriété > ( a gauche tu trouveras ges de peripherique ) clicl deçu > une liste apparait > va dans carte reseau !
Dans tous les cas normalement il devrait etre la bas ,
2/Verifie si tu est connecter a deux reseau en meme temps (connecter a internet ) !
Merci de repondre !
a++
*Miodo
0

Vous n’avez pas trouvé la réponse que vous recherchez ?

Posez votre question
calimthar Messages postés 6 Date d'inscription jeudi 3 avril 2014 Statut Membre Dernière intervention 4 avril 2014
4 avril 2014 à 12:49
Alors dans l'onglet carte reseau j'en ai 6!

Bluetooth device (Personal Area Network)
Bluetooth Device (RFCOMM Protocol TDI)
Intel(R) Wireless-N 7260
Killer e2200 Gigabit Ethernet Controller (NDIS 6.30)
Microsoft Kernel Debug Network Adapter

le dernier a un point d'exclamation devant: Teredop tunneling Pseudo-Interface

voila
0
Miodo Messages postés 57 Date d'inscription vendredi 7 décembre 2012 Statut Membre Dernière intervention 11 avril 2014 6
Modifié par Miodo le 4/04/2014 à 14:44
Bonjour,
Avant de commencez les grandes procedures ( si il va en avoir ) verifie si tout tes drivers son a jour (je parle bien du reseau ) !
(si tu cherche comment va sur ma-config.com)
Poste pour dire si il ya une mise a jour pour tes cartes reseaux
Aussi voila un screen de ce que je demander exactement dans l'autre poste ! ( me dire si tu est connecter a plusiers reseaux )
0
calimthar Messages postés 6 Date d'inscription jeudi 3 avril 2014 Statut Membre Dernière intervention 4 avril 2014
Modifié par calimthar le 4/04/2014 à 16:23
Tu veux un screen de quoi? juste l'onglet de windows 8?
0
Miodo Messages postés 57 Date d'inscription vendredi 7 décembre 2012 Statut Membre Dernière intervention 11 avril 2014 6
4 avril 2014 à 16:16
des reseaux au quel tu est connecter
0
calimthar Messages postés 6 Date d'inscription jeudi 3 avril 2014 Statut Membre Dernière intervention 4 avril 2014
4 avril 2014 à 16:58
je peux pas screen mais je suis connecté a ma box par cable et il me l'affiche aussi en wifi. c'est tout
0
Miodo Messages postés 57 Date d'inscription vendredi 7 décembre 2012 Statut Membre Dernière intervention 11 avril 2014 6
4 avril 2014 à 21:54
pour faire clair cela peut etre causer du a la connexion a plusiers reseau je peux te proposer d'essayer de desactiver un d'entre eux pour voir :D
A++
*Miodo
0