Random crashes on new computer

No, you didn't use the Beta log collector, you use the older DM_Log_collector.

There were two BSODs on 1/12. Both were Bugcheck 116 which is a video problem.

Code:

1/12/2019 6:08 AM
Windows Error Reporting
Fault bucket 0x116_TdrBCR:D_Tdr:9_IMAGE_atikmpag.sys, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: b7724446-2993-47c5-97c4-c2fb701949c5
Problem signature:
P1: 116
P2: ffffc08e27cce480
P3: fffff8030f36f818
P4: 0
P5: d
P6: 10_0_17763
P7: 0_0
P8: 768_1
P9: 
P10: 
Attached files:
\\?\C:\Windows\Minidump\011119-5531-01.dmp
\\?\C:\Windows\TEMP\WER-7421-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2618.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2628.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2627.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2638.tmp.txt
These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_116_298bc945cb35704dcb523b9ac783d393d5d15a_00000000_cab_0211e007
Analysis symbol: 
Rechecking for solution: 0
Report Id: 8baf8506-44a1-4e29-a8f3-a612afb50ba9
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0

1/12/2019 6:02 AM
Windows Error Reporting
Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0
Problem signature:
P1: 116
P2: ffffc08e27cce480
P3: fffff8030f36f818
P4: 0
P5: d
P6: 10_0_17763
P7: 0_0
P8: 768_1
P9: 
P10: 
Attached files:
\\?\C:\Windows\Minidump\011119-5531-01.dmp
\\?\C:\Windows\TEMP\WER-7421-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2618.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2628.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2627.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2638.tmp.txt
These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_116_298bc945cb35704dcb523b9ac783d393d5d15a_00000000_cab_02d82635
Analysis symbol: 
Rechecking for solution: 0
Report Id: 8baf8506-44a1-4e29-a8f3-a612afb50ba9
Report Status: 4
Hashed bucket: 
Cab Guid: 0

I can't find anything in Event Viewer log (Eventlog.txt) that provides any info on why it failed. It does have this which BSODhunter already mentioned:

No idea why this one shows on 1/11 while the others show on 1/12.

Code:

Event[873]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2019-01-11T22:02:32.772
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-ORL2N9T
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000116 (0xffffc08e27cce480, 0xfffff8030f36f818, 0x0000000000000000, 0x000000000000000d). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 8baf8506-44a1-4e29-a8f3-a612afb50ba9.

Unfortunately MEMORY.DMP has been deleted so we have no dumps to look at.

A Google search turns up several reasons for this type of failure.

Nvidia driver (You have the latest)
Video Card or Chip not properly seated
Overclocking
Defective Video card or chip

You could try some of the older Nvidia drivers, see if they work any better. If you want to do rthis I recommend using DDU to completely uninstall the existing driver then do a custom install of only the Nvidia Graphics and PhysX driver.
Get the older drivers for your Nvidia card here: NVIDIA Driver Downloads
Completely uninstall the current Nvidia display drivers using Display Driver Uninstaller (DDU) from WagnardMobile here: Official Download Here. Do this in Safe Mode.

Then do a custom install of only the Nvidia Graphics and PhysX driver.

See if that gets rid of the problem.

Good luck. Let us know how you make out with the new card.

Thanks for letting us know Kinni. Glad all is well.