How to prepare GRIDNET Core crash reports

WARNING: the files produced do NOT share publicly. Share only privately with the Development Team.

In the world of complex software development, even with a highly skilled and meticulous Development Team like ours, when it comes to extremely complicated pieces of technology such as GRIDNET Core - unforeseen issues can arise, potentially leading to crashes.

These rare occurrences are opportunities for us to further refine our product. By following this guide, you can aid our team in swiftly pinpointing and addressing the root causes of any crashes.

This process involves utilizing Microsoft’s Debug Diagnostic Tool, a powerful and official utility, to gather detailed data from GRIDNET Core during these critical moments. Your contribution in collecting and sharing this data is essential for our continuous efforts to enhance GRIDNET Core’s reliability and performance, ensuring the highest quality experience for all users.

To set up the Debug Diagnostic Tool for GRIDNET Core, follow these steps:

  1. Download and Install: Acquire Debug Diagnostic Tool v2 Update 3.2 and install it.
    Download directly from Microsoft:

  2. Launch DebugDiag 2 Collection: This will prompt you to create a rule.

IMPORTANT: Update first if update available just as shown below:

Choose yes. Download new version and begin anew.

  1. Create Rule: Select ‘Crash’ for the type of rule.

  2. Choose Process: Opt for ‘A specific process’ and select “GRIDNET Core.exe” on next screen (as shown on second screenshot down below ).

Press next and select 'GRIDNET Core.


  1. Action Type: Select ‘Full UserDump’ for first chance exceptions.

  2. Confirmation: Click ‘Yes’ to proceed.

  3. Rule Name: Accept the default name or enter a new one.

  4. Activate Rule: Choose to activate the rule now.

  5. Answer YES to question below.

  6. Monitor Userdump Count: It will increase with each crash or reach a set maximum.

  7. Complete Collection: If the count maxes out without a crash, restart the process.

  8. File Sharing: Share the latest dump file, focusing on those with ‘Second_Chance_Exception’.

  9. Cleanup: Delete dump files after analysis to free up storage.

By following the provided instructions for using the Debug Diagnostic Tool with GRIDNET Core, you’re not just troubleshooting — you’re joining a pioneering endeavor to develop GRIDNET OS, the first decentralized operating system. Your contributions, through data collection and sharing, are invaluable. They don’t just help resolve immediate issues; they propel the evolution of GRIDNET OS, making it more robust and efficient.

WARNING: the files produced do NOT share publicly. Share only privately with the Development Team.

This is your chance to be part of a groundbreaking journey in technology, where every piece of data and every user plays a crucial role in shaping the future of operating systems.

1 Like