Windows 10: File Explorer issues since Win. 10 Auto update

Has anyone else experienced Windows 'File Explorer' frequently crashing into 'oblivion'? and restarting desktop view/taskbar after blank screen.

Other running programs are not lost, but its a major imposition and started happening since W10 automatic upgrade recently.


Regards,


Lee

Event log example:

********************************************************************************************

EvenLog Name: Application
Source: Application Error
Date: 09/09/2019 14:10:30
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: Lee-Vaio
Description:
Faulting application name: explorer.exe, version: 10.0.18362.329, time stamp: 0xdbc8cf38
Faulting module name: DivX.dll, version: 5.0.5.830, time stamp: 0x3ea73f16
Exception code: 0xc0000005
Fault offset: 0x001b6001
Faulting process ID: 0x20cc
Faulting application start time: 0x01d5670fbfd28a0d
Faulting application path: C:\WINDOWS\explorer.exe
Faulting module path: C:\WINDOWS\SYSTEM32\DivX.dll
Report ID: 56ee7f0a-152b-44fb-9789-8dcc6725203a
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2019-09-09T13:10:30.822360400Z" />
<EventRecordID>2143</EventRecordID>
<Channel>Application</Channel>
<Computer>Lee-Vaio</Computer>
<Security />
</System>
<EventData>
<Data>explorer.exe</Data>
<Data>10.0.18362.329</Data>
<Data>dbc8cf38</Data>
<Data>DivX.dll</Data>
<Data>5.0.5.830</Data>
<Data>3ea73f16</Data>
<Data>c0000005</Data>
<Data>001b6001</Data>
<Data>20cc</Data>
<Data>01d5670fbfd28a0d</Data>
<Data>C:\WINDOWS\explorer.exe</Data>
<Data>C:\WINDOWS\SYSTEM32\DivX.dll</Data>
<Data>56ee7f0a-152b-44fb-9789-8dcc6725203a</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>t log




(Also, this garbled Admin Event log below, appears to fit the timeline of explorer fail..., but may be a 'red herring'


*********************************************************************************************

Log Name: Microsoft-Windows-User Device Registration/Admin
Source: Microsoft-Windows-User Device Registration
Date: 09/09/2019 14:10:39
Event ID: 360
Task Category: None
Level: Warning
Keywords:
User: LEE-VAIO\Lee
Computer: Lee-Vaio
Description:
Ŵîήđöщś Ηėŀļò ƒøř Βùśіñèšŝ φŕőνĭşιőиïňġ ẅіŀľ ŋòŧ ьė ℓáųʼnćħęď.
Đзνĩςë іŝ ÀĄĐ јöíиέð ( ÄΑĎĴ őѓ ĐĴ++ ): Not Tested
Ùѕёг ħдѕ łõģĝéð őņ ẅϊţћ ĄΔĎ ¢řеďèņťϊåļŝ: No
Шїπðŏẁş Ĥ℮ĺĺǿ ƒθг Βŭşįʼnëŝѕ рōļїςý ĭş έʼnǻъŀēδ: Not Tested
Шĩⁿďθώš Ήëŀļσ ƒôř Вûśîņεŝš ρóŝŧ-ŀбġбй рѓöνίѕĩōňΐñğ ίŝ епǻьŀзď: Not Tested
Ľö¢āŀ ĉοмρůŧέŗ мēзτš Щιʼnδσώş ђеłļǿ ƒõŕ ьüŝïņэŝѕ ћäѓďẃåѓę яэqűířемεņţѕ: Not Tested
Űšęѓ їŝ ηőŧ ςσиŋèςţěð тο ŧĥē ма¢ĥϊñε νįă Řёмõтε Ðĕšќŧόр: Yes
Ůśėѓ ¢ěřŧîƒιċąтè ƒοř øл ρґĕmїѕě ăüŧħ рõℓĭ¢ŷ īş êńàвļëđ: Not Tested
Μαçнĩñé įş ĝόνεяиĕď ьÿ none рøłīςŷ.
Ŝęë https://go.microsoft.com/fwlink/?linkid=832647 ƒøѓ mоřę đĕτãïłѕ.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-User Device Registration" Guid="{23b8d46b-67dd-40a3-b636-d43e50552c6d}" />
<EventID>360</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2019-09-09T13:10:39.693997100Z" />
<EventRecordID>42</EventRecordID>
<Correlation />
<Execution ProcessID="7888" ThreadID="9112" />
<Channel>Microsoft-Windows-User Device Registration/Admin</Channel>
<Computer>Lee-Vaio</Computer>
<Security UserID="S-1-5-21-2578669900-737466333-4031914577-1000" />
</System>
<EventData>
<Data Name="Message">Ŵîήđöщś Ηėŀļò ƒøř Βùśіñèšŝ φŕőνĭşιőиïňġ ẅіŀľ ŋòŧ ьė ℓáųʼnćħęď.</Data>
<Data Name="DeviceIsJoined">Not Tested</Data>
<Data Name="AADPrt">No</Data>
<Data Name="NgcPolicyEnabled">Not Tested</Data>
<Data Name="NgcPostLogonProvisioningEnabled">Not Tested</Data>
<Data Name="NgcHardwarePolicyMet">Not Tested</Data>
<Data Name="UserIsRemote">Yes</Data>
<Data Name="LogonCertRequired">Not Tested</Data>
<Data Name="MachinePolicySource">none</Data>
</EventData>
</Event>

*********************************************************************************************************

:)

 

Win 10 (64 bit) File Explorer Does not Auto Refresh

• When did you start experiencing this problem?

Since I started using the folder system on this browser. It seems to be a WIndows 10 issue (or default setting?). The only way I can refresh at this point is hitting F5 or left clicking to the Refresh option. THere is no Auto Refresh when I add a file to
folder.

• Did you make any changes to your computer prior to the issue?

No. This is a new machine with a freshly installed version of WIndows 10. I have not seen it work the way it did in WIndows 7 on my old laptop.

• Does the issue happen to all the folders in File Explorer?

Yes. I've tried dragging and dropping files into different folders in various different view options (Details / Large Icons etc). The new file added is visible but it is placed at the end of the file list and not auto arranged in alphabetical order as I
am familiar with in the past. Is there an auto arrange option for this?

 

Windows 10 Tweaks

Pressing “Windows+Pause Break” (it’s up there next to scroll lock) opens the “System” Window.

Windows 10: In the new version of Windows, Explorer has a section called Quick Access. This includes your frequent folders and recent files. Explorer defaults to opening this page when you open a new window. If you’d rather open the usual This PC, with links to your drives and library folders, follow these steps:

• Open a new Explorer window.
• Click View in the ribbon.
• Click Options.
• Under General, next to “Open File Explorer to:” choose “This PC.”
• Click OK

credit to Lifehacker.

 

AMD FX OC'ers Club

That's what the auto setting will do since you're over the 1333 mark it jumps to the next step which isn't listed or officially supported I assume by that ram.

At this point though I would suggest dropping the multi one step or .5 so that we can get something stable and possibly take the heat issue out of the picture for now.