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: Newest
  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-10-01T12:10:29+00:00

    Same, also AC Odyssey, Origins, Warzone, and a few others. It has crashed just in the system browsing files a couple times as well.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2020-09-30T12:58:35+00:00

    It is a tragedy how we are treated - as a customers - by this companies...

    Basically - for months already -  Microsoft Is Aware about that ISSUE and also Nvidia Is Aware about that ISSUE - and They don't give a (cookie) about. 

    Have problem? BUY a NEW HARDWARE (like 2080s or 3080...). And pray for less issues with. Till new update...

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2020-09-30T09:13:32+00:00

    This problem happend to me each time nvidia drivers gets updated since the feb 2020.

    The only solution I found was to update the drivers, before restarting enter the device manager and disable this: https://imgur.com/lAJH4UM

    They are all the new devices that are added/re-enabled by the driver update.

    If I forget to do that the system is unstable and even just using the browser can trigger the driver crash and a system self-reboot.

    I have not found a permanent solution to this.

    In addition to this issue there is a connected issue that is very rare, the screen seems to constantly change display size every 200ms or so but it get solved by rebooting and never leads to a BSOD or crash, event the log viewer is clean.

    This is the solution, thanks a lot man. 

    The issue is caused by NVIDIA audio codecs which uses Virtual Audio Cable software. Same goes for AMD.

    As the software was made by Eugene Muzychenko in 1998, but the stable release was in july 17,2020. (go google)

    Both AMD and NVIDIA use the same codecs as Virtual Audio Device (WDM). Anything connected to this device pipeline and along with the device needs to be disabled. Cause Microsoft updated their Codecs, whereas NVIDIA and AMD didn't update their codecs. Thus causing an stability issue. 

    Nvidia HD Audio driver Codec last update date was : 14 March, 2019

    AMD : I don't know. 

    As long as NVIDIA don't update their codecs, this issue will persist. 

    P.S: I suggested to update windows to 20H2 through beta ring in my previous post, don't do that. As it will create even more issues.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2020-09-29T21:02:56+00:00

    Getting this issue too. It has been extremely annoying. I've tried reinstalling windows to no avail, reinstalling graphics drivers, the whole shebang. Nothing seems to resolve this. BTW, I'm still running my 1080Ti and since a few driver updates before the 30xx Launch, this has been happening. It's really starting to peeve me. And I can't find a driver that works anymore, nor can I resolve this issue in windows. :(

    Was this answer helpful?

    0 comments No comments