Skip to Content

[Help] Problème Bluescreen !

Dernière contribution

14 posts / 0 nouveau(x)
Portrait de Dafternoon
Hors ligne
A rejoint: 23 novembre 2012
Contributions: 130
[Help] Problème Bluescreen !

Bonjour à tous.

Je viens à vous pour avoir des conseils et je l'espère une solution pour résoudre mon problème.
Je subit en effet le fatal bluescreen depuis quelques temps.
Sans raison apparente : l'ordinateur ne chauffe pas, il n'est pas forcément en pleine opération...
J'ai également vérifier la mémoire mais rien. Pas de virus apparent non plus (Microsoft Security Essential).
Je nettoie régulièrement mon ordinateur à l'aide de CCleaner et range au mieux mon espace de travail.
C'est pour cela que je ne comprend pas d'où cela peut bien venir.

Voici ma config :

Citation:
Windows 7 Edition Familiale Premium
Intel core i5 4670k à 3.40 GHZ
8 GO de ram
Nvidia GTX 670 - 2 GO

Et voici le détail du message d'erreur qu'il me met au redémarrage de Windows :

Citation:
Signature du problème :
Nom d’événement de problème: BlueScreen
Version du système: 6.1.7601.2.1.0.768.3
Identificateur de paramètres régionaux: 1036

Informations supplémentaires sur le problème :
BCCode: d1
BCP1: FFFFF88000B5E000
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFF8800F0DCFA0
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Fichiers aidant à décrire le problème :
C:\Windows\Minidump\110614-4851-01.dmp
C:\Users\Pierre\AppData\Local\Temp\WER-12292-0.sysdata.xml

Lire notre déclaration de confidentialité en ligne :
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x040c

Si la déclaration de confidentialité en ligne n’est pas disponible, lisez la version hors connexion :
C:\Windows\system32\fr-FR\erofflps.txt

Je suis disposé à répondre à toute vos question pour m'aider au mieux.
Merci d'avance à tous !

Dafter'

Edité par lemartialou le 02/07/2015 - 15:03

We are human, after all...

Spoiler

H
Portrait de H
Hors ligne
A rejoint: 18 septembre 2014
Contributions: 781
Re: [Help] Problème Bluescreen !

Salut.

"BCCode: d1" c'est une erreur de driver normalement. Est-ce que tu as installé un truc récemment ?

Juste pour être sûr que j'ai bien compris : le bluescreen apparait au bout d'un moment et pas de suite au démarrage ?

Portrait de Dafternoon
Hors ligne
A rejoint: 23 novembre 2012
Contributions: 130
Re: [Help] Problème Bluescreen !

Salut.
Je ne pense pas avoir installé quelque chose en particulier mis à part des jeux peut être et des màj.
Faudrait il que je regarde si je peux mettre à jour des drivers ?
Et pour répondre à ta dernière question, le bluescreen ne se produit pas au demarrage. Il m'est arrivé en revanche qu'il se produise 3 fois en 1 jour...

We are human, after all...

Spoiler

Portrait de nexy
Hors ligne
A rejoint: 29 décembre 2011
Contributions: 18922
Re: [Help] Problème Bluescreen !

Vérifies les drivers de ta CG, vérifies aussi sa température, vérifies également si ton alim est adapté a ta CG, car si a un moment ou a un autre l'alim ne fournie pas assez, c'est le blue screen.

L’écran bleu survient aussi quand le PC est au repos et tu ne fais rien dessus?
C'est un PC de bureau ou portable?

Portrait de PsyKTribe
Hors ligne
A rejoint: 20 juin 2014
Contributions: 407
Re: [Help] Problème Bluescreen !

Citation:
Fichiers aidant à décrire le problème :
C:\Windows\Minidump\110614-4851-01.dmp
C:\Users\Pierre\AppData\Local\Temp\WER-12292-0.sysdata.xml

Peut tu nous indiquez ce qui est raconter dans le rapport de dump?

Portrait de Dafternoon
Hors ligne
A rejoint: 23 novembre 2012
Contributions: 130
Re: [Help] Problème Bluescreen !

Alors déjà, les drivers de ma carte graphique sont toujours à jour avec le logiciel Nvidia Geforce Experience.
Mon alimentation est une 550 Watts il me semble.
Mais c'est un Pc que j'ai acheté monté donc en principe ils mettent des composants qui sont compatible (cela fait 2 ans que j'ai ce pc de bureau).
Le bluescreen ne m'est jamais vraiment arrivé au repos puisque j'étais toujours en train de faire quelque chose mais en tout cas pas à plein puissance loin de la.

Enfin, je n'arrive pas à acceder aux fichiers qu'ils indiquent pour décrire le problème. Je ne les trouve pas dans le AppData :/

We are human, after all...

Spoiler

Maître du monde
Portrait de Elfmaniac
Hors ligne
A rejoint: 1 septembre 2011
Contributions: 9180
Re: [Help] Problème Bluescreen !

Tu n'as peut-être pas activé l'affichage des fichiers et dossiers cachés.

Edité par Elfmaniac le 08/11/2014 - 14:53

Hébéééé! Ce jeu n'a aucun sens !

Portrait de Dafternoon
Hors ligne
A rejoint: 23 novembre 2012
Contributions: 130
Re: [Help] Problème Bluescreen !

Je ne le trouve pas non plus.
J'ai juste trouver le fichier situé dans " C:\Windows\Minidump\110614-4851-01.dmp " mais je ne peux pas l'ouvrir...

We are human, after all...

Spoiler

Portrait de nexy
Hors ligne
A rejoint: 29 décembre 2011
Contributions: 18922
Re: [Help] Problème Bluescreen !

T'as regardé la température de la CG?

Portrait de PsyKTribe
Hors ligne
A rejoint: 20 juin 2014
Contributions: 407
Re: [Help] Problème Bluescreen !

Installe ce logiciel il va scanner les dmp et te les afficher

Portrait de Dafternoon
Hors ligne
A rejoint: 23 novembre 2012
Contributions: 130
Re: [Help] Problème Bluescreen !

Pour ceux qui ont le courage... Merci.

Citation:
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 10/11/2014 19:27:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111014-4726-01.dmp
This was probably caused by the following module: e22w7x64.sys (0xFFFFF88006A6FFA0)
Bugcheck code: 0xD1 (0xFFFFF880054FE000, 0x2, 0x0, 0xFFFFF88006A6FFA0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\e22w7x64.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: e22w7x64.sys (Killer e2200 PCI-E Gigabit Ethernet Controller, Qualcomm Atheros, Inc.).
Google query: Qualcomm Atheros, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL

On Mon 10/11/2014 19:27:46 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: e22w7x64.sys (e22w7x64+0x19FA0)
Bugcheck code: 0xD1 (0xFFFFF880054FE000, 0x2, 0x0, 0xFFFFF88006A6FFA0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\e22w7x64.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: e22w7x64.sys (Killer e2200 PCI-E Gigabit Ethernet Controller, Qualcomm Atheros, Inc.).
Google query: Qualcomm Atheros, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL

On Thu 06/11/2014 17:55:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\110614-3978-01.dmp
This was probably caused by the following module: e22w7x64.sys (0xFFFFF88006A19FA0)
Bugcheck code: 0xD1 (0xFFFFF8800E031000, 0x2, 0x0, 0xFFFFF88006A19FA0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\e22w7x64.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: e22w7x64.sys (Killer e2200 PCI-E Gigabit Ethernet Controller, Qualcomm Atheros, Inc.).
Google query: Qualcomm Atheros, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL

On Thu 06/11/2014 16:44:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\110614-4851-01.dmp
This was probably caused by the following module: e22w7x64.sys (0xFFFFF8800F0DCFA0)
Bugcheck code: 0xD1 (0xFFFFF88000B5E000, 0x2, 0x0, 0xFFFFF8800F0DCFA0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\e22w7x64.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: e22w7x64.sys (Killer e2200 PCI-E Gigabit Ethernet Controller, Qualcomm Atheros, Inc.).
Google query: Qualcomm Atheros, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL

On Tue 04/11/2014 21:27:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\110414-4758-01.dmp
This was probably caused by the following module: e22w7x64.sys (0xFFFFF88006C19FA0)
Bugcheck code: 0xD1 (0xFFFFF88000BD1000, 0x2, 0x0, 0xFFFFF88006C19FA0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\e22w7x64.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: e22w7x64.sys (Killer e2200 PCI-E Gigabit Ethernet Controller, Qualcomm Atheros, Inc.).
Google query: Qualcomm Atheros, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL

On Sun 02/11/2014 19:17:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\110214-5475-01.dmp
This was probably caused by the following module: e22w7x64.sys (0xFFFFF88006C79FA0)
Bugcheck code: 0xD1 (0xFFFFF88005494000, 0x2, 0x0, 0xFFFFF88006C79FA0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\e22w7x64.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: e22w7x64.sys (Killer e2200 PCI-E Gigabit Ethernet Controller, Qualcomm Atheros, Inc.).
Google query: Qualcomm Atheros, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL

On Sun 02/11/2014 14:12:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\110214-5460-01.dmp
This was probably caused by the following module: e22w7x64.sys (0xFFFFF88006DDEFA0)
Bugcheck code: 0xD1 (0xFFFFF8800E132000, 0x2, 0x0, 0xFFFFF88006DDEFA0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\e22w7x64.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: e22w7x64.sys (Killer e2200 PCI-E Gigabit Ethernet Controller, Qualcomm Atheros, Inc.).
Google query: Qualcomm Atheros, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL

On Sun 02/11/2014 11:17:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\110214-5506-01.dmp
This was probably caused by the following module: e22w7x64.sys (0xFFFFF88006BCAFA0)
Bugcheck code: 0xD1 (0xFFFFF88002AC5000, 0x2, 0x0, 0xFFFFF88006BCAFA0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\e22w7x64.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: e22w7x64.sys (Killer e2200 PCI-E Gigabit Ethernet Controller, Qualcomm Atheros, Inc.).
Google query: Qualcomm Atheros, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL

On Sun 19/10/2014 15:30:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101914-4789-01.dmp
This was probably caused by the following module: e22w7x64.sys (0xFFFFF88006A19FA0)
Bugcheck code: 0xD1 (0xFFFFF88000B40000, 0x2, 0x0, 0xFFFFF88006A19FA0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\e22w7x64.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: e22w7x64.sys (Killer e2200 PCI-E Gigabit Ethernet Controller, Qualcomm Atheros, Inc.).
Google query: Qualcomm Atheros, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL

On Fri 17/10/2014 18:19:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101714-4929-01.dmp
This was probably caused by the following module: e22w7x64.sys (0xFFFFF88006C19FA0)
Bugcheck code: 0xD1 (0xFFFFF880054A4000, 0x2, 0x0, 0xFFFFF88006C19FA0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\e22w7x64.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: e22w7x64.sys (Killer e2200 PCI-E Gigabit Ethernet Controller, Qualcomm Atheros, Inc.).
Google query: Qualcomm Atheros, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL

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

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

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

We are human, after all...

Spoiler