Microsoft Edge Content Process crashes in 1803 with Kaspersky AV installed

Confirmed Issue #17325951 • Assigned to Sermet I.


Brok3n C.
May 1, 2018
This issue is public.
Found in
  • Microsoft Edge
Reported by 12 people

Sign in to watch or report this issue.

Steps to reproduce


This is happening since the April Update. It happened both in 17133 (after a week or so of absolutely no crashing…) and also now on 17134. It’s not happening while I use Edge, it’s something in the background, I only see it in Reliability/Event Viewer. Sadly I have no idea how to reproduce it as it seems completely random, although there are 2-5 crashes/day.

Faulting Application Path: C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\MicrosoftEdgeCP.exe

Problem signature
Problem Event Name: MoOsMitigation
Package Full Name: Microsoft.MicrosoftEdge_42.17134.1.0_neutral__8wekyb3d8bbwe
Application Name: praid:ContentProcess
Application Version: 11.0.17134.1
Application Timestamp: 5acd8993
Fault Module Name: StackHash_6017
Fault Module Version:
Fault Module Timestamp: 00000005
Exception Offset: PCH_FE_FROM_win32u+0x00000000000021A4
Exception Code: c000001c
Exception Data: 000000000000008c
OS Version: 10.0.17134.
Locale ID: 1033
Additional Information 1: 6017
Additional Information 2: 60170fe41fdd82096ad7abb5ea7d5968
Additional Information 3: a912
Additional Information 4: a912c7e38ea781d5d2e6471cff90e402

Extra information about the problem
Bucket ID: dd3a1b7d06004a80499eed754b65251d (1846173985300358429)[/code]


Comments and activity

  • I have this too, i update and then wich time i start Windows it apears in reliability/event viewer… upfully one fix will stop it… whatever this is.

    the only thing that apears to be wrong is when ia chenge from auto to 1080p in youtube stops the vídeo and then i have to refresh the page and problema solve de vídeo continues in 1080p or the defenition i had chose

    and sorry my poor english in advance

  • Goof to hear I’m not the only one. This happens multiple times/day, it crashed 4 times already today.

  • Same problem, happens with the exact same signature. It happens to me each time I start the computer.

    To reproduce, simply open Edge and type in a URL then enter.
    It will start loading then the tab will revert to the “new tab” header (that’s when the process crashes), then I need to open another tab and close this one to continue browsing.

  • I have the same problem. When I start the PC/Windows und then l look in the reliability viewer, I see that Edge crashed (look attachement Capture2).

  • It does appear on reboot. I can reliably make the event happen by rebooting and opening Edge. I was able to send a feedback with bug reproduction on the Feedback Hub app.

    Meanwhile… did anyone take a look at this? Do you require additional data? If that’s so, please let us know so we can send what’s needed.

    Thank you.

  • Same problem as describe in others comments:

    Nom d’événement du problème : MoOsMitigation
    Nom complet du package: Microsoft.MicrosoftEdge_42.17134.1.0_neutral__8wekyb3d8bbwe
    Nom de l’application: praid:ContentProcess
    Version de l’application: 11.0.17134.48
    Horodatage de l’application: 5ae3f17b
    Nom du module par défaut: StackHash_6017
    Version du module par défaut:

  • J’ai refais une installation complète de Windows 10 april suite à un gros bug lors de la mise à jour (une demande répétée qu’un de mes disques étaient pleins et que j’ai vidé sans trop me poser de questions, alors que c’était une partition système qui était d’un seul coup redevenu visible et accessible).
    Depuis cette installation complète, avec formatage complet du ssd, j’ai constamment cette erreur MoOsMitigation d’Edge Content process. Pour le moment, cela ne me gêne pas, car au final tout fonctionne bien sans crash visible. Mais j’ai constaté que cela se répète à chaque fermeture d’Edge, donc 10-15 fois par jour. Cela m’inquiète pour la stabilité du système.

  • Microsoft Edge Team

    Changed Assigned To to “James M.”

  • Hello,

    Thank you for providing this information about the issue. If you have submitted a Feedback Hub report, please provide us with that link or case ID. If not, please download and install debug diag from 

    1. Open DebugDiag 2 Collection. Allow permission if prompted. 
    2. If the Select Target Type window does not automatically open, click Add Rule… 
    3. Select ‘Crash’ and click Next. 
    4. Select ‘A specific process’ and click Next. 
    5. Click the Process Name heading to sort alphabetically and select any one of the MicrosoftEdgeCP.exe processes and click Next. 
    6. In the Advanced Configuration, please just click Next. 
    7. Lastly, in the Rule Output Location, please choose and take note of the location where the dump file will be written; click Next then click Finish. 
    8. Reproduce the crash in Edge, and open the folder location from the step above. Locate the file ending in .dmp; please compress/zip the .dmp file(s) and attach it to this case.

    Best Wishes,
    The MS Edge Team

  • Hello and thanks for taking a look at this.

    This is the feedback that should have attached a replication of the crash:

    I am not 100% sure it’s this one so I made a new one just to be sure:

  • About the DebugDiag2 method:
    This is not a “full” crash, so it doesn’t produce any dumps. The application does not exit. Instead, when I start Edge it would have a delay and not load any page while the event happens. DebugDiag will detect some exceptions in its logs though such as:


    | Count | Exception  |
    | 819   | 0X406D1388 |
    | 30    | 0XE06D7363 |
    | 2     | 0X40080201 |
    | 1     | 0X40080202 |

    **** Some exception details were omitted due to the following reasons
    The maximum number of stacks (MAX_NATIVE_EXCEPTION_STACKS_PER_EXCEPTION_TYPE = 100) for this native exception type have been collected: ‘0X406D1388’
    Native exception rate is more than MAX_NATIVE_EXCEPTION_STACKS_PER_SECOND (30 exceptions / sec)

    Debugging Overhead Cost:
    Total Elapsed Ticks = 51500 (100%)
    Total Ticks Spent in Debugger Engine = 3077 (6%)
    Total Ticks Spent in Crash Rule Script = 13015 (25%)

  • Crash of MirosoftEdgeCP

  • Kiedy problem zostanie wreszcie rozwiązany ???

  • I have a question for the other people reporting this issue:
    Are you using Kaspersky? Uninstalling it seems to have fixed it for me, at least I can no longer produce these events on starting Edge after a reboot.
    If uninstalling Kaspersky (or other 3rd party AV) fixes this for you, please report this to your AV vendor.

  • Thank you Brok3n C. for the Information. Yes of course, my internet security is Kaspersky. Have you reported the bug to Kaspersky?

  • Yes reported to Kaspersky. They require traces:
    If you wanna help them solve this faster, help them with it please.

  • ok it makes sense, i also use kaspersky … im tired of the problems with kaspersky and W10… pearhaps last year form me and welcome bitdefender if this is truth

  • @ruben:
    Windows Defender is very capable in RS4, you can use that until Kaspersky fixes it. At the same time, it’s worth noticing that this is a pretty low priority (yet annoying) bug that doesn’t have any negative impact outside spamming Event Viewer entries and making your Reliability History look really, really bad.
    Used Bitdefender too for a while but I found that it took way too many automated actions for my liking, I personally prefer the verbose pop-up spam from Kaspersky, hence always turning off its automatic actions.

  • @Brok3n C: thanks for your opinion and I always liked kaspersky because it is simple to use and at least I do not remember having a virus but in this case since I have w10 I already had to reinstall too many times … it is probably microsoft problem but they should be prepared for this and if there is anything else wrong I do not know sincerely

  • Odinstalowanie Kasperskiego faktycznie pomogło, ale czy jest to właściwy kierunek ? W poprzednich wersjach Win 10 ten problem nie istniał.

  • Je pense que Kaspersky et Microsoft peuvent quand même travailler ensemble pour régler ce bug, qui même s’il n’est pas bloquant, est extrêmement répétitif. J’espère ne pas devoir attendre des mois entiers pour voir ce bug être réglé.

  • If you want this fixed fast so you don’t need to wait months, again, send traces to Kaspersky:
    RS4 has changed things over RS3, Kaspersky will have to adapt. They’ll solve the issue, no biggie, but they will need help - i.e. traces.

  • Microsoft Edge Team

    Changed Assigned To to “wptsixtri”

  • From Kaspersky:

    "Dear customer,

    Developers have raised a new ticket with Microsoft. We are waiting for ticket resolution from Microsoft side.

    We will keep you update .

    Thank you for understanding !"

    There’s hope :)

  • Thank you

  • Microsoft Edge Team

    Changed Title from “Microsoft Edge Content Process crashes” to “Microsoft Edge Content Process crashes in 1803 with Kaspersky AV installed”

    Changed Assigned To from “wptsixtri” to “Sermet I.”

    Changed Status to “Confirmed”

  • I don’t think it is related to Kaspersky. I use Windows Defender and have the same problem.

  • @bogdan d.: it must be something different. I ditched Kaspersky for the time until they fix this and using Defender for weeks, not one error. Meanwhile on a virtual machine I still have KIS and the last Windows 10 x64 (1803) and Edge still crashes, maybe not on the first launch, but on the second one for sure.

    So, sadly, the bug is still present, after all this time.

  • Any news? The problem still persist.

  • Ja, irgendwie stellt sich schon die Frage nach Neuigkeiten,
    denn das Problem besteht nach wie vor ebenfalls nach meiner Beobachtung.
    Vielleicht gibt es ja im zeitlichen Zusammenhang mit dem Erscheinen von Windows 10, Version 1809 eine Lösung zum Problem?

    Hatte vorsorglich auch zur Thematik bei Kaspersky Support angefragt:
    Feedback vom 27.07.2018 dazu:
    Angesichts des Edge - Problems mit der Zuverlässigkeit sind die Entwickler noch in Kontakt mit Microsoft. Hier gibt es leider noch nichts Neues. …“

    Neben diesem Link zum Thema beispielhaft mal noch zwei andere:
    Siehe u. a. dort Beitrag vom 27.06.2018.

  • Fehler scheint behoben zu sein.
    Zumindest nach letztem Updates unter Windows 10 Version 1803
    ( vgl. )
    und KIS Version ©
    ( )
    sowie inzwischen unter Windows 10 Version 1809
    wurde meinerseits o. g. Fehler im Zuverlässigkeitsverlauf bisher nicht mehr gesichtet.

  • Oui, effectivement, il semble qu’enfin le bug soit bien fixé et résolu avec la nouvelle version de Kaspersky et de Windows 1809. J’ai remis depuis deux jours Kaspersky Total Sécurity et toujours aucune erreur signalé.
    Bravo les équipes ^^ (même si cela a fallu attendre de très nombreux mois avant d’avoir le bug fixé).

  • I think I can confirm that the bug is fixed in 1809/RS5 with the latest KIS ©. I tried to force the error by closing and reopening Edge a few times and it’s not happening like it used to.
    Took a whole Feature Update cycle to fix though. I’m not sure how this is acceptable, but considering the low gravity of the issue, oh well.

  • I’m just writing to say that i have uninstalled KIS yet again. I used this app since there was no Internet Security suite and the firewall was separate, and I never wanted another.
    But boy I am pissed at how many issues it has with Windows 10.

    In short, after reinstalling KIS on RS5/1809, 2 things happened:

    • cortana.signals.dll would crash each reboot. Stealthily, in the background, exactly how Edge used to
    • the whole tab of System Protection in System Properties, the one that is used for System Restore, would be unable to populate the list with drives and give some error

    I had to reinstall the OS to fix that, no amount of policies and services being restarted would do.

    I don’t think Kaspersky are 100% responsible of this. I think Windows 10 is updating way too often and companies just can’t keep up properly, also the OS is simply becoming very complex and conflicts can happen. KIS already has limitations depending on what you choose to activate in the OS, like Core Isolation>Memory Integrity for example.


    I’m done with KIS. I’m done with other AVs. I’ll just stick to Defender. I just wish they made it easier to change/create firewall rules.

  • Windows Defender obtient en effet d’excellentes notes dans les tests des anti-virus, et est aussi bon que Kaspersky et Bitdefender et autres. Je suis de ton avis, Brok3n C. J’attend simplement que mon abonnement avec KIS arrive à expiration (car après tout j’ai payé pour toute l’année) et je pense n’utiliser que Defender par la suite. Cela soulagera les processus de mon pc ^^

  • Even to this day, in 1809 now, this is still happening. I just can’t believe it. Reported in May, now we’re in December, and hell, I wanted to try KIS again and return to it, but no:

    Each damn reboot+Edge launch. Not gonna try to mince words: this is shameful.

    [code]Faulting Application Path: C:\Windows\System32\MicrosoftEdgeSH.exe

    Problem signature
    Problem Event Name: MoOsMitigation
    Package Full Name: Microsoft.MicrosoftEdge_44.17763.1.0_neutral__8wekyb3d8bbwe
    Application Name: praid:MicrosoftEdge
    Application Version: 11.0.17763.1
    Application Timestamp: 1244354f
    Fault Module Name: StackHash_6017
    Fault Module Version:
    Fault Module Timestamp: 00000005
    Exception Offset: PCH_E9_FROM_win32u+0x00000000000021C4
    Exception Code: c000001c
    Exception Data: 000000000000008c
    OS Version: 10.0.17763.
    Locale ID: 1033
    Additional Information 1: 6017
    Additional Information 2: 60170fe41fdd82096ad7abb5ea7d5968
    Additional Information 3: 6061
    Additional Information 4: 6061d22450747f4716bcbd2fdc8f8e0f

    Extra information about the problem
    Bucket ID: 42f32ca12bd734362423849386f68d5a (1451149274102795610)

  • Con Win10 1809 y KIS 19 tambien aparece el error. Antes de la actualización a 1809 no aparecía.
    He observado que no en todos los WIN10 que tengo. Sólo se produce el error en el Win10 Home. Esta actualización la realicé con Windows10upgrade y no con windows10 update como en los otros en los que no se produce el error.
    He visto que aunque se procuce el error no afecta al sistema por lo que creo que no lo solucionan con la prontitud que deseamos. Opino lo mismo que Brok3n C y que un error tan antiguo tiene que tener una solución ya y no dejarla en el trastero.

    Traducido por google:
    With Win10 1809 and KIS 19 the error also appears. Before the update to 1809 it did not appear.
    I have noticed that not in all the WIN10 that I have. Only the error occurs in the Win10 Home. This update was made with Windows10upgrade and not with windows10 update as in the others where the error does not occur.
    I have seen that although the error is tried does not affect the system so I think that they do not solve it as promptly as we want. I think the same as Brok3n C and that an error so old has to have a solution already and not leave it in the storeroom.

  • Considering that Microsoft pretty much announced they will abandon the Edge engine and make it run on Chromium, which is a bad choice in my opinion, as that leaves just Firefox with an alternative engine, and that’s really messed up, I can now see why this is not getting fixed.
    I assume Edge as it is now in 1809/RS5 is almost abandonware, and will only receive security fixes until the new Edge with Chromium will replace it.
    Oh well. At least I know for a fact that Kaspersky and Chromium play nice. Maybe I’ll finally return to KIS once again.

  • Mein Post vom 03.10.2018 ist überholt.
    Soweit meine Beobachtungen reichen,
    entweder mit dem Update Windows 10 Version 1809 vom 09.10.2018 (oder vom 13.11.2018) war der Fehler wieder vorhanden; ebenso zeigt sich der Fehler ganz aktuell nach wie vor mit der neuesten Version von KIS.

  • Inzwischen wurde die 2020er Version von KIS pro getestet.
    Bisher jedenfalls alles in Ordnung!
    Besagter Fehler i.Z.m. KIS pro und ebenso etwaige andere konnten bisher nicht bei aktuellem Stand von Win 10 mit Version 1903 beobachtet werden.

  • 16th July 2019 Kaspersky “subject matter expert” advised, is KSEC 2020, which was commercially released 10th July 2019.
    Even tho the link is titled KIS, the contents of the list are for KSEC 2020.

    They further advised, atm, only KSEC 2020 Commercial release (CR) is available (all regions).

    Anyone wishing to use KIS/KAV/KTS 2020 - Technical release (TR), may make a direct request to Kaspersky Technical Support.

    Furthermore - (they said) the way to know when KIS/KAV/KTS 2020 (CR) is available is, go to:, IF, the product you are interested in, has 2020 in the display window, that is 2020 CR for that product.

  • eeech, “f😱rmatting” in previous post - cannot find an edit button ? I guess 👓 will not be needed by readers😉

You need to sign in to your Microsoft account to add a comment.

Sign in