Перейти к содержимому


Фото
- - - - -

Windows Subsystem for Linux : écran bleu à chaque lancement de Ubuntu...


  • Please log in to reply
14 ответов в этой теме

#1 Manuel

Manuel

    Newbie

  • Posters
  • 9 Сообщений:

Отправлено 02 Май 2018 - 21:14

Bonsoir,

 

J'utilise Ubuntu sur mon Windows (Windows Subsystem for Linux). Jusqu'à la mise à jour, tout fonctionnait.

 

J'avais profité du week-end pour faire la grosse mise à jour de mon Windows 10 (version de Windows 10 famille suite à cette mise à jour : 1803), suite a cela il y a eu une mise a jour de Dr Web.

 

Ce matin, en voulant démarrer Ubuntu ( Windows Subsystem for Linux ), j'ai obtenu un écran bleu.

J'ai vérifié mes mis à jours logiciels matériel, "réparation Microsoft store", rien n'y fait.

 

J'ai mis à zéro mon système d'exploitation (restauration de systèmes), réinstallé Dr Web, et Ubuntu via Microsoft Store (dans cet ordre) ; de nouveau écran bleu.

 

J'ai consulté les dump du système (voir ci-après). Ils m'indiquent que c'est l'antivirus qui serait en défaut. Je désinstalle Dr Web ainsi qu'Ubuntu. Je redémarre le système réinstalle Ubuntu. cela fonctionne.

 

À la réinstallation de Dr Web : de nouveau écran bleu.

 

Pourriez vous regarder ceci et m'apporter une solution s'il vous plait? Merci d'avance.

 

Cordialement, Manuel.

 

System Information (local)


Computer name:
Windows version: Windows 10 , 10.0, build: 17134
Windows dir: C:\WINDOWS
Hardware: SATELLITE L50-B, TOSHIBA, Type2 - Board Vendor Name1, Type2 - Board Product Name1
CPU: GenuineIntel Intel® Core™ i7-4500U CPU @ 1.80GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8506195968 bytes total





Crash Dump Analysis


Crash dumps are enabled on your computer.

Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump

On Wed 02/05/2018 19:49:22 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\050218-7750-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x197650)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80287C655B0, 0xFFFFF60F63B46D70, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 02/05/2018 19:49:22 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: dwprot.sys (dwprot+0x50EE1)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80287C655B0, 0xFFFFF60F63B46D70, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\dwprot.sys
product: Dr.Web Anti-Virus
company: Doctor Web, Ltd.
description: Dr.Web Protection for Windows
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.
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: dwprot.sys (Dr.Web Protection for Windows, Doctor Web, Ltd.).
Google query: dwprot.sys Doctor Web, Ltd. SYSTEM_SERVICE_EXCEPTION



On Wed 02/05/2018 19:03:05 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\050218-8031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x197650)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8014C8F75B0, 0xFFFFB4074AC66D70, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 02/05/2018 16:06:10 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\050218-8046-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x197650)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF803BF8F05B0, 0xFFFF828AAFDC4D70, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 02/05/2018 15:06:52 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\050218-7468-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x197650)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF803AF46C5B0, 0xFFFFEE81443C4D70, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 02/05/2018 14:54:08 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\050218-16390-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x197650)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800544DF5B0, 0xFFFFEA8A0E583D70, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.






Conclusion

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

dwprot.sys (Dr.Web Protection for Windows, Doctor Web, Ltd.)

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.
 



#2 Manuel

Manuel

    Newbie

  • Posters
  • 9 Сообщений:

Отправлено 03 Май 2018 - 13:03

Bonjour,

dernières précision par rapport a ce que j'ai recherché ce matin :

  • J'ai forcé les mise à jours au cas ou cela aurait débloqué quelques choses, rien n'y fait.
  • Toutes recherche sur Googles, au près de Microsoft, etc, ne m'ont mené nulle part.
  • J'ai désinstallé Dr Web : Windows Subsystem for Linux marche à nouveau. (par contre travailler sans antivirus :unsure: ).

 

Éventuellement, s'il y a des manipulations complémentaire à faire pour compléter vos recherches, n'hésitez pas à me le demander.

 

Cordialement, Manuel.
 



#3 Konstantin Yudin

Konstantin Yudin

    Смотрящий

  • Dr.Web Staff
  • 17 602 Сообщений:

Отправлено 03 Май 2018 - 14:29

Fix released very soon
With best regards, Konstantin Yudin
Doctor Web, Ltd.

#4 Konstantin Yudin

Konstantin Yudin

    Смотрящий

  • Dr.Web Staff
  • 17 602 Сообщений:

Отправлено 07 Май 2018 - 17:29

Fix released, just run auto update
With best regards, Konstantin Yudin
Doctor Web, Ltd.

#5 shansing

shansing

    Newbie

  • Members
  • 2 Сообщений:

Отправлено 08 Май 2018 - 09:02

Fix released, just run auto update

 

Thank you for the fix.

I am another WSL user with Dr.Web on Windows 10 1803. I was troubled by the issue and later found this post. After this update, I can open WSL successfully without bluescreen.

However, network in WSL seems not working. For example, when I execute "ping 8.8.8.8", I get the error "ping: sendmsg: Permission denied", which made me convinced that it is not a normal issue. What's more, when I turn off Dr.Web's Firewall, network in WSL runs good. Hope you can attach attention to the issue, for I really like Dr.Web.


Сообщение было изменено shansing: 08 Май 2018 - 09:03


#6 Konstantin Yudin

Konstantin Yudin

    Смотрящий

  • Dr.Web Staff
  • 17 602 Сообщений:

Отправлено 08 Май 2018 - 11:29

In Windows 10 RS4 Microsoft changed policy about WSL processes, part of them can't be catch by antivirus anymore, you need create manualy rule in our firewall for this files.
With best regards, Konstantin Yudin
Doctor Web, Ltd.

#7 Konstantin Yudin

Konstantin Yudin

    Смотрящий

  • Dr.Web Staff
  • 17 602 Сообщений:

Отправлено 08 Май 2018 - 12:22

we will create WA in our firewall for this changes in new upcoming update 11.5
With best regards, Konstantin Yudin
Doctor Web, Ltd.

#8 Manuel

Manuel

    Newbie

  • Posters
  • 9 Сообщений:

Отправлено 08 Май 2018 - 12:24

Bonjour,

J'ai fais la mise à jour de Dr Web, WSL fonctionne à nouveau.

Merci.



#9 Manuel

Manuel

    Newbie

  • Posters
  • 9 Сообщений:

Отправлено 08 Май 2018 - 14:15

J'avoue que j'ai parlé un peu trop vite je suis aussi embêté par le firewall.

 

J'ai essayé d'ouvrir le firewall à WSL, en incluant l'application ubuntu dans la liste : sans succès.

 

Autre constatation ma mère qui joue à un jeu provenant MS store sur un autre ordinateur protégé par Dr Web, a les mêmes problèmes. J'ai inclue son application dans le firewall : sans succès. ( "MS Solitaire Collection" dont pas mal de choses se passent sur internet et les challenges que ma mère affectionne...)

 

Il se peut que ce soit deux problèmes différents, mais je constate que les deux produits en question proviennent du MS store.

 

s'il y a un autre programme du système gérant le réseau à mettre dans la liste, je ne vois pas le quel...


Сообщение было изменено Manuel: 08 Май 2018 - 14:18


#10 shansing

shansing

    Newbie

  • Members
  • 2 Сообщений:

Отправлено 08 Май 2018 - 15:19

Yeah. Just like what Manuel says, it's useless to add WSL files to the exclusion list. Even I am using the all-pass mode (allow unknown connection), can't I let WSL connecting to network properly. Turning the Firewall off seems the only workaround by now.

 

By the way, what does WA mean, please?



#11 IlyaS

IlyaS

    Massive Poster

  • Posters
  • 2 800 Сообщений:

Отправлено 08 Май 2018 - 23:22

WA is a workaround.

#12 Manuel

Manuel

    Newbie

  • Posters
  • 9 Сообщений:

Отправлено 09 Май 2018 - 12:11

Bonjour,

J'ajoute un petit point : quand je ping le 127.0.0.1 sur la console WSL, j'ai comme message : " ping: sendmsg: Permission denied " et " ping: recvmsg: Permission denied " donc WSL n'atteint pas du tout les protocoles réseaux quand le firewall est en fonctionnement.


Сообщение было изменено Manuel: 09 Май 2018 - 12:13


#13 Konstantin Yudin

Konstantin Yudin

    Смотрящий

  • Dr.Web Staff
  • 17 602 Сообщений:

Отправлено 09 Май 2018 - 14:11

Thanks microsoft for these stupid changes in RS4, they make regression in RS4 and secure hole (like bashware) again. Yesterday we released WA in our firewall in the beta version. for some WSL processes in RS4 no legal way anaymore get process path. when microsoft created WSL, they forgot about antivirus, only year later they added api for control WSL.
With best regards, Konstantin Yudin
Doctor Web, Ltd.

#14 Konstantin Yudin

Konstantin Yudin

    Смотрящий

  • Dr.Web Staff
  • 17 602 Сообщений:

Отправлено 31 Май 2018 - 19:26

all fixes released today in 11.5
With best regards, Konstantin Yudin
Doctor Web, Ltd.

#15 Manuel

Manuel

    Newbie

  • Posters
  • 9 Сообщений:

Отправлено 01 Июнь 2018 - 01:35

Merci pour cette mise à jour, tout à l'air de fonctionner 




Читают тему: 0

0 пользователей, 0 гостей, 0 скрытых