BSOD support post

A blue screen of death is actually a diagnostic tool used to help address bad drivers, or hardware failures. I'm having to run to work so I can't see if my own system is crashing, but lo and behold, I'm going to work and will most likely need to be dealing with businesses whose staff have blue screening computers.

If you want to be constructive and help pinpoint a common fault, a reason why Ark is triggering a blue screen stop code, the following information is required:

1) A system information and driver report. An easy way to get this is a direct x diagnostics report. To do this, press the Windows Key+ R keys, type "dxdiag" and press enter. Once Direct X has collected your information, there will be a save report button on the bottom right.
The reason for this report is because there are literally hundreds, maybe thousands of hardware combinations, especially if you don't have a system built by a manufacturer, such as Dell or HP. This will also help in seeing if a driver needs updating.

2) we need some information on the crash itself. I don't know about you, but my own system reboots from a blue screen faster than I can load my camera or grab a pen and paper. Thankfully, for most blue screen events windows is able to capture information about what was running when the STOP code was thrown. It captures this in two locations:
C:\Windows\minidump and collectively in a single file located in C:\Windows\MEMORY.DMP

There is a free program that you can download called Blue Screen View which will turn this dump file into an easy to read display, which will highlight the following information:
The Stop Code, the 4 bug check parameters, what was running when the system locked up. This is the most critical information, but note that blue screen view can only read mini dump files because the MEMORY.DMP has a record of EVERY SINGLE CRASH. so it's not uncommon to see that file exceed 1GB. If you aren't getting minidump files, follow the link below how to turn them on.

https://blog.nirsoft.net/2010/07/27/how-to-configure-windows-to-create-minidump-files-on-bsod/

it takes a few minutes and will diagnostically make life easier in the future as minidump collect information on one BSOD event only.

If you could post that specific information (The Stop Code, the 4 bug check parameters, what was running when the system locked up.) then we can see if this is as a result of a conflict or issue with drivers that ARK is triggering for some reason. We might even be able to work together to find a workaround as well