Skip to content

Instantly share code, notes, and snippets.

@wk-j
Last active October 18, 2015 08:54
Show Gist options
  • Save wk-j/b6581fecac9d93bb145b to your computer and use it in GitHub Desktop.
Save wk-j/b6581fecac9d93bb145b to your computer and use it in GitHub Desktop.
windows-critical-error

http://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_perf/a-critical-error-has-occurred-in-the-shell/ffa743a6-5c16-4ff4-b7a4-ea287bf4456b

I am pretty sure I found the culprit here. If you go to the control panel, scheduled tasks you will find two tasks in the Microsoft tree under MemoryDiagnostic

Both have a condition set if idle for 10 minutes and are triggered off several different events. Once I disabled both of these tasks I have seen no more of this error.

Now, the evidence is if I triggered these tasks manually I got the error immediately so I am 95% sure this is the culprit. Question is, what are these MemoryDiagnostic tasks for?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment