New
#1
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. 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
- antivirus antispyware (even did it on clean install just incase)
- memtest86 overnight, 0 errors
- Seagate disk tools, whatever it's called. Did SMART tests, and both short and long tests.
- Encoding some DVDs into MKV using handbrake. CPU sat taxed %100 both cores for about 5 hours.
Current system setup:
Windows 7 Professional x64 (from MSDN-AA)
Dell Inspiron 530Code:MD5: 7b7af5fe3a01e9fd76de4dacb45a796b SHA1: 50127304441a793ee51b3f501289f6599a559e9f CRC32: 502c42c1
C2D E8400 3.0GHz
Nvidia GTX 260 (Non Core 216)
Foxconn Dell OEM motherboard
4GB DDR2 800MHZ (1GB x 4)
250GB Seagate HDD
Onboard realtek sound
650W Power Supply
I will follow your Windows debugging guide as well on the previous pages and upload the result when I can get explorer to crash again. I can't make it happen... it just happens. :)
I just wanted to add the "me too" factor.
For what it's worth, I have two other machines that don't exhibit this behavior. Software wise, all machines share the same basic setup.
Dumps attached per discussion HERE. (Note, these are two new dumps, one from the shell process and the other from a seperate file manager explorer.exe process) - yes I tell explorer to start a new process when starting the file manager, etc.