BSOD shortly after boot up. wdfilter.sys

It was already on that when I went into do as requested, Do you want me to uncheck automatic and move it and switch back to automatic?Attachment 197910

The goal is to have only C: listed.
There should be no E: listed.
The no paging file should allow the page file to start at zero and then it is reset for its next use.
So the page file will only be on the windows drive, C: and it will display size of 0 after it was off and now on.

Yea, I don't know why it is picking up my storage drive (2nd HD) but it is. I unchecked auto switched it from custom to system managed and on paging file for E it says None. for file size. Here are a few shots.Attachment 197911Attachment 197912Attachment 197913

The paging file on E may need to be deleted.
Or the E: drive can be removed during the troubleshooting process.
There is a driver for the crash dumps.
Sometimes this driver malfunctions during the BSOD and there is no dump file creation.
So the optimal settings are to have only one paging file on the windows drive and settings on automatic manage paging file size for all drives.

With the above changes in the prior posts the dump files should be able to be created.
After each BSOD run the BETA log collector and post a new zip and for the next BSOD use file explorer to find the memory.dmp and if < 2Gb zip and post a one drive or drop box share link into the thread.

Well I have not seen it happen since maybe it was just a glitch in the system due to opening to many things at once? the machine is pretty strong as far as I know but it did do some updates the day before I haven't cleared the event log and I have removed the ccleaner program due to avast being avast and avasting it up. Here are some shots of the even log.Attachment 198423Attachment 198422Attachment 198421
If I get it to repeat the error I will come back and update the post, thank you for all of your help mainly you zbook.

The BETA log collector will collect the event viewer logs.
It may be easier for you to view it in this format.
If there are any BSOD or non-BSOD crashes you can post a new BETA log collector zip for troubleshooting.

zbook said:

The BETA log collector will collect the event viewer logs.
It may be easier for you to view it in this format.
If there are any BSOD or non-BSOD crashes you can post a new BETA log collector zip for troubleshooting.

Alright! just trying to give the correct info in a quick update :) thank you again zbook.

You are welcome.
If you post a new BETA it can be checked to see if there are any new problems.
https://www.tenforums.com/attachment...-v2-beta10.zip
(extract > open)

zbook said:

You are welcome.
If you post a new BETA it can be checked to see if there are any new problems.
https://www.tenforums.com/attachment...-v2-beta10.zip
(extract > open)

You bet man here we go, just encase you are curious Attachment 198427

The logs had been cleaned and started on 7/31/2018.

Code:

Event[0]:
  Log Name: System
  Source: Microsoft-Windows-Eventlog
  Date: 2018-07-31T13:54:32.061
  Event ID: 104
  Task: Log clear
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-21-4245869934-1179019648-633353147-1001
  User Name: DESKTOP-SM6S54N\Tekur
  Computer: DESKTOP-SM6S54N
  Description: 
The System log file was cleared.

They look good and are unremarkable.