Windows 8 Pro - Windows Explorer has crashed
Start menu and Windows enhancement software
Brought to you by:
ibeltchev
Menu
▾
▴
#194 Windows 8 Pro - Windows Explorer has crashed
Running Win 8 Pro RTM x64; ClassicShell 3.6.2
After upgrading to 3.6.2 I started having Windows Explorer crash when trying to do some Classic Shell searches. No particular search, but I've created it randomly a half dozen times since installing 6.2.
For Example: I hit the Windows key and start typing something like "remote" - to get remote desktop to launch, but the search ?lags? or something, as it doesn't find 'remote', I get a popup from Classic Shell saying that 'remote' could not be found, and then it and/or Windows Explorer crashes and restarts, and ClassicShell behaves normally for a while longer. Never had this happen under 3.6.1 at all.
The search hasn't changed between 3.6.1 and 3.6.2. Also, the search should not show any popups. Please send an email to classicshell@ibeltchev.com. We can do some troubleshooting steps to try and figure out this crash.
I have this exact same problem under Win7 (x86, SP1, patches up to date). In my case I was typing "gallery" to try to find the photo importer. It happened whether or not what I type exists in the Start menu. Explorer (just the one for the taskbar) crashes.
I'd remembered I'd disabled the Windows Search service, so I re-enabled it and started it. Explorer still crashes sometimes. (Of course, now that I'm trying to make it happen, it's behaving. LOL!)
Eventvwr kicks out an event 1000, followed by a 1001 and a 1002 (explorer restarted). I'm going to paste these three below.
See if disabling auto-complete from the search box settings will fix the crash.
Also, does it happen right after coming out of sleep/hibernate or also in the middle of a session?
This happens on my Windows 8 desktop system. If I search for something that it can not find it tells me this and then explorer crashes. Not every time but most times. I am attaching my xml file.
Log Name: Application
Source: Application Error
Date: 12/30/2012 11:48:49 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: tardis
Description:
Faulting application name: Explorer.EXE, version: 6.2.9200.16433, time stamp: 0x50763312
Faulting module name: SHELL32.dll, version: 6.2.9200.16451, time stamp: 0x50986d34
Exception code: 0xc0000005
Fault offset: 0x0000000000036414
Faulting process id: 0xd64
Faulting application start time: 0x01cde6a6ddd1901f
Faulting application path: C:\Windows\Explorer.EXE
Faulting module path: C:\Windows\system32\SHELL32.dll
Report Id: 5dac6f14-5305-11e2-be90-d4bed9e9f9c1
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<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="2012-12-31T04:48:49.000000000Z"/>
<EventRecordID>26481</EventRecordID>
<Channel>Application</Channel>
<Computer>tardis</Computer>
<Security/>
</System>
<EventData>
<Data>Explorer.EXE</Data>
<Data>6.2.9200.16433</Data>
<Data>50763312</Data>
<Data>SHELL32.dll</Data>
<Data>6.2.9200.16451</Data>
<Data>50986d34</Data>
<Data>c0000005</Data>
<Data>0000000000036414</Data>
<Data>d64</Data>
<Data>01cde6a6ddd1901f</Data>
<Data>C:\Windows\Explorer.EXE</Data>
<Data>C:\Windows\system32\SHELL32.dll</Data>
<Data>5dac6f14-5305-11e2-be90-d4bed9e9f9c1</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>
I've been able to consistently recreate this issue by doing this:
Put computer to sleep. Wake up, and within ~30 seconds of unlocking the machine, hit windows key and start typing -- I note that nothing gets found for about 15-30 seconds. If I hit enter before it finds something, Explorer will crash. If I wait for the search to populate, then it won't crash.
I've also found that if the machine's been logged in and awake for >30 sec, even a search for something that I know doesn't exist (i.e. "Popcorn") and hit enter I only get an error that it wasn't found, and I don't get the crash. I've also never had this issue manifest in a circumstance where I have not /just/ woken it up. It works like a champ otherwise.
This issue has existed on every version since 3.6.2 - .1 is not affected.
I'm currently using .5 - and have just learned to wait that 30 seconds after opening up the laptop to start my searches. I can't do without the feature. I'd go back to Win7 before turning it off, but I'm sure it would be interesting for Ivo to know if you have the issue created under the same circumstances, or if you've found something new. I know you mention that it's "not every time" - I too thought it was random until I really started tracking what I did before it happened.
We tracked King Moo's problem to the auto-complete system. See if the crash will go away after you disable the auto-complete.
I don't think my problem is related to sleep mode since it is a desktop and does not go to sleep. I have disabled autocomplete and so far I have not seen the problem. I'll let you know if it reoccurs.