Windows 7 Explorer Frequently Crashes - Error 0xc0000374

Crashing constantly. Right click on desktop icons, clicking on system tray icons, clicking on control panel list via start menu (as configured).

Faulting application name: Explorer.EXE, version: 6.1.7600.16450, time stamp: 0x4aebab8d

Faulting module name: comctl32.dll, version: 6.10.7600.16385, time stamp: 0x4a5bde67

Exception code: 0xc000041d

Fault offset: 0x000000000005235b

Faulting process id: 0xb9c

Faulting application start time: 0x01cab92a358fa70f

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

Faulting module path: C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7600.16385_none_fa645303170382f6\comctl32.dll

Report Id: 85ec2905-251d-11df-99c3-00248c624e1b

Greetings,

Just got done loading my computer and am having the exact same Windows Explorer crashes. I get no BSOD's, just Windows Exporer crashing and then restarting. Happens randomly while I am performing various tasks, doesn't happen while its idle. Happens more frequently after installing a new app but clears up somewhat after a reboot.

The error from the log is:

Log Name:      Application

Source:        Application Error

Date:          1/4/2010 17:36:25

Event ID:      1000

Task Category: (100)

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      PHOENIX

Description:

Faulting application name: Explorer.EXE, version: 6.1.7600.16404, time stamp: 0x4a765771

Faulting module name: ntdll.dll, version: 6.1.7600.16385, time stamp: 0x4a5be02b

Exception code: 0xc0000005

Fault offset: 0x0000000000051da0

Faulting process id: 0x728

Faulting application start time: 0x01ca8d515f8f6305

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

Faulting module path: C:\Windows\SYSTEM32\ntdll.dll

Report Id: 4c15d657-f94f-11de-b86c-90e6ba15e407

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="2010-01-04T16:36:25.000000000Z" />

    <EventRecordID>4012</EventRecordID>

    <Channel>Application</Channel>

    <Computer>PHOENIX</Computer>

    <Security />

  </System>

  <EventData>

    <Data>Explorer.EXE</Data>

    <Data>6.1.7600.16404</Data>

    <Data>4a765771</Data>

    <Data>ntdll.dll</Data>

    <Data>6.1.7600.16385</Data>

    <Data>4a5be02b</Data>

    <Data>c0000005</Data>

    <Data>0000000000051da0</Data>

    <Data>728</Data>

    <Data>01ca8d515f8f6305</Data>

    <Data>C:\Windows\Explorer.EXE</Data>

    <Data>C:\Windows\SYSTEM32\ntdll.dll</Data>

    <Data>4c15d657-f94f-11de-b86c-90e6ba15e407</Data>

  </EventData>

</Event>

Would be nice if MS came out with a fix for this. I followed all MS guidelines on installing the system (MB drivers first and then working outwards) and this is the only issue I am having.

I'm pretty sure I know what the problem is but unfortunately I don't have a solution. I have exactly the same problem as you and I think it is being caused by your wireless N d-link adaptor. I know it's not really solution but try running your computer without the card and see if it stops it from crashing. You might also find that the computer crashes more often when you are using high bandwidth, i.e. when downloading torrents or whatever...

If anyone does come up with a solution for this could you please let me know as well because this is a pain in the ____..

Cheers,

Maverick

As far as the BSOD is concerned ... it will only happen when I run VMWare with my iPhone connected ... vmware does have some of its own drivers for usb stuff ... when I disconnect the iPhone while VMWare is running the USB drivers hang and cause a BSOD when I attempt to restart the computer.. wacky stuffs.

I use avast antivirus ... and today there has been about a half a dozen times or so crashes... this is getting extremely annoying!!!!

Some Event Logs ....

Faulting application name: explorer.exe, version: 6.1.7600.16404, time stamp: 0x4a765771

Faulting module name: ntdll.dll, version: 6.1.7600.16385, time stamp: 0x4a5be02b

Exception code: 0xc0000005

Fault offset: 0x0000000000051da0

Faulting process id: 0x778

Faulting application start time: 0x01ca62982cc743c0

Faulting application path: C:\Windows\explorer.exe

Faulting module path: C:\Windows\SYSTEM32\ntdll.dll

Report Id: 88904da0-ce8b-11de-b9d7-005056c00008

Faulting application name: explorer.exe, version: 6.1.7600.16404, time stamp: 0x4a765771

Faulting module name: ntdll.dll, version: 6.1.7600.16385, time stamp: 0x4a5be02b

Exception code: 0xc0000374

Fault offset: 0x00000000000c6cd2

Faulting process id: 0x106c

Faulting application start time: 0x01ca626108d551a0

Faulting application path: C:\Windows\explorer.exe

Faulting module path: C:\Windows\SYSTEM32\ntdll.dll

Report Id: 68b95d00-ce8b-11de-b9d7-005056c00008

Faulting application name: Explorer.EXE, version: 6.1.7600.16404, time stamp: 0x4a765771

Faulting module name: ntdll.dll, version: 6.1.7600.16385, time stamp: 0x4a5be02b

Exception code: 0xc000041d

Fault offset: 0x0000000000051da0

Faulting process id: 0xebc

Faulting application start time: 0x01ca6260fd3e3f50

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

Faulting module path: C:\Windows\SYSTEM32\ntdll.dll

Report Id: 44902e40-ce54-11de-b9d7-005056c00008

Faulting application name: Explorer.EXE, version: 6.1.7600.16404, time stamp: 0x4a765771

Faulting module name: ntdll.dll, version: 6.1.7600.16385, time stamp: 0x4a5be02b

Exception code: 0xc0000005

Fault offset: 0x0000000000051da0

Faulting process id: 0xb10

Faulting application start time: 0x01ca61ccf4a88560

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

Faulting module path: C:\Windows\SYSTEM32\ntdll.dll

Report Id: 353b77b0-ce54-11de-b9d7-005056c00008

If it's BSOD'ing then that's pretty suspecious and points to hardware issues...  Given BSOD's are commonly caused by drivers are you sure that all of your hardware drivers are Windows 7 compatible?

Also - are you using Antivirus and is that a Windows 7 certified release?  AV vendors commonly use driver technology to implement their solutions and as such can cause similar issues too...

Regards,

Jon

http://www.insidetheregistry.com