Ecran bleu windows doit redémarrer erreur

Bonsoir,

Il serait bien d'avoir le code de l'erreur stop.

Sinon encore mieux faîtes cette manip

Pourriez vous lancer ce logiciel gratuit Merci

Cliquez pour l'obtenir

vous nous donnerez le résultat en mettant le fichier créé dans Cjoint

http://www.cjoint.com/

vous faîtes parcourir pour le trouver et une fois trouvé
vous laissez tout par défaut et vous cliquez sur



vous copier/coller le lien créé dans votre réponse Merci.

---------------
Je n'utilise plus et je ne fais plus utiliser les logithèques ..........  
Je les dirige vers les sites éditeurs en priorité, quand c'est possible.

Hommage à Stephen HAWKING Le pire ennemi de la connaissance ce n'est pas l'ignorance, mais l'illusion de la connaissance

BONSOIR

http://www.cjoint.com/c/GKiaKh​Cjprr

Merci de votre aide, comme le logiciel est en anglais j'espère avoir saisi le bon fichier du rapport

Cordialement

Mme BOUABID

Bonjour, melaniewm

Merci de votre réponse

Le système redémarre après avoir collecté les erreurs

J'ai scanné mon système avec Whocrached, le rapport spécifiait une réparation du driver zone alarm et comme cela persistait ne sachant pas le réparer j'ai désinstallé zone alarm.

Je vous envoie une copie du rapport :
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 10/11/2017 19:46:20 your computer crashed
crash dump file: C:\Windows\Minidump\111017-242​50-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF801F110FF29)
Bugcheck code: 0xD1 (0x50, 0x2, 0x0, 0xFFFFF801F110FF29)
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 10/11/2017 19:46:20 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: vsdatant.sys (vsdatant+0x1742A)
Bugcheck code: 0xD1 (0x50, 0x2, 0x0, 0xFFFFF801F110FF29)
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. It is suggested you look for an update for the following driver: vsdatant.sys .
Google query: vsdatant.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Fri 10/11/2017 19:02:57 your computer crashed
crash dump file: C:\Windows\Minidump\111017-202​65-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0x12D79)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80022971D79, 0xFFFFD001FB34EDE0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Tue 07/11/2017 17:49:15 your computer crashed
crash dump file: C:\Windows\Minidump\110717-204​37-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0x12D79)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF801BF72ED79, 0xFFFFD00037904DE0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Tue 07/11/2017 02:59:29 your computer crashed
crash dump file: C:\Windows\Minidump\110717-213​12-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0x12D79)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF801DF98AD79, 0xFFFFD0003B168DE0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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.





------------------------------​------------------------------​--------------------
Conclusion
------------------------------​------------------------------​--------------------

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

vsdatant.sys

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.

Je crois qu'il y a un autre souci avec un autre driver, je n'ai pu poursuivre car en consultant les différents sites, malwaresbytes me les bloquait, de plus je ne m'y connait pas en informatique.

Merci de votre aide

Cordialement

Hathor

Bonjour,

Désolé de ma réponse tardive plus de 17 jours sans ADSL → donc pas de connexion internet.

Pouvez vous désinstaller pour essai Zone Alarme.

Puis vérifier si vous avez encore des BSODs.

---------------
Je n'utilise plus et je ne fais plus utiliser les logithèques ..........  
Je les dirige vers les sites éditeurs en priorité, quand c'est possible.

Hommage à Stephen HAWKING Le pire ennemi de la connaissance ce n'est pas l'ignorance, mais l'illusion de la connaissance