Today’s post continues an ongoing series on Polarity User Tips. Data tells a story, Polarity helps you see it with Augmented Reality overlaying contextual information as you work, giving you the right data at the right time to make informed decisions and take action with speed (no glasses or goggles required). This guide explains how you can see the story in your data with Polarity using the Microsoft Bug Check Code References Reference Channel.
Intro to Polarity Reference Channels
Polarity Channels are a way to organize Entities and Annotations into logical groups, such as all of your assets or your LinkedIn contacts.
Reference channels are a Polarity Channel that is based on another source of information that is used just for reference purposes by Polarity Users. Reference channels can be anything from a list of internal or external threats to a list of assets to the Microsoft Bugcheck list.
Where to find Reference Channels
On the Polarity Github page, download the Microsoft Bug Check Code References reference channel or browse our library of reference channels for better data awareness and recall.
What is Microsoft Bug Check Code Reference?
The Microsoft Bug Check Code Reference list is a common list of bug check codes that Microsoft will display when a user gets an error on the blue bug check screen. The codes are typically in hexadecimal format, so it’s difficult to fully understand what that code is referring to.
Microsoft Bug Check References Reference Channels in Polarity
Based on the list of bug check references, we have put together a CSV that you can easily upload into Polarity as a reference channel. The reference channel will instantly map the bug check error codes that are in hexadecimal to what the code means and link out to Microsoft’s error page for more information.
For example, when the user sees a bug code on-screen, like “0x00000005” in the image below, they will be able to see what the bug references and link out to the documentation on the bug in question.
In this image, notice the highlighted bug code 0x00000005 on the left. You can see that Polarity’s computer vision recognized the text on screen, and in real-time while the analyst is working, it has provided contextual information from the Microsoft Bug Check Code References Reference Channel in the overlay window on the right.