Windows 10: Working on an online dump file analyzer

I created an online dump file analysis website called DebugLearn - Upload - DebugLearn I'm a Windows driver developer and this is my pet project. My short term goal is to learn about web technology and Azure. The long term goal is collect enough data sets to mine for patterns or trends. Of course, the benefit to the users is that the debug analysis can be automated. How does it work? It's fairly simple. The user uploads a mini dump. The backend server runs debug commands and parses the outputs from the debug engine. The front end parses the result and provide recommendations to the users. Limitations Currently it accepts only mini-dumps. No full dumps or zipped dumps. Only limited number of BSODs (9F, 116) have its unique debug scripts. Everything else runs generic debug scripts. I'm not sure if this post breaks any of the site policy, but I thought that this website might be useful to the audience here. I'm okay if you want me to link the analysis results back to this forum.

:)

 

Need help for analyzing dump files!

Can someone help to analyze the dump files for bluescreen reasons?

The following link has the dump files

https://1drv.ms/u/s!AsowNH1JWNPygpkJWLYu3ZJtgV5x2g?e=eWLHVR

 

Need help analyzing dump file.

If your computer crashes, how can you find out what happened, fix the issue and it prevent it from happening again? You may find the small memory dump file useful in this situation. The small memory dump file contains
the smallest amount of useful information that could help you identify why your computer crashed. The memory dump file contains the following information:

• The Stop message, its parameters and other data
• A list of loaded drivers
• The processor context (PRCB) for the processor that stopped
• The process information and kernel context (EPROCESS) for the process that stopped
• The process information and kernel context (ETHREAD) for the thread that stopped
• The Kernel-mode call stack for the thread that stopped

To create a memory dump file, Windows requires a paging file on the boot volume that is at least 2 megabytes (MB) in size. On computers that are running Microsoft Windows 2000, or a later version of Windows, a new memory
dump file is created each time that a computer crash may occur. A history of these files is stored in a folder. If a second problem occurs and if Windows creates a second small memory dump file, Windows preserves the previous file. Windows gives each file
a distinct, date-encoded file name. For example, Mini022900-01.dmp is the first memory dump file that was generated on February 29, 2000. Windows keeps a list of all the small memory dump files in the %SystemRoot%\Minidump folder.

The small memory dump file can be useful when hard disk space is limited. However, because of the limited information that is included, errors that were not directly caused by the thread that was running at the time of
the problem may not be discovered by an analysis of this file.

 

Help analyze another DUmp File

Hi,

1. Please see the dump file on the link below

MiniDump S – Google Drive

2. If anyone has a tool to help analyze minidump errors that can be shared with other user,

Thank you in advance

Jef