Windows 7 Explorer Frequently Crashes - Error 0xc0000374

Dear Zombie,

With the help of Windows 7 installation media rebuilt your boot configurations. There is a possibility that they have been facing problems thus Windows Explorer crashes.

1. Insert Windows 7 64 Bit installation disc.
2. Properly configure the CMOS settings in such a way that the disc is set to be the first boot media and your hard disk as the second one.
3. Save the changes and restart.
4. Press any key when prompted.
5. Wait till the setup wizard loads. Once it is loaded, click Repair your computer link provided on its first welcome page.
6. Click Command Prompt in the new screen that appears.
7. Type the following command and press ENTER:

BOOTCFG /REBUILD

8. After your boot configurations are rebuild successfully, type EXITand press ENTER.
9. Restart the system as usual.

<removed>

Hi Zombie,

Check for hard disk drive errors. Bad sectors and errors with your hard disk can result in computer crashes. Run Disk CheckUp utility as below:

1. Double click My Computer icon on your desktop.
2. Right click your system drive (usually drive C:).
3. Select Properties.
4. In the new dialog click Tools tab and then Check Now button.
5. Click Startto begin the process.

If you find that the above solution does not work for you then check-out these this post: http://windows7crashing.com/ . There are other solutions too.

Your processor can be overheating. There are many free CPU monitoring software available on the internet. After you check the temperature of your processor remove the dust from all the components inside your CPU. Clean the processor fan too.

If the overheating is not the root reason then check your RAM for problems. Use Windows Memory Diagnostic tool which is located in your Start menu. Do the steps given below to locate it and run the test:

1. Click Start, type Windows Memory Diagnostic in the Search Box and press ENTER.
2. Click Restart now and check for problems.
3. The system shall restart now and check for problems with your RAM. Hold on until.

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

My crash report:

Nome do Log:   Application

Fonte:         Application Error

Data:          5/17/2013 2:47:21 PM

Identificação do Evento:1000

Categoria da Tarefa:(100)

Nível:         Erro

Palavras-chave:Clássico

Usuário:       N/D

Computador:    Daniel-STI

Descrição:

Nome de aplicativo com falha: Explorer.EXE, versão: 6.1.7601.17567, carimbo de hora: 0x4d6727a7

Nome do módulo de falhas: ntdll.dll, versão: 6.1.7601.17725, carimbo de hora: 0x4ec49b60

Código de exceção: 0xc0000374

Deslocamento com falha: 0x000c380b

Identificação do processo com falha: 0x484

Hora de início do aplicativo com falha: 0x01ce53248d4bf818

Caminho do aplicativo com falha: C:\Windows\Explorer.EXE

FCaminho do módulo de falhas: C:\Windows\SYSTEM32\ntdll.dll

Identificação do Relatório: d29d3d18-bf19-11e2-9aeb-00030de765a7

XML de Evento:

<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="2013-05-17T17:47:21.000000000Z" />

    <EventRecordID>108865</EventRecordID>

    <Channel>Application</Channel>

    <Computer>Daniel-STI</Computer>

    <Security />

  </System>

  <EventData>

    <Data>Explorer.EXE</Data>

    <Data>6.1.7601.17567</Data>

    <Data>4d6727a7</Data>

    <Data>ntdll.dll</Data>

    <Data>6.1.7601.17725</Data>

    <Data>4ec49b60</Data>

    <Data>c0000374</Data>

    <Data>000c380b</Data>

    <Data>484</Data>

    <Data>01ce53248d4bf818</Data>

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

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

    <Data>d29d3d18-bf19-11e2-9aeb-00030de765a7</Data>

  </EventData>

</Event>

Makes sense that if it has something to do with the wireless card, since, the last time it crashed I was downloading files from my website http://www.thebrazilianlanguage.com, which usuallly are pretty big files. But is the wireless card just a provocation or would replacing it end the crashes?

Hi There,

Have a client that is  getting this repeatedly on any hardware, whenever they right click a local or network drive/share in windows explorer, they get the error that Explorer has stopped working with the below event viewer error:

Here's a link to the DMP file: http://sdrv.ms/12z8Cjv

Hope you can assist.

"

Faulting application name: explorer.exe, version: 6.1.7601.17567, time stamp: 0x4d672ee4

Faulting module name: ole32.dll, version: 6.1.7601.17514, time stamp: 0x4ce7c92c

Exception code: 0xc0000005

Fault offset: 0x00000000000fd1b2

Faulting process id: 0x19d0

Faulting application start time: 0x01ce7e90d6feeb7b

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

Faulting module path: C:\Windows\system32\ole32.dll

Report Id: 208fed79-ea84-11e2-a4a3-000df0a9cc94

Faulting application name: Explorer.EXE, version: 6.1.7601.17567, time stamp: 0x4d672ee4

Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec4aa8e

Exception code: 0xc0000005

Fault offset: 0x00000000000532d0

Faulting process id: 0xe94

Faulting application start time: 0x01ce7e8df1b43a94

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

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

Report Id: 149f9017-ea84-11e2-a4a3-000df0a9cc94

Its looks like that 0xc0000005 error with explorer.exe may mean you have a rootkit

Download then run tdsskiller. If it picks anything up, select cure wait for it to finish then reboot