Hi JoshMan9,
Welcome to Ten Forums.
There was only 1 bsod mini dump file in the zip.
When it was debugged it did not display a definitive misbehaving driver.
There were multiple bsod noted but only one mini dump.
There were many faulting applications that were related to gaming.
Open administrative command prompt and type or copy and paste these commands:
1) sfc /scannow
2) dism /online /cleanup-image /restorehealth
3) chkdsk /scan
4) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread
5) Make sure that there is no over clocking while troubleshooting.Sometimes there are problems in the bios that produce bsod.
6) To ensure that there are no improper bios settings please reset the bios.
Sometimes there can be failure to boot after resetting the bios.
7) So please make sure your files are backed up.
8) Please make a backup image with Macrium:
Macrium Software | Macrium Reflect Free:
Macrium Software | Your Image is Everything
9) And please create a brand new restore point.
How to Clear Your Computers CMOS to Reset BIOS Settings:
How to Clear Your Computers CMOS to Reset BIOS Settings
3 Ways to Reset Your BIOS - wikiHow:
3 Ways to Reset Your BIOS - wikiHow
10) windows driver verifier is a tool that is used to find misbehaving drivers.
It will repetitively produce bsod until all misbehaving drivers are fixed or until windows driver verifier is turned off.
There are 3 methods to turn off windows driver verifier:
All methods are done using the windows recovery or windows advanced troubleshooting menu.
1) startup options (not startup repair) > select #6 safe mode with command prompt >
type: verifier /reset
2) command prompt opens Administrator X: \windows\system32\cmd.exe >
type: verifier /bootmode /resetonbootfail
3) system restore
Always attempt to turn off windows driver verifier with safe mode with command prompt verifier /reset
System restore unfortunately leads to loss of the mini dump file so little progress is made in the troubleshooting.
To practice navigating within the windows advanced recovery open administrative command prompt and type: shutdown /r /o /f /t 00
When using windows driver verifier you will want to be able to view the bsod window. Make sure automatic restart is unchecked so that you have time to view the bsod window. The bsod window typically displays a stop code driver verifier detected violation and sometimes displays the misbehaving driver in the form *.sys. If you see the driver displayed please record it and post it in the thread.
The system settings need to be modified to not automatically restart so that you have ample time to view the bsod window. Follow the settings in this link: BSOD Finding and fixing them - Microsoft Community
Keyboard: win + r keys simultaneously > type or copy and paste: sysdm.cpl > click advanced tab > under startup and recover click settings > under system failure uncheck automatically restart
See this link: BSOD Finding and fixing them - Microsoft Community: https://answers.microsoft.com/en-us/...d-e95ee5d8669d
Please read this link so that you understand how to use windows driver verifer. It has custom settings to use for the testing.
https://answers.microsoft.com/en-us/...3-c48669e4c983
After each bsod you will turn off windows driver verifier and return to the desktop. On the desktop you will use bluescreenview and whocrashed to process the bsod mini dump file. You will then update or uninstall and reinstall the misbehaving drivers. Then you will reactivate windows driver verifier to find the next misbehaving driver. You can update or uninstall all misbehaving drivers first and after there are no more bsod start installing drivers. Alternatively you can reinstall a driver as soon as it is uninstalled. It is personal preference. The end result should be the same.
Blue screen of death (STOP error) information in dump files.
http://www.resplendence.com/whocrashed
Enable and Disable Driver Verifier in Windows 10 Windows 10 Performance Maintenance Tutorials
Please make sure that you create a brand new restore point before using windows driver verifier.
You can start using the tool when you have time to process the bsod and feel comfortable navigating the windows advanced troubleshooting menu.
As you have bsod please update the zip file: BSOD - Posting Instructions - Windows 10 Forums
Code:
Crash dump initialization failed!
Code:
BugCheck 1, {7ffd6a028c34, 0, 200000, ffff8001cdcefb00}Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExitPico+194 )
Code:
Problem signature:P1: CorsairLink4.Service.exe