BSOD Occurrences - OS Test
The blue screen of death (BSOD), also known as a stop error screen, blue screen error, fatal error or bugcheck is a critical error screen that can be displayed by Microsoft Windows operating systems (OSes). If and when a BSOD appears, it indicates that Microsoft Windows has encountered a very serious issue from which the system cannot recover on its own. The BSOD functionally renders an affected system non-operational until the issue that triggered the BSOD is resolved with some form of intervention by the user. The BSOD incident typically comes with no warning leading to loosing of all unsaved work.
The BSOD occurs due to various reasons for example, hardware failures, outdated or corrupted drivers, faulty/incompatible software, malware, operating system issues, etc. Administrators may want to track the BSOD occurrences so that they can easily detect the underlying issues in the target host and promptly resolve issues before it permanently renders the host to halt. This is where the BSOD Occurrences test helps!
This test reports the count of BSOD incidents that occurred on the target host. Detailed diagnostics reported by this test can help the administrators to rapidly identify and efficiently troubleshoot the issues that caused the BSOD.
Target of the test : A Windows virtual desktop on the cloud
Agent deploying the test : A remote agent
Outputs of the test : One set of results for the Windows virtual desktop on the cloud.
Parameter | Description |
---|---|
Test Period |
How often should the test be executed. |
Host |
The nick name of the Cloud Desktops component for which this test is to be configured. |
Port |
Refers to the port at which the specified host listens to. By default, this is NULL. |
Inside View Using |
To obtain the 'inside view' of performance of the cloud-hosted Windows desktops - i.e., to measure the internal performance of the Windows virtual desktops - this test uses a light-weight eG VM Agent software deployed on each of the desktops. Accordingly, this parameter is by default set to eG VM Agent (Windows). |
Report Powered OS |
This flag is relevant only for those tests that are mapped to the Inside View of Desktops layer. If this flag is set to Yes (which is the default setting), then the 'inside view' tests will report measures for even those Windows virtual desktops that do not have any users logged in currently. Such desktops will be identified by their name and not by the username_on_virtualdesktopname. On the other hand, if this flag is set to No, then this test will not report measures for those Windows virtual desktops to which no users are logged in currently. |
Is Cloud VMs |
Since this test runs for a 'Cloud Desktops' component, this flag is set to Yes by default. |
DD Frequency |
Refers to the frequency with which detailed diagnosis measures are to be generated for this test. For instance, if you set to 1:1, it means that detailed measures will be generated every time this test runs, and also every time the test detects a problem. |
Detailed Diagnosis |
To make diagnosis more efficient and accurate, the eG suite embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:
|
Measurement | Description | Measurement Unit | Interpretation |
---|---|---|---|
Blue screen of death occurrences in the last hour |
Indicates the number of Blue screen of death (BSOD) errors occurred during the last measurement period. |
Number |
The value of this measure should be 0. A non-zero value is a cause for concern. The detailed diagnosis of this measure reveals the name of the dump file created when the BSOD occurred, the time stamp at which the crash occurred, the check code and string of the bug that caused the crash, the size of dump file, name of the system, etc. |