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

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

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.

If you don't have something helpful to say, please go get the attention you so desperately crave elsewhere.

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.

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.

I've been reading anything even slightly related and can offer at least that disabling the services for AMD user experience program and AMD external event utility have little to no impact on general use, and can fix data spikes which ruin gameplay at times. I'll get back with more info after running with those disabled over the next few days.

One other semi-fix I want to reiterate is making sure your bios/cmos setting for your power supply are set to typical or higher-demand load when idle. this helps prevent the system spitting the dummy if a power spike for the GPU comes through that it didn't anticipate. It reduiced the frequency of my green screen crashes by more than half.