Windows 10: Help Identifying problem drive from memory dumps

Hello,I need a little help Identifying what driver may be causing a CRITICAL_STRUCTURE_CORRUPTION 109 BSOD. I will post the dump from the original crash followed by the 4 mini dumps from the subsequent crashes after turning on the driver verifier.original analysis of crash:1: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis **

:)

 

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.

 

Need solution for automating transferring of files to flash drives

I am wary of jumping straight in at the deep end so I have a couple of questions.

1 How do you know which files to copy to which memory stick? Can you put a list for each one in a text file?
2 Are you free to give each memory stick a specific label so that it can be detected in order to trigger the specific list that you have written for that memory stick?

I do have a batch file procedure for identifying the drive letter currently being used for a given external drive label. So perhaps you could trigger a common batch file that
Step 1 - checks each drive in turn to read its label and then find its current drive letter
Step 2 - for each detected drive, look up the list given in the batch file to identify which [if any] text file to look in to find the files to copy to that memory stick.
Step 3 - copies the files listed in the relevant text file

Denis

 

Frequent Memory Dumps

Thank you for your response.

I have uninstalled cccleANER as suggested.

I have turned off real time scanning on McAfee Total Protection.

A couple of questions:

1. How can I check that I am not getting Memory dump files anymore? - they were detected by cccleANER
2. How can I check that I'm not getting interference between Malwarebytes and McAfee? - i.e. I need to know what level of RAM?
   

Thank you for your assistance