GPU crashes, Failed with 0x57 retrieving AppModel Runtime status for package Windows.

Anonymous
2020-06-21T22:42:15+00:00

Gidday all, I've been running into a issue with my GPU crashing and I have nailed it down to the error in event viewer " Failed with 0x57 retrieving AppModel Runtime status for package Windows. "

I have changed gpu drivers, completely uninstalled drivers, wiped my m.2 and reinstalled windows and nothing worked. Any ideas? Thank you

Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

91 answers

Sort by: Most helpful
  1. Anonymous
    2020-10-03T01:52:38+00:00

    It has to do with a bug between Windows 10 and Source games I'm pretty sure. Back when CS had problems with it, the fix was the same. Having dealt with the problem of Apex crashing for about a week on Alt Tabbing, and then remembering the CS go problem. My crashing from Alt-Tabbing is cured.

    Below are the steps on how to fix the crashing:

    1. go to Focus Assist Settings
    2. turn off all the automatic rules

    Fixes my errors and also my friends.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2020-07-25T15:48:28+00:00

    I have another way to cause the error to occur.

    While having the Radeon Adrenaline window open to Global Graphics > Display, I get a grey glitch bar which looks like screen tear if I click between display one and display two buttons on the Adrenaline client. Each time the glitch occurs, if I refresh my event viewer I see a new entry of "Failed with 0x57 retrieving AppModel Runtime status for package Windows" (ID 65) logged at about two or three seconds before the glitch grey-bar flashed. The bar flashes about a quater down from the top of both displays.

    I've also seen that after twenty or so entries of the aforementioned error, a Distributed COM warning appears in the event log and after that the Error ID 65 stops being logged for a while, but I can still cause the grey-bar to glitch flash by doing the same thing. I'm wondering if this issue might have to do with using multiple displays and/or switching between them. I've read that some users don't get this problem, and monitor count is something which varies from PC to PC, along with whether DP or HDMI is used (I use both monitors via HDMI). I'm releived that a range of brands and models of hardware suffer this issue, it means that I probably won't need to replace any one thing or another.

    Also, I have reduced the frequency of the crashes by changing a bunch of Services settings from maual to automatic, to try and make sure whichever component couldn't access/be accessed was started at the time it was needed. It's better, but I still get occasional crashes.

    Hopefully this is helpful in some way.

    Thanks to everyone so far. All the officials have had to say collectively is "It's not a DCOM issue, ignore the DCOM warnings." It seems like this one's up to us to figure out.

    System specs:

    Windows 10 version 2004

    Ryzen 5 2600

    Sapphire 5700xt Nitro+

    MSI B450M-A Pro

    16GB G.Skill Fortis 2400

    OS SSD is a WD green 240GB

    Monitors are BenQ RL2455 (main), Asus VE248. Both through HDMI at 1920x1080 60hz.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2020-07-08T05:48:10+00:00

    Have the same problem, it crashes my games Rainbow Six and CoD. Also have hiccups sometimes even if I'm just on chrome.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2020-07-03T22:10:50+00:00

    I get the same exact issue with an RTX 2070 Super and Intel i7-8086K CPU, also on Windows 10 Pro 2004 19041.330.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2020-07-03T00:38:24+00:00

    Windows 10, 2004, 

    I can reproduce this issue over and over.

    This is how I reproduce it :

    Install Badlion (Minecraft launcher)

    Open Badlion, leave on default settings (Minecraft 1.8.9, optifine = enabled) Click Launch.

    Start a single player world.  Sometimes, loading the world will cause the 0x57 error to appear.  

    How to reproduce everytime?  Once the single player world has loaded, open "Options", "Video settings",

    Toggle "Graphics" from "Fancy" to "Fast" and then back to "Fancy".  Check event logs.

    I have tested two different graphics cards, a Nvidia 2080ti and a Nvidia gt710, not overclocked and the error appears regardless of which graphics card is installed.  I also tested a few different drivers, including windows 10 stock 432.00 driver and the latest 451.48 driver, after using Display Driver Uninstaller, to no avail.

    Watch this video (I apologize about the quality being 720p) - https://streamable.com/zu47a3

    I have ran the usual sfc /scannow, Dism and chkdsk, no errors found.

    Pc specs :

    Ryzen 3700x

    Motherboard : B450 Mortar max

    Ram : Crucial Ballistix sport, passes memtest86 overnight

    Hard drive : Crucial M4

    Operating System : Windows 10, build 19041.329

    Graphics : Tested two cards, 2080ti and gt710 (error appears regardless of card installed)

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments