explorer.exe crashes constantly

[Kalos]

A few minutes after booting up, I'll get the "Windows explorer has stopped working..." message. If I restart it, then all that happens is that the error message appears again in less than five seconds after the restart.

I've done a virus scan and come up with nothing, explorer.exe won't run long enough for me to even make it to the event viewer to look up anything else that is going on.

This is what I can get from the Problem Details
Problem signature:
Problem Event Name: APPCRASH
Application Name: explorer.exe
Application Version: 6.1.7600.16450
Application Timestamp: 4aebab8d
Fault Module Name: explorer.exe
Fault Module Version: 6.1.7600.16450
Fault Module Timestamp: 4aebab8d
Exception Code: c000041d
Exception Offset: 000000000002cc2b
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033

 

[Carolyn]

Try System Restore. Use a Restore Point that predates this issue.

http://www.sevenforums.com/tutorials/700-system-restore.html

 

[Kalos]

No dice. I've tried booting into safe mode and it doesn't do it like that, but when I do a clean boot (not safe mode) it does.

 

[Kalos]

Bump.

EDIT: Found the explorer.exe crash solutions thread. None of them worked (though SFC /scannow fixed a completely unrelated problem I'd been having for months). Backing up my music and reinstalling Windows.

 

[therealjustin]

Kalos, I am having the same problem and I reinstalled W7 on Wednesday. By Friday I had explorer.exe and other strange issues all over again. I believe it has something to do with an update from Microsoft and even a clean install will not solve it because Windows will install the updates anyway. I am going to do a clean install again tonight and I will try not installing SP1 to see if that helps.


Just wondering too, what is your graphics card and are you using the latest drivers?

 

[therealjustin]

I reinstalled everything last night but chose not to reinstall SP1. I went to install my printer tonight and explorer.exe crashed again.

It says the faulty module was DUI70.dll. A search indicates this is related to the Windows UI, better known as the AERO interface. The file is no corrupt because I ran a SFC and nothing was found so that leaves the nVidia driver! I am using 270.61.