Ecran bleu sur Windows 7

[Nesto]

Bonjour,

Cela fait un petit moment que je me prend des écrans bleu, cela peut venir en peu de temps comme me laisser tranquille pendant plusieurs jours, j'ai donc pris des photos de ces écrans bleu pour savoir si vous pouviez identifier la source de mon problème. Merci par avance à la communauté !

Ecran bleu N°1: https://image.noelshack.com/fichiers/2017/28/7/1500205653-bluescreen01.jpg

Ecran bleu N°2: https://image.noelshack.com/fichiers/2017/28/7/1500205653-bluescreen02.jpg

[routman54]

Bonjour ,
Tu as deux écrans bleus pour des raisons différentes . Bien souvent c'est du à un problème de rams . Vérifies qu'elles soient bien enfichées . Si c'est le cas essaies une journée avec une puis le lendemain avec l'autre .
Tu peux également le faire avec Memtest mais c'est pareil cinq à six passes barrette par barrette .
Bonne continuation .

[Pac428]

Salut Nesto.

Tu peux aussi essayer d'en savoir un peu plus avec WhoCrashed. Poste nous les rapports stp.

WhoCrashed c'est ici : http://www.resplendence.com/downloads ( le sixième logiciel en descendant.)

++

[routman54]

Bonjour ,
Ou BlueScreenview que l'on peut télécharger en Français( en bas de la page ) . Nirsoft a fait pas mal de logiciels sympa .
Bonne continuation .

[Nesto]

Bonsoir,

Merci pour votre aide, je regarde ça demain, j'ai reçu mon nouveau boitier et mon watercooling ce matin, j'en ai donc profité pour faire un nettoyage de mes composants avant l’installation, et je n'ai pas eu d'écran bleu depuis.

Encore merci, je reviens vers vous!

PS: Finalement j'ai encore eu un écran bleu!

Voici ce qui en sort de WhoCrashed

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

This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) screen of death, suddenly rebooted or shut down then this program might help you find the root cause of the problem and a solution.

Whenever a computer suddenly reboots without displaying any notice or blue (or black) 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 or black 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.

Please note that this version of WhoCrashed is not licensed for use by professional support engineers.

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


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

Computer name: ERNESTO-PC
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Hardware: MS-7693, MSI, 970 GAMING (MS-7693)
CPU: AuthenticAMD AMD FX(tm)-6300 Six-Core Processor AMD586, level: 21
6 logical processors, active mask: 63
RAM: 8535728128 bytes total




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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Tue 18/07/2017 10:09:48 your computer crashed
crash dump file: C:\Windows\Minidump\071817-26988-01.dmp
This was probably caused by the following module: bflwfx64.sys (0xFFFFF88004A22450)
Bugcheck code: 0xD1 (0xFFFFFA800E661000, 0x2, 0x0, 0xFFFFF88004A22450)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\bflwfx64.sys
product: Killer Bandwidth Control
company: Rivet Networks, LLC.
description: Killer Bandwidth Control Filter Driver
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: bflwfx64.sys (Killer Bandwidth Control Filter Driver, Rivet Networks, LLC.).
Google query: Rivet Networks, LLC. DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Tue 18/07/2017 10:09:48 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: bflwfx64.sys (bflwfx64+0x11450)
Bugcheck code: 0xD1 (0xFFFFFA800E661000, 0x2, 0x0, 0xFFFFF88004A22450)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\bflwfx64.sys
product: Killer Bandwidth Control
company: Rivet Networks, LLC.
description: Killer Bandwidth Control Filter Driver
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: bflwfx64.sys (Killer Bandwidth Control Filter Driver, Rivet Networks, LLC.).
Google query: Rivet Networks, LLC. DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Mon 17/07/2017 14:43:19 your computer crashed
crash dump file: C:\Windows\Minidump\071717-25584-01.dmp
This was probably caused by the following module: bflwfx64.sys (0xFFFFF88004A65450)
Bugcheck code: 0xD1 (0xFFFFFA8011BD0000, 0x2, 0x0, 0xFFFFF88004A65450)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\bflwfx64.sys
product: Killer Bandwidth Control
company: Rivet Networks, LLC.
description: Killer Bandwidth Control Filter Driver
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: bflwfx64.sys (Killer Bandwidth Control Filter Driver, Rivet Networks, LLC.).
Google query: Rivet Networks, LLC. DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Sun 16/07/2017 23:15:36 your computer crashed
crash dump file: C:\Windows\Minidump\071617-21247-01.dmp
This was probably caused by the following module: bflwfx64.sys (0xFFFFF88004C93450)
Bugcheck code: 0xD1 (0xFFFFFA800FC17000, 0x2, 0x0, 0xFFFFF88004C93450)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\bflwfx64.sys
product: Killer Bandwidth Control
company: Rivet Networks, LLC.
description: Killer Bandwidth Control Filter Driver
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: bflwfx64.sys (Killer Bandwidth Control Filter Driver, Rivet Networks, LLC.).
Google query: Rivet Networks, LLC. DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Sat 15/07/2017 16:00:53 your computer crashed
crash dump file: C:\Windows\Minidump\071517-19843-01.dmp
This was probably caused by the following module: bflwfx64.sys (0xFFFFF88004A8C450)
Bugcheck code: 0xD1 (0xFFFFFA800FF5D000, 0x2, 0x0, 0xFFFFF88004A8C450)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\bflwfx64.sys
product: Killer Bandwidth Control
company: Rivet Networks, LLC.
description: Killer Bandwidth Control Filter Driver
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: bflwfx64.sys (Killer Bandwidth Control Filter Driver, Rivet Networks, LLC.).
Google query: Rivet Networks, LLC. DRIVER_IRQL_NOT_LESS_OR_EQUAL





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

11 crash dumps have been found and analyzed. Only 5 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:

bflwfx64.sys (Killer Bandwidth Control Filter Driver, Rivet Networks, LLC.)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by 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.

[routman54]

Bonjour ,
On voit bien que la coupable est ta carte réseau Rivet Networks , rends toi sur le site de TLD j'ai vu qu'il y avait ces pilotes , lances une détection et il te proposera les pilotes pour mettre à jour ton appareil dont ceux de la carte réseau .
Bonne continuation .

[Nesto]

Bonjour ,
On voit bien que la coupable est ta carte réseau Rivet Networks , rends toi sur le site de TLD j'ai vu qu'il y avait ces pilotes , lances une détection et il te proposera les pilotes pour mettre à jour ton appareil dont ceux de la carte réseau .
Bonne continuation .

Merci pour ton aide, effectivement j'ai de grosse mise à jour à faire, je reviens vers vous pour vous dire quoi!

[Nesto]

Bonsoir,

J'ai beau installer le pilote pour internet mais il le re-propose à chaque analyse de le re-télécharger, comme si l'installation n'avait pas eu lieu...

Précision, j'ai eu ces problèmes après avoir pris une version payante d'Avast et ensuite avoir fais une analyse avec...

[routman54]

Bonsoir ,
Quand tu l'installes tu n'aurai pas une mise en garde d'Avast te disant que le fichier n'est pas signé ?
Essaies de le télécharger , tu le laisses dans son package sans le dézipper , tu te coupes d' Internet et tu désactives les agents Avast pour admettons jusqu'au redémarrage . Tu lances ton installation puis seulement après tu coupes ton ordinateur et le redémarres .
Pas sûr à 100% mais ça peut marcher .
Bonne continuation .

[Nesto]

Je n'ai aucun avertissement d'Avast. J'ai même désinstallé le Killer Ethernet Manager, et le pilote, pour réinstaller le tout manuellement, sans le manager.

J'ai fait une autre analyse et on peut voir qu'Avast y figure aussi maintenant.

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 19/07/2017 15:35:59 your computer crashed
crash dump file: C:\Windows\Minidump\071917-71822-01.dmp
This was probably caused by the following module: bflwfx64.sys (0xFFFFF88004881450)
Bugcheck code: 0xD1 (0xFFFFFA8008634000, 0x2, 0x0, 0xFFFFF88004881450)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\bflwfx64.sys
product: Killer Bandwidth Control
company: Rivet Networks, LLC.
description: Killer Bandwidth Control Filter Driver
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: bflwfx64.sys (Killer Bandwidth Control Filter Driver, Rivet Networks, LLC.).
Google query: Rivet Networks, LLC. DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Wed 19/07/2017 15:35:59 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: aswnetsec.sys (aswNetSec+0x48EAB)
Bugcheck code: 0xD1 (0xFFFFFA8008634000, 0x2, 0x0, 0xFFFFF88004881450)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\aswnetsec.sys
product: Avast Antivirus
company: AVAST Software
description: Avast Firewall Driver
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: aswnetsec.sys (Avast Firewall Driver, AVAST Software).
Google query: AVAST Software DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Tue 18/07/2017 10:09:48 your computer crashed
crash dump file: C:\Windows\Minidump\071817-26988-01.dmp
This was probably caused by the following module: bflwfx64.sys (0xFFFFF88004A22450)
Bugcheck code: 0xD1 (0xFFFFFA800E661000, 0x2, 0x0, 0xFFFFF88004A22450)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\bflwfx64.sys
product: Killer Bandwidth Control
company: Rivet Networks, LLC.
description: Killer Bandwidth Control Filter Driver
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: bflwfx64.sys (Killer Bandwidth Control Filter Driver, Rivet Networks, LLC.).
Google query: Rivet Networks, LLC. DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Mon 17/07/2017 14:43:19 your computer crashed
crash dump file: C:\Windows\Minidump\071717-25584-01.dmp
This was probably caused by the following module: bflwfx64.sys (0xFFFFF88004A65450)
Bugcheck code: 0xD1 (0xFFFFFA8011BD0000, 0x2, 0x0, 0xFFFFF88004A65450)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\bflwfx64.sys
product: Killer Bandwidth Control
company: Rivet Networks, LLC.
description: Killer Bandwidth Control Filter Driver
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: bflwfx64.sys (Killer Bandwidth Control Filter Driver, Rivet Networks, LLC.).
Google query: Rivet Networks, LLC. DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Sun 16/07/2017 23:15:36 your computer crashed
crash dump file: C:\Windows\Minidump\071617-21247-01.dmp
This was probably caused by the following module: bflwfx64.sys (0xFFFFF88004C93450)
Bugcheck code: 0xD1 (0xFFFFFA800FC17000, 0x2, 0x0, 0xFFFFF88004C93450)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\bflwfx64.sys
product: Killer Bandwidth Control
company: Rivet Networks, LLC.
description: Killer Bandwidth Control Filter Driver
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: bflwfx64.sys (Killer Bandwidth Control Filter Driver, Rivet Networks, LLC.).
Google query: Rivet Networks, LLC. DRIVER_IRQL_NOT_LESS_OR_EQUAL

[routman54]

Bonsoir ,
On va passer outre de Avast , en bas à droite tu cliques sur la petite flèche montante , les icônes de barre de tâche cachées seront visible tu cliques sur celui d'Avast . Une fenêtre Avast s'ouvre tu cliques en bas à gauche sur Paramètres , dans la nouvelle fenêtre Général ouverte tu sélectionnes l'avant dernière ligne en bas Exclusion et tu marques le chemin ou est ton fichier Killer Bandwidth Control Filter Drivers . Je pense que c'est : C:\Windows\system32\drivers\bflwfx64.sys .
Sinon on choisira un autre antivirus gratuit ce n'est pas ce qui manque .
J'ai déjà rencontré des soucis avec Avast mais aussi avec d'autres , moi j'ai Avast depuis des années donc je ne m'en plains pas mais j'ai vu restaurer entièrement des ordinateurs et ceux ci refusés Avast , donc je choisissais son concurrent Avira par exemple .
On teste comme cela et tu me le redis.
Bonne continuation .

[Nesto]

Hello, merci pour ton aide! Du coup j'ai fait la manipulation, je dois faire un truc en plus ? Ou je regarde sur le temps si j'ai encore le problème ?

[routman54]

Re ,
Tu regardes sur le temps , si le problème est réglé passes me le dire . Ça peut en aider d'autres .
Bonne continuation .

[Nesto]

Re ,
Tu regardes sur le temps , si le problème est réglé passes me le dire . Ça peut en aider d'autres .
Bonne continuation .

Très bien! Je reviens pas ce vendredi mais l'autre pour faire mon "rapport" !

Encore merci à toi

[Nesto]

Hello! Petit retour pour vous tenir informé et vous dire avec joie que je n'ai plus eu aucun écran bleu

Merci pour votre aide!