Windows 10 Fall Creators Update - Windows Explorer - display corrupted

Ever since upgrading to Windows 10 Home x64 Fall Creators Update, what appears to happen is Windows Explorer will work correctly for up to 7 days from logging in but it seems like it is running out of resources or something since as little as 2 days or up to 7 days, it appears that Windows Explorer will not work correctly in displaying things as shown below when I open a folder or if I right clicked on a item as the later will only show a bunch of arrows instead of the actual items.



I have already tried killing and restarting the explorer.exe and dwm.exe processes but the results is still the same as only a reboot will fix it. Anyone has any ideas how to fix this and what is causing it?

Already tried the latest video drivers, made no difference. In fact, with any of the 388.x drivers from nVidia, it does not play well if you tried to do a in-place install with the ISO as what happens is it will reach about 33% and then screen will just lose video with no way to get it back even after a few hours so hard reboot will cause it to restore to previous version of windows, it happened with all versions after 387.92 which meant 388.00, 388.13 and 388.31. This doesn't happen with the 387.92 driver which is the first version compatible with Fall Creators Update. Also, it seems related to the uptime as the problem doesn't happen until a few days later. It seems like the problem was every 1-2 days when I originally used FCU as my computer is on 24/7 but now happens after 7 days ever since patch Tuesday for November so it could actually be a bug in Windows as even though I have 32GB of memory. Unlike Windows 7 (might be XP) and earlier, it no longer has that resource heap limits one can change in the registry for csrss.exe as mentioned here:
https://support.microsoft.com/en-us/...of-the-desktop

https://support.microsoft.com/en-us/...instances-runn

A thread that talks about the issue is in:
Out of Memory with plenty free???? Solved - Windows 10 Forums

I am running 93 browser tabs in Chrome and 5-6 in EDGE... I noticed the problem happens faster if I opened 16 tabs new tabs and then close the 16 new tabs a few times.

Windows may or may not release all the resources it used so the longer the uptime, the lower the resources available.

sfc /scannow did not find anything other than claiming 4 files are corrupted for gpedit which is a hacked version as Home doesn't come with Group Policy Editor so it will always complain about the following files:

2017-11-19 03:37:30, Info CSI 00007733 [SR] Could not reproject corrupted file \??\C:\WINDOWS\SysWOW64\fdeploy.dll; source file in store is also corrupted

2017-11-19 03:37:31, Info CSI 00007766 [SR] Could not reproject corrupted file \??\C:\WINDOWS\SysWOW64\fde.dll; source file in store is also corrupted

2017-11-19 03:37:37, Info CSI 00007828 [SR] Could not reproject corrupted file \??\C:\WINDOWS\SysWOW64\gpedit.dll; source file in store is also corrupted

2017-11-19 03:37:38, Info CSI 00007832 [SR] Could not reproject corrupted file \??\C:\WINDOWS\SysWOW64\gptext.dll; source file in store is also corrupted

Also, just for reference, here is the dism output:
C:\WINDOWS\system32>dism /online /cleanup-image /checkhealth


Deployment Image Servicing and Management tool
Version: 10.0.16299.15


Image Version: 10.0.16299.64


No component store corruption detected.
The operation completed successfully.


C:\WINDOWS\system32>dism /online /cleanup-image /scanhealth


Deployment Image Servicing and Management tool
Version: 10.0.16299.15


Image Version: 10.0.16299.64


[==========================100.0%==========================] The component store is repairable.
The operation completed successfully.


C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth


Deployment Image Servicing and Management tool
Version: 10.0.16299.15


Image Version: 10.0.16299.64


[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.


C:\WINDOWS\system32>

The problem is Windows run out of resources as it depends on how many files were copied around as seen here:
Right-click menu contains blank lines or is - Microsoft Community