Blue Screen problème TCP/IP

Blue Screen problème TCP/IP - Win 10 - Windows & Software

Marsh Posté le 01-03-2017 à 12:53:29    

Bonjour,  
 
Je suis victime de blue screen intempestif depuis quelques temps, le message est toujours le même : DRIVER_IRQL_NOT_LESS_OR_EQUAL
J'ai un MSI GS60, et j'ai ce message très aléatoirement, 2 fois par semaine et après plus rien pendant 3 mois par exemple..
 
System Information (local)
--------------------------------------------------------------------------------
 
Computer name: DESKTOP-Q8LGA76
Windows version: Windows 10 , 10.0, build: 14393
Windows dir: C:\WINDOWS
Hardware: GS60 2QD, Micro-Star International Co., Ltd., MS-16H5
CPU: GenuineIntel Intel(R) Core(TM) i7-4720HQ CPU @ 2.60GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 12799983616 bytes total
 
 
 
 
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
 
Crash dump directory: C:\WINDOWS\Minidump
 
Crash dumps are enabled on your computer.
 
On Wed 01/03/2017 11:16:21 your computer crashed
crash dump file: C:\WINDOWS\Minidump\030117-8531-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF803E77CC9CC)  
Bugcheck code: 0xD1 (0xA, 0x2, 0x0, 0xFFFFF803E77CC9CC)
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 Wed 01/03/2017 11:16:21 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x2C9CC)  
Bugcheck code: 0xD1 (0xA, 0x2, 0x0, 0xFFFFF803E77CC9CC)
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.  
 
 
Une piste ?
En vous remerciant

Reply

Marsh Posté le 01-03-2017 à 12:53:29   

Reply

Marsh Posté le 01-03-2017 à 13:06:06    

Avec les infos que tu as donné, ça peut être un souci de drivers réseaux ou un souci matériel.
 
Vérifie que tu as la dernière version des drivers sur le site du constructeur.
Vérifie l'intégrité de ton système avec la commande  

sfc /scannow


---------------
#TeamNoBidouille || Come to the Dark Side, we have cookies || Mangez 5 fruits et légumes par an ! || Le digital, c'est les doigts
Reply

Marsh Posté le 07-03-2017 à 12:25:55    

Toujours le même problème.
Driver à jour à priori.
 
scannnow + memtest et rien n'a été trouvé.
 
J'ai aussi eu un autre blue screen :
 
On Tue 07/03/2017 01:15:14 your computer crashed
crash dump file: C:\WINDOWS\Minidump\030717-7250-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)  
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).  
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.  
 
Qui semble lié au premier...
Que faire ?

Reply

Marsh Posté le 07-03-2017 à 12:33:29    

Pour moi ça semble lié aux drivers réseau.
Essaye de les réinstaller avec la dernière version :

http://www.killernetworking.com/driver-downloads?task=callelement&format=raw&item_id=17&element=f85c494b-2b32-4109-b8c1-083cca2b7db6&method=download&args[0]=31b11d2756bbaf33d075857136ae007a

 

Pour info, les drivers KillerNetworks ne sont pas connus pour leur grande qualité...


Message édité par nex84 le 07-03-2017 à 12:34:57

---------------
#TeamNoBidouille || Come to the Dark Side, we have cookies || Mangez 5 fruits et légumes par an ! || Le digital, c'est les doigts
Reply

Marsh Posté le 07-03-2017 à 13:30:03    

Cette version marchera-t-elle sur mon PC ?

Reply

Marsh Posté le 07-03-2017 à 14:00:51    

Oui.
Au pire, l'installeur refusera d'installer les pilotes si ton PC n'est pas compatible.


---------------
#TeamNoBidouille || Come to the Dark Side, we have cookies || Mangez 5 fruits et légumes par an ! || Le digital, c'est les doigts
Reply

Marsh Posté le 25-03-2017 à 21:57:27    

Bonjour,
 
Le problème est résolu pendant 2 semaines et là j'ai eu des blue screen avec le même problème mais le fichier concerné est nwifi.sys, rapport :
 
On Sat 25/03/2017 21:50:50 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFF80F1BDBDCEC)  
Bugcheck code: 0xD1 (0xDECAFC37, 0x2, 0x0, 0xFFFFF80F1BDBDCEC)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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.  
Google query: DRIVER_IRQL_NOT_LESS_OR_EQUAL
 
 
 
On Thu 23/03/2017 18:49:14 your computer crashed
crash dump file: C:\WINDOWS\Minidump\032317-8468-01.dmp
This was probably caused by the following module: nwifi.sys (0xFFFFF800CFABDCEC)  
Bugcheck code: 0xD1 (0xDECAFC37, 0x2, 0x0, 0xFFFFF800CFABDCEC)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\nwifi.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de miniport WiFi natif
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.  
 
Des choses à me conseiller ?
Merci

Reply

Marsh Posté le 27-03-2017 à 00:06:06    

personne ?

Reply

Marsh Posté le 27-03-2017 à 10:54:49    

Salut, ca semble etre encore le pilote wifi le probleme,
 
Essai de desactiver ta carte wifi dans le gestionnaire peripherique et branche toi en ethernet
 
En supposant que tu as déja tenté de mettre le dernier pilote du constructeur
 
si ca résoud le probleme tu pourrais au pire changer ta carte wifi, d'occasion ca doit pas couter tres cher
 
----------
 
Donne nous egalement les details du peripherique wifi, dans gestionnaire periph clic droit sur carte reseau wifi
 
et propriete / details  / Numéro d'identification du periphérique


Message édité par azertyiop le 27-03-2017 à 10:58:39
Reply

Sujets relatifs:

Leave a Replay

Make sure you enter the(*)required information where indicate.HTML code is not allowed