Forum Discussion
Device Health question
MicrosoftToday we provide a summary of each BSOD including stop code, failure ID, etc. to accelerate diagnostic and support efforts. I love what you are proposing as a next step. I would love to get enterprises access to their own dump files as well for follow up analytics and to further accelerate support experiences (e.g., instead of doing a bunch of work to generate *another* dump to work with Microsoft or 3rd party support, you could use the original dump from the original incident.). This is tricky to implement as we have to get the privacy and access exactly right. Dump files are closely guarded.
Please tell us more about what you would do with the dump files if you had access. This will help us to justify investments in that space.
Thanks Matthew. I can definately understand the privacy requirements for something like this. Also I probably should have made my original question around data provided for the "AbnormalShutdownCount" instead of the BSOD kernal crashes. I just imported a couple of devices into my workspace and can see that one has some unexpected shutdowns but I cannot seem to find any info on what caused them. Am I missing a configuration to pull in that data or is this just supposed to provide a count that could indicate an issue on the device?
- Matthew ReynoldsWe recently added the abnormal shutdown count in addition to the bluescreen count. This could potentially be used by organizations to help quantify trends such as certain device configurations encountering high rates of non-blue-screen abnormal shutdowns, such as black-screen+hard-power-down. Currently we don't include any diagnostic details for these, only the count-- and then only in log search mode (not in any of the default graphs). If we go further down that path... what information about the abnormal shutdowns would be useful to you?
Thanks for that reply Matthew. I guess its difficult to provide any further details for an abnormal shutdown other than the count since there is no real diagnotic details available on what causes them. I think the count is probably as best that we can expect. ANd now that I have devices actually showing with BSOD crash details in my console, I can see the differentiation more clearly as previously I had no devices with kernal crashes. Great for the environment but not great for understanding the product entirely.
Thanks
