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

I have the same issue. I reinstalled windows, twice, swapped GPUs, swapped RAM, swapped PSU.. this is 100% an issue with Windows 10 latest update. I believe it started with 19041.329. Super annoying, system hangs sometimes and the only way to fix is a hard restart.

unfortunately as usual the users have grabbed onto something like a dog bone and got it completely BACKWARDS.

your systems are crashing due to driver or hardware instability, the log is thrown because something using the gpu has lost the device context.

The event logged is not causing the gpu to crash.

Unfortunately as usual someone who understands the problem has jumped onto the train and treated us like were idiots, then only offered the information 'that's not the problem.'

Sure there are poeple who don't look deeper, but most people here have tried a lot of troubleshooting and are at their wit's end trying to solve it, so get off our backs and instead go and direct your ire at people who get upset and demand a solution without even trying to diagnose the issue. Well actually, most of those sorts of people are on Macs anyway so the community here would be very accepting of any actual help. This issue has occured across all brands of hardware, and pertinently it happens to various models of both Nvidia and AMD GPUs. If we understood how this problem is obviously not a Windows error we wouldn't need the help. For example, explaining how you determined that the log is thrown and what it means when a GPU loses device context, that would be very helpful. Just like in legal vernacular, general wordage often has a highly abstracted use in different environments, and 'device context' might not be a simple concept to understand to someone like me with very little programming knowledge.

So not just for you, but for every 'expert' who has posted a condecending reply, stop talking to us like we're idiots. We came here to problem solve, because we're willing to investigate and search for solutions to a problem. I wouldn't expect you to know about how a gearbox in a car works because you're not a mechanic, I wouldn't expect you to know about the War of the Roses because you're not a historian, I wouldn't expect you to know about the rule changes fifteen-odd years ago in Olympic Taekwondo allowing the referee to prompt action from the fighters because that's not where your knowledge is, so I find it completely inappropriate for you lot to keep talking to us like we're dull and dimensionless and wasting your time. Nobody so far has been willing to go into detail about WHY this error is even here, or why it has nothing to do with the crashes we're having. From our POV, all we see is a littany of Distributed COM errors or something similar before every system crash. We want to understand what the system is doing prior to the crash, so we can at least change our behaviour or usage habits to prevent it.

What we really need to be taught, is how to determine the cause of the crash without relying on software to find out the cause. We're willing to comb through the System Management options, I've even started flipping switches when I have no idea what they do! Experimentation is how we learn things, and offering a little bit of direction could save us weeks of trial and error.

Now this thread is getting longer I'm not keeping up with it as well as I could do, so please let me know if someone has indeed answered the query fully. Otherwise, please offer help, and don't generalise us a cluster of dopey numbskulls. We're people who want to be a part of the solution, not just consumers crowding the help desk.

All that said, I could have handled your comment a lot better myself and I apologise for my abrasive demeanour. I just felt it was time to bite back after countless advisors have replied without tact and made little effort to to explain the relationships - or lack thereof - between these errors and graqphics related crahses. Thank you for being at least one person among millions who know more than we do, who offers information of any sort.

This may or may not be related, but I'm mentioning it as It as been around since those errors have appeared in event viewer.

Whilst web browsing the web if I leave the mouse untouched for a few seconds, then scroll, theres a huge stutter.  It doesn't always happen, but most of the time it does.  This stutter is very apparent in Firefox, which uses Smooth scrolling, as scrolling webpages is silky smooth in general and any signs of stuttering will be obvious. 

I opened Msi Afterburner to monitor the gpu usage, and my GPU spikes to low level 3d clocks when i leave the mouse untouched for a few seconds whilst browsing the web, then scroll, that spike correlates to the stuttering.   I tested two different graphics cards, a 2080ti and a GT710, it happens regardless of which card is installed and I have installed many graphic card drivers, after using DDU.  Its not Windows power plan causing the stutter as I have switched between all of them.  The Cpu and Ram have both passed multiple stress tests and show no signs of instability.  I am not overclocking the cpu or gpu. 

I have tested 144hz, 120hz and 60hz using two different graphic cards, testing using both displayport and hdmi ports, to no avail.

I found that Client Server Runtime Process is spiking my Gpu usage when it happens.

I always make sure before im troubleshooting stuttering that no 3rd party apps are running in the background, cpu and gpu and harddrive usage is very low.

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.

I don't get this error anymore since i have updated my windows 10 to version 19042.423 (20H2) through windows insider beta channel ring