Actualité informatique
Test comparatif matériel informatique
Jeux vidéo
Astuces informatique
Vidéo
Télécharger
Services en ligne
Forum informatique
01Business

|-  SECURITE


|||-  

Ecran bleu avec :( ... Diver irql not less or equal (netiosys)

 

139 utilisateurs inconnus
Ajouter une réponse
 

 
Page photos
 
     
Vider la liste des messages à citer
 
 Page :
1
Auteur
 Sujet :

Ecran bleu avec :( ... Diver irql not less or equal (netiosys)

RÉSOLU
Prévenir les modérateurs en cas d'abus 
bileg
bileg
Débutant confirmé (de 1 000 à 4 999 messages postés)
  1. Posté le 22/02/2014 à 22:46:05  
  1. answer
  1. Prévenir les modérateurs en cas d'abus
 
Bonjour
De temps en temps j'ai un écran bleu qui commence par :( en très gros puis : votre ordinateur a rencontré un problème et doit redémarrer, en dessous il y a en lettres majuscule : DRIVER IRQL NOT LESS OR EQUAL (NETIOSYS)

d’où peut venir ce problème ?
Parfois l'ordinateur redémarre, sinon je suis obliger de forcer l’arrêt.

J'ai Windows 8.1

Cordialement
Message édité par bileg le 22/02/2014 à 22:57:28
La Mayenne-son calme -sa verdu
Profil : Equipe sécurité
  1. homepage
bernard53
Membre impliqué (de 20 000 à 29 999 messages postés) Helpeur confirmé Fan Club de Clic-Clic
  1. Posté le 23/02/2014 à 14:01:20  
  1. answer
  1. Prévenir les modérateurs en cas d'abus
 
Bonjour
Fait ceci s.t.p.

Télécharger whocrashedSetup

Installer le logiciel et une fois installé cliquez sur Analyse http://nsm01.casimages.com/img​/2009/03/22//09032202013660773​353481.jpg
. Si tu as une anomalie mets-le rapport ici.

(Publicité)
bileg
Débutant confirmé (de 1 000 à 4 999 messages postés)
  1. Posté le 24/02/2014 à 15:56:37  
  1. answer
  1. Prévenir les modérateurs en cas d'abus
 
Bonjour
Voici le rapport, j'espère qu'il n' est pas trop gros :
System Information (local)
------------------------------​------------------------------​--------------------

computer name: PC-DE-GILBERT
windows version: Windows 8 , 6.2, build: 9200
windows dir: C:\WINDOWS
Hardware: EasyNote TR85 , Packard Bell , SJM50MV
CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU T6400 @ 2.00GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 3215814656 total
VM: 2147352576, free: 1945153536




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

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Sat 22/02/2014 20:48:10 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\022214-602​96-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0x142CD)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFFFFF83352AF7)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\ne​tio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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 Sat 22/02/2014 20:41:52 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\022214-661​25-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0x142CD)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFFFFF82504AF7)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\ne​tio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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 Sat 22/02/2014 19:53:48 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\022214-664​53-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0x142CD)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFFFFF82529AF7)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\ne​tio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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 Fri 21/02/2014 13:09:52 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\022114-452​50-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0x14E90)
Bugcheck code: 0xD1 (0x68, 0x2, 0x0, 0xFFFFFFFF81EFD813)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\ne​tio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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 05/02/2014 13:35:13 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\020514-390​31-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0x142CD)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFFFFF8211FAF7)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\ne​tio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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 05/02/2014 13:14:42 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\020514-464​21-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0x142CD)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFFFFF8BD7BAF7)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\ne​tio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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 Mon 20/01/2014 18:19:36 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\012014-353​43-01.dmp
This was probably caused by the following module: urlfilter.sys (UrlFilter+0x1A8E)
Bugcheck code: 0xD1 (0x4, 0x2, 0x0, 0xFFFFFFFF8BB529C4)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Program Files\IObit\IObit Malware Fighter\drivers\win7_x86\UrlFi​lter.sys
product: IObit Malware Fighter
company: IObit.com
description: URL Filter
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: urlfilter.sys (URL Filter, IObit.com).
Google query: IObit.com DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Sat 18/01/2014 07:50:06 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\011814-434​84-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x115839)
Bugcheck code: 0x9F (0x4, 0x12C, 0xFFFFFFFF896B7040, 0xFFFFFFFF8299BB10)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.e​xe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 Sat 11/01/2014 19:00:58 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\011114-535​46-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0x142CD)
Bugcheck code: 0xD1 (0x4, 0x2, 0x0, 0xFFFFFFFF8BB639C4)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\ne​tio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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 08/01/2014 12:53:42 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\010814-321​71-01.dmp
This was probably caused by the following module: urlfilter.sys (UrlFilter+0x1A8E)
Bugcheck code: 0xD1 (0x4, 0x2, 0x0, 0xFFFFFFFF827259C4)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Program Files\IObit\IObit Malware Fighter\drivers\win7_x86\UrlFi​lter.sys
product: IObit Malware Fighter
company: IObit.com
description: URL Filter
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: urlfilter.sys (URL Filter, IObit.com).
Google query: IObit.com 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:

urlfilter.sys (URL Filter, IObit.com)

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.

La Mayenne-son calme -sa verdu
Profil : Equipe sécurité
  1. homepage
bernard53
Membre impliqué (de 20 000 à 29 999 messages postés) Helpeur confirmé Fan Club de Clic-Clic
  1. Posté le 24/02/2014 à 19:56:46  
  1. answer
  1. Prévenir les modérateurs en cas d'abus
 
ok vérifies sur le site constructeur ou ici si des pilotes non pas besoin d'être mis à jour.
http://www.touslesdrivers.com/​?v_page=29

bileg
Débutant confirmé (de 1 000 à 4 999 messages postés)
  1. Posté le 24/02/2014 à 22:52:13  
  1. answer
  1. Prévenir les modérateurs en cas d'abus
 
Bonjour
j'ai réussi à installer 3 driver sur les 4 qui ne sont pas à jour.
pour le 4ème de chez intel qui concerne les ports SATA , il semble vouloir s'installer et au final il est toujours détecté comme manquant.
je ne sait pas comment faire d'autant plus que la date de cette mise à jour peut correspondre sensiblement au commencement de mes ennuis
Cordialement

(Publicité)
La Mayenne-son calme -sa verdu
Profil : Equipe sécurité
  1. homepage
bernard53
Membre impliqué (de 20 000 à 29 999 messages postés) Helpeur confirmé Fan Club de Clic-Clic
  1. Posté le 25/02/2014 à 12:49:05  
  1. answer
  1. Prévenir les modérateurs en cas d'abus
 
Attends pour les port SATA possible que l'installation des 3 autres va résoudre ton soucis.

bileg
Débutant confirmé (de 1 000 à 4 999 messages postés)
  1. Posté le 26/02/2014 à 12:57:57  
  1. answer
  1. Prévenir les modérateurs en cas d'abus
 
Bonjour
Pour le moment le problème n'est pas réapparu, je considère donc le problème comme étant réglé.
Merci

La Mayenne-son calme -sa verdu
Profil : Equipe sécurité
  1. homepage
bernard53
Membre impliqué (de 20 000 à 29 999 messages postés) Helpeur confirmé Fan Club de Clic-Clic
  1. Posté le 26/02/2014 à 13:04:22  
  1. answer
  1. Prévenir les modérateurs en cas d'abus
 
:super:
Bon après midi :)

(Publicité)
 Page :
1

Aller à :
 

Sujets relatifs
Ecran bleu atapi.sys ecran bleu windows7
pc lent et ecran bleu mon écran bouge tout seul
Plantage à l'arret du pc (irql_not_less_or_equal)  
Plus de sujets relatifs à : Ecran bleu avec :( ... Diver irql not less or equal (netiosys)

Les 5 sujets de discussion précédents Nombre de réponses Dernier message
Mails envoyés en plusieurs exemplaires 2
pc lent 13
sosssss je suis envahis par intrus 1
supprimer my search dial 1
mots soulignés deux fois en bleu 9