Windows 10: SHELL32.dll 0xc0000005 when opening folders in windows explorer or 7-zip

This has been going on for a while It started when I cant remember details exactly but I downloaded a zip and tried to extract it then cancelled it from the explorer UI thing mid extracting then my explorer wouldn't open at all and my taskbar and stuff kept coming and going explorer was restarting and if im remembering correctly event log showed 0xc0000005 for shell32I troubleshooted this though by going into a new user account and noticed it didn't persist then I deleted the folder I the one I cancelled mid extracting using another user account and then everything was finebut since then

:)

 

Windows 7 - Explorer Has stopped Working - SHELL32.dll

i keep getting this message every time my Explorer has stopped working:






i have tired countless time to replace explorer.exe and shell32.dll from Windows 7 Ultimate x86 with and out Service Pack 1, same result.

Sometimes it comes when i exe timerviewer or some else does it.

Anyone got a fix for this? bcs reinstall doesn't help it comes a week or two after a clean installation and it doesn't matter if i mod explorer, shell32 or uses windows2door.com's unblur for Windows 7 it comes even with stock theme or i change colour and wallpaper.

 

Windows 7 - Explorer Has stopped Working - SHELL32.dll

if u want me to check in Event Viewer --> Windows Logs --> Application here is the error:

Code: Faulting application name: explorer.exe, version: 6.1.7601.17567, time stamp: 0x4d6727a7 Faulting module name: SHELL32.dll, version: 6.1.7601.17755, time stamp: 0x4f0412de Exception code: 0xc0000005 Fault offset: 0x000b4c80 Faulting process id: 0xd5c Faulting application start time: 0x01cd4982623f13f4 Faulting application path: C:\Windows\explorer.exe Faulting module path: C:\Windows\system32\SHELL32.dll Report Id: 2f95e9ed-b633-11e1-91c5-5404a648ba12[/quote] i got that yesterday.

 

Windows 10 File Explorer crashing due to Shell32.dll with exception code 0xc0000005 after opening 128 folders

Hello,

I'm in a bind and currently exhausted all ideas on how to fix this issue.

As stated the issue I'm having, while odd, can be iritating, and I narrowed it down to following:

When opening a fresh file explorer if I open around 128 folders, one by one, explorer.exe will crash, and the crash will be caused by shell32.dll. Explorer.exe process will then restart itself. To be exact around 126/127 folder I can see a normaly spinning wheel on the mouse cursor indicating something is happening/loading, but this time the circle is static, and on the next folder the crash will happen.

This can be done either by going one by one folder in navigation window, or with going in the main window, entering a folder, hitting backspace, entering another, etc.

If I then open a new file by that point, and recreate the steps, no new crash will occur.

The issue will show up again if I do those steps again after PC reboot.

If i stop before 127/128th folder, close File explorer, open a new one I would need to hit full 128 folders for the issue to occur.

Event logger shows the following Application Errors (translated as much as I could):

1:

Faulting application name: Explorer.EXE, version: 10.0.19041.3448, time stamp: 0xa1694e98

Faulting module name: SHELL32.dll, version: 10.0.19041.3393, time stamp: 0x480c18d7

Exception code: 0xc0000005

Fault offset: 0x000000000056b829

Faulting process id: 0x2a20

Faulting application start time: 0x01d9f619a75debe3

Faulting application path: C:\WINDOWS\Explorer.EXE

Faulting module path: C:\WINDOWS\System32\SHELL32.dll

Report Id: 7aefb4c8-7a0b-4bad-ae75-872f3f5ef752

2:

Faulting application name: rundll32.exe_shell32.dll, version: 10.0.19041.746, time stamp: 0xfb4a9a6b

Faulting module name: shell32.dll, version: 10.0.19041.3393, time stamp: 0x480c18d7

Exception code: 0xc0000005

Fault offset: 0x000000000056b829

Faulting process id: 0x2f40

Faulting application start time: 0x01d9f61a83354679

Faulting application path: C:\WINDOWS\System32\rundll32.exe

Faulting module path: C:\WINDOWS\System32\shell32.dll

Report Id: c692335e-f0e4-44b6-aeed-018a516bf244

3 (after updating to KB5030300):

Faulting application name:: Explorer.EXE, version: 10.0.19041.3516, time stamp: 0xbf6d7543

Faulting module name: SHELL32.dll, version: 10.0.19041.3516, time stamp: 0x4b28a4ad

Exception code: 0xc0000005

Fault offset: 0x000000000056b599

Faulting process id: 0x2610

Faulting application start time: 0x01d9f62912a4e5a2

Faulting application path: C:\WINDOWS\Explorer.EXE

Faulting module path: C:\WINDOWS\System32\SHELL32.dll

Report Id: 59650c77-babd-4fdb-9717-8eb9126ddd31

From the System And Conservation menu I pulled the following info:
Fault Signature
Fault Name: APPCRASH
Application Name: Explorer.EXE
Application Version: 10.0.19041.3448
Application Time Stamp: a1694e98
Faulting Module Name: SHELL32.dll
Faulting Module Version: 10.0.19041.3393
Faulting Module Time Stamp: 480c18d7
Exception Code: c0000005
Fault Offset: 000000000056b829
OS Version: 10.0.19045.2.0.0.256.48
Regional settings ID: 1045
Additional Information 1: 90d6
Additional Information 2: 90d6706c5e4d8aaa6614ae9527d3d24a
Additional Information 3: b92b
Additional Information 4: b92b55c69334f98ed1efda00b9c3875f

Additional Information about the Issue
Packet ID: 408ad5ec287233fb0dc5f93e4608cca7 (2145394843370179751)

Some things I have tried:

1. Running chkdsk /r /f - no issue found
   
2. Running SFC /scannow - no issue found
   
3. Running
   DISM.exe /Online /Cleanup-image /Scanhealth
   DISM.exe /Online /Cleanup-image /Restorehealth
   DISM.exe /Online /Cleanup-image /startcomponentcleanup
   those yielded no result
   
4. Running with KB5030211 (as it updated shell32.dll)
   
5. Upgrading to KB5030300 (as it updated shell32.dll) - no change
   
6. I was using Classical Shell, removed it, rebooted PC - no change
   
7. Installed Open Shell, rebooted PC - no change
   
8. Did a DDU from safe mode removal of GPU drivers, rebooted PC with no internet, installed fresh GPU drivers - no change
   
9. I tried to see if this happens in minimal safe mode - it does
   
10. Did a File Explorer history clean - did not help
    
11. Asked a friend who was running Windows 10 with KB5030300 installed today. He had no issue even with 215 folders.
    

At this point I'm out of ideas of how to fix this, apart from very heavy solutions like full system reinstall, which I would rather avoid for such an issue.

I can only guess the number 127/128 being significant here, or it maybe being connected to recent folders history and maybe that exceeding some buffer on my system, but got no way to further debug it.

Any help or ideas would be welcome at this point, as while the issue is not often occuring, if I forget to refresh File explorer, it can get annoying.

EDIT:

Additional steps taken after post was made:

1. Installed KB5001716 and KB5030180 (both installed at the same time) - no change
   
2. Cleared AutomaticDestinations, and rebooted PC, crash happened at 106th folder, rebooted again, crash at 129th folder
   
3. Tried to recreate this issue on my work laptop thats managed by my company. It happened there as well. The only thing in common I could think between my laptop and my PC is that I also had Classic Shell installed on it. However during my debugging I removed that from my PC, rebooted and that did not help the issue.
   I have also removed Classic Shell from my laptop, did a reboot and the issue was still present there as well. I tried going through all applications that could be common between my PC and laptop, removed them from PC, but nothing helped. There are still probably a few that I got in common like Adobie, Python, etc but those come on the laptop form my company store, so they are common in organization, and my colege from work does not have those troubles.
   So all in all I still don't know what might be causing it.
   

Best regards,

Greg