Basically it is the same problem presented in related topics, the only difference is the affected module. In my case it is a Windows 7 Ultimate 32 bits clean installation with only few softwares installed. I can use windows explorer itself mas cannot use any control panel module. The problem persisted even with a clean boot . I followed the steps presented in topic "windows explorer repeated crashes" using Process Explorer and created a .txt file and a dump file. How can I send it to the forum?

I mean, the error is as follow: Assinatura do problema: Nome do Evento de Problema: APPCRASH Nome do Aplicativo: Explorer.EXE Versão do Aplicativo: 6.1.7601.17514 Carimbo de Data/Hora do Aplicativo: 4ce796f3 Nome do Módulo de Falhas: StackHash_2a75 Versão do Módulo de Falhas: 6.1.7601.17514 Carimbo de Data/Hora do Módulo de Falhas: 4ce7b96e Código de Exceção: c0000374 Deslocamento de Exceção: 000c37b7 Versão do sistema operacional: 6.1.7601.2.1.0.256.1 Identificação da Localidade: 1046 Informações Adicionais 1: 2a75 Informações Adicionais 2: 2a75187157f5f57bfdd807e126104541 Informações Adicionais 3: 9012 Informações Adicionais 4: 901222a913bf6d91c3e8eb8b7e854d7f

The line Nome do Mdulo de Falhas: StackHash_2a75 means the module can't be indentified. The stack is hashed to 2a75 so you can see if crashes are the same. Crashes with the same hash are likely the same. Stacks is where info on nested function calls are stored. The exception code 0xC0000374L means // MessageId: STATUS_HEAP_CORRUPTION // MessageText: // A heap has been corrupted. A heap is a section of memory the program can allocate from. Type memory in Start's search box and choose Memory Diagnostic then Reboot. Run both Normal and Advanced. This will take a few minutes. In Computer right click your drives and choose Properties, then Tools tab, then click Check Now. Tick BOTH checkboxes then Start. Reboot. This will take overnight. After running chkdsk (which is what the above does) check for file corruption by clicking Start - All Programs - Accessories - Right click Command Prompt and choose Run As Administrator. Type sfc /scannow To view the problems only in the log In a command prompt (type command in Start's search box then right click and choose Run As Administrator) type To view it ------------- findstr /c:"[SR] Cannot" %windir%\logs\cbs\cbs.log |more To copy to clipboard --------------------------- findstr /c:"[SR] Cannot" %windir%\logs\cbs\cbs.log |clip It might becaused by a shell extension. Explorer is built on addin programs called Shell Extensions. The standard ones are supplied by MS but programs add their own. Download http://www.nirsoft.net/utils/shexview.html Disable all non microsoft shell extensions, and if it helps, reenable one by one to identify which one. It might be caused by a third party program. Try clean boot troubleshooting. http://support.microsoft.com/kb/331796 -- .. -- "TedCarvalho" wrote in message news:c25199e8-80e2-4248-b5f2-77464b07f04b... >I mean, the error is as follow: > > Assinatura do problema: > Nome do Evento de Problema: APPCRASH > Nome do Aplicativo: Explorer.EXE > Verso do Aplicativo: 6.1.7601.17514 > Carimbo de Data/Hora do Aplicativo: 4ce796f3 > Nome do Mdulo de Falhas: StackHash_2a75 > Verso do Mdulo de Falhas: 6.1.7601.17514 > Carimbo de Data/Hora do Mdulo de Falhas: 4ce7b96e > Cdigo de Exceo: c0000374 > Deslocamento de Exceo: 000c37b7 > Verso do sistema operacional: 6.1.7601.2.1.0.256.1 > Identificao da Localidade: 1046 > Informaes Adicionais 1: 2a75 > Informaes Adicionais 2: 2a75187157f5f57bfdd807e126104541 > Informaes Adicionais 3: 9012 > Informaes Adicionais 4: 901222a913bf6d91c3e8eb8b7e854d7f > > >

The machine runs a dual boot Windows Ultimate 64/Windows Ultimate 32 and on Windows 64 there is no trouble at all. So I am sure the problem is not memory related. Chkdsk /f does not fix any errors also but I will try sfc /scannow. Thank you

The fact that it works on another OS doesn't mean its ok. If it is memory that memory may be unused on the other OS. I suspect the ShExView program will find the culprit as it's most likely a faulty Shell Extension. -- .. -- "TedCarvalho" wrote in message news:f7361d5a-38fa-40ad-b889-eba0c15902f6... > The machine runs a dual boot Windows Ultimate 64/Windows Ultimate 32 and > on Windows 64 there is no trouble at all. So I am sure the problem is not > memory related. Chkdsk /f does not fix any errors also but I will try sfc > /scannow. > > Thank you >

reporting now the results of tools used: sfc /scannow di not find any anomalies and the command findstr /c:"[SR] Cannot" %windir%\logs\cbs\cbs.log |clip came blank, no report at all. Memory Diagnostic Tool did not find any error In ShExView program all extensions are Microsoft but I do not know how to find errors. How can I send the .html report for analysis?

You use ShExView by selecting 15 shell extensions (ShExView won't let you disable more than 15 Microsoft extensions at one time), disabling them, and seeing if that fixes the fault. If it doesn't reenable those and select 15 more. Problems tend to be caused by NON microsoft shell extensions. Microsoft's extensions tend to be well tested and not cause problems. To restart Explorer without rebooting; Ctrl + Shift and Right click blank area on Start or Shutdown buttons Menu item to close down Window's shell in a normal shutdown without logging off.. Use Task Manager's File - New Task (Run) ... dialog to and type Explorer to restart the shell. With one exception ShExView doesn't do the applets that are control panel apps (they are a different technology to shell extensions). How control panel apps are found and programmed has changed over time. Start with the traditional ones. Files in c:\windows\system32 with the extension of cpl are loaded by control panel when it starts. Try removing all cpl files from system32 and see if control panel now works. A problem with this approach is to have permission to do this. You need to take ownership of the files, then give yourself permissions for full control. That's as much as I can type now. I just got home from work. -- .. -- "TedCarvalho" wrote in message news:8df172c2-93df-483f-a448-19e1e86b48c7... > reporting now the results of tools used: > > sfc /scannow di not find any anomalies and the command findstr /c:"[SR] > Cannot" %windir%\logs\cbs\cbs.log |clip came blank, no report at all. > > Memory Diagnostic Tool did not find any error > > In ShExView program all extensions are Microsoft but I do not know how to > find errors. How can I send the .html report for analysis? >

Hi, Could be conflict with certain 32bit\64bit software, certain things you can try are to find out the root cause of the problem are given below. 1. Have a look whether you can reproduce the problem in safe mode. Start your computer in safe mode http://windows.microsoft.com/en-US/windows-vista/Start-your-computer-in-safe-mode If behavior doesn’t persist in safe mode, it indicates that a third party program or service is preventing you from performing the action as supposed to. To validate or determine which service/startup item could be causing this, restart the computer and boot to desktop normally. Once done, perform clean boot. 2. Clean Boot prevents software conflicts by preventing the startup items and non Microsoft services from loading. This way you can safely follow the process of elimination to check which application is causing this behavior. Refer: How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7 http://support.microsoft.com/kb/929135 Note: Ensure that you put your computer back to normal startup mode after completing the troubleshooting steps. Steps are available in the article given above.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Yes, Magon the problem persisted in safe mode. Not knowing what else to do I reinstalled Windows 32 in the same partition (formatting the partition during installation) and installed again the same software, as before. Until now everything is working just fine. Thank you and David for helping.

Hi, Could be corrupt system files. Glad it is working now. Regards,Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.