Hello
A lot of crash dmps there so took a look at the first three and the latest three to see if there was a pattern, there is but nothing that identifies any particular driver or service/s so you could be looking at 1: bad RAM. 2: a flaky storage device, one of your crash dmps below to which I have added some notes in blue to what I have highlighted in red;
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
2) A developer attempted to set a normal kernel breakpoint using a kernel
debugger that was not attached when the system was booted. Normal breakpoints,
"bp", can only be set if the debugger is attached at boot time. Hardware
breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a01f596419da9a, Reserved
Arg2: b3b72bdfb69a93d7, Reserved
Arg3: 0000000000000001, Failure type dependent information
Arg4: 0000000000000018, Type of corrupted region, can be
0 : A generic data region
1 : Modification of a function or .pdata
2 : A processor IDT
3 : A processor GDT
4 : Type 1 process list corruption
5 : Type 2 process list corruption
6 : Debug routine modification
7 : Critical MSR modification
Debugging Details:
------------------
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
BUGCHECK_STR: 0x109
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: System A driver or software issue would be named here if it was responsible for the crash, the fact that none are means it could be hardware related.
CURRENT_IRQL: 2
BAD_PAGES_DETECTED: 943e
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff802145d2760
STACK_TEXT:
ffffd000`ed1e20b8 00000000`00000000 : 00000000`00000109 a3a01f59`6419da9a b3b72bdf`b69a93d7 00000000`00000001 : nt!KeBugCheckEx
STACK_COMMAND: kb
SYMBOL_NAME: PAGE_NOT_ZERO
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module As above no driver or software identified as the cause so could again point to bad RAM or storage device.
IMAGE_NAME: Unknown_Image As above.
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUCKET_ID: PAGE_NOT_ZERO
Followup: MachineOwner
---------
*** Memory manager detected 37950 instance(s) of page corruption, target is likely to have memory corruption. Points towards bad RAM or flaky storage device.
Couple of things for you to do but will only suggest one at a time to make things easier for both of us;
Try running the computer in Safe Mode only (no networking) use the computer offline for a while and see if it crashes, if not, restart in Safe Mode with Networking, use the computer as you normally would including internet connection, see if the computer crashes and then post back with an update for us please.
Windows 10 Safe Mode instructions below courtesy of MS;
Restart your PC. When you get to the sign-in screen, hold the Shift key down while you select Power Power icon
> Restart.
After your PC restarts to the Choose an option screen, select Troubleshoot > Advanced options > Startup Settings > Restart.
After your PC restarts, you'll see a list of options. Select 4 or F4 to start your PC in Safe Mode. Or if you'll need to use the Internet, select 5 or F5 for Safe Mode with Networking.