BSOD shortly after boot up. wdfilter.sys

Hey all I like to think that I am pretty decent when it comes to keeping my pc running smoothly and for the first time in about 8-9 years I need some help with my personal rig. While I was booting up my PC this morning I noticed that I got a BSOD and it said wdfilter.sys, Now I have done some general research with this but I am ending up with the equivalent of googling a health problem (cancer etc) but in PC terms Hardware fault / failure, whether it be RAM, GPU or otherwise.

I went and looked for the dump file and can't seem to locate the mini dump. I have however the full dump and its its roughly 914MB and I can't seem to open it.

I ran the windows memory diagnostics tool and it found no errors and I do not have the time to memtest each ram stick individually at this current time, I have reinstalled my GPU driver ( clean install ) and I have ran a SFC scan too. I made sure windows was fully up2date and that all of my third party software was as well. It appeared to have crashed when I went to launch MSI command center. I do notice that this programs freezes from time to time.

With doing all of this I have rebooted about 6-7x now and have not been able to replicate my BSOD. I have even mass launched as many programs as possible including command center and EVGAs X software. The last thing I want to do is reinstall but I will if I must. I come here in search of others who might possibly be able to give me other ideas/areas to check or bounce off of.

System Specs:
CPU: 6700k
GPU: EVGA 1080 TI FTW 3.
BIOS: Latest from manufacture
Ram: Corsair LPX 32GB, Config: 4x8 sticks @ X.M.P. 1 @ 2400MHZ
MB: MSI Gaming M5, Z270.
PSU: EVGA G2 supernova 850W
Monitor: VG248QE
Temps: CPU -idle 25-33c, Load 55-70c. | GPU - 31-33C Idle, 45-55c Load.
CPU cooler Noctua NH D15
SSD: Samsung Evo 500GB NVME

See posting instructions.
Please use the BETA log collector on the bottom of the web page.

zbook said:

See posting instructions.
Please use the BETA log collector on the bottom of the web page.

Uploaded, Thank you for pointing that out.

Hi rinji07 ,

Welcome to the Ten Forums BSOD forum.

There were no dump files collected.
The log files were cleaned today.

1) Open Ccleaner > click windows tab > scroll down to system and advanced > post an image into the thread

2) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings
a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery into the thread.
b) > on the advanced tab under performance > click on settings > under performance options > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory tab into the thread

3) During the troubleshooting make sure that there is:
a) no over clocking
b) no software that automatically installs drivers
c) no driver accelerators
d) no registry cleaning

4) Uninstall Glary Utilities

5) For any BSOD > run the BETA log collector and post a new zip into the thread

As requested. Attachment 197899Attachment 197900Attachment 197901Attachment 197902

1) For startup and recovery system failure:
a) Un-check automatically restart
b) Change write debugging information from small memory dump to automatic memory dump
c) reboot


2) For virtual memory click on the advanced tab and view the section: performance > click on settings > on the performance options windows click on the advanced tab > look in the virtual memory section > click on change > post an image of the virtual memory window into the thread

3) For Ccleaner un-check:
a) Memory Dumps
b) Windows log files
c) Windows error reporting
d) Windows event logs

4) When automatic restart is checked it can be easy to miss BSOD when away from the computer. With this box unchecked you should now see a BSOD windows with bugcheck and : (.
Sometimes you may see a misbehaving driver in the form *.sys.
At the start of a BSOD you may see a % counter. Allow this counter to rise to 100 % before rebooting so that there is sufficient time for the dump file creation.

As requested.Attachment 197903Attachment 197904Attachment 197905

For virtual memory:
a) check the box to automatically manage paging file size for all drives
b) make sure that there is only one paging file and that the paging file is on the Windows drive
c) reboot


After the troubleshooting process has completed you can modify all of the settings.
During the troubleshooting process these settings should optimize the ability to generate the troubleshooting files.

Yes sir, last step performed. Attachment 197906

On the virtual memory
1) first move the dot to no paging file then reboot
2) then move the dot from custom size to system managed size > reboot