Debug Error Heap Corruption Detected Explorer.exe
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeWindows 10Windows 10 MobilePrevious versionsMDOPSurfaceSurface HubLibraryForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Windows 7 Explorer C++ Error Windows 7 IT Pro > Windows 7 User Interface Question 0 Sign in to vote Hi Folks, I have a Windows 7 Ultimate x64 OS that is providing a C++ error message when I try to right-click on a folder to do something like Delete, Cut, Copy, Moveetc.The error appears before I can make any selection. The error is as follows: Microsoft Visual C++ Debug Library DEbug Error! Program: c:\Windows\explorer.exe HEAP CORRUPTION DETECTED: after Normal block (#59) at 0x0000000005077A30. CRT detected that the application wrote to memory after end of heap buffer. When I press the Abort, Retry or Cancel buttons, the desktop clears and Explorer resets itself. Subsequent attempts to perform the action create the same arror again. After reviewing some similar posts in this forum, I ensured all my Windows Updates were up-to-date, and then downloaded vcredist_x86. I installed it and then allowed the C++ update to install, rebooted and tried the action again. No joy; the error remains. Does anyone have any suggestions on the next steps to take to resolve this issue? Friday, November 05, 2010 8:59 PM Reply | Quote Answers 3 Sign in to vote Hi Pete, I checked the dump and saw the cause: user32!DispatchHookW+0x2c user32!fnHkINLPCWPSTRUCTW+0x60 user32!_fnDWORD+0x2d ntdll!KiUserCallbackDispatcherContinue user32!ZwUserDestroyWindow+0xa ole32!alloca_probe+0xec8e ole32!CleanupTlsMap+0x78 ole32!DllMain+0x21f ole32!CRT_INIT+0x2af ntdll!LdrShutdownProcess+0x1db ntdll!RtlExitUserProcess+0x90 contmenu +0x460cb 0x2 0xaf41070 explorer!CMorePrograms::s_WndProc+0x6d 0x2 explorer!CSearchOpenView::s_WndProc+0x349 contmenu +0x46c3c The DLL contmenudll is the cause: Image path: C:\Program Files (x86)\ZipGenius 6\contmenu.dll Image name: contmenu.dll Timestamp: Sun Mar 21 22:47:22 2010 So the file belongs to ZipGenius. Update the program. If this is the latest version
Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks. Windows 7 Help Forums Windows 7 help and support BSOD Help and Support » User Name Remember Me? Password Advanced Search Show Threads Show Posts Advanced Search Go to Page... Windows 7: Windows 7 Pro x64 explorer.exe crashing Page 1 of 3 1 23 > 23 Sep 2009 #1 Porkrinds Windows 7 Professional https://social.technet.microsoft.com/Forums/windows/en-US/641ab1b8-46ba-4e24-ba21-9b930c9cb3cb/windows-7-explorer-c-error?forum=w7itproui x64 MSDN-AA RTM 15 posts Windows 7 Pro x64 explorer.exe crashing I have been following the people complaining about this here, as well as on the other forums and searching google day in and day out for a solution to this problem. Here is my exact problem: Random explorer.exe crashes. Be it the desktop process, or the file manager process. http://www.sevenforums.com/bsod-help-support/26108-windows-7-pro-x64-explorer-exe-crashing.html ALSO, when I get these crashes, MMC.EXE will crash when I try to open Event Viewer. Eventually it will stop crashing and I can view everything fine and it's like nothing happened at all. Eventlog is always an error with one of the following, from most often to least often: ntdll.dll, comctl.dll (deep inside the filesystem 'WinSxS'?), msvcrt.dll. 99% of the time it is ntdll.dll as others have reported. I can always tell when the crash is coming because there is a very small delay and the cursor turns to the busy spinning turquoise circle. Now, the fun part is that I started having this issue in Windows Vista Home Premium x64 before blaming my old install and moving to Windows 7 Professional x64 from MSDN-AA. The crashing happened. I googled to try and fix it, but alas came up empty handed. I re-installed and only installed the basics that were listed as Windows 7 compatible: Intel chipset (it listed Windows 7) and Nvidia current drivers as of today. The crashing is totally random. I ran several diagnostics: - sfc /scannow - antivir
LearningModern CodeNetworkingOpen SourceStorageToolsDeveloper TypeEmbedded SystemsGame DevMediaTechnical, Enterprise, HPCWebOSAll ToolsAndroid*HTML5Linux*OS X*Windows*ResourcesCode SamplesContact SupportDocumentationFree SoftwareIntel Registration CenterProduct ForumsSDKsResourcesPartner with IntelAcademic ProgramPartner SpotlightBlack Belt DeveloperDeveloper MeshInnovator ProgramSuccess StoriesLearnBlogBusiness TipsEventsVideosSupportContact SupportDeveloper EvangelistsFAQsForums Search form https://software.intel.com/en-us/forums/intel-visual-fortran-compiler-for-windows/topic/300734 Search You are hereHome › Forums › Intel® Software Development Products › Intel® Visual Fortran Compiler for Windows* FacebookLinkedInTwitterDiggDeliciousGoogle Plus heap corruption error heap corruption error carlos8410 Mon, 09/08/2008 - 21:35 Hi, I created some ALLOCATABLE variables, I defined the size for them, and after using them, I DEALLOCATE them. debug error Then the heap corruption error pop-out. The error message is listed below in sequence. And the source code is also listed. This is strange that the code doesn't have this problem before, but after I fixed an error (one of the variable is not assigned value.) in the code, this error debug error heap come out. And the heap corruption does not happen when I use the pointers, but happens when I release them. This is the first warning window appears:==========================================Windows has triggered a breakpoint in powell_test.8.26.exe. This may be due to a corruption of the heap, which indicates a bug in powell_test.8.26.exe or any of the DLLs it has loaded. This may also be due to the user pressing F12 while powell_test.8.26.exe has focus. The output window may have more diagnostic information.========================================== This is the error message I got from the debug.============================================Debug Error! Program:.... HEAP CORRUPTION DETECTED: after Normal block (#103) at 0x003A3748. CRT detected that the application wrote to memory after end of heap buffer.-------------------------------------------------------------------------------* If this ASSERT fails, a bad pointer has been passed in. It may be * totally bogus, or it may have been allocated from another heap. * The pointer MUST come from the 'local' heap. */ _ASSERTE(_Cr