Windows 10: Help Analyzing System Crash Mini Dump Files

Hello,

I am looking for support in analyzing these system dump files.


My suspicion is that it is a memory issue in the explorer.exe process. The user says that this has been happening somewhat frequently when transferring images (about 35) into a web application for upload.


Link to 3 zipped mini dump files

https://drive.google.com/file/d/1BRPMDlstia4WOsISHVraWQ9MXAXxH8We/view?usp=sharing


Link to MSInfo32 File

https://drive.google.com/file/d/1lol8DZXJ-sD2r5r9G_1_T00AbfFrTfKD/view?usp=sharing

:)

 

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.

 

Windows 10 - Interpreting two BSOD Crash Mini Dump Files

After reinstalling Windows 10 stable release over the Windows 10 Insider Preview OS I had two separate BSOD crashes. I ran them both through WinDbg and have links to the plain text of the Windbg !analyze -v outputs.

BSOD Error Mini-Dump File #1 (Think it's something to do with Broadcom Driver) - Solutions?

Win 10 Crash Mini-Dump Output#1

BSOD Error Mini-Dump File #2 (This one is FREAKING ME OUT because it's saying something about memory corruption?!) - Cause?/Hardware?/Software? - because maybe I installed Windows 10 on top
of Windows 10 Insider (not a clean install)--- most importantly.... Solutions?!?

Win 10 Crash Mini-Dump File #2

Thank you all!

 

Please Help analyze MiniDump Files (included)/BSODs/ ntoskrnl.exe/

Hi,

In most cases, this problem is caused by corrupted system files. For us to provide the best resolution possible, we'll be needing additional information:

• Have you made any recent changes on your computer prior to the issue?
• Was there an error code displayed when experiencing the blue screen error?

Meanwhile, we suggest following the troubleshooting steps provided on this
article to help fix the blue screen error. We also recommend posting on
TechNet forum to analyze the dump files.

If you need further assistance, don't hesitate to reach out.