Exception code: 0xc0000005 explorer.exe crashes

llloyd4 · 27 Sep 2017

Hello! I had a bunch of Explorer windows open when they all closed, the task bar cleared out and repopulated again, and peeking at the Application Log I see

Faulting application name: Explorer.EXE, version: 10.0.14393.1198, time stamp: 0x590281fa
Faulting module name: KERNEL32.DLL, version: 10.0.14393.1198, time stamp: 0x59028368
Exception code: 0xc0000005
Fault offset: 0x000000000001345d
Faulting process id: 0x1360
Faulting application start time: 0x01d32a97633caf3d
Faulting application path: C:\Windows\Explorer.EXE
Faulting module path: C:\Windows\System32\KERNEL32.DLL
Report Id: 4de15fd9-c759-421a-9553-c5a4ecba81ae
Faulting package full name:
Faulting package-relative application ID:

And, as it wouldn't hurt, I ran a cmd shell as admin and ran sfc /scannow , the results are...

C:\Windows\system32>sfc /scannow
Beginning system scan.
This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.Windows Resource Protection did not find any integrity violations.
C:\Windows\system32>

So... Anyone might know what is causing these mini crashes? Thanks!

AndreTen · 27 Sep 2017

Running any extra context menu entries? (nvidia, 7zip?)

llloyd4 · 27 Sep 2017

Umm, WinRar and VLC by the looks of it.

f14tomcat · 27 Sep 2017

llloyd4 said:

Umm, WinRar and VLC by the looks of it.

That happened to me this morning on the Insider build. Ran 7-zip and Explorer crashed. I ran 2 (right-click>extract to) quickly back-to-back. Crashed on second one. Never repeated.

Superfly · 27 Sep 2017

Error 5's are access related errors - very common (in some instances as in our activation thread it occurs with file permissions corruption)
-- but in this instance, I guess a process couldn't access some memory allocation and fell over.

Explorer recovered and should continue as before, unless there is a hardware fault causing it.

Duyenhip · 28 Sep 2017

Try these first:

1. Open a command window and type "chkdsk c: /f /v /r" (without quotes) then hit <enter>. Answer the resulting message with a Y, then reboot. This'll take a while.

2. Download memtest86 ( http://www.memtest86.com/ ), burn it to CD, boot it and run at least 3 complete cycles on each stick of RAM individually in each slot followed by pairs, alternating slots between tests (gonna take a LONG while).