Windows 7 Explorer Frequently Crashes - Error 0xc0000374

Question

original title: Windows 7 Explorer Frequently Crashes!!! **** ... no way!!! yep. It usually happens when my computer is left on overnight or after a few hours of some serious php scripting with but of course MS Expression Web 3. lmfao. It usually results in not being able to rename something ... right click ... delete ... etc. Its one of these not multiples ... that causes a explorer crash and in order to fix this annoying undocumented feature ... i MUST REBOOT! Do you know how annoying this is when your right in the middle of editing some plain text documents!!!!! ... the initial installation took about 20-30min to actually start up and took an excessively long long time to install to begin with.

WTF Microsoft ... I thought Win7 wasnt going to have any of the previous OS issues! Linux FTW!

HW:

MSI 9800GT - Video Card - Not OC

Gigabyte S Series Motherboard

AMD 4000+ AM2 64x2 Processor - Copper Cooling Block not OC

2x1GB Ram ( Single Channel )

500GB SATA Seagate Barricuda HDD - Brand NEW

Razer DeathAdder USB Mouse

D-Link Wireless N Card

Standard Keyboard (PS2 Connector)

HP DVD Burner ( ide )

Answer 1

When Explorer crashes it writes the error to the event logs. Can you post the errors?

---

Kerry Brown MS-MVP - Windows Desktop Experience

Answer 2

Explorer Crash:

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: 0x0000000000051d1e

Faulting process id: 0x179c

Faulting application start time: 0x01ca5dff66498ba0

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

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

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: 0x15ac

Faulting application start time: 0x01ca5cf825192490

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

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

• app hang

The program Explorer.EXE version 6.1.7600.16404 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.

 Process ID: b8c

 Start Time: 01ca5b67cd79ef80

 Termination Time: 49

 Application Path: C:\Windows\Explorer.EXE

 Report Id: 5d8bdb11-c8eb-11de-aeca-005056c00008

MS Expression App Hang ....

The program ExpressionWeb.exe version 3.0.1762.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.

 Process ID: c70

 Start Time: 01ca5e5fea793320

 Termination Time: 85

 Application Path: C:\Program Files (x86)\Microsoft Expression\Web 3\ExpressionWeb.exe

 Report Id: 67862b21-ca53-11de-b36b-005056c00008

Answer 3

Ahh ... more crashes this morning!!!

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: 0xe6c

Faulting application start time: 0x01ca5f1024102de0

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

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

Report Id: 86736f10-cb03-11de-8f68-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: 0x000000000003202d

Faulting process id: 0x8e0

Faulting application start time: 0x01ca5e981b387830

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

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

Report Id: 5d6bbdc0-cb03-11de-8f68-005056c00008

Faulting application name: WORDPAD.EXE, version: 6.1.7600.16385, time stamp: 0x4a5bca2a

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

Exception code: 0xc0000005

Fault offset: 0x0000000000051da0

Faulting process id: 0x10d4

Faulting application start time: 0x01ca5eb021a4adc0

Faulting application path: C:\Program Files\Windows NT\Accessories\WORDPAD.EXE

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

Report Id: 59db1cf0-cb03-11de-8f68-005056c00008

Btw, Windows 7 will also BSOD with a combination of an iPhone and VMWare Workstation .... rofl.

Answer 4

The crashes appear pretty random. Have you tried testing the memory?

---

Kerry Brown MS-MVP - Windows Desktop Experience

Answer 5

I actually just replaced the 2gig single channel with some 4gig dual channel.

The first set of crashes was using the 2gig ram the second set was the 4gig of ram ... but i will run some memory and cpu tests to rule those out....