BSOD - drivers Killer Network en cause

Marsh Posté le 24-01-2016 à 09:58:52

Bonjour,

J'ai acheté un alienware 17 R2 en avril dernier et dès l'achat j'ai eu occasionnellement des BSOD (ecran bleu windows). C'était assez exceptionnel pour ne pas que je m'en préoccupe. Entre temps je suis passé à windows 8, 8.1 puis 10 avec, toujours le même problème malgré des installations clean. Puis récemment le BSOD s'est mis à se faire récurrent au point de m'empêcher de travailler. J'ai contacté DELL puisque le PC est encore sous garantie, un technicien est venu remplacer la carte mère du pc, mais à mon grand malheur, ça n'a absolument pas réglé le problème. Les diagnostics du PC ne montrent aucune défaillance, j'ai lancé memtest86+ un nombre incalculable de fois sans jamais trouver d'erreurs. J'ai scanné et rescanné mes disques sans trouver le moindre problème détectable.

Honnêtement je sais plus quoi faire, si le problème n'est pas hardware, aucune défaillance et carte mère neuve, ni software car le même problème continue malgré les reformatages je ne comprends pas.

J'ai eu principalement les messages d'erreurs suivants :
Kernel security check failure
Driver IRQL not less or equal

Ma config est un intel core i7 4710HQ avec 16 Go Ram, mon système est installé sur un SSD LiteOn jugé en bon état par HDtune et SSDlife, accompagné d'un disque dur WD pour les données, et la carte graphique est une Nvidia GTX 980M.

Fait étrange j'ignore si c'est important, mais je n'ai jamais eu de BSOD durant un jeu quand le PC chauffe, le problème survient beaucoup notamment quand je lance des applications du style illustrator, logiciel de compta, quand je télécharge ou alors quand je laisse le pc au repos je le récupère et je vois qu'il a redémarré, et l'historique des erreurs me confirme que windows s'est arrêté de manière inattendue. Ca contribue à rendre mon problème encore plus inexplicable. :??:

Help quelqu'un a une piste svp??

Message édité par Mnevis le 26-01-2016 à 20:51:26

---------------
Sony Vaio SVZ1311C5E - Core i7-3632QM @ 2.2GHz - 8GB DDR3 1600MHz - SSD 512GB Gen3 - LCD 1920x1080 Premium 13.1" Full HD - Noir Premium

Reply

Marsh Posté le 24-01-2016 à 09:58:52

Reply

Marsh Posté le 24-01-2016 à 10:15:05

Hello.

Il serait bon de commencer à logger/lister tes BSOD avec des outils classiques pour s'orienter un peu:

http://www.resplendence.com/whocrashed

http://www.bleepingcomputer.com/do [...] creenview/

---------------
Guide OC x58 - Guide d'achat de config - ALIMS:qui fait quoi? - RKO - Radiooooo

Reply

Marsh Posté le 24-01-2016 à 13:33:58

Hello, merci pour ta réponse super rapide!

J'ai fait une analyse avec whocrashed :

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

Computer name: ALIEN-M17
Windows version: Windows 10 , 10.0, build: 10586
Windows dir: C:\WINDOWS
Hardware: Alienware 17 R2, Alienware
CPU: GenuineIntel Intel(R) Core(TM) i7-4710HQ CPU @ 2.50GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17059758080 bytes total

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

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Fri 22/01/2016 03:49:57 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\012216-17562-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x139 (0x3, 0xFFFFD00024127750, 0xFFFFD000241276A8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Fri 22/01/2016 03:49:57 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x139 (0x3, 0xFFFFD00024127750, 0xFFFFD000241276A8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Thu 21/01/2016 11:53:19 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\012116-17703-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x9F (0x3, 0xFFFFE000A0078060, 0xFFFFD0006F05B990, 0xFFFFE000A37FAC60)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Tue 12/01/2016 20:31:38 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\011216-18218-01.dmp
This was probably caused by the following module: ntfs.sys (NTFS!NtfsAllocateNonpagedFcb+0x50)
Bugcheck code: 0x139 (0x3, 0xFFFFD00028F247D0, 0xFFFFD00028F24728, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: The kernel has detected the corruption of a critical data structure.
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 Tue 12/01/2016 20:27:13 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\011216-17218-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl!DXGDEVICE::Initialize+0xF4)
Bugcheck code: 0x139 (0x3, 0xFFFFD000232866C0, 0xFFFFD00023286618, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: The kernel has detected the corruption of a critical data structure.
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 Tue 12/01/2016 20:23:52 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\011216-16484-01.dmp
This was probably caused by the following module: dxgmms2.sys (dxgmms2!VidSchTerminateDevice+0xB6)
Bugcheck code: 0x139 (0x3, 0xFFFFD0017F3AB610, 0xFFFFD0017F3AB568, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\drivers\dxgmms2.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: The kernel has detected the corruption of a critical data structure.
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 Tue 12/01/2016 20:21:07 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\011216-17625-01.dmp
This was probably caused by the following module: dxgmms2.sys (dxgmms2!VidSchTerminateDevice+0xB6)
Bugcheck code: 0x139 (0x3, 0xFFFFD000340FD610, 0xFFFFD000340FD568, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\drivers\dxgmms2.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: The kernel has detected the corruption of a critical data structure.
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 11/01/2016 03:22:19 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\011116-16796-01.dmp
This was probably caused by the following module: bwcw10x64.sys (0xFFFFF80134C04623)
Bugcheck code: 0xD1 (0xFFFFE0014CA74000, 0x2, 0x0, 0xFFFFF80134C04623)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\bwcw10x64.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: bwcw10x64.sys (Killer Bandwidth Control Filter Driver, Rivet Networks, LLC.).
Google query: Rivet Networks, LLC. DRIVER_IRQL_NOT_LESS_OR_EQUAL

On Fri 08/01/2016 23:03:21 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\010916-7828-01.dmp
This was probably caused by the following module: bwcw10x64.sys (0xFFFFF8019A2A4623)
Bugcheck code: 0xD1 (0xFFFFE00130758000, 0x2, 0x0, 0xFFFFF8019A2A4623)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\bwcw10x64.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: bwcw10x64.sys (Killer Bandwidth Control Filter Driver, Rivet Networks, LLC.).
Google query: Rivet Networks, LLC. DRIVER_IRQL_NOT_LESS_OR_EQUAL

On Fri 08/01/2016 22:26:04 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\010816-17234-01.dmp
This was probably caused by the following module: bwcw10x64.sys (0xFFFFF8007B0F4623)
Bugcheck code: 0xD1 (0xFFFFE000A99BC000, 0x2, 0x0, 0xFFFFF8007B0F4623)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\bwcw10x64.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: bwcw10x64.sys (Killer Bandwidth Control Filter Driver, Rivet Networks, LLC.).
Google query: Rivet Networks, LLC. DRIVER_IRQL_NOT_LESS_OR_EQUAL

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

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

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

Du coup si je comprend bien, ça pourrait provenir du driver de ma carte réseau, le logiciel killer network manager étant le logiciel qui gère les drivers wifi/ethernet. Je me suis assuré d'avoir les derniers drivers en date plusieurs fois, donc il me reste à chercher les solutions des problèmes similaires comme le conseille le soft.
Une question demeure tout de même, est-ce que les erreurs de kernel security failure sont dues au même problème? Il y a des chances pour ce que soit le cas non?
Ca m'avance déjà pas mal de connaître une des causes du dysfonctionnement, merci

Message édité par Mnevis le 24-01-2016 à 13:40:25

---------------
Sony Vaio SVZ1311C5E - Core i7-3632QM @ 2.2GHz - 8GB DDR3 1600MHz - SSD 512GB Gen3 - LCD 1920x1080 Premium 13.1" Full HD - Noir Premium

Reply

Marsh Posté le 24-01-2016 à 13:37:05

Ah effectivement, c'est la fiesta du BSOD

1) les "killer network" sont une surcouche logicielle et non pas les pilotes il me semble non? Ca met un boxon pas possible sur plein de configs = a supprimer complètement (si ça n'inclut pas la partie purement "pilote" )

2) si ça n'est pas ça, la "variété" des BSOD peut orienter vers la RAM => UBCD / Memtest86+ http://www.ultimatebootcd.com/

---------------
Guide OC x58 - Guide d'achat de config - ALIMS:qui fait quoi? - RKO - Radiooooo

Reply

Marsh Posté le 24-01-2016 à 14:16:30

Ah ouais? C'est parti pour tester sans le killer network alors on va voir ça. Si c'est ça je leur en toucherai 2 mots à Dell. Au prix où ça coûte les alienware ça empêche pas de se retrouver avec des logiciels vérolés

J'ai trouvé quelqu'un qui avait le même problème sur le forum
http://forum.hardware.fr/hfr/Hardw [...] 4562_1.htm

Tout ça me fait dire que killer manager = BSOD :non:

---------------
Sony Vaio SVZ1311C5E - Core i7-3632QM @ 2.2GHz - 8GB DDR3 1600MHz - SSD 512GB Gen3 - LCD 1920x1080 Premium 13.1" Full HD - Noir Premium

Reply

Marsh Posté le 26-01-2016 à 20:49:51

Bonjour, je n'ai pas encore eu l'occasion de tester, car je vais refaire une installation clean de mon système.

Il est possible d'installer le drivers sans le soft killer mais en lui substituant un autre driver de chez atheros, l'astuce ne m'inspire tout de même pas super confiance, mais c'est une solution.

Sinon j'ai trouvé les drivers chez le constructeur killer, dont les drivers sont plus à jour que chez dell, et dans le changelog :

Killer Bandwidth Control
Fixed BSOD crashes under stress scenarios.

Je ferais un feedback si j'y pense après un mois d'utilisation, voir si ça résout le problème des bsod, si ça peut servir à quelqu'un.

Edit du titre

---------------
Sony Vaio SVZ1311C5E - Core i7-3632QM @ 2.2GHz - 8GB DDR3 1600MHz - SSD 512GB Gen3 - LCD 1920x1080 Premium 13.1" Full HD - Noir Premium

Reply

BSOD - drivers Killer Network en cause

Sujets relatifs:

Leave a Replay