Windows 7 Explorer Frequently Crashes - Error 0xc0000374

Anonymous

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 )

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

47 answers

Anonymous

2009-11-11T06:42:00+00:00

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
Was this answer helpful?

0 comments No comments
Anonymous

2009-11-08T02:54:19+00:00

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
Was this answer helpful?

0 comments No comments
Anonymous

2009-11-07T02:07:19+00:00

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....
Was this answer helpful?

0 comments No comments
Anonymous

2009-11-06T22:04:09+00:00

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

Kerry Brown MS-MVP - Windows Desktop Experience
Was this answer helpful?

0 comments No comments
Anonymous

2009-11-06T18:40:22+00:00

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.
Was this answer helpful?

0 comments No comments