Crash Report GUID Correlation System

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current crash reporter systems lack sufficient context, such as hardware and software configurations, and application usage information, making it difficult to determine the root cause of computer crashes.

Innovation Solution

A method and system that establish a network of computing resources with globally unique identifiers (GUIDs), allowing for the correlation of crash reports with configuration and usage information to provide additional context for crash analysis.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If only stack trace information is collected in crash reports, then the crash report size remains small and transmission is fast, but the information is insufficient to determine the root cause of the crash

Engineering Contradiction:
Improvecrash context informationVSAvoidcrash report system
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The system performs preliminary actions by assigning GUIDs to computing resources before crashes occur and collecting configuration information in advance. When a crash happens, the pre-assigned GUID is already embedded in the crash report, and configuration data is already stored and associated with that GUID, eliminating the need for complex post-crash data gathering and correlation systems.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The GUID acts as an intermediary element that connects crash reports with configuration information. Instead of directly linking complex crash data with detailed system configuration, the GUID serves as a simple mediator that associates these two information sets, reducing the complexity of the correlation mechanism while ensuring complete information retrieval.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of information

If detailed configuration and usage information is collected for every computing resource, then comprehensive diagnostic data is available, but the complexity of managing and correlating this data increases significantly

Engineering Contradiction:
Improvehardware and software configuration contextVSAvoiddata correlation system
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The GUID serves as an intermediary key that simplifies the correlation between computing resources and their configuration data. Each computing resource is assigned a unique GUID, and all configuration information is stored with references to this GUID. When analyzing crashes, the GUID in the crash report directly retrieves the associated configuration without requiring complex matching or correlation algorithms.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system segments the diagnostic process into independent components: crash data collection, configuration data collection, and correlation through GUID matching. This segmentation allows each component to operate independently and simplifies the overall system architecture, as the correlation step becomes a simple key-lookup operation rather than a complex many-to-many matching problem.

Inventive Principle:
Principle #1Segmentation

3Reliability

If GUIDs are assigned and tracked for all computing resources, then crash reports can be accurately correlated with configuration information, but the system requires additional infrastructure for GUID management

Engineering Contradiction:
Improvecrash analysis accuracyVSAvoidGUID management infrastructure
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

GUID assignment is performed as a preliminary action during computing resource setup or first interaction with the system. This ensures that every resource has a unique identifier before any crashes can occur, eliminating the need for complex post-assignment management while ensuring reliable correlation from the first crash report.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9846607B2Method and system for associating crash reports with end user analytics
Publication Date: 2017.12.19 NVIDIA CORP
  • US9846607B2 patent drawing
  • US9846607B2 patent drawing
  • US9846607B2 patent drawing

AI summary

A method for linking information related to a computer crash. The method includes establishing a network of computing resources communicatively coupled to a network, wherein each computing resource is associated with a corresponding hardware configuration capable of executing and displaying at least one application, wherein each of the network of computing resources is associated with a globally unique identifier (GUID). The method includes receiving configuration information relating to the network of computing resources. The method includes receiving a crash report of a crash occurring on a crashed computing system within the network of computing resources. The method includes extracting a GUID from the crash report, wherein the GUID identifies said crashed computing resource. The method includes determining configuration information for the crashed computing resource, and correlating the configuration information with the crash information.