Explorer.exe Crashes Constantly! Help Please!

By CHardy316 ·
So, about every 5 seconds I keep getting "Windows Explorer has stopped working." It checks for a solution, and then just restarts.

I have windows 7 x64. Haven't had any problems until I got home from work today and turned on my computer and this keeps popping up.

I check the even viewer and see these errors....

Faulting application name: Explorer.EXE, version: 6.1.7600.16450, time stamp: 0x4aebab8d
Faulting module name: Explorer.EXE, version: 6.1.7600.16450, time stamp: 0x4aebab8d
Exception code: 0xc000041d
Fault offset: 0x000000000002cc2b
Faulting process id: 0xa14
Faulting application start time: 0x01cb719a6d0f4a60
Faulting application path: C:\Windows\Explorer.EXE
Faulting module path: C:\Windows\Explorer.EXE
Report Id: adfb0a50-dd8d-11df-8d9a-001d92e09ac8

Does anyone have any idea whats going on?


This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -

Could be a virus

by TobiF In reply to Explorer.exe Crashes Cons ...

or something else that is hooked into the operation of winexplorer.

Try to boot into safe mode and do some malware scans.

Collapse -

I had that happen to me a few months ago.

by .Martin. In reply to Explorer.exe Crashes Cons ...

turned out I had a bad case of apocalyps32 and conficker (I think). even after I successfully removed the two of them, windows explorer was still crashing.

only solution = reinstall windows.

Collapse -

try these two programs

by .Martin. In reply to I had that happen to me a ...

First malwarebytes:

Then ComboFix:
once you have run combofix, post the log here.

Collapse -

Not A Virus

by CHardy316 In reply to try these two programs

I restarted in safe mode, and ran anti-malwarebytes and CCleaner, neither turned up any results. After looking at some more event viewer entires, I found these....

"The winlogon notification subscriber <GPClient> was unavailable to handle a notification event."

"The maximum file size for session "ReadyBoot" has been reached. As a result, events might be lost (not logged) to file "C:\Windows\Prefetch\ReadyBoot\ReadyBoot.etl". The maximum files size is currently set to 20971520 bytes."

"The Network List Service service depends on the Network Location Awareness service which failed to start because of the following error:
The dependency service or group failed to start."

"DCOM got error "1084" attempting to start the service WSearch with arguments "" in order to run the server:

Any of this stuff make any sense?

Collapse -

Restore points?

by TobiF In reply to Not A Virus

If you have any recent restore point, you could try rolling back the system a bit.

You could probably free up space for that log by deleting the current one. (But that's not what's taking your system down.)

No idea about the other two things, except that they, in themselves, don't seem to be fully needed for a system to work. But I have no idea what kind of additional things may depend on them.

But again, try rolling back a restore point, or so, if possible.

Collapse -


by CHardy316 In reply to Restore points?

Unfortunately I've tried that already. Sorry for not mentioning that in my original post.

It was very weird what was happening. Remember, this stuff started happening this evening (10/21) when I got home from work.

I tried to restore to a week ago, but as it was about to finish, an error popped up and said that system restore could not be completed because of an unexpected error, and then listed some kind of code. At that point the computer would restart, and start up to my desktop, and I would then get a pop up window that said "Windows has been successfully restored to [insert date here]".

At the moment I'm re-upgrading Windows in a hope that it will overwrite the old drivers that might be corrupted or something.

Collapse -

try this:

by .Martin. In reply to Not A Virus


the solution is simple - just increase the max file size! Go to:


The MaxFileSize key is a DWORD with a default decimal value of 20. Increase this to, say 60, and the problem will go away.

Collapse -


by TobiF In reply to Not A Virus

Just in order to exclude it, try running sysinternals rootkitrevealer (if your reload of windows won't help.)

Related Discussions

Related Forums