Varios BSOD errors - Crash at any point

Hi Wild Fires, welcome to tenforums.

First thing I see is you have a G19s Gaming Keyboard but the drivers for it are not installed. Don't know if that matters yet but something to think about.

Also see your BIOS is down level, version 2.70 dated 06/11/2014 is available. You have version 2.00 dated 15/10/2012.

Your Nvidia driver is also down level. You have version 388.13 dated 27/10/2017. Version 399.07 dated 27/08/2018 is available.

The eventlog.txt file has thousands of these:

Code:

Event[821]:
  Log Name: System
  Source: Ntfs
  Date: 2018-08-28T17:59:30.889
  Event ID: 134
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-0TAR8SA
  Description: 
The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.

This post from 2014 should still apply, even though it was for Windows 7 as the file system is the same.

Karthik Vengaloor - This issue occurs if the Windows file system transaction log is corrupted. The Windows file system uses the transaction log to recover system transactions when a file error occurs.The Common Log File System (CLFS) transaction logs may be left in an inconsistent state. When the CLFS transaction logs are in an inconsistent state.
To resolve this problem, delete the .blf files and the .regtrans-ms files from the %Windir%\System32\SMI\Store\Machine folder.

After you restart the computer, the registry regenerates the deleted files. These regenerated files are in a consistent state.

a. Press Windows key+X and select Command prompt(Admin).
b. At command prompt, type the following command, and then press ENTER:

fsutil resource setautoreset true c:\

Note These steps assume that Windows is installed in the default location, on drive C. If this is not the case, adjust the drive letter of the folder path to match your configuration.
c. Restart the computer.

Above posted here: https://answers.microsoft.com/en-us/...d-89730e593710

I don't see any new resource manager problems, so that's good. Nvidia driver looks good and up to date as does the BIOS.

You had 16 BSODs on the 30th, here is a list of most of them:

Code:

2018-08-30T17:03:53.476  0x0000001e
2018-08-30T17:15:24.470  0x0000001e
2018-08-30T17:39:47.561  0x000000da
2018-08-30T17:58:32.843  0x0000000a
2018-08-30T18:25:11.003  0x00000101
2018-08-30T18:42:23.866  0x0000003b
2018-08-30T19:00:38.736  0x0000003b
2018-08-30T19:37:04.656  0x000000d1
2018-08-30T19:48:08.001  0x000000f7
2018-08-30T20:03:33.371  0x0000000a
2018-08-30T20:09:32.677  0x0000000a
2018-08-30T20:20:36.922  0x0000000a

As you can see there are 6 different crash codes. The dumps I looked at all point to Windows drivers which doesn't help as they are not at all likely to be the cause. Something else if triggering this.

Let's start by doing a Clean Boot, see if that gets rid of the BSODs. If yes then that is pretty conclusive that it's a non-Microsoft device driver problem and the way to resolve it is to enable them a few at a time until the BSODs start occurring again. Once we know what driver/device is the cause we can see how to fix it.

See here: How to Perform a Clean Boot in Windows 10 to Troubleshoot Software Conflicts

If that doesn't identify the cause the next step is to enable Driver Verifier to try and force a device driver error, as follows:
===================================================
Driver Verifier is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The required result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.
Machines exposed to Driver Verifier may run very sluggishly due to the stress being applied to the drivers.

Driver Verifier - Enable and Disable in Windows 10

Pay close attention to PART TWO and make sure the correct boxes are checked.

Warning:
It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.

Always create a Restore Point prior to enabling Driver Verifier so you have a way to recover if it goes haywire. Seldom does but it can happen.

What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it. If you get a BSOD, rerun the log collector and upload the resulting zip file.

One other thing I'd like you to do is use the v2-Beta12 collector listed at the bottom of the BSOD posting instructions link. It collects additional info that may be helpful in figuring this problem out. Run it now and upload the zip then use it from now on instead of the dm_log_collector.exe.

Not too hopeful of Driver Verifier showing anything then as Clean Boot didn't improve things. Time will tell.